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 131 October 2006
Table 6-1: Networking Parameters (continues on pages 130 to 138)
ini File Field Name
Web Parameter Name
Valid Range and Description
DNS2IP
[Internal DNS Table]
Internal DNS table, used to resolve host names to IP addresses. Two different
IP addresses (in dotted format notation) can be assigned to a hostname.
DNS2IP = <Hostname>, <first IP address>, <second IP address>
Note 1: If the internal DNS table is configured, the gateway first tries to resolve
a domain name using this table. If the domain name isn’t found, the gateway
performs a DNS resolution using an external DNS server.
Note 2: This parameter can appear up to 10 times.
EnableSTUN
[Enable STUN]
0 = STUN protocol is disabled (default).
1 = STUN protocol is enabled.
When enabled, the gateway functions as a STUN client and communicates with
a STUN server located in the public internet. STUN is used to discover whether
the gateway is located behind a NAT and the type of that NAT. In addition, it is
used to determine the IP addresses and port numbers that the NAT assigns to
outgoing signaling messages (using SIP) and media streams (using RTP,
RTCP and T.38). STUN works with many existing NAT types, and does not
require any special behavior from them.
This parameter cannot be changed on-the-fly and requires a gateway reset.
STUNServerPrimaryIP
[STUN Server Primary IP]
The IP address of the primary STUN server.
STUNServerSecondaryIP
[STUN Server Secondary IP]
The IP address of the secondary STUN server.
STUNServerDomainName
Defines the domain name for the Simple Traversal of User Datagram Protocol
(STUN) server's address (used for retrieving all STUN servers with an SRV
query). The STUN client can perform the required SRV query to resolve this
domain name to an IP address and port, sort the server list, and use the servers
according to the sorted list.
Note: Use either the STUNServerPrimaryIP or the STUNServerDomainName
parameter, with priority to the first one.
NATBindingDefaultTimeout
Defines the default NAT binding lifetime in seconds. STUN is used to refresh
the binding information after this time expires.
The valid range is 0 to 2592000. The default value is 30.
DisableNAT
Enables / disables the Network Address Translation (NAT) mechanism.
0 = Enabled.
1 = Disabled (default).
Note: The compare operation that is performed on the IP address is enabled by
default and is controlled by the parameter ‘EnableIPAddrTranslation’. The
compare operation that is performed on the UDP port is disabled by default and
is controlled by the parameter ‘EnableUDPPortTranslation’.
EnableRport
Enables / disables the usage of the ‘rport’ parameter in the Via header.
0 = Enabled.
1 = Disabled (default).
The gateway adds an ‘rport’ parameter to the Via header field of each outgoing
SIP message. The first Proxy that receives this message sets the ‘rport’ value
of the response to the actual port from which the request was received. This
method is used, for example, to enable the gateway to identify its port mapping
outside a NAT.
If the Via doesn’t include ‘rport’ tag, the destination port of the response will be
taken from the host part of the VIA.
If the Via includes ‘rport’ tag with no port value, the destination port of the
response will be the source port of the incoming request.
If the Via includes ‘rport’ tag with a port value (rport=1001), the destination port
of the response will be the port indicated in the ‘rport’ tag.