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

SIP User's Manual 6. Gateway's ini File Configuration
Version 5.0 187 October 2006
Table 6-10: Number Manipulation and Routing Parameters (continues on pages 180 to 188)
ini File Field Name
Web Parameter Name
Valid Range and Description
AltRouteCauseTel2IP
[Reasons for Alternative
Routing Table]
Table of call failure reason values received from the IP side. If a call is released
as a result of one of these reasons, the gateway tries to find an alternative route
to that call in the ‘Tel to IP Routing’ table.
For example:
AltRouteCauseTel2IP = 486 (Busy here).
AltRouteCauseTel2IP = 480 (Temporarily unavailable).
AltRouteCauseTel2IP = 408 (No response).
Note 1: The 408 reason can be used to specify that there was no response
from the remote party to the INVITE request.
Note 2: This parameter can appear up to 5 times.
AltRouteCauseIP2Tel
[Reasons for Alternative
Routing Table]
Table of call failure reason values received from the PSTN side (in Q.931
presentation). If a call is released as a result of one of these reasons, the
gateway tries to find an alternative trunk group to that call in the ‘IP to Trunk
Group Routing’ table.
For example:
AltRouteCauseIP2Tel = 3 (No route to destination).
AltRouteCauseIP2Tel = 1 (Unallocated number).
AltRouteCauseIP2Tel = 17 (Busy here).
Note 1: This parameter can appear up to 5 times.
Note 2: If the gateway fails to establish a cal to the PSTN because it has no
available channels in a specific trunk group (e.g., all of the trunk group’s
channels are occupied, or the trunk group’s spans are disconnected or out of
sync), it uses the internal release cause ‘3’ (no route to destination). This cause
can be used in the ‘AltRouteCauseIP2Tel’ table to define routing to an
alternative trunk group.
FilterCalls2IP
[Filter Calls To IP]
0 = Disabled (default)
1 = Enabled
If the filter calls to IP feature is enabled, then when a Proxy is used, the
gateway first checks the TelÆIP routing table before making a call through the
Proxy. If the number is not allowed (number isn’t listed or a Call Restriction
routing rule, IP=0.0.0.0, is applied), the call is released.
Alternative Routing Parameters
AltRoutingTel2IPEnable
[Enable Alt Routing Tel to IP]
Operation modes of the Alternative Routing mechanism:
0 = Disabled (default).
1 = Enabled.
2 = Enabled for status only, not for routing decisions.
AltRoutingTel2IPMode
[Alt Routing Tel to IP Mode]
0 (None) = Alternative routing is not used.
1 (Conn) = Alternative routing is performed if ping to initial destination failed.
2 (QoS) = Alternative routing is performed if poor quality of service was
detected.
3 (All) = Alternative routing is performed if, either ping to initial destination
failed, or poor quality of service was detected, or DNS host name is not
resolved (default).
Note: QoS is quantified according to delay and packet loss, calculated
according to previous calls. QoS statistics are reset if no new data is received
for two minutes.
For information on the Alternative Routing feature, refer to Section
8.3 on page
210.
IPConnQoSMaxAllowedPL
[Max Allowed Packet Loss for
Alt Routing]
Packet loss percentage at which the IP connection is considered a failure.
The range is 1% to 20%. The default value is 20%.