Ip-To-Ip Routing Application; Dsp Channel Resources For Sbc/Ip-To-Ip/Ip Media Functionality - AudioCodes Mediant 600 User Manual

SIP User's Manual
9.2

IP-to-IP Routing Application

The AudioCodes device supports IP-to-IP VoIP call routing (or SIP trunking). The device
enables Enterprises to seamlessly connect their IP-PBX to a SIP trunk provided by an
Internet Telephony Service Provider (ITSP). The Enterprise can communicate with the
PSTN through the ITSP, which interfaces directly with PSTN. Alternatively, the device can
also provide the interface with the PSTN.
At the same time, the device can also provide an interface with the traditional PSTN
network, enabling PSTN fallback in case of IP network failure. In addition, the device
supports multiple SIP trunks, whereby if a connection to one ITSP fails, the call can
immediately be transferred to another ITSP. By allowing multiple SIP trunks where each
trunk is designated a specific ITSP, the device can route calls to an ITSP based on call
destination (e.g., country code). Therefore, in addition to providing VoIP communication
within an Enterpise's LAN, the device allows the Enterprise to communicate outside of the
corporate LAN, using SIP trunking.
The device interfaces between the Enterprise's IP-PBX and ITSP, allowing SIP trunking
implementation by the Enterprise, for example, in the following scenarios:
VoIP between headquarters and remote offices
VoIP between Enterprise and PSTN through their ITSP
For a detailed explanation on configuring IP-to-IP call routing, refer to the document IP-to-IP
SIP Call Routing Application Note.
9.3 DSP Channel Resources for SBC/IP-to-IP/IP Media
Functionality
The device supports the IP-to-IP call routing application as well as IP media server
capabilities. The device provides the required DSP resources (channels) for these
applications (in addition to the DSP resources needed for the PRI Trunk interfaces). The
device provides flexibility in making DSP resources readily available for these applications,
employing a method whereby DSP resources are obtained from the interface module itself
(Media Processing Module - MPM), as well as DSP resources "borrowed" from the
TRUNKS modules (for PRI interfaces).
Notes:
To enable the IP-to-IP call routing, and/or IP media server applications, and allow optimal
management of the required DSP resources, the following needs to be addressed:
Existence of appropriate Feature Keys
Suitable hardware configuration
Correct ini file configuration
The issues listed above are described in detail below.
1. Feature Keys:
Version 5.8
•
For the IP-to-IP call routing application, each IP-to-IP call session
includes two legs, utilizing two DSP resources.
•
In some scenarios, IP-to-IP routing also has the capability of not requiring
DSP's.
465
9. IP Telephony Capabilities
September 2009