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 195 October 2006
Table 6-11: E1/T1/J1 Configuration Parameters (continues on pages 189 to 195)
ini File Field Name
Web Parameter Name
Valid Range and Description
ISDNGeneralCCBehavior
[General Call Control
Behavior]
16 = The gateway clears down the call if it receives a NOTIFY message
specifying ‘User-Suspended’. A NOTIFY (User-Suspended) message is used
by some networks (e.g., in Italy or Denmark) to indicate that the remote user
has cleared the call, especially in the case of a long distance voice call.
32 = Applies only to ETSI E1 lines (30B+D). Enables handling the differences
between the newer QSIG standard (ETS 300-172) and other ETSI-based
standards (ETS 300-102 and ETS 300-403) in the conversion of B-channel ID
values into timeslot values:
• In ‘regular ETSI’ standards, the timeslot is identical to the B-channel ID
value, and the range for both is 1 to 15 and 17 to 31. The D-channel is
identified as channel-id #16 and carried into the timeslot #16.
• In newer QSIG standards, the channel-id range is 1 to 30, but the timeslot
range is still 1 to 15 and 17 to 31. The D-channel is not identified as
channel-id #16, but is still carried into the timeslot #16.
When this bit is set, the channel ID #16 is considered as a valid B-channel ID,
but timeslot values are converted to reflect the range 1 to 15 and 17 to 31. This
is the new QSIG mode of operation. When this bit is not set (default), the
channel_id #16 is not allowed, as for all ETSI-like standards.
ISDNOutCallsBehavior
[Outgoing Calls Behavior]
1024 = Numbering plan / type for T1 IPÆTel calling number are defined
according to the manipulation tables or according to RPID header (default).
Otherwise, the Plan / type for T1 calls are set according to the length of the
calling number
ISDNIBehavior_x
[Q.931 Layer Response
Behavior]
Same as the description for parameter ‘ISDNIBehavior’ for a specific trunk ID (x
= 0 to 7)
ISDNInCallsBehavior_x
[Incoming Calls Behavior]
Same as the description for parameter ‘ISDNInCallsBehavior’ for a specific
trunk ID (x = 0 to 7)
ISDNOutCallsBehavior_x
[Outgoing Calls Behavior]
Same as the description for parameter ‘ISDNOutCallsBehavior’ for a specific
trunk ID (x = 0 to 7)