92 Dialogic
®
Global Call IP Technology Guide — November 2007
Dialogic Corporation
IP Call Scenarios
3.3.6.3 No Initial NOTIFY after REFER Accepted
Figure 35 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 35. SIP Call Transfer Failure - No Initial NOTIFY After REFER is Accepted
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.