6.2.  Protocol File Naming Conventions

When a protocol is installed on your system, several files are installed, including the protocol module(s), firmware parameter files, and country dependent parameter files. For most protocols, the files are named according to the conventions in Table 11.

Table 11.  Protocol File Naming Conventions

File Name	Description
ccl_cc_tt_d.hot and ccl_cc_tt_d.qs	PDK protocol module (DM3)
ccl_cc_tt_d.psi	PDK protocol module (Springware)
ccl_cc_tt_d.so or ccl_cc_tt_ffff_d.so	ICAPI protocol module for Linux (Springware only)
ccl_cc_tt_d.dll or ccl_cc_tt_ffff_d.dll	ICAPI protocol module for Windows (Springware only)
ccl_cc_tt_d.cdp or ccl_cc_tt_ffff_d.cdp	Country dependent parameter file (DM3 and Springware)
ccl_cc_nn0.prm	Country-specific voice and network parameter file (Springware only)

where:

• ccl indicates the call control library for which the protocol is written, for example, pdk represents the PDKRT call control library. For the ICAPI call control library, ccl is blank.
• cc is a 2-character ISO country code, regional code (for example, es = Spain, fr = France, mx = Mexico, na = North America, etc.), or an indication of a switch-specific protocol.
• tt is a 2-character protocol type. Valid types are:
  • em: a T-1 protocol using E&M signaling with support for DTMF digits only
  • mf: a T-1 protocol using E&M signaling with support for MF digits
  • r2: a protocol using R2 MFC signaling
  • r1: a protocol using R1 MFC signaling
  • e1: a pulse, MF SOCOTEL, or other E-1 protocol
  • sw: a protocol that is switch specific
  • ls: a loop start protocol
• d is a 1- or 2-character direction indicator. Valid directions are:
  • i: inbound
  • o: outbound
  • io: inbound/outbound
• ffff is optional and defines a special software or hardware feature supported by the protocol; 1 to 4 characters. If the protocol type is "sw", then this field provides additional information about the switch.

  NOTE:

  Requires ICAPI call control library level 2, or else a compatibility error, EGC_COMPATIBILITY, will be generated when the application attempts to load the protocol.

• nn is the number of channels in a single span, typically 24 for T-1 and 30 for E-1.

The protocol name used in the devicename parameter of the gc_OpenEx( ) function is the root name of the .cdp file. Most ICAPI protocol releases use separate protocol modules to handle the inbound and the outbound portions of a protocol. For example, Table 12 describes the files included for the Argentina R2 ICAPI protocol.

Table 12.  Sample ICAPI Protocol File Set

Description	Protocol Files
	Linux	Windows
Inbound protocol module	ar_r2_i.so	ar_r2_i.dll
Outbound protocol module	ar_r2_o.so	ar_r2_o.dll
Inbound country dependent parameters	ar_r2_i.cdp	ar_r2_i.cdp
Outbound country dependent parameters	ar_r2_o.cdp	ar_r2_o.cdp
Voice and network firmware parameters	ar_300.prm	ar_300.prm

PDK protocols are bidirectional protocols. For example, Table 13 describes the files included with the Argentina R2 PDK protocol.

Table 13.  Sample PDK Protocol File Set

Description	Protocol Files
	Linux and Windows
Bidirectional protocol module (DM3)	pdk_ar_r2_io.hot, pdk_ar_r2_io.qs
Bidirectional protocol module (Springware)	pdk_ar_r2_io.psi
Bidirectional country dependent parameters (DM3 and Springware)	pdk_ar_r2_io. cdp
Voice and network firmware parameters (Springware only)	ar_300.prm

Click here to contact Telecom Support Resources