11.1.5 Dynamically Loaded Protocol Modules

When an application uses ANAPI, ICAPI or PDK protocols, protocol libraries and modules are also dynamically loaded when requested by an application, typically when a device that uses the protocol is opened using gc_OpenEx( ).

Caution: For System Release 5.1 or later, you must use protocols from the Global Call Protocol Package CD that contains shared library versions of all protocols for each operating system that Global Call supports. Previously released static protocol modules are not supported by System Release 5.1 or later.

For the ANAPI (analog) protocol, the libgcan.dll is dynamically loaded. In additon, a protocol module is loaded. The protocol module uses the following naming format:

• cc_an_ffff_io.dll or cc_an_d.dll
  Where: cc=country, an=analog, ffff=special hardware or software feature, io=input/output, d=direction

For PDK protocols (E-1 CAS or T-1 robbed bit), protocol modules [protocol state information (.psi) files] are also dynamically loaded when required by the application. These protocol modules use the following naming format:

• ccl_cc_tt_ffff_d.psi or cc_tt_d.psi
  Where: ccl=call control library, cc=country code, tt=protocol type, ffff=special hardware or software feature, d=direction indicator

For ICAPI protocols (E-1 CAS or T-1 robbed bit), protocol modules are dynamically loaded when required by the application. These protocol modules use the following naming format:

• ccl_cc_tt_ffff_d.dll or ccl_cc_tt_d.dll
  Where: ccl=call control library, cc=country code, tt=protocol type, ffff=special hardware or software feature, d=direction indicator

See the Global Call E-1/T-1 CAS/R2 Technology User's Guide for more information.

See the Global Call ISDN Technology User's Guide for more information about using ISDN protocols.

Click here to contact Telecom Support Resources