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 70 Document #: LTRT-68805
5.5.5 Configuring the Routing Tables
Use this submenu to configure the gateway’s IPÆTel and TelÆIP routing tables and their
associated parameters.
5.5.5.1 Tel to IP Routing Table
The Tel to IP Routing Table is used to route incoming Tel calls to IP addresses. This
routing table associates a called / calling telephone number’s prefixes with a destination IP
address or with an FQDN (Fully Qualified Domain Name). When a call is routed through
the VoIP gateway (Proxy isn’t used), the called and calling numbers are compared to the
list of prefixes on the IP Routing Table (up to 50 prefixes can be configured); Calls that
match these prefixes are sent to the corresponding IP address. If the number dialed does
not match these prefixes, the call is not made.
When using a Proxy server, you do not need to configure the Telephone to IP Routing
Table. However, if you want to use fallback routing when communication with Proxy is lost,
or to use the ‘Filter Calls to IP’ and IP Security features, or to obtain different SIP URI host
names (per called number), you need to configure the IP Routing Table.
Note that for the Tel to IP Routing table to take precedence over a Proxy for routing calls,
set the parameter ‘PreferRouteTable’ to 1. The gateway checks the 'Destination IP
Address' field in the 'Tel to IP Routing' table for a match with the outgoing call. Only if a
match is not found, a Proxy is used.
Possible uses for Telephone to IP Routing can be as follows:
Can fallback to internal routing table if there is no communication with the Proxy.
Call Restriction – (when Proxy isn’t used), reject all outgoing TelÆIP calls that are
associated with the destination IP address: 0.0.0.0.
IP Security – When the IP Security feature is enabled (SecureCallFromIP = 1), the
VoIP gateway accepts only those IPÆTel calls with a source IP address identical to
one of the IP addresses entered in the Telephone to IP Routing Table.
Filter Calls to IP – When a Proxy is used, the gateway checks the TelÆIP routing
table before a telephone number is routed to the Proxy. If the number is not allowed
(number isn’t listed or a Call Restriction routing rule was applied), the call is released.
Always Use Routing Table – When this feature is enabled (AlwaysUseRouteTable =
1), even if a Proxy server is used, the SIP URI host name in the sent INVITE message
is obtained from this table. Using this feature, users are able to assign a different SIP
URI host name for different called and/or calling numbers.
Assign Profiles to destination address (also when a Proxy is used).
Alternative Routing – (When Proxy isn’t used) an alternative IP destination for
telephone number prefixes is available. To associate an alternative IP address to
called telephone number prefix, assign it with an additional entry (with a different IP
address), or use an FQDN that resolves to two IP addresses. Call is sent to the
alternative destination when one of the following occurs:
• No ping to the initial destination is available, or when poor Quality of Service
(QoS) (delay or packet loss, calculated according to previous calls) is detected, or
when a DNS host name is not resolved. For detailed information on Alternative
Routing, refer to Section 8.3 on page 210.
• When a release reason that is defined in the ‘Reasons for Alternative Tel to IP
Routing’ table is received. For detailed information on the ‘Reasons for
Alternative Routing Tables’, refer to Section 5.5.5.4 on page 75.