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 332 Document #: LTRT-68805
16.2 Prerecorded Tones (PRT) File
The Call Progress Tones mechanism has several limitations, such as a limited number of
predefined tones and a limited number of frequency integrations in one tone. To work
around these limitations and provide tone generation capability that is more flexible, the
PRT file can be used. If a specific prerecorded tone exists in the PRT file, it takes
precedence over the same tone that exists in the CPT file and is played instead of it.
Note that the prerecorded tones are used only for generation of tones. Detection of tones is
performed according to the CPT file.
16.2.1 PRT File Format
The PRT dat file contains a set of prerecorded tones to be played by the gateway during
operation. Up to 40 tones (totaling approximately 10 minutes) can be stored in a single file
in flash memory. The prerecorded tones (raw data PCM or L8 files) are prepared offline
using standard recording utilities (such as CoolEdit
TM
) and combined into a single file using
the TrunkPack Downloadable Conversion utility (refer to Section
G.1.5 on page 375).
The raw data files must be recorded with the following characteristics:
Coders: G.711 A-law, G.711 µ-law or Linear PCM
Rate: 8 kHz
Resolution: 8-bit
Channels: mono
The generated PRT file can then be loaded to the gateway using the BootP/TFTP utility
(refer to Section
6.18 on page201) or via the Embedded Web Server (Section 5.8.2 on
page 119).
The prerecorded tones are played repeatedly. This enables you to record only part of the
tone and play it for the full duration. For example, if a tone has a cadence of 2 seconds on
and 4 seconds off, the recorded file should contain only these 6 seconds. The PRT module
repeatedly plays this cadence for the configured duration. Similarly, a continuous tone can
be played by repeating only part of it.
16.3 Voice Prompts File
The voice announcement file contains a set of Voice Prompts to be played by the gateway
during operation. The voice announcements are prepared offline using standard recording
utilities and combined into a single file using the TrunkPack Downloadable Conversion
Utility.
The generated announcement file can then be loaded to the gateway using the
BootP/TFTP utility (refer to Section
6.18 on page 201) or via the Embedded Web Server
(Section
5.8.2 on page 119).
If the size of the combined Voice Prompts file is less than 1 MB, it can permanently be
stored in flash memory. Larger files, up to 10 MB, are stored in RAM, and should be loaded
again (using BootP/TFTP utility) after the gateway is reset.
The Voice Prompts integrated file is a collection of raw voice recordings and / or wav files.
These recordings can be prepared using standard utilities, such as CoolEdit, Goldwave
TM
and others. The raw voice recordings must be sampled at 8000 kHz / mono / 8 bit. The wav
files must be recorded with G.711µ-Law/A-Law/Linear.
When the list of recorded files is converted to a single voiceprompts.dat file, every Voice
Prompt is tagged with an ID number, starting with ‘1’. This ID is used later by the gateway
to start playing the correct announcement. Up to 1000 Voice Prompts can be used.
AudioCodes provides a professionally recorded English (U.S.) Voice Prompts file.