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 127 October 2006
6 Gateway's ini File Configuration
As an alternative to configuring the VoIP gateway using the Web Interface (refer to Chapter
5 on page 55), it can be configured by loading the ini file containing Customer-configured
parameters.
The ini file is loaded via the BootP/TFTP utility (refer to Appendix
D on page 353) or via
any standard TFTP server. It can also be loaded through the Web Interface (refer to
Section
5.6.6 on page 96).
The ini file configuration parameters are stored in the gateway's non-volatile memory after
the file is loaded. When a parameter is missing from the ini file, a default value is assigned
to that parameter (according to the cmp file loaded on the gateway) and stored in the non-
volatile memory (thereby overriding the value previously defined for that parameter).
Therefore, to restore the default configuration parameters, use the ini file without any valid
parameters or with a semicolon (;) preceding all lines in the file.
Some of the gateway's parameters are configurable through the ini file only (and not via the
Web). These parameters usually determine a low-level functionality and are seldom
changed for a specific application.
6.1 Secured ini File
The ini file contains sensitive information that is required for the functioning of the gateway.
It is loaded to, or retrieved from, the device via TFTP or HTTP. These protocols are
unsecured and vulnerable to potential hackers. Therefore an encoded ini file significantly
reduces these threats.
You can choose to load an encoded ini file to the gateway. When you load an encoded ini
file, the retrieved ini file is also encoded. Use the ‘TrunkPack Downloadable Conversion
Utility’ to encode or decode the ini file before you load it to, or retrieve it from, the device.
Note that the encoded ini file’s loading procedure is identical to the regular ini file’s loading
procedure. For information on encoding / decoding an ini file, refer to Section
G.1.4 on
page 374.
6.2 Modifying an ini File
¾ To modify the ini file, take these 3 steps:
1. Get the ini file from the gateway using the Embedded Web Server (refer to Section
5.6.6 on page 96).
2. Open the file (the file opens in Notepad or a Customer-defined text file editor) and
modify the ini file parameters according to your requirements. Save and close the file.
3. Load the modified ini file to the gateway (using either the BootP/TFTP utility or the
Embedded Web Server).
This method preserves the programming that already exists in the device, including special
default values that were preconfigured when the unit was manufactured.
Tip: Before loading the ini file to the gateway, verify that the extension of the ini
file saved on your PC is correct. On your PC, verify that the check box
‘Hide file extension for known file types’ (My computer > Tools > Folder
Options > View) is unchecked. Then, confirm that the ini file name
extension is xxx.ini and NOT erroneously xxx.ini.ini or xxx~.ini.