Remote Diversion - Outbound

Step	API	Action/Result	Event
1	gc_MakeCall( )	--->
2	gc_SndMsg( ) (SndMsg_Divert, Diversion Location: DIVERT_REMOTE)	<---	GCEV_PROCEEDING(with Diversion IE, Diversion Location: DIVERT_REMOTE)
3	gc_DropCall( )	--->
4		<---	GCEV_DROPCALL
5	gc_ReleaseCall( )	--->
6	gc_MakeCall( ) (with Diversion IE)	--->
	---	Divert succeeded	---
7		<---	GCEV_PROCEEDING
8		<---	GCEV_DIVERTED
9		<---	GCEV_CONNECTED
	---	Divert failed	---
10		<---	GCEV_DISCONNECTED

The procedure is as follows:

1. Party 1 calls Party 2 by issuing the gc_MakeCall( ) function.
2. Party 1 receives a GCEV_PROCEEDING event from Party 2 with an indication that the call needs to be diverted to Party 3. The Diversion IE will contain the telephone number of Party 3. See Table 60, Diversion IE for the Diversion IE format.
3. Party 1 disconnects original call to Party 2 using a gc_DropCall( ) function.
4. Party 1 receives a call disconnect (GCEV_DROPCALL) event from Party 2.
5. The application releases the first call using a gc_ReleaseCall( ) function.
6. Party 1 diverts the call to Party 3 by issuing a gc_MakeCall( ) function. Calling party number IE should contain Party 3's telephone number. Diversion IE should contain Party 2's telephone number. See the gc_SetUserInfo( ) function description in the Global Call API Library Reference and Section 2.33, gc_SetUserInfo( ) for ISDN-specific information.
7. Party 1 receives a proceeding (GCEV_PROCEEDING) event from Party 3.
8. Party 1 receives a divert successful (GCEV_DIVERTED) event from Party 3.
9. Party 1 receives a call connected (GCEV_CONNECTED) event from Party 3. The call is successfully diverted.
10. Party 1 receives a divert failed (GCEV_DISCONNECT) event from Party 3. The call was not diverted.

Click here to contact Telecom Support Resources