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 362 Document #: LTRT-68805
TFTP Server IP: This field contains the IP address of the TFTP utility that is used for
file transfer of software and initialization files to the gateway. When creating a new
client, this field is populated with the IP address used by the BootP Tool. If a different
TFTP utility is to be used, change the IP address in this field to the IP address used by
the other utility.
Boot File: This field specifies the file name for the software (cmp) file that is loaded by
the TFTP utility to the VoIP gateway after the VoIP gateway receives the BootReply
message. The actual software file is located in the TFTP utility directory that is
specified in the BootP Preferences window. The software file can be followed by
command line switches. For information on available command line switches, refer to
Section D.11.6 on page 362.
Notes:
• Once the software file loads into the gateway, the gateway begins
functioning from that software. In order to save this software to non-
volatile memory, (only the cmp file, i.e., the compressed firmware file, can
be burned to your device's flash memory), the -fb flag must be added to
the end of the file name. If the file is not saved, the gateway reverts to the
old version of software after the next reset.
• The Boot file field can contain up to two file names: cmp file name to be
used for load of application image and ini file name to be used for
gateway provisioning. Either one, two or no file names can appear in the
Boot file field. To use both file names use the ‘;’ separator (without blank
spaces) between the xxx.cmp and the yyy.ini files (e.g.,
ram.cmp;SIPgw.ini).
ini File: This field specifies the configuration ini file that the gateway uses to program
its various settings. Enter the name of the file that is loaded by the TFTP utility to the
VoIP gateway after it receives the BootReply message. The actual ini file is located in
the TFTP utility directory that is specified in the BootP Preferences window.
D.11.6 Using Command Line Switches
You can add command line switches in the field Boot File.
¾ To use a Command Line Switch, take these 4 steps:
1. In the field Boot File, leave the file name defined in the field as it is (e.g.,
ramxxx.cmp).
2. Place your cursor after cmp
3. Press the space bar
4. Type in the switch you require.
Example: ‘ramxxx.cmp –fb’ to burn flash memory.
‘ramxxx.cmp -fb -em 4’ to burn flash memory and for Ethernet Mode 4 (auto-negotiate).
Table
D-1 lists and describes the switches that are available: