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 204 Document #: LTRT-68805
7.2 Using DHCP
When the gateway is configured to use DHCP (DHCPEnable = 1), it attempts to contact the
enterprise’s DHCP server to obtain the networking parameters (IP address, subnet mask,
default gateway, primary/secondary DNS server and two SIP server addresses). These
network parameters have a ‘time limit’. After the time limit expires, the gateway must
‘renew’ its lease from the DHCP server.
Note that if the DHCP server denies the use of the gateway's current IP address and
specifies a different IP address (according to RFC 1541), the gateway must change its
networking parameters. If this happens while calls are in progress, they are not
automatically rerouted to the new network address (since this function is beyond the scope
of a VoIP gateway). Therefore, administrators are advised to configure DHCP servers to
allow renewal of IP addresses.
Note: If the gateway's network cable is disconnected and reconnected, a DHCP renewal is
performed (to verify that the gateway is still connected to the same network).
When DHCP is enabled, the gateway also includes its product name (e.g., ‘Mediant 2000’)
in the DHCP ‘option 60’ Vendor Class Identifier. The DHCP server can use this product
name to assign an IP address accordingly.
Note: After power-up, the gateway performs two distinct DHCP sequences. Only in the
second sequence, DHCP ‘option 60’ is contained. If the gateway is reset from the
Web/SNMP, only a single DHCP sequence containing ‘option 60’ is sent.
If DHCP procedure is used, the new gateway IP address, allocated by the DHCP server,
must be detected.
Note: If, during operation, the IP address of the gateway is changed as a result of
a DHCP renewal, the gateway is automatically reset.
¾ To detect the gateway’s IP address, follow one of the procedures
below:
Starting with Boot version 1.92, the gateway can use a host name in the DHCP
request. The host name is set to acl_nnnnn, where nnnnn stands for the gateway’s
serial number (the serial number is equal to the last 6 digits of the MAC address
converted from Hex to decimal). If the DHCP server registers this host name to a DNS
server, the user can access the gateway (through a Web browser) using a URL of
http://acl_<serial number> (instead of using the gateway’s IP address). For example, if
the gateway’s MAC address is 00908f010280, the DNS name is acl_66176.
After physically resetting the gateway its IP address is displayed in the ‘Client Info’
column in the BootP/TFTP configuration utility (refer to Figure D-1 on page 355).
Contact your System Administrator.