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 173 October 2006
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
PlayRBTone2Trunk_ID
[Play Ringback Tone to
Trunk]
ID = Trunk number (0-7).
0 (Don’t play) = The ISDN / CAS gateway doesn’t play a Ringback Tone (RBT).
No PI is sent to the ISDN, unless the parameter ‘Progress Indicator to ISDN’ is
configured differently.
1 (Play) =
The CAS gateway plays a local RBT to PSTN after receipt of a 180 ringing
response (with or without SDP).
Note: Reception of a 183 response doesn’t cause the CAS gateway to play an
RBT (unless ‘SIP183Behaviour = 1’).
The ISDN gateway functions according to the parameter ‘LocalISDNRBSource’:
• If the ISDN gateway receives a 180 ringing response (with or without SDP)
and ‘LocalISDNRBSource = 1’, it plays a RBT and sends an Alert with PI = 8
(unless the parameter ‘Progress Indicator to ISDN’ is configured differently).
• If ‘LocalISDNRBSource = 0’, the ISDN gateway doesn’t play an RBT and an
Alert message (without PI) is sent to the ISDN. In this case, the PBX / PSTN
should play the RBT to the originating terminal by itself.
Note: Reception of a 183 response doesn’t cause the ISDN gateway to play an
RBT; the gateway issues a Progress message (unless ‘SIP183Behaviour = 1’).
If ‘SIP183Behaviour = 1’, the 183 response is treated the same way as a 180
ringing response.
2 = Play according to ‘early media’ (default).
If a 180 response is received and the voice channel is already open (due to a
previous 183 early media response or due to an SDP in the current 180 response),
the ISDN / CAS gateway doesn’t play the RBT; PI = 8 is sent in an ISDN Alert
message (unless the parameter ‘Progress Indicator to ISDN’ is configured
differently).
If a 180 response is received but the ‘early media’ voice channel is not opened, the
CAS gateway plays an RBT to the PSTN; the ISDN gateway functions according
to the parameter ‘LocalISDNRBSource’:
• If ‘LocalISDNRBSource = 1’, the ISDN gateway plays an RBT and sends an
ISDN Alert with PI = 8 to the ISDN (unless the parameter ‘Progress Indicator
to ISDN’ is configured differently).
• If ‘LocalISDNRBSource = 0’, the ISDN gateway doesn’t play an RBT.
No PI is sent in the ISDN Alert message (unless the parameter ‘Progress
Indicator to ISDN’ is configured differently). In this case, the PBX / PSTN
should play an RBT tone to the originating terminal by itself.
Note: Reception of a 183 response results in an ISDN Progress message (unless
‘SIP183Behaviour = 1’).
If ‘SIP183Behaviour = 1’ (183 is handled in the same way as a 180+SDP), the
gateway sends an Alert message with PI = 8, without playing an RBT.
PlayRBTone2Tel
[Play Ringback Tone to
Tel]
Determines the method used to play Ringback tone to the Tel side.
It applies to all trunks that are not configured by the parameter
PlayRBTone2Trunk.
Similar description as the parameter ‘PlayRBTone2Trunk’.