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 11. Advanced System Capabilities
Version 5.0 255 October 2006
11.5.5 Using the ini File to Configure Parameter Tables
You can use the ini file to add / modify parameter tables. When using tables, Read-Only
parameters are not loaded, as they cause an error when trying to reload the loaded file.
Therefore, Read-Only parameters mustn’t be included in tables in the ini file.
Consequently, tables are loaded with all parameters having at least one of the following
permissions: Write, Create or Maintenance Write.
Parameter tables (in an uploaded ini file) are grouped according to the applications they
configure (e.g., NFS, IPSec). When loading an ini file to the gateway, the recommended
policy is to include only tables that belong to applications that are to be configured
(Dynamic tables of other applications are empty, but static tables are not).
The ini file includes a Format line that defines the columns of the table to be modified (this
may vary from ini file to ini file for the same table). The Format line must only include
columns that can be modified (parameters that are not specified as Read-Only).
An exception is Index-fields that are always mandatory. In the example provided in Table
11-1, all fields except for the ‘Time Connected’ field are loaded.
11.5.5.1 Structure of Parameter Tables in the ini File
Tables are composed of four elements:
The title of the table - The name of the table in square brackets (e.g.,
[MY_TABLE_NAME]).
A Format line - Specifies the columns of the table (by their string names) that are to be
configured.
• The first word of the Format line must be ’FORMAT’, followed by the names of
the Indices fields, and an equal sign '='. After the equal sign the names of the
columns are listed.
• Items must be separated by a comma ','.
• The Format line must end with a semicolon ';'.
Data line(s) – Contain the actual values of the parameters. The values are interpreted
according to the Format line. The first word of the Data line must be the table’s string
name followed by the Index fields.
• Items must be separated by a comma ','.
• A Data line must end with a semicolon ';'.
End-of-Table-Mark - Indicates the end of the table. The same string used for the
table’s title, preceded by a forward slash '\' (e.g., [\MY_TABLE_NAME]).