How many voice channels can a VoIP system support?

Capacity planning for DTNA

Individual core processing speed is no longer relevant for Blueworx Voice Response. The overall system relative performance, or rPerf, is the defining factor in how many channels can be supported. As a guideline, an rPerf of 20 can support a 480-channel Blueworx Voice Response LPAR running speech-enabled VoiceXML applications. See http://www.ibm.com/systems/power/hardware/notices/rperf.html for further information on rPerf.

The use of secure SIP and secure RTP, increases the system performance requirements of Blueworx Voice Response by approximately 30%. As a guideline, a system performance rPerf of 26 can support a 480-channel secure SIP and secure RTP Blueworx Voice Response LPAR running speech-enabled VoiceXML applications.

To minimize CPU impact, consider the following:

• Ensure that RFC2833 RTP Payloads are used for DTMF transmission rather than DTMF tones. Most modern SIP devices support RFC2833, usually by default. The VOIP_MONITOR utility, provided with Blueworx Voice Response to support SIP, can be used to ensure that Telephone Event is being offered in the SDP (body) part of the SIP Invite message, and then accepted as the DTMF method to be used, as indicated in the SDP (body) part of the 200 OK response to the SIP Invite. If this is not found to be the case, either Blueworx Voice Response (DTEA and DTNA parameters) or the remote SIP endpoint (or both) need to be reconfigured to support RFC2833.
• Ensure that your application uses uncompressed play and recording using either G711 A or µ law. This is because the overhead of converting between the Blueworx Voice Response internal 5:1 algorithm voice format and uncompressed G711 A and µ law as sent/received over the line, is significant.
  • For Java and VoiceXML applications, uncompressed play and recording is always used, and no further action need be taken.
  • Most State Table applications will already have been written to use uncompressed voice (on account of the higher quality) and therefore no further actions are required.
  • However, if your State Table application uses compressed prompts (or messages, audio names and/or greetings) but does no recording in the compressed format, you need to take this into account in capacity sizings. If your application also does compressed recording, this factor also needs to be taken into account when planning channel capacity. Alternatively, consider changing your application to use uncompressed voice throughout.
  • Unified Messaging for Blueworx Voice Response is a voice messaging application. The Blueworx Voice Response and Unified Messaging supports the use of compressed or uncompressed voice in messages, audio names and greetings through setting options in Blueworx Voice Response System Configuration. If you are planning to operate Unified Messaging for Blueworx Voice Response in uncompressed mode for all voice objects from the outset, or to migrate your existing Unified Messaging for Blueworx Voice Response system to uncompressed voice, you need take no further action.

For the most recent information on suitable processors and capacity planning for VoIP, contact your Blueworx representative.