Transfer

Step	Dialogic API	Action/Result	Dialogic Event
1		<--	CCEV_OFFERED (CRN 1)
2	cc_AnswerCall( ) (CRN 1)	-->
3	cc_HoldCall( ) (CRN 1)	-->
4		<--	CCEV_HOLDACK (CRN 1)
5	cc_MakeCall( ) (CRN 2, with Inquiry IE)	-->
6		<--	CCEV_PROCEEDING (CRN 2 with Inquiry IE)
7		<--	CCEV_CONNECTED (CRN 2 with Inquiry IE)
8	cc_SndMsg( ) (SndMsg_Transfer, CRN 1)	-->
9	cc_SndMsg( ) (SngMsg_Transfer, CRN 2)	-->
10		<--	CCEV_TRANSFERACK (CRN 1)
11		<--	CCEV_TRANSFERACK (CRN 2)
12	Cross connect CRN 1's and CRN 2's SCbus time slot
13		<--	CCEV_TRANSIT (CRN 1)
14	cc_SndMsg( ) (SndMsg_Transit, CRN 2)	-->
15		<--	CCEV_TRANSIT (CRN 2)
16	cc_SndMsg( ) (SndMsg_Transit, CRN 1)	-->
17		<--	CCEV_DISCONNECT (CRN 1)
18	cc_DropCall( ) (CRN 1)	-->
19		<--	CCEV_DROPCALL (CRN 1)
20	cc_ReleaseCall( ) (CRN 1)	-->
21		<--	CCEV_DISCONNECT (CRN 2)
22	cc_DropCall( ) (CRN 2)	-->
23		<--	CCEV_DROPCALL (CRN 2)
24	cc_ReleaseCall( ) (CRN 2)	-->

1. Party 2 receives incoming call (CCEV_OFFERED) from Party 1.
2. Party 2 answers call (cc_AnswerCall( )) from Party 1.
3. Party 2 places call on hold (cc_HoldCall( )).
   NOTE: Some switches may not support Hold.
4. Party 2 receives call on hold acknowledge (CCEV_HOLDACK) event.
5. Party 2 places an inquiry call (cc_MakeCall( )) to Party 3. Application should use Party 1's telephone number as the calling party number and Party 3's telephone number as called party number. See Appendix C for the Inquiry IE format.
6. Party 2 receives call proceeding (CCEV_PROCEEDING) event with Inquiry IE from Party 3. See Appendix C for the Inquiry IE format.
7. Party 2 receives call connected (CCEV_CONNECTED) event with Inquiry IE from Party 3. See Appendix C for the Inquiry IE format.
8. Party 2 sends transfer request (cc_SndMsg( )) to Party 1 with TRANSFER_ORIG as transfer direction. See Appendix C for message format.
9. Party 2 sends transfer request (cc_SndMsg( )) to Party 3 with TRANSFER_TERM as transfer direction. See Appendix C for message format.
10. Party 2 receives transfer acknowledge (CCEV_TRANSFERACK) from Party 1.
11. Party 2 receives transfer acknowledge (CCEV_TRANSFERACK) from Party 3. Transfer completed. At this time, Party 2 loses control of the call.
12. Application should cause Party 1 to listen to Party 2's transmit time slot and Party 2 to listen to Party 1's transmit time slot.
13. Party 2 receives transit (CCEV_TRANSIT) event from Party 1. Party 2 should retrieve the content of the Transmit Message using cc_GetSigInfo( ).
14. Party 2 sends content of Transmit Message (unchanged) from Party 1 to Party 3 (cc_SndMsg( )). See Appendix C for message format.
15. Party 2 receives transit (CCEV_TRANSIT) event from Party 3. Party 2 should retrieve the content of the Transit Message using cc_GetSigInfo( ).
16. Party 2 sends content of Transit Message (unchanged) from Party 3 to Party 1 (cc_SndMsg( )). See Appendix C for message format.
17. Party 2 receives disconnect all (CCEV_DISCONNECT) event from Party 1.
18. Party 2 drops call (cc_DropCall( )) to Party 1.
19. Party 2 receives drop call event (CCEV_DROPCALL) event from Party 1.
20. Releases call to Party 1.
21. Party 2 receives disconnect all (CCEV_DISCONNECT) event from Party 3.
22. Party 2 drops call (cc_DropCall( )) to Party 3.
23. Party 2 receives drop call event (CCEV_DROPCALL) event from Party 3.
24. Releases call to Party 3.

NOTES:

NOTES: 1. Steps 3 and 4 are optional and need not be carried out on most switches.

2. Steps 12 through 16 may be repeated multiple times depending on when or whether the distant PBX supports Route Optimization. When Route Optimization occurs, or if either end of the transferred call is terminated, the call flow proceeds to step 17.

Click here to contact Dialogic Customer Engineering