Dialogic 05-2239-009 User Manual

61

Dialogic Corporation

There are a several of scenarios where a blind call transfer may fail. The most common scenarios 
are described in the following topics: 

 

 

 

For simplification purposes, none of the following figures indicate the opening and closing of 
logical channels (and the associated media sessions) because the control procedures are consistent 
with typical non-transfer related H.323 calls. 

As indicated in Figure 15, the application at the transferred endpoint (party B) may call the 
gc_RejectXfer( ) function to signal via the ctInitiate.ReturnResult APDU that it cannot participate 
in a transfer. As a result, the GCEV_INVOKE_XFER_REJ termination event is received at 
transferring endpoint (party A) and the original primary call is left connected and in the 
GCST_CONNECTED state from the perspective of both A and B. 

A

(Transferring)

IP CCLib

B

(Transferred)

App

B

(Transferred)

IP CCLib

C

(Transferred To)

App

C

(Transferred To)

IP CCLib

gc_InvokeXfer(CRNp)

FACILITY(ctInitiate.Invoke)

Post condition:  Parties A and B remain connected.

GCEV_REQ_XFER

(CRNp)

gc_RejectXfer(CRNp,

GCVAL_REJREASON_

UNAVAIL)

GCEV_

REJ_XFER

(CRNp)

Pre condition:  Primary call between A and B is connected (not shown).

FACILITY(ctInitiate.ReturnResult = notAvailable)

GCEV_

INVOKE_XFER_REJ

(CRNp, GCRV_

REMOTEREJ_

UNAVAIL)

A

(Transferring)

App