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 16. Configuration Files
Version 5.0 329 October 2006
16 Configuration Files
This section describes the configuration (dat) files that are load (in addition to the ini file) to
the gateway. The configuration files are:
Call Progress Tones file (refer to Section 16.1 below).
Prerecorded Tones file (refer to Section 16.2on page 332 ).
Voice Prompts file (refer to Section 16.3 on page 332).
CAS protocol configuration files (refer to Section 16.4 on page 333).
User Information file (refer to Section 16.5 on page 333).
To load any of the configuration files to the gateway use the Embedded Web Server (refer
to Section
5.8.2 on page 119) or alternatively specify the name of the relevant configuration
file in the gateway’s ini file and load it (the ini file) to the gateway (refer to Section
D.6 on
page 354).
16.1 Configuring the Call Progress Tones
The Call Progress Tones, configuration file used by the gateway is a binary file (with the
extension dat) which contains the definitions of the Call Progress Tones (levels and
frequencies) that are detected / generated by the gateway.
Users can either use, one of the supplied gateway configuration (dat) files, or construct
their own file. To construct their own configuration file, users are recommended, to modify
the supplied usa_tone.ini file (in any standard text editor) to suit their specific requirements,
and to convert it (the modified ini file) into binary format using the TrunkPack Downloadable
Conversion Utility. For the description of the procedure on how to convert CPT ini file to a
binary dat file, refer to Section
G.1.1 on page 370.
To load the Call Progress Tones (dat) file to the gateway, use the Embedded Web Server
(refer to Section
5.8.2 on page 119) or the ini file (refer to Section 6.18 on page 201).
Note: Only the dat file can be loaded to the gateway.
16.1.1 Format of the Call Progress Tones Section in the ini File
Users can create up to 32 different Call Progress Tones, each with frequency and format
attributes.
The frequency attribute can be single or dual-frequency (in the range of 300 Hz to 1980
Hz), or an Amplitude Modulated (AM). In total, up to 64 different frequencies are supported.
Only eight AM tones, in the range of 1 to 128 kHz, can be configured (the detection range
is limited to 1 to 50 kHz). Note that when a tone is composed of a single frequency, the
second frequency field must be set to zero.
The format attribute can be one of the following:
Continues: (e.g., dial tone) a steady non-interrupted sound. Only the ‘First Signal On
time’ should be specified. All other on and off periods must be set to zero. In this case,
the parameter specifies the detection period. For example, if it equals 300, the tone is
detected after 3 seconds (300 x 10 msec). The minimum detection time is 100 msec.
Cadence: A repeating sequence of on and off sounds. Up to four different sets of on /
off periods can be specified.