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 183 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
Prefix
[Tel to IP Routing Table]
Prefix = <Destination Phone Prefix>,<Destination IP Address>,<Source Phone
Prefix>,<Profile ID>
For example:
Prefix = 20,10.2.10.2,202,1
Prefix = 10[340-451]xxx#,10.2.10.6,*,1
Prefix = *,gateway.domain.com,*
Note 1: <destination / source phone prefix> can be single number or a range of
numbers.
Note 2: This parameter can appear up to 50 times.
Note 3: Parameters can be skipped by using the sign ‘$$’, for example:
Prefix = $$,10.2.10.2,202,1
Note 4: The <Destination IP Address> field can be either in dotted format
notation or a FQDN. This field can also include a selected port to use
(in the format: <IP Address>:<Port>).
Note 5: The IP address can include wildcards. The ‘x’ wildcard is used to
represent single digits, e.g., 10.8.8.xx represents all 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.
Note 6: If the string 'ENUM' is specified in the Destination IP Address field, an
ENUM query containing the destination phone number is sent to the DNS
server. The ENUM reply includes a SIP URI, used as the Request-URI in the
outgoing INVITE and for routing (if Proxy is not used).
For available notations, refer to Section
5.5.3.1 on page 67.
For detailed information on this feature, refer to Section 5.5.5.1 on page 70.
PSTNPrefix
[IP to Trunk Group Routing
Table]
PSTNPrefix = a,b,c,d,e
a = Destination Number Prefix
b = Trunk group ID (1 to 99)
c = Source Number Prefix
d = Source IP address (obtained from the Contact header in the INVITE
message)
e = IP Profile ID (1 to 4)
Selection of trunk groups (for IP to Tel calls) is according to destination number,
source number and source IP address.
Note 1: To support the ‘in call alternative routing’ feature, users can use two
entries that support the same call, but assigned it with a different trunk groups.
The second entree functions as an alternative selection if the first rule fails as a
result of one of the release reasons listed in the AltRouteCauseIP2Tel table.
Note 2: An optional IP ProfileID (1 to 4) can be applied to each routing rule.
Note 3: The Source IP Address can include the ‘x’ wildcard to represent single
digits. For example: 10.8.8.xx represents all IP 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.
Note 4: If the Source IP field includes an FQDN, DNS resolution is performed
according to DNSQueryType.