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 5. Web Management
Version 5.0 77 October 2006
5.5.5.6 Release Cause Mapping
The Release Cause Mapping screen enables the gateway to map (up to 12) different SIP
Responses to Q.850 Release Causes and vice versa, thereby overriding the hard-coded
mapping mechanism (described in Appendix
H on page 379).
¾ To configure the release cause mapping, take these 5 steps:
1. Open the ‘Release Cause Mapping’ screen (Protocol Management menu > Routing
Tables submenu > Release Cause Mapping option); the ‘Release Cause Mapping’
screen is displayed.
Figure 5-13: Release Cause Mapping from ISDN to SIP
2. In the ‘Release Cause Mapping from ISDN to SIP’ table, define (up to 12) different
Q.850 Release Causes and the SIP Responses they are mapped to.
3. In the ‘Release Cause Mapping from SIP to ISDN’ table, define (up to 12) different SIP
Responses and the Q.850 Release Causes they are mapped to.
4. Click the Submit button to save your changes.
5. To save the changes so they are available after a power fail, refer to Section 5.9.2 on
page 124.
5.5.6 Configuring the Profile Definitions
Utilizing the Profiles feature, the gateway provides high-level adaptation when connected to
a variety of equipment (from both Tel and IP sides) and protocols, each of which requires a
different system behavior. Using Profiles, users can assign different Profiles (behavior) on
a per-call basis, using the Tel to IP and IP to Trunk Group Routing tables, or associate
different Profiles to the gateway’s B-channels(s). The Profiles contain parameters such as
Coders, T.38 Relay, Voice and DTMF Gains, Silence Suppression, Echo Canceler, RTP
DiffServ and more. The Profiles feature allows users to tune these parameters or turn them
on or off, per source or destination routing and/or the specific gateway or its ports. For
example, specific E1/T spans can be designated for to have a profile which always uses
G.711.
Each call can be associated with one or two Profiles, Tel Profile and (or) IP Profile. If both
IP and Tel profiles apply to the same call, the coders and other common parameters of the
preferred Profile (determined by the Preference option) are applied to that call. If the
Preference of the Tel and IP Profiles is identical, the Tel Profile parameters are applied.
Note: The default values of the parameters in the Tel and IP Profiles are identical
to the Web/ini file parameter values. If a value of a parameter is changed in
the Web/ini file, it is automatically updated in the Profiles correspondingly.
After any parameter in the Profile is modified by the user, modifications to
parameters in the Web/ini file no longer impact that Profile.