User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 201
Dialogic Corporation
Figure 13. SIP Call Transfer Failure - No Response from Party C
Party B Drops Transferred Call Early
Figure 14 illustrates a scenario in which the Transferee (party B) drops the transferred call
before receiving a response to the INVITE it sent to party C. As a result, the
GCEV_INVOKE_XFER_FAIL termination event is received at the Transferor (party A) and
the GCEV_XFER_FAIL termination event is received a the Transferee (party B). The
original primary call is left connected and in the GCST_CONNECTED state from the
perspective of both A and B.
A
(Transferring,
Transferor)
App
A
(Transferring,
Transferor)
IP CCLib
B
(Transferred,
Transferee)
App
B
(Transferred,
Transferee)
IP CCLib
C
(Transferred To,
Transfer Target)
App
C
(Transferred To,
Transfer Target)
IP CCLib
GCEV_REQ_
XFER(CRNp)
Pre condition: Primary call between A and B is connected (not shown).
GCEV_DIALING
(CRNt)
GCEV_DROPCALL
(CRNt)
gc_ReleaseCallEx
(CRNt)
GCEV_RELEASECALL
(CRNt)
202 Accepted
GCEV_ACCEPT_
XFER(CRNp)
GCEV_
INVOKE_XFER_
ACCEPTED(CRNp)
NOTIFY(100 Trying)
Subscription-State=active; expires=300
200 OK
GCEV_XFER_FAIL
(CRNp)
REFER
gc_InvokeXfer
(CRNp)
INVITE
gc_DropCall(CRNt)
Parties A and B remain connected.
Post condition:
GCEV_OFFERED
(CRNt)
Cause = IPEC_SIPReasonStatus408 Request Timeout
gc_MakeCall
(CRNt, CRNp)
GCEV_
DISCONNECTED
(CRNt)
Network timeout
No response from C
NOTIFY (408 Request Timeout)
Subscription-State = terminated
200 OK
Cause = IPEC_SIPReasonStatus408 Request Timeout
GCEV_DROPCALL
(CRNt)
gc_ReleaseCallEx
(CRNt)
GCEV_RELEASECALL
(CRNt)
gc_DropCall(CRNt)
GCEV_
INVOKE_XFER_
FAIL(CRNp)
gc_AcceptXfer
(CRNp)