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 230 Document #: LTRT-68805
For correct functionality of the redundancy mechanism, it is recommended to configure
both links to the same mode. It is essential that both link partners (the primary link partner
and the secondary link partner) have the same capabilities, so that whenever a switchover
occurs the gateway is able to provide at least the same Ethernet services as were provided
prior to the switchover.
For correct functionality of the redundancy mechanism, it is recommended to set the
physical secondary link prior to the gateway being reset (since the MAC configuration
cannot be changed thereafter).
Note that as the two Ethernet ports use the same MAC address, the external switches
connected to the gateways can in some cases create a noticeable switchover delay due to
their internal switching logic, though on the gateway level, the switchover delay is minimal
(milliseconds).
9.3 NAT Support
Network Address Translation (NAT) is a mechanism that maps a set of internal IP
addresses used within a private network to global IP addresses, providing transparent
routing to end hosts. The primary advantages of NAT are (1) reduces the number of global
IP addresses required in a private network (global IP addresses are only used to connect
to the Internet); (2) provides a better network security by hiding its internal architecture.
Figure
9-1 below illustrates the supported NAT architecture.
Figure 9-1: NAT Functioning
The way SIP is designed creates a problem for VoIP traffic to pass through NAT. SIP uses
IP addresses and port numbers in its message body. The NAT server can’t modify SIP
messages and therefore, can’t change local to global addresses.
Two different streams traverse through NAT: signaling and media. A gateway (located
behind a NAT) that initiates a signaling path will have problems in receiving incoming
signaling responses (they will be blocked by the NAT). Furthermore, the initiating gateway
must notify the receiving gateway where to send the media to.
To solve these problems the following mechanisms are available:
STUN (refer to Section 9.3.1 below).
First Incoming Packet Mechanism (refer to Section 9.3.2 on page 232)
RTP No-Op packets according to the avt-rtp-noop draft (refer to Section 9.3.3on page
232).
For SNMP NAT traversal, refer to Section 15.10 on page 326.