3.2 Editing Configuration Files

In both Linux and Windows environments, you must edit the demo configuration file to customize it to your specific configuration.

Note: In Linux environments, there is also a UNIX makefile, but it is preconfigured for operation in a Linux environment and does not need to be modified.

The executable demo programs use the gc_basic_call_model.cfg configuration file. You must edit this configuration file before running the demo program using a standard text editor to include the protocols and products used by your application.

The protocol and resource information for each channel and the telephone number dialed (up to 24 digits) are defined in these configuration files. The configuration is specified in the following order:

1. Network device
2. Protocol name
3. Direction
4. Voice device (for technologies that require a voice resource to make a call)
5. Phone number

A digital network interface is not used for an analog call.

Note: Do not enter a digital interface for an analog board or channel. Use the value "NONE" instead.

The following is an extract from the gc_basic_call_model.cfg file:

####################################################################################
# For ICAPI Protocols
# Board #1
dtiB1T1          ar_r2_i           In        dxxxB1C1                1234567
#
# Board #2
dtiB2T1          ar_r2_o           Out       dxxxB9C1                1234567
####################################################################################  

The first uncommented line specifies that time slot 1 on digital network interface board 1 (dtiB1T1) is the inbound channel (In), running the Argentina for ICAPI inbound protocol (ar_r2_i), using the voice resource on virtual board 1, channel 1 (dxxxB1C1), with an associated phone number (1234567).

The second uncommented line specifies that time slot 1 on digital network interface board 2 (dtiB2T1) is the outbound channel (Out), running the Argentina for ICAPI outbound protocol (ar_r2_o), using the voice resource on virtual board 9, channel 1 (dxxxB9C1), with an associated phone number (1234567).

Example of Configuration File

The example configuration file (gc_basic_call_model.cfg) shown below configures one channel on one T-1 span to handle inbound calls using the United States T-1 for ICAPI inbound protocol (us_mf_i) and one channel on one T-1 span to handle outbound calls using the United States T-1 for ICAPI outbound protocol (us_mf_o).

Note: No voice resources are dedicated to either digital interface.

#########################################
#      gc_basic_call_model.cfg          #
#     DEFAULT CONFIGURATION FILE        #
#########################################
#
#
####################################################################################
#NetworkDev         ProtName     Direction   VoiceDevice(If any)      Phone #
# CAUTIONS: NONE is case sensitive
#           Follow the case sensitivity as provided in the sample fields
#           All fields must be used, including the phone # for the inbound direction
####################################################################################  
####################################################################################
# For PDK protocols
# Board #1
#Caution: For PDK protocols: Outbound channels must be listed before the 
#associated Inbound channel
#This is a timing issue related to doing back-to-back testing using one application
#and the unmodified, cdp protocol file as shipped.
#This is NOT an issue if you have both an inbound and outbound app where the inbound
#side starts before the outbound side OR your application is attached to a live trunk
#
#dtiB1T1          pdk_ar_r2_io      Out       dxxxB1C1                1234567
#
# Board #2
#dtiB2T1          pdk_ar_r2_io      In        dxxxB2C1                1234567
###################################################################################  
###################################################################################
# For ICAPI Protocols
# Board #1
dtiB1T1          us_mf_i           In        dxxxB1C1                1234567
#dtiB1T1          ar_r2_i           In        dxxxB1C1                1234567
#
# Board #2
dtiB2T1          us_mf_o           Out       dxxxB2C1                1234567
#dtiB2T1          ar_r2_o           Out       dxxxB2C1                1234567
###################################################################################  
###################################################################################
# For ISDN Protocols
# Board #1
#dtiB1T1          ISDN               In       NONE                    1234567
#
# Board #2
#dtiB2T1          ISDN               Out      NONE                    1234567
###################################################################################
# For SS7 protocols
# Board #1
#dtiB1T1          SS7                In       dxxxB1C1                1234567
#
# Board #2
#dtiB2T1          SS7                Out      dxxxB2C1                1234567
###################################################################################  
###################################################################################
# For PDK Analog protocols
# Board #1
#NONE            pdk_na_an_io        In       dxxxB73C1               102
#
# Board #2
#NONE           pdk_na_an_io         Out      dxxxB73C2               101
###################################################################################  
###################################################################################
# For ANAPI protocols
#Board #1
#NONE            na_an_io           In       dxxxB1C1               102
#
# Board #2
#NONE            na_an_io           Out      dxxxB2C2               101
###################################################################################  

Click here to contact Telecom Support Resources