Intel 05-2409-003 1.4 Call Control Libraries

22 Global Call API for HMP on Windows Programming Guide — August 2006

Product Description

1.4 Call Control Libraries

Each supported network technology requires a call control library to provide the interface between

the network and the Global Call library. The call control libraries currently supported by the

GlobalCall API for HMP are as follows:

GC_CUSTOM1_LIB

The first of two call control library place holders for custom call control libraries. Any third-

party Global Call compatible call control library can be used as a custom library. The Global

Call library supports up to two custom libraries.

GC_CUSTOM2_LIB

The second of two call control library place holders for custom call control libraries. Any

third-party Global Call compatible call control library can be used as a custom library. The

Global Call library supports up to two custom libraries.

GC_DM3CC_LIB

The call control library that controls access to network interfaces on Digital Network Interface

boards. This library is used for call control using ISDN and CAS/R2MF (PDK protocols)

signaling on Digital Network Interface boards.

GC_H3R_LIB

The call control library that controls access to IP network interfaces. This call control library

supports IP H.323 and SIP protocols and is used in conjunction with GC_IPM_LIB.

GC_IPM_LIB

The call control library that provides access to IP media resources. This library is used for

H323/SIP call control signaling and is used in conjunction with GC_H3R_LIB.

Call control libraries must be started before they can be used by the Global Call functions. The call

control libraries are started when a gc_Start() function is issued. The gc_Sta rt( ) function allows

the selective starting of call control libraries where the application can specify if all the call control

libraries are to be started or only specified libraries are to be started. The application can also start

a custom call control library that is not supported by Global Call. See the Global Call API Library

Reference for more information about the gc_Start() function.

Note: Invoking gc_Start(NULL) loads all call control libraries and consequently the memory footprint

includes memory that is allocated for all call control libraries. To reduce the memory footprint,

selective loading of call control libraries is recommended. For more information and an example,

see the gc_Start( ) function in the Global Call API Library Reference.

The initial state of all the call control libraries is the Configured state. When a call control library is

successfully started, the library will be in the Available state. If the call control library fails to start,

the library will be in the Failed state as shown in the diagram below. If the call control library is not

started, it remains in the Configured state.