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

Mediant 2000 & TP-1610 & TP-260
SIP User's Manual 172 Document #: LTRT-68805
6.14 ISDN and CAS Interworking-Related Parameters
Table 6-9: ISDN and CAS Interworking-Related Parameters (continues on pages 172 to 179)
ini File Field Name
Web Parameter Name
Valid Range and Description
EnableTDMoverIP
[Enable TDM Tunneling]
0 = Disabled (default).
1 = TDM Tunneling is enabled.
When TDM Tunneling is enabled, the originating gateway automatically initiates
SIP calls from all enabled B-channels belonging to the E1/T1/J1 spans that are
configured with the ‘Transparent’ protocol. The called number of each call is the
internal phone number of the B-channel that the call originates from. The IP to
Trunk Group routing table is used to define the destination IP address of the
terminating gateway. The terminating gateway automatically answers these calls
if its E1/T1 protocol is set to ‘Transparent’ (ProtocolType = 5).
EnableISDNTunnelingTel
2IP
[Enable ISDN Tunneling
Tel2IP]
Valid options include:
0 = Disable (default).
1 = Enable ISDN Tunneling from ISDN PRI to SIP using a proprietary SIP header
2 = Enable ISDN Tunneling from ISDN PRI to SIP using a dedicated message
body
When ISDN Tunneling is enabled, the gateway sends all ISDN PRI messages
using the correlated SIP messages. Setup is tunneled using INVITE, all mid-call
messages are tunneled using INFO, and Disconnect/Release is tunneled using
BYE. The raw data from the ISDN is inserted into a proprietary SIP header (X-
ISDNTunnelingInfo) or a dedicated message body (application/isdn) in the SIP
messages.
Note: It is necessary to set the parameter ISDNDuplicateQ931BuffMode to 128
(duplicate all messages) for this mechanism to function.
EnableISDNTunnelingIP2
Tel
[Enable ISDN Tunneling
IP2Tel]
Valid options include:
0 = Disable (default)
1 = Enable ISDN Tunneling from SIP to ISDN PRI using a proprietary SIP header
2 = Enable ISDN Tunneling from SIP to ISDN PRI using a dedicated message
body
When ISDN Tunneling is enabled, the gateway extracts the raw data received in a
proprietary SIP header (X-ISDNTunnelingInfo) or a dedicated message body
(application/isdn) in the SIP messages and sends the data as ISDN messages to
the PSTN side.
ISDNDuplicateQ931BuffM
ode
Controls the activation / deactivation of delivering raw Q.931 messages.
0 = ISDN messages aren’t duplicated (default).
128 = All ISDN messages are duplicated.
Note: This parameter is not updated on-the-fly and requires a gateway reset.
EnableQSIGTunneling
[Enable QSIG Tunneling]
Enables QSIG tunneling over SIP according to <draft-elwell-sipping-qsig-tunnel-
03>.
0 = Disable (default).
1 = Enable QSIG tunneling from QSIG to SIP and vice versa.
When QSIG tunneling is enabled, all QSIG messages are sent as raw data in
corresponding SIP messages using a dedicated message body. Note that QSIG
tunneling must be enabled on both the originating and terminating gateways.
Note: It is necessary to set the parameter ‘ISDNDuplicateQ931BuffMode’ to 128
(duplicate all messages) so that this mechanism can function.