User`s manual
Table Of Contents
- Mediant 2000 & TP-1610 & TP-260/UNI SIP User’s Manual Version 5.0
- Table of Contents
- List of Figures
- List of Tables
- Notices
- 1. Overview
- 2. Physical Description
- 3. Installation
- 4. Getting Started
- 5. Web Management
- Computer Requirements
- Protection and Security Mechanisms
- Accessing the Embedded Web Server
- Getting Acquainted with the Web Interface
- Protocol Management
- Advanced Configuration
- Status & Diagnostic
- Software Update Menu
- Maintenance
- Logging Off the Embedded Web Server
- 6. Gateway's ini File Configuration
- Secured ini File
- Modifying an ini File
- The ini File Content
- The ini File Structure
- The ini File Example
- Networking Parameters
- System Parameters
- Web and Telnet Parameters
- Security Parameters
- RADIUS Parameters
- SNMP Parameters
- SIP Configuration Parameters
- Voice Mail Parameters
- ISDN and CAS Interworking-Related Parameters
- Number Manipulation and Routing Parameters
- E1/T1 Configuration Parameters
- Channel Parameters
- Configuration Files Parameters
- 7. Using BootP / DHCP
- 8. Telephony Capabilities
- Working with Supplementary Services
- Configuring the DTMF Transport Types
- Fax & Modem Transport Modes
- Event Notification using X-Detect Header
- ThroughPacket™
- Dynamic Jitter Buffer Operation
- Configuring the Gateway’s Alternative Routing (based on Conn
- Call Detail Report
- Supported RADIUS Attributes
- Trunk to Trunk Routing Example
- Proxy or Registrar Registration Example
- SIP Call Flow Example
- SIP Authentication Example
- 9. Networking Capabilities
- 10. Advanced PSTN Configuration
- 11. Advanced System Capabilities
- 12. Special Applications
- 13. Security
- 14. Diagnostics
- 15. SNMP-Based Management
- SNMP Standards and Objects
- Carrier Grade Alarm System
- Cold Start Trap
- Third-Party Performance Monitoring Measurements
- TrunkPack-VoP Series Supported MIBs
- Traps
- SNMP Interface Details
- SNMP Manager Backward Compatibility
- Dual Module Interface
- SNMP NAT Traversal
- SNMP Administrative State Control
- AudioCodes’ Element Management System
- 16. Configuration Files
- Appendix A. Selected Technical Specifications
- Appendix B. Supplied SIP Software Kit
- Appendix C. SIP Compliance Tables
- Appendix D. The BootP/TFTP Configuration Utility
- Appendix E. RTP/RTCP Payload Types and Port Allocation
- Appendix F. RTP Control Protocol Extended Reports (RTCP-XR)
- Appendix G. Accessory Programs and Tools
- Appendix H. Release Reason Mapping
- Appendix I. SNMP Traps
- Appendix J. Installation and Configuration of Apache HTTP Server
- Appendix K. Regulatory Information

Mediant 2000 & TP-1610 & TP-260
SIP User's Manual 216 Document #: LTRT-68805
8.7 Configuring the Gateway’s Alternative Routing
(based on Connectivity and QoS)
The Alternative Routing feature enables reliable routing of Tel to IP calls when Proxy isn’t
used. The gateway periodically checks the availability of connectivity and suitable Quality
of Service (QoS) before routing. If the expected quality cannot be achieved, an alternative
IP route for the prefix (phone number) is selected.
Note that if the alternative routing destination is the gateway itself, the call can be
configured to be routed back to one of the gateway’s trunk groups and thus back into the
PSTN (PSTN Fallback).
8.7.1 Alternative Routing Mechanism
When a TelÆIP call is routed through the gateway, the call’s destination number is
compared to the list of prefixes defined in the Tel to IP Routing table (described in Section
5.5.5.1 on page 70). The Tel to IP Routing table is scanned for the destination number’s
prefix starting at the top of the table. When an appropriate entry (destination number
matches one of the prefixes) is found; the prefix’s corresponding destination IP address is
checked. If the destination IP address is disallowed, an alternative route is searched for in
the following table entries.
Destination IP address is disallowed if no ping to the destination is available (ping is
continuously initiated every 7 seconds), when an inappropriate level of QoS was detected,
or when DNS host name is not resolved. The QoS level is calculated according to delay or
packet loss of previously ended calls. If no call statistics are received for two minutes, the
QoS information is reset.
The gateway matches the rules starting at the top of the table. For this reason, enter the
main IP route above any alternative route.
8.7.2 Determining the Availability of Destination IP Addresses
To determine the availability of each destination IP address (or host name) in the routing
table, one (or all) of the following (configurable) methods are applied:
Connectivity: The destination IP address is queried periodically (currently only by
ping).
QoS: The QoS of an IP connection is determined according to RTCP (Real-Time
Control Protocol) statistics of previous calls. Network delay (in msec) and network
packet loss (in percentage) are separately quantified and compared to a certain
(configurable) threshold. If the calculated amounts (of delay or packet loss) exceed
these thresholds the IP connection is disallowed.
DNS resolution: When host name is used (instead of IP address) for the destination
route, it is resolved to an IP address by a DNS server. Connectivity and QoS are then
applied to the resolved IP address.
8.7.3 PSTN Fallback as a Special Case of Alternative Routing
The purpose of the PSTN Fallback feature is to enable the gateway to redirect PSTN
originated calls back to the legacy PSTN network if a destination IP route is found
unsuitable (disallowed) for voice traffic at a specific time.
To enable PSTN fallback, assign the IP address of the gateway itself as an alternative
route to the desired prefixes. Note that calls (now referred to as IP to Tel calls) can be re-
routed to a specific trunk group using the Routing parameters.