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 370 Document #: LTRT-68805
G.1.1 Converting a CPT ini File to a Binary dat File
For detailed information on creating a CPT ini file, refer to Section 16.1 on page 329.
¾ To convert a CPT ini file to a binary dat file, take these 10 steps:
1. Execute the TrunkPack Downloadable Conversion Utility, DConvert.exe (supplied with
the software package); the utility’s main screen opens (shown in Figure G-1).
2. Click the Process Call Progress Tones File(s) button; the Call Progress Tones
screen, shown in Figure G-2, opens.
Figure G-2: Call Progress Tones Conversion Screen
3. Click the Select File… button that is in the ‘Call Progress Tone File’ box.
4. Navigate to the folder that contains the CPT ini file you want to convert.
5. Click the ini file and click the Open button; the name and path of both the ini file and
the (output) dat file appears in the fields below the Select File button.
6. Enter the Vendor Name, Version Number and Version Description in the
corresponding required fields under the ‘User Data’ section.
• The maximum length of the Vendor field is 256 characters.
• The format of the Version field is composed of two integers separated by a period
‘.’ (e.g., 1.2, 23.4, 5.22).
• The maximum length of the Version Description field is 256 characters.
7. The default value of the CPT Version drop-down list is Version 3. Do one of the
following:
• If the software version you are using is prior to version 4.4, select Version 1 (to
maintain backward compatibility).
• If the software version you are using is 4.4, select Version 2.
• Otherwise, leave the value at its default.
8. Check the ‘Use dBm units for Tone Levels’ check box. Note that the levels of the Call
Progress Tones (in the CPT file) must be in -dBm units.
9. Click the Make File button; you’re prompted that the operation (conversion) was
successful.
10. Close the application.