3.4. Inbound Calls, Synchronous Mode
Table 18 describes the sequencing of function calls and the messages exchanged with the ISDN carrier during a synchronous mode inbound call. The items denoted by an asterisk (*) are optional functions/events or maskable events that may be reported to the application for specific signaling protocols.
Table 18. ISDN Inbound Call Set-Up (Synchronous)
|
Function/Event
|
Action/Description
|
| gc_WaitCall( ) |
Enables notification of an incoming call after line device opened with gc_Open( ) or gc_OpenEx( ) Incoming calls are unblocked |
| Incoming call |
A Setup message is received from the network A Proceeding message is sent to network
- When using Springware boards, by default, the Proceeding message is automatically sent to the network
- When using DM3 boards, by default, the application must explicitly use the gc_CallAck( ) function to send the Proceeding message
- Note: Application may connect a voice resource channel to the B channel at this time.
|
| gc_GetDNIS( ) |
Request DNIS information; information returned is stored in buffer. |
| gc_GetANI( )* |
Information returned is stored in buffer. |
| gc_CallProgress( )* |
Progress message sent to acknowledge that call was received. No response expected from network. |
| gc_AcceptCall( )* |
Alerting message sent to acknowledge that a call was received but called party has not answered. |
| gc_AnswerCall( ) |
- Note: Application may connect a voice resource channel to the B channel.
Connect message sent to connect call to called party (answer inbound call). Calling party may respond with a Connect Acknowledged message. |
| * = Optional function/event |
