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 212 Document #: LTRT-68805
8.4 Event Notification using X-Detect Header
The gateway supports the sending of notifications to a remote party notifying the
occurrence (or detection) of certain events on the media stream. Event detection and
notifications is performed using the X-Detect SIP message header, and only when
establishing a SIP dialog.
For supporting some events, certain gateway configurations need to be performed. The
table below lists the support event types (and subtypes) and the corresponding gateway
configurations, if required:
Table 8-1: Supported X-Detect Event Types
Events Required Gateway Configuration
Type Subtype
AMD
voice
automata
silence
unknown
EnableDSPIPMDetectors = 1
AMDTimeout = 2000 (msec)
CPT
SIT SITDetectorEnable = 1
UserDefinedToneDetectorEnable = 1
Note: Differentiation of SIT is not supported in 5.0.
FAX
CED (IsFaxUsed ≠ 0) or (IsFaxUsed = 0 and FaxTransportMode ≠ 0)
modem VxxModemTransportType = 3
PTT
voice-start
voice-end
EnableDSPIPMDetectors = 1
The X-Detect event notification process is as follows:
1. For IP-to-Tel or Tel-to-IP calls, the gateway receives a SIP request message (using
the X-Detect header) that the remote party wishes to detect events on the media
stream. For incoming (IP-to-Tel) calls, the request must be indicated in the initial
INVITE and responded to either in the 183 response (for early dialogs) or in the 200
OK response (for confirmed dialogs). For outgoing calls (Tel-to-IP), the request may
be received in the 183 (for early dialogs) and responded to in the PRACK, or received
in the 200 OK (for confirmed dialogs) and responded to in the ACK.
2. Once the gateway receives such a request, it sends a SIP response message (using
the X-Detect header) to the remote party, listing all supported events that can be
detected. The absence of the X-Detect header indicates that no detections are
available.
3. Each time the gateway detects a supported event, the event is notified to the remote
party, by sending an INFO message with the following message body:
• Content-Type: application/X-DETECT
• Type = [AMD | CPT | FAX | PTT…]
• Subtype = xxx (according to the defined subtypes of each type)