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 74 Document #: LTRT-68805
Table 5-7: IP to Trunk Group Routing Table (continues on pages 73 to 74)
Parameter Description
Source IP Address Each entry in the Source IP Address fields represents the source IP
address of an IPÆTel call (obtained from the Contact header in the
INVITE message).
Note: The source IP address can include the ‘x’ wildcard to represent
single digits. For example: 10.8.8.xx represents all the addresses
between 10.8.8.10 to 10.8.8.99. The ‘*’ wildcard represents any
number between 0 and 255, e.g., 10.8.8.* represents all addresses
between 10.8.8.0 and 10.8.8.255.
Any SIP incoming call whose destination number matches the prefix defined in the ‘Destination Phone Prefix’
field and its source number matches the prefix defined in the adjacent ‘Source Phone Prefix‘ field and its source
IP address matches the address defined in the ‘Source IP Address’ field, is assigned to the trunk group entered
in the field to the right of these fields.
Note that IP to trunk group routing can be performed according to any combination of source / destination phone
prefixes and source IP address, or using each independently.
Note: For available notations that represent multiple numbers (used in the prefix columns), refer to Section
5.5.3.1 on page 67.
Trunk Group ID In each of the Trunk Group ID fields, enter the trunk group ID to which
calls that match these prefixes are assigned.
Profile ID Enter the number of the IP profile that is assigned to the routing rule.
5.5.5.3 Internal DNS Table
The internal DNS table, similar to a DNS resolution, translates hostnames into IP
addresses. This table is used when hostname translation is required (e.g., ‘Tel to IP
Routing’ table). Two different IP addresses can be assigned to the same hostname. If the
hostname isn’t found in this table, the gateway communicates with an external DNS server.
Assigning two IP addresses to hostname can be used for alternative routing (using the ‘Tel
to IP Routing’ table).
¾ To configure the internal DNS table, take these 7 steps:
1. Open the ‘Internal DNS Table’ screen (Protocol Management menu > Routing
Tables submenu > Internal DNS Table option); the ‘Internal DNS Table’ screen is
displayed.
Figure 5-10: Internal DNS Table Screen
2. In the ‘DNS Name’ field, enter the hostname to be translated. You can enter a string
up to 31 characters long.
3. In the ‘First IP Address’ field, enter the first IP address to which the hostname is
translated.
4. In the ‘Second IP Address’ field, enter the second IP address to which the hostname is
translated.
5. Repeat steps 2 to 4, for each Internal DNS Table entry.
6. Click the Submit button to save your changes.
7. To save the changes, refer to Section 5.9.2 on page 124.