Many protocol features can differ from country to country, or even within the same country.
Configure CAS API TCP parameters to specify the appropriate behavior for different countries and networks. When you install CAS for NCC, you specify the country and protocols to use. CAS runs protocols for only one country at a time (the last country loaded). You can load multiple protocols for a single country. You can also override the defaults for particular parameters by editing the corresponding ASCII .par file for that country.
This topic describes:
Many of the protocols included in this manual can do more than is described here. For more information, contact Dialogic Services and Support.
Before configuring a TCP, make sure that the appropriate CAS parameter files are in the proper locations.
A binary parameter file for the target country must be in the directory specified by the AGLOAD environment variable. These binary files contain compiled-in default values for all of the country-specific parameters. NaturalAccess loads these parameters when it is initialized.
Parameter file |
Description |
---|---|
nccxadi.pf |
Defines the NaturalAccess parameter category NNC.X.ADI_START and NCC.X.ADI_PLACECALL. These parameter categories include all of the country-specific parameters for AG and CG boards. |
nccstart.pf |
Defines the NaturalAccess parameter category NCC.START. NCC.START parameters include country-specific parameters for the last country installed. |
nccxprt.pf where prt indicates the protocol. |
Defines the NaturalAccess parameter category NCC.X.ADI_prt. This category holds all protocol-specific parameters for the specified protocol. The parameter default values defined by this file apply to the TCP implementing the protocol for the last country installed. |
A single country-specific instance of the binary parameter file is in the AGLOAD path for each protocol. Otherwise, the NCC service will not start.
The NaturalAccess installation program installs backup copies of the binary parameter files. The following table lists the names and locations of these backup files. Where prt indicates the protocol and cty indicates the country where used:
Binary parameter file |
Backup file |
Windows backup file location |
UNIX backup file location |
---|---|---|---|
nccxprt.pf |
nccxprtcty.pf |
\nms\ag\cfg\country |
/opt/nms/ag/cfg/country |
nccxadi.pf |
nccxadicty.pf |
\nms\ag\cfg\country |
/opt/nms/ag/cfg/country |
nccstart.pf |
nccstartcty.pf |
\nms\ag\cfg\country |
/opt/nms/ag/cfg/country |
To manually add protocols for a particular country, copy the binary parameter files for that country/protocol from the backup directory to the binary parameter file directory:
Copy this file... |
From this directory... |
To this directory... |
And rename the file to... |
---|---|---|---|
nccxprtcty.pf |
Windows: \nms\ag\cfg\country or UNIX: /opt/nms/ag/cfg/country |
Windows: \nms\ag\cfg or UNIX: /opt/nms/ag/cfg |
nccxprt.pf |
prt indicates the protocol and cty indicates the country where used.
To reset the values of the country-specific parameters, use the ASCII parameter value definition files. These files can be used to set the parameter values system-wide, using ctdaemon, or the application can parse the values for dynamic parameter management with NaturalAccess functions.
Parameters within the ASCI parameter files fall within the following classes:
Those that you can change to fit the application's needs
Those that should not be changed because they have regulatory relevance.
The following table lists the ASCII parameter value definition files:
File |
Location |
Description |
---|---|---|
nccxprt.par |
Windows: \nms\ctaccess\cfg UNIX: /opt/nms/ctaccess/cfg |
Defines the NaturalAccess parameter category NCC.X.ADI_prt. This category holds all protocol-specific parameters for the prt protocol. The parameter default values defined by these files apply to the TCP implementing the protocol prt for the last country installed. |
nccxadi.par |
Windows: \nms\ctaccess\cfg\ UNIX: /opt/nms/ctaccess/cfg |
Defines the NaturalAccess parameter category NNC.X.ADI_START and NCC.X.ADI_PLACECALL. These parameter categories include all of the country-specific parameters for AG and CG boards. |
nccstart.par |
Windows: \nms\ctaccess\cfg UNIX: /opt/nms/ctaccess/cfg |
Defines the NaturalAccess parameter category NCC.START. NCC.START parameters include all of the country-specific parameters for the last country installed. |
Complete the following steps to manually change default TCP parameters:
Step |
Action | ||||||||
1 |
Make changes to the values in ASCII parameter files (*.par file) and save the changes. | ||||||||
2 |
Copy ASCII parameter files to the appropriate directory and rename:
prt indicates the protocol and cty indicates the country where used. | ||||||||
3 |
Load the changed parameters in one of the following ways: Use ctdaemon to set system-wide parameters by entering: ctdaemon -f filename where filename can be one of the previously listed files or an edited file containing all of the changed parameters. You can add all the changed parameters to the ctapar section of cta.cfg. Any NaturalAccess application started subsequently on the system will share the parameter values contained in the *prt.par file, as long as ctdaemon is kept running. Refer to the Dialogic® NaturalAccess™ Software Developer’s Manual for more information. | ||||||||
4 |
In your application, call ctaLoadParameterFile and provide the appropriate parameter file as the function's argument. Call ctaSetParmByName for each parameter specified in the file. This sets new default values. Use this procedure for systems running in command line mode in Windows and other operating systems. When running as a Windows service, copy the modified parameters to cta.cfg. Then restart the service. Note: You must modify parameters before starting the specified TCP for the new parameter values to take effect. |
Warning: |
You can change only a subset of parameters for each CAS protocol without affecting regulatory approvals. For information about what parameters you can and cannot edit for a specific protocol, refer to the protocol topics in this document. Editing other parameters may result in violations of country-specific regulations. |
To change the specified country for CAS protocols, copy the country specific binary parameters files for that country and protocols from the backup directory to the binary parameter file directory:
Copy this file... |
From this directory... |
To this directory... |
And rename the file to... |
---|---|---|---|
nccxprtcty.pf nccxadicty.pf nccstartcty.pf |
Windows: \nms\ag\cfg\country or UNIX: /opt/nms/ag/cfg/country |
Windows:\nms\ag\cfg or UNIX: /opt/nms/ag/cfg |
nccxprt.pf nccxadi.pf nccstart.pf |
prt indicates the protocol and cty indicates the country where used.
Note: You can use CAS protocols for only one country at a time. The country used is the last country whose protocols were loaded.
The CAS API includes a switchpar utility for adding and changing binary and ASCII parameter files for particular protocols. switchpar automatically copies and renames the appropriate parameter files to the correct directories and file names.
To use switchpar, run the following command from the command line:
Operating system |
Command |
Windows |
switchpar cty prt nmsroot |
UNIX |
switchpar.sh cty prt |
Where:
cty indicates the three letter country abbreviation
prt indicates the three letter protocol abbreviation
nmsroot indicates the root directory for NaturalAccess software on the system (the default is \nms).
Note: Running switchpar for a protocol that has already been installed automatically overwrites any changes you may have made to that protocol's editable parameters.
If ctdaemon is running when you change parameters, stop and restart the program to initialize the parameters.