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 333 October 2006
¾ To generate and load the Voice Prompts file, take these 3 steps:
1. Prepare one or more voice files using standard utilities.
2. Use the TrunkPack Downloadable Conversion Utility to generate the voiceprompts.dat
file from the pre-recorded voice messages (refer to Section G.1.2 on page 371).
3. Load the voiceprompts.dat file to the gateway either by using a TFTP procedure (refer
to Section 6.18 on page 201), or via the Embedded Web Server (Section 5.8.2 on
page 119).
16.4 CAS Protocol Configuration Files
The CAS Protocol Configuration Files contain the CAS Protocol definitions to be used for
CAS-terminated trunks, users can either use the files supplied or construct their own files.
It is possible to load up to eight files and to use different files for different trunks.
Note that all CAS files loaded together must belong to the same Trunk Type (either E1 or
T1).
16.5 User Information File
The User Information file maps PBX extensions to global IP numbers. In this context, a
global IP number serves as a routing identifier for calls in the ‘IP World’. The PBX
extension uses this mapping to emulate the behavior of an IP phone. Note that the
mapping mechanism is disabled by default and must be activated using the parameter
‘EnableUserInfoUsage’ (described in Section
6.12 on page 150).
Each line in the file represents a mapping rule of a single PBX extension (up to 1000 rules
can be configured). Each line includes five items separated with commas. The items are
described in Table
16-1 below. An example of a User Information file is shown in Figure
16-4 below.
Each PBX extension registers (and authenticated) separately (a REGISTER message is
sent for each entry, only if AuthenticationMode is set to ‘Per Endpoint’) using the IP number
in the From / To headers. The REGISTER messages are sent gradually (i.e., initially, the
gateway sends requests according to the maximum number of allowed SIP dialogs
(configured by the parameter NumberOfActiveDialogs), after each received response, the
subsequent request is sent). Therefore, no more than ‘NumberOfActiveDialogs’ dialogs are
active simultaneously. The username and password are used for SIP Authentication when
required.
The calling number of outgoing Tel to IP calls is first translated to an IP number and then (if
defined) the manipulation rules are performed. The Display Name is used in the From
header in addition to the IP number.
The called number of incoming IP to Tel calls is translated to a PBX extension only after
manipulation rules (if defined) are performed.
The User Information file is a text file (the file size mustn’t exceed 108,000 bytes) that can
be loaded via the ini file (UserInfoFileName, described in Section
6.18 on page 201), the
Embedded Web Server (refer to Section
5.8.2 on page 119) or by using the automatic
update mechanism (UserInfoFileURL, refer to Section
11.3 on page 249).