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 253 October 2006
11.5 Using Parameter Tables
The gateway uses parameter tables to group related parameters of specific entities and
manage them together. These tables, similar to regular parameters, can be configured via
the ini file, Embedded Web Server, SNMP, etc.
Tables are composed of lines and columns. Columns represent parameters’ types. Lines
represent specific entities. The instances in each line are called line attributes. Lines in
table may represent (for example) a trunk, an NFS file system, list of timers for a given
application, etc.
Table
11-1 and Table 11-2 below provide useful examples for reference.
Table 11-1: Example of Parameter Table - Remote Management Connections
Index Fields:
1. Connection Number
Connection
Number
User Name User Password
Time Connected
(msec)
Permissions
0 Admin Yellow9 0 All
1 Gillian Red5 1266656 Read Only
2 David Orange6 0 Read Write
Table 11-2: Example of Parameter Table - Port-to-Port Connections
Index Fields:
1. Source Ports
2. Destination IP
3. Destination Port
Source Port Destination IP Destination Port Connection Name Application Type
2020 10.4.1.50 2020 ATM_TEST_EQ LAB_EQ
2314 212.199.201.20 4050 ATM_ITROP_LOOP LAB_EQ
6010 10.3.3.41 6010 REMOTE_MGMT MGMT
Note: Table 11-1 and Table 11-2 are provided as examples for the purpose of
illustration only and are not actually implemented in the gateway.
11.5.1 Table Indices
Each line in a table must be unique. Therefore, each table defines one or more Index
fields. The combination of the Index fields determines the 'line-tag'. Each line-tag appears
only once.
In the example provided in Table
11-1 there is only one Index field. This is the simplest way
to mark lines.
In the example provided in Table
11-2 there are three Index fields. This more complicated
method is a result of the application it represents.