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 376 Document #: LTRT-68805
5. For each raw data file, define a Tone Type, a Coder and a Default Duration by
completing the following 6 steps:
• Double-click or right-click the required file; the ‘File Data’ window (shown in
Figure G-4) appears.
• From the ‘Type’ drop-down list, select the tone type this raw data file is
associated with.
• From the ‘Coder’ drop-down list, select the coder that corresponds to the coder
this raw data file was originally recorded with.
• In the ‘Description’ field, enter additional identifying information (optional).
• In the ’Default’ field, enter the default duration this raw data file is repeatedly
played.
• Close the ‘File Data’ window (press the Esc key to cancel your changes); you are
returned to the Prerecorded Tones File(s) screen.
Figure G-8: File Data Window
6. In the ‘Output’ field, specify the output directory in which the PRT file is generated
followed by the name of the PRT file (the default name is prerecordedtones.dat).
Alternatively, use the Browse button to select a different output file. Navigate to the
desired file and select it; the selected file name and its path appear in the ‘Output’
field.
7. Click the Make File(s) button; the Progress bar at the bottom of the window is
activated. The dat file is generated and placed in the directory specified in the ‘Output’
field. A message box informing you that the operation was successful indicates that
the process is completed.
G.2 PSTN Trace Utility
These utilities are designed to convert PSTN trace binary files to textual form. The binary
PSTN trace files are generated when the user sets the PSTN interface to trace mode.
G.2.1 Operation
Generating textual trace/audit file for CAS protocols:
To generate a readable text file out of the binary trace file when using CAS protocols,
rename the PSTN trace binary file to CASTrace0.dat and copy it to the same directory
in which the translation utility CAS_Trace.exe is located. Then, run CAS_Trace.exe
(no arguments are required). As a result, the textual file CASTrace0.txt is created.
Generating textual trace/audit file for ISDN PRI protocols:
To generate a readable text file out of the binary trace file when using ISDN protocols,
copy the PSTN trace binary file to the same directory in which the translation utility
Convert_Trace.bat is located. The following files should reside in the same directory:
Dumpview.exe, Dumpview.cfg and ReadMe.txt. Please read carefully the
ReadMe.txt in order to understand the usage of the translation utility. Next, run the
Convert_Trace.bat. As a result, the textual file is created.
To start and collect the PSTN trace via the Web, please use the following instructions.
(Refer to Figure
G-9 for a view of the Trunk Traces). Also, please note if the PSTN trace
was of a PRI of CAS collection based on the framer involved in the trace. This information
is needed to properly parse the captured data.