| Add_workflow_for_techpubs |
|---|
| AUTH2 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ce5f0b8d8a00a02355cd1c2f0155cd26cb41059c, userName='null'} |
|---|
| AUTH1 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
|---|
| JIRAIDAUTH | CHOR-1899, CHOR-23973017 |
|---|
| REV5 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
|---|
| REV6 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
|---|
| REV3 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c99e02c0, userName='null'} | REV4 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c91d01f9, userName='null'} |
|---|
| REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c9d6032b, userName='null'} |
|---|
| REV2 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cabc04c38a00a02355cd1c2f0155cd26ca2f03d1, userName='null'} |
|---|
|
...
| Multiexcerpt |
|---|
| MultiExcerptName | Performance |
|---|
|
| Div |
|---|
| | Caption |
|---|
| 0 | Table |
|---|
| 1 | Call Performance - KVM, VMware, Microsoft Hyper-V On-Premises Deployments |
|---|
|
| SWe Lite Virtual Machine Resources, applicable to all supported hypervisors (KVM, VMware® Microsoft Hyper-V) | Maximum SIP
with corresponding
RTP Media Sessions1 | SIP Signaling Session Limits | RTP Media Session Limits | Maximum Call Rate Setup (CPS) | | Media Manipulation Mode2 (Requires Virtual DSP Intervention) | Proxy Media Mode (No Virtual DSP Intervention) | Audio/Video Streams3 | | vCPU # | GB RAM | Maximum TCP/TLS-based SIP↔SIP Signaling Sessions | Maximum SIP Registrations (60 minute refresh rate) | No transcode, with in-band services scenario | Default scenario: G.711/G.729ab RTP ↔ G.729ab/G.711SRTP, with in-band services | Encryption services: G.711 RTP ↔ G.711 SRTP | No encryption services: RTP ↔ RTP/SRTP ↔ SRTP | | 1 | 1 GiB | 100 | 300 | 1000 | 100 | 100 | 3006 | 3006 | 25 | 10 | | 2 | 1.5 GiB | 1000 | 1000 | 1000 | 200 | 200 | 10006 | 10006 | 50 | 10 | | 4 | 2.5 GiB | 1000 | 10004/6005 | 5000 | 4504/6005 | 4504/6005 | 10006 | 10006 | 100 | 10 | | 10 | 2.5 GiB | 1000 | 1200 | 5000 | 1200 | 1200 | 1200 | 1200 | 100 | 10 |
|
|
1Maximum number of concurrent sessions. The number assumes that calls are made using RTP/SRTP Proxy mode, or a mix of RTP/SRTP Proxy, media manipulation and video calls. 3Maximum number of concurrent audio/video sessions. The total system capacity is affected if A/V calls are introduced into the call mix. Maximum number of calls is reduced by the number of video streams used. For example, 1 vCPU instance processing 25 A/V calls has a total capacity of: 300 (max number of calls) - 25 (calls processed with 1 vCPU instance) = 275 calls. 4Maximum number of concurrent sessions (when virtual DSP intervention is applied to 450 sessions) is 1000. 5Maximum number of concurrent sessions (when virtual DSP intervention is applied to 600 sessions) is 600. 6Maximum number of proxy media mode concurrent sessions is reduced by a count equivalent to the active number of concurrent RTP media manipulation sessions. Refer to note 1. | Caption |
|---|
| 0 | Table |
|---|
| 1 | Call Performance - Microsoft Azure Cloud |
|---|
|
| Azure Virtual Machine (VM) Resources | Maximum SIP
with corresponding
RTP Media Sessions1 | SIP Signaling Session Limits | RTP Media Session Limits | | Media Manipulation Mode2 (Requires Virtual DSP Intervention) | Proxy Media Mode (No Virtual DSP Intervention) | | VM Instance | vCPU | Maximum TCP/TLS-based SIP↔SIP Signaling Sessions | Maximum SIP Registrations (60 minute refresh rate) | No transcode, with in-band services scenario | Default scenario: G.711/G.729ab RTP ↔ G.729ab/G.711SRTP, with in-band services | Encryption services: G.711 RTP ↔ G.711 SRTP | No encryption services: RTP ↔ RTP/SRTP ↔ SRTP | | B1MS | 1 | 10 | 10 | 100 | 10 | 10 | 103 | 103 | | F1s | 1 | 300 | 300 | 1000 | 100 | 100 | 3003 | 3003 | | F2s | 2 | 1000 | 1000 | 1000 | 200 | 200 | 4003 | 10003 | | F4s | 4 | 1000 | 1000 | 5000 | 400 | 400 | 4503 | 10003 |
1Maximum number of concurrent sessions. The number assumes that calls are made using RTP/SRTP Proxy mode, or a mix of RTP/SRTP Proxy, media manipulation and video calls. 2Maximum number of concurrent sessions with virtual DSP intervention. See Transcoding Capacity below for details. 3Maximum number of proxy media mode concurrent sessions is reduced by a count equivalent to the active number of concurrent RTP media manipulation sessions. Refer to note 1. |
| Note |
|---|
| title | Number of RTP Port Pairs must be increased above maximum call capacity |
|---|
| The number of RTP Port Pairs must be configured slightly larger than the actual number of ports required to support the projected number of calls. We recommend you over-allocate the number of port pairs by approximately 25 - 30% above the number of calls you want to support. For details, see Configuring the Media System. |
| Note |
|---|
| title | Call Capacity Limitations |
|---|
| - Call capacity is limited to 4 calls per second when Info level logging is enabled. Additional logging verbosity reduces the call capacity.
- Although the call setup rate is 10 calls per second, if Call Admission Control (CAC) is enabled, calls over the rate limit will be rejected with the message 480 Temporary Not Available.
|
|
Transcoding Capacity
The table below indicates the maximum number of concurrent transcoded calls for specific CODEC combinations and system size.
| Multiexcerpt |
|---|
| MultiExcerptName | Transcoding - For KVM, VMWare and Microsoft Hyper-V |
|---|
|
| Div |
|---|
| | Caption |
|---|
0 | Table |
|---|
| 1 | | Caption |
|---|
| 0 | Table |
|---|
| 1 | Transcoding Capacity - KVM, VMware, Microsoft Hyper-V On-premises Deployments (1, 2, 4 vCPU) |
|---|
| | Transcoding Scenario | Virtual Machine vCPU Count | | CODEC 1 | CODEC 2 | 1 vCPU | 2 vCPU | 4 vCPU |
|---|
| G.711A-law or G.711u-law | G.711A-law or G.711u-law | 100 | 200 | 600 | | G.711A-law or G.711u-law | G.723 | 80 | 160 | 480 | | G.711A-law or G.711u-law | G.726 or G.729 | 100 | 200 | 600 | | G.711A-law or G.711u-law | AMR WB | 38 | 76 | 225 | | G.711A-law or G.711u-law | Opus | 24 | 54 | 165 | | G.711A-law or G.711u-law | T.38 | 50 | 100 | 300 |
|
| Caption |
|---|
| 0 | Table |
|---|
| 1 | Transcoding Capacity - KVM, VMware, Microsoft Hyper-V On-premises Deployments (10 vCPU) |
|---|
| | CODEC 1 | CODEC 2 | 10 vCPU |
|---|
| G.711A-law or G.711u-law | G.711A-law or G.711u-law | 1200 | | G.711A-law or G.711u-law | G.729 | 1200 |
|
|---|
|
| Multiexcerpt |
|---|
| MultiExcerptName | Transcoding - For Azure |
|---|
|
| Div |
|---|
| | Caption |
|---|
| 0 | Table |
|---|
| 1 | Transcoding Capacity - Microsoft Azure Cloud Deployments |
|---|
| Capacity - Microsoft Azure Cloud Deployments| Transcoding Scenario | Microsoft Azure VM Instance | | CODEC 1 | CODEC 2 | B1MS VM | F1s VM | F2s VM | F4s VM |
|---|
| G.711A-law or G.711u-law | G.711A-law or G.711u-law | 10 | 100 | 200 | 400 | | G.711A-law or G.711u-law | G.726 or G.729 | 10 | 100 | 200 | 400 |
|
|
|
...
| Caption |
|---|
| 0 | Table |
|---|
| 1 | SBC SWe Lite Maximum Configuration Values |
|---|
|
Feature | Maximum supported |
|---|
Number of Signaling Groups | 100 | Cumulative number of channels* across all the Signaling Groups | 1000 (1 vCPU) 4000 (2 vCPU, 4 vCPU, or 4 10 vCPU) | | Call Route Tables | 100 | Call Route Entries (all Call Route Tables combined) | 1000 | | Static Routes | 1024 | Registrar Table entries | 1000 (1 vCPU, 1 GiB)
5000 (2 vCPU, 1.5 GiB)
5000 (4 vCPU or 10 vCPU, 2.5 GiB) | Contact Registrant Table entries | 1000 | | Transformation Tables | 50 | Transformation Table entries | 1000 | Media Profiles entries | 20 | | Callback Number Tables | 80 | | Callback Numbers (in Callback Numbers List) | 16 | | SIP Server Table entries | 40 | | IP/FQDN or DNS-SRV entries (within each SIP Server Table entry) | 99 | | SIP Message Rule Tables | 100
(32 SIP Message Rules per Table) | | SIP Profiles | 100 |
*A SIP Channel is a Signaling Group (SG) logical attribute used to represent a potential path for a SIP session (call) leg between the SBC and the remote peer associated with the SG. The SIP channel is not synonymous with a SIP session; the number of SIP channels may equal or exceed the number of supported maximum SIP sessions. |
...