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 6. Gateway's ini File Configuration
Version 5.0 201 October 2006
6.18 Configuration Files Parameters
The configuration files (Call Progress Tones, PRT, Voice Prompts and CAS) can be loaded
to the gateway via the Embedded Web Server (refer to Section
5.8.2 on page 119), or via
TFTP session.
¾ To load the configuration files via TFTP, take these 3 steps:
1. In the ini file, define the files to be loaded to the device. You can also define in the ini
file whether the loaded files should be stored in the non-volatile memory so that the
TFTP process is not required every time the device boots up.
2. Locate the configuration files you want to load and the ini file in the same directory.
3. Invoke a BootP/TFTP session; the ini and configuration files are loaded onto the
device.
Table
6-13 below describes the ini file parameters that are associated with the
configuration files.
Table 6-13: Configuration File Parameters
ini File Field Name
Valid Range and Description
CallProgressTonesFilename
The name of the file containing the Call Progress Tones definitions. Refer to
Section
16 for additional information on how to create and load this file.
VoicePromptsFileName
The name (and path) of the file containing the Voice Prompts definitions. Refer
to Section
16.2 on page 331 for additional information on how to create and
load this file.
CASFileName
This is the name of the file containing specific CAS protocol definition (such as
‘E_M_WinkTable.dat’). These files are provided to support various types of
CAS signaling.
CASFileName_x
CAS file name (e.g., ‘E_M_WinkTable.dat’) that defines the CAS protocol. It is
possible to define up to eight different CAS files by repeating this parameter.
Each CAS file can be associated with one or more of the gateway trunks using
the parameter CASTableIndex_x.
CASTablesNum
Number, 1 to 8. Specifies how many CAS configuration files are loaded.
PrerecordedTonesFileName
The name (and path) of the file containing the Prerecorded Tones.
UserInfoFileName
The name (and path) of the file containing the User Information data.
SaveConfiguration
Determines if the gateway’s configuration (parameters and files) is saved to
flash (non-volatile memory).
0 = Configuration isn’t saved to flash memory.
1 = Configuration is saved to flash memory (default).