Table 7-1: Supported X-Detect Event Types - AudioCodes MediaPack MP-11X User Manual

SIP User's Manual
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:
Events
Type Subtype
CPT
FAX CED
modem
PTT voice-start
voice-end
The X-Detect event notification process is as follows:
For IP-to-Tel or Tel-to-IP calls, the gateway receives a SIP request message (using
1.
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.
Once the gateway receives such a request, it sends a SIP response message (using
2.
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.
Each time the gateway detects a supported event, the event is notified to the remote
3.
party, by sending an INFO message with the following message body:
•
Content-Type: application/X-DETECT
•
Type = [CPT | FAX | PTT...]
•
Subtype = xxx (according to the defined subtypes of each type)
Version 5.2

Table 7-1: Supported X-Detect Event Types

SIT SITDetectorEnable = 1
UserDefinedToneDetectorEnable = 1
Note: Differentiation of SIT is not supported in 5.0.
(IsFaxUsed ≠ 0) or (IsFaxUsed = 0, and FaxTransportMode ≠ 0)
VxxModemTransportType = 3
EnableDSPIPMDetectors = 1
Required Configuration
339
7. Telephony Capabilities
August 2007