User`s guide

Dialogic
®
System Release 6.0 PCI for Windows
®
Release Update, Rev 62 — January 30, 2008 199
Dialogic Corporation
termination event. The original primary call is left connected and in the
GCST_CONNECTED state from the perspective of both party A and party B.
Figure 10. SIP Call Transfer Failure - No Response from Party B
No Initial NOTIFY after REFER Accepted
Figure 11 illustrates a scenario in which the Transferee (party B) does not send a NOTIFY
after it accepts the REFER, causing the timer at party A to expire. The original primary call
is left connected and in the GCST_CONNECTED state from the perspective of both party
A and party B.
Figure 11. SIP Call Transfer Failure - No Initial NOTIFY after REFER Is Accepted
REFER Subscription Expires
Figure 12 illustrates a scenario in which the REFER subscription expires, causing both
party A and party B to time out. After the timeout, the Transferee application receives a
GCEV_XFER_FAIL termination event and the Transferor application receives a
Pre condition: Primary call between A and B is connected (not shown).
A
(Transferring,
Transferor)
App
A
(Transferring,
Transferor)
IP CCLib
B
(Transferred,
Transferee)
IP CCLib
C
(Transferred To,
Transfer Target)
App
C
(Transferred To,
Transfer Target)
IP CCLib
B
(Transferred,
Transferee)
App
Post condition: Parties A and B remain connected.
gc_InvokeXfer
(CRNp)
REFER
GCEV_REQ_
XFER(CRNp)
GCEV_INVOKE_
XFER_FAIL(CRNp)
Timeout/
network error
(No response from
B application)
Cause = IPEC_InternalReasonNoResponse
A
(Transferring,
Transferor)
App
A
(Transferring,
Transferor)
IP CCLib
B
(Transferred,
Transferee)
non-Global Call
C
(Transferred To,
Transfer Target)
App
C
(Transferred To,
Transfer Target)
IP CCLib
GCEV_INVOKE_
XFER_ACCEPTED
(CRNp)
Parties A and B remain connected.
Post condition:
gc_InvokeXfer
(CRNp, CNRs)
Primary call between A and B is connected (not shown).
Pre condition:
GCEV_INVOKE_
XFER_FAIL(CRNp)
REFER
202 Accepted
Cause = IPEC_NO_NOTIFY_TIME_OUT
No initial NOTIFY
before timeout.