| 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 Streams 3 | | vCPU # | GB RAM | Maximum TCP/TLS-based SIP↔SIP Signaling Sessions7 | Maximum SIP Registrations (60 minute refresh rate) | No transcode, with in-band services scenario8 | Default scenario: G.711/G.729ab RTP ↔ G.729ab/G.711SRTP, with in-band services9 | Encryption services: G.711 RTP ↔ G.711 SRTP8 | No encryption services: RTP ↔ RTP/SRTP ↔ SRTP10 | | 1 | 1 GiB | 100 | 300 | 1000 | 100 | 100 | 300 6 | 300 6 | 25 | 10 | | 2 | 1.5 GiB | 1000 | 1000 | 1000 | 200 | 200 | 1000 6 | 1000 6 | 50 | 10 | | 4 | 2.5 GiB | 1000 | 1000 4 /600 5 | 5000 | 450 4 /600 5 | 450 4 /600 5 | 1000 6 | 1000 6 | 100 | 10 | | 10 | 2.5 GiB | 1000 | 1200 | 5000 | 1200 | 1200 | 1200 | 1200 | 100 | 10 |
|
|
1 Maximum 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. 3 Maximum 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. 4 Maximum number of concurrent sessions (when virtual DSP intervention is applied to 450 sessions) is 1000. 5 Maximum number of concurrent sessions (when virtual DSP intervention is applied to 600 sessions) is 600. 6 Maximum 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. 7 Supported by *-SG/*-SGX/*-SP licenses. 8 Supported by *-SGX/*-SP licenses. 9 Supported only by *-SP licenses. 10 Supported by -SGX/-SG/-SP. See "SIP Signaling & RTP Direct Media/RTP Proxy Sessions without Encryption Services" in Working with Licenses. | Available_since |
|---|
| Type | Modified For |
|---|
| Release | 8.1.5 |
|---|
|
| 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 | Maximum Call Rate Setup (CPS)
| | Media Manipulation Mode2 (Requires Virtual DSP Intervention) | Proxy Media Mode (No Virtual DSP Intervention) | | VM Instance | vCPU | Maximum TCP/TLS-based SIP↔SIP Signaling Sessions4 | Maximum SIP Registrations (60 minute refresh rate) | No transcode, with in-band services scenario5 | Default scenario: G.711/G.729ab RTP ↔ G.729ab/G.711SRTP, with in-band services6 | Encryption services: G.711 RTP ↔ G.711 SRTP5 | No encryption services: RTP ↔ RTP/SRTP ↔ SRTP4 | | B1ms | 1 | 10 | 10 | 100 | 10 | 10 | 10 3 | 10 3 | 10 | | B2s | 2 | 100 | 100 | 500 | 30 | 30 | 100 3 | 1003 | 10 | | DS1_v2 | 1 | 300 | 300 | 1000 | 100 | 100 | 300 3 | 300 3 | 10 | | DS3_v2 | 4 | 1000 | 1000 | 5000 | 400 | 400 | 500 3 | 1000 3 | 10 | 1 Maximum 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. 2 Maximum number of concurrent sessions with virtual DSP intervention. See Transcoding Capacity below for details. 3 Maximum 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. 4Supported by -SG-CLOUD/-SGX-CLOUD/-SP-CLOUD licenses. 5 Supported by -SGX-CLOUD/-SP-CLOUD licenses. 6 Supported by -SP-CLOUD license.
|
| 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.
|
|