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 9. Networking Capabilities
Version 5.0 235 October 2006
When working in a PPPoE environment, the gateway negotiates for its IP address (as
described above). However, if the user desires to disable the PPPoE client, the gateway
can be configured to use default values for IP address, subnet mask and default gateway.
This can be done using ini file parameters PPPoERecoverIPAddress,
PPPoERecoverSubnetMask and PPPoERecoverDfgwAddress. These parameters indicate
to the gateway that if the PPPoE is disabled and no BootP server is activated, as required
in the gateway to use a PPPoE environment, then the gateway should use these defaults
for its IP configuration.
For a detailed description of the ini file parameters for PPPoE, refer to Section
6.6 on page
130.
Note: When working with a PPPoE server (Access Concentrator) that does not
reply to LCP Echo messages (which by default, the gateway periodically
sends) you may want to disable the LCP Echo messages by using the ini
file parameter PPPoELCPEchoEnable. (For a description of this
parameter, refer to Section 6.6 on page 130.)
9.5 IP Multicasting
The gateway supports IP Multicasting level 1 according to RFC 2236 (i.e. IGMP version 2)
for RTP channels. The gateway is capable of transmitting and receiving Multicast packets.
9.6 Robust Reception of RTP Streams
This mechanism filters out unwanted RTP streams that are sent to the same port number
on the gateway. These multiple RTP streams can result from traces of previous calls, call
control errors and deliberate attacks.
When more than one RTP stream reaches the gateway on the same port number, the
gateway accepts only one of the RTP streams and rejects the rest of the streams. The RTP
stream is selected according to the following procedure:
The first packet arriving on a newly opened channel sets the source IP address and UDP
port from which further packets are received. Thus, the source IP address and UDP port
identify the currently accepted stream. If a new packet arrives whose source IP address or
UDP port are different to the currently accepted RTP stream, there are two options:
The new packet has a source IP address and UDP port which are the same as the
remote IP address and UDP port that were stated during the opening of the channel.
In this case, the gateway reverts to this new RTP stream.
The new packet has any other source IP address and UDP port, in which case the
packet is dropped.
9.7 Multiple Routers Support
Multiple routers support is designed to assist the media gateway when it operates in a
multiple routers network. The gateway learns the network topology by responding to ICMP
redirections and caches them as routing rules (with expiration time).
When a set of routers operating within the same subnet serve as gateways to that network
and intercommunicate using a dynamic routing protocol, the routers can determine the
shortest path to a certain destination and signal the remote host the existence of the better
route. Using multiple router support the media gateway can utilize these router messages
to change its next hop and establish the best path.
Note: Multiple Routers support is an integral feature that doesn’t require configuration.