
SIP User's Manual 332 Document #: LTRT-65411
MediaPack Series
The blind transfer call process is as follows:
• FXO receives a REFER request from the IP side
• FXO sends a hook-flash to the PBX, dials the digits (that are received in the
Refer-To header), and then drops the line (on-hook). Note that the time between
flash to dial is according to the WaitForDialTime parameter.
• PBX performs the transfer internally
Hold / Transfer toward the IP side: The FXO device doesn't initiate hold / transfer as
a response to input from the Tel side. If the FXO receives a REFER request (with or
without replaces), it generates a new INVITE according to the Refer-To header.
7.5 Event Notification using X-Detect Header
The device 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 device configurations need to be performed. The table
below lists the support event types (and subtypes) and the corresponding device
configurations, if required:
Table 7-1: Supported X-Detect Event Types
Events Type Subtype Required Configuration
CPT
SIT SITDetectorEnable = 1
UserDefinedToneDetectorEnable = 1
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 device 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 device 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 device 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 = [CPT | FAX | PTT…]
• Subtype = xxx (according to the defined subtypes of each type)
Kommentare zu diesen Handbüchern