PSTN Connector and SSG Capacity Testing
These two tables (for PSTN Connector and SSG Capacity) describe the capacity testing for overall system performance when the PSTN Connector or Supplementary Services Gateway components are tested with multiple Media Control Platform instances. In addition, CPUs of varying types and speeds were used for testing on Windows, and are specified for each application.
Application Type | Hardware | Peak CAPS | Peak Ports | Comments |
---|---|---|---|---|
PSTN Connector (Windows) | ||||
PSTN Connector VoiceXML_App1 |
2x Xeon 3.0 GHz | N/A | 8 T1/E1 spans | Tested with two DMV boards. |
PSTN Connector VoiceXML_App3 |
2x Xeon 3.0 GHz | N/A | 8 T1/E1 spans | Tested with two DMV boards. |
PSTN Connector (Linux) | ||||
PSTN Connector VoiceXML_App1 |
2x Xeon 3.0 GHz | N/A | 8 T1/E1 spans (ISDN only) | Tested with two DMV boards. (RHEL 5.8 x86 only) |
PSTN Connector VoiceXML_App3 |
2x Xeon 3.0 GHz | N/A | 8 T1/E1 spans (ISDN only) | Tested with two DMV boards. (RHEL 5.8 x86 only) |
Application Type | Hardware | Peak CAPS | Peak Ports | Comments |
---|---|---|---|---|
Supplementary Services Gateway (Windows) | ||||
Supplementary Services Gateway (SSG) outbound call application | 2x Core2Quad Xeon E5335 2.53GHz | 65 | N/A | The SSG makes outbound calls through SIP Server, which becomes the overall system bottleneck. Multiple Media Control Platform instances are required to achieve peak capacity. GVP 8.1.5 with SIP Server 8.1.0 or later. |
SSG outbound call application | 2x Core2Quad Xeon E5335 2.53GHz | 50 | N/A | The SSG makes outbound calls through SIP Server which becomes the overall system bottleneck. Multiple Media Control Platform instances are required to achieve peak capacity. GVP 8.1.3 or 8.1.4 with SIP Server 8.0.4 or later. |
SSG outbound call application | 2x Core 2 Quad Xeon x5355, 2.66 GHz | 40 | N/A | The SSG makes outbound calls through SIP Server which becomes the overall system bottleneck. Multiple Media Control Platform instances are required to achieve peak capacity. Pre-GVP 8.1.3 with SIP Server 8.0.3. |
Supplementary Services Gateway (Linux) | ||||
Supplementary Services Gateway (SSG) outbound call application | 2x Quad Core Xeon E5335 @ 2.00GHZ, 4 GB RAM, 67 GB SAS hdd | 66 | N/A | The SSG makes outbound calls through SIP Server, which becomes the overall system bottleneck. Multiple MCP instances are required to achieve peak capacity. GVP 8.1.5 on RHEL 5.x with SIP Server 8.1.000.54. |
SSG outbound call application (overall system) performance, with multiple MCPs) | 2x Core2Quad Xeon E5335 2.00GHz | 64 CAPS (overall system) | N/A | SSG makes outbound calls via SIP Server which becomes the bottleneck overall system. Multiple MCPs are required to achieve peak capacity. GVP 8.1.7 on RHEL 6.4 x64 with SIP Server 8.1.1. |
SSG outbound call application | 2x Quad Core Xeon E5335 @ 2.53GHZ, 4 GB RAM, 67 GB SAS hdd | 50 | N/A | The SSG makes outbound calls through SIP Server which become the overall system bottleneck. Multiple Media Control Platform instances are required to achieve peak capacity. GVP 8.1.3 and 8.1.4 releases with SIP Server 8.0.4. |
SSG outbound call application | 2x Core 2 Quad Xeon x5355, 2.66 GHz | 40 | N/A | The SSG makes outbound calls through SIP Server which become the overall system bottleneck. Multiple Media Control Platform instances are required to achieve peak capacity. Pre-GVP 8.1.3 with SIP Server 8.0.3. |
This page was last edited on August 28, 2014, at 21:59.
Comments or questions about this documentation? Contact us for support!