PREV TOC HOME INDEX NEXT


Executive Intrusion - With Prior Validation

Step

API

Action/Result

Event

1 gc_MakeCall( )(with Intrusion IE) --->
2
<--- GCEV_PROCEEDING(with Busy IE)
3 gc_SndMsg( )(SndMsg_Intrude) --->
4 --- Intrusion succeeded<--- ---GCEV_CONNECTED
5 --- Intrusion failed<--- ---GCEV_DISCONNECTED

The procedure is as follows:

  1. Application places an outgoing call using the gc_MakeCall( ) function to a busy extension with Intrusion Type set to the INTRUDE_PRIOR_VALIDATION value. See Table 67, Intrusion IE for the format of the Intrusion IE.
  2. Receives call proceeding (GCEV_PROCEEDING) event with indication that the remote party was busy. Use the gc_GetSigInfo( ) function to retrieve the BUSY_IE value. See for more information. See Table 59, Intrusion IE for the format of the Busy IE.
  3. Application sends intrude request using the gc_SndMsg( ) function. See the gc_SndMsg( ) function description in the Global Call API Library Reference and Section 2.36, gc_SndMsg( ) for ISDN-specific information.
  4. Receives call connected (GCEV_CONNECTED) event. Call successfully intruded.
  5. Receives call disconnected (GCEV_DISCONNECTED) event. Call was not intruded.

PREV TOC HOME INDEX NEXT

Click here to contact Telecom Support Resources

Copyright 2003, Intel Corporation
All rights reserved
This page generated January, 2003