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 356 Document #: LTRT-68805
Figure D-2: Reset Screen
When a gateway resets, it first sends a BootRequest. Therefore, Reset can be used to
force a BootP session with a gateway without needing to power cycle the gateway. As with
any BootP session, the computer running the BootP Tool must be located on the same
subnet as the controlled VoIP gateway.
D.9 Log Window
The log window (refer to Figure D-1 on the previous page) records all BootP request and
BootP reply transactions, as well as TFTP transactions. For each transaction, the log
window displays the following information:
Client: shows the Client address of the VoIP gateway, which is the MAC address of
the client for BootP transactions or the IP address of the client for TFTP transactions.
Date: shows the date of the transaction, based on the internal calendar of the
computer.
Time: shows the time of day of the transaction, based on the internal clock of the
computer.
Status: indicates the status of the transaction.
• Client Not Found: A BootRequest was received but there is no matching client
entry in the BootP Tool.
• Client Found: A BootRequest was received and there is a matching client entry in
the BootP Tool. A BootReply is sent.
• Client’s MAC Changed: There is a client entered for this IP address but with a
different MAC address.
• Client Disabled: A BootRequest was received and there is a matching client entry
in the BootP tool but this entry is disabled.
• Listed At: Another BootP utility is listed as supporting a particular client when the
Test Selected Client button is clicked (for details on Testing a client, refer to
Section D.11.4 on page 361).
• Download Status: Progress of a TFTP load to a client, shown in %.
New IP / File: shows the IP address applied to the client as a result of the BootP
transaction, as well as the file name and path of a file transfer for a TFTP transaction.
Client Name: shows the client name, as configured for that client in the Client
Configuration screen.