1.7. ISDN Extension IDs
Global Call provides a common interface to multiple network interface libraries for features that are abstracted across multiple call control libraries. The Feature Transparency and Extension (FTE) module of Global Call provides the flexibility to extend the Global Call API to access all technology or protocol-specific features unique to any given network interface. For further details, refer to the Global Call API Programming Guide.
To use one of these supported features directly through the Global Call API, the gc_Extension( ) function is called with an extension function identifier, ext_id, defined in this section for ISDN. If the extension function is supported and called in asynchronous mode, relevant information or network event notification is returned via the call control library through an extension event, GCEV_EXTENSION. For more information on the gc_Extension( ) function and GCEV_EXTENSION, refer to the Global Call API Programming Guide.
Table 3 gives provides a list of the extension IDs for ISDN and indicates whether the ID is supported in synchronous and/or asynchronous mode, and if there are termination events.
Table 3. ISDN Extension IDs
|
Extension ID
|
Mode
|
Termination Event
|
GCIS_EXID_CALLPROGRESS
when using Springware boards
Note:
When using DM3 boards, call progress can be sent using gc_SndMsg( ).
|
Sync |
No |
GCIS_EXID_GETBCHANSTATE
when using Springware boards
Note:
When using DM3 boards, B channel state can be retrieved using gc_GetLineDevState( ).
|
Sync |
No |
GCIS_EXID_GETDCHANSTATE
when using Springware boards
Note:
When using DM3 boards, D channel state can be retrieved using gc_GetLineDevState( ).
|
Sync |
No |
| GCIS_EXID_GETDLINKSTATE when using Springware boards |
Sync, |
No |
GCIS_EXID_GETENDPOINTwhen
using Springware boards
Note:
When using DM3 boards, retrieving CES and SAPI is not supported. |
Sync |
No |
GCIS_EXID_GETFRAME
when using Springware boards
Note:
When using DM3 boards, ISDN frames can be retrieved using gc_GetFrame( ).
|
Sync |
No |
GCIS_EXID_GETNETCRV
when using Springware boards
Note:
When using DM3 boards, the CRV can be retrieved using gc_GetNetCRV( ).
|
Sync |
No |
GCIS_EXID_GETNONCALLMSG
when using Springware boards
Note:
When using DM3 boards, retrieving information associated with the global
and null CRN is not supported. |
Sync |
No |
GCIS_EXID_PLAYTONE
when using Springware boards
Note:
When using DM3 boards, playing a user defined tone is not supported. |
Sync, Async |
Yes |
GCIS_EXID_SETDLINKSTATE
when using DM3 and Springware boards
Note:
When using Springware boards, only Sync mode is supported. When using
DM3 boards, both the Sync and Async modes are supported; the termination
event in Async mode is GCEV_EXTENSION. |
Sync, Async |
No |
GCIS_EXID_SNDFRAME
when using Springware boards
Note:
When using DM3 boards, sending frames can be achieved using gc_SndFrame( ).
|
Sync |
No |
GCIS_EXID_SNDMSG
when using Springware boards
Note:
When using DM3 boards, sending a non-call related message can be achieved
using gc_SndMsg( ) |
Sync |
No |
GCIS_EXID_SNDNONCALLMSG
when using Springware boards
Note:
When using DM3 boards, sending non-call related messages is not supported.
|
Sync |
No |
GCIS_EXID_STOPTONE
when using Springware boards
Note:
When using DM3 boards, stopping the playing of a tone is not supported.
|
Sync, Async |
Yes |
GCIS_EXID_TONEREDEFINE
when using Springware boards
Note:
When using DM3 boards, redefining call progress tone attributes is not
supported. |
None |
Yes |
The following sections describe the ISDN extension IDs (ext_id) and provide additional information related to their input parameters, as well as cautions, if applicable, and example codes. The set and parameter IDs are described in Chapter 4, ISDN-Specific Parameter Set Reference.
