(Page 1 of 1 in this chapter) Version

Chapter 4

Loading and Starting CAS TCPs

4.1 Introduction
4.2 Using Country-Specific Parameters
4.2.1 Before Configuring TCPs
4.2.2 Changing Parameter Files with switchpar
4.2.3 Adding Protocols for a Particular Country
4.2.4 Changing Default TCP Parameters
4.2.5 Changing Country Parameter Files
4.3 Starting CAS Protocols
4.3.1 Starting CAS Protocols with Resource Management

4.1 Introduction

Before starting a CAS TCP, the application must initialize CT Access and obtain CT Access context handles. The application should then start a TCP on each CTA context. For information about initializing CT Access and obtaining CT Access context handles refer to the CT Access Developer's Reference Manual.

This chapter describes:

4.2 Using Country-Specific Parameters

Many protocol features can differ from country to country or even within the same country. For this reason, AG CAS TCP parameters must be configured differently to specify the TCP behavior appropriately for various countries and networks. When you install AG CAS for NCC package, you specify the country and protocols that you want to use.

AG CAS will only run protocols for one country at a time. This is always the last country loaded. However, multiple protocols can be loaded for a single country. In addition, you can override the defaults for particular parameters by editing the corresponding ASCII .par file for that country.

The following sections describe:

4.2.1 Before Configuring TCPs

Before configuring a TCP:

4.2.2 Changing Parameter Files with switchpar

AG CAS for Natural Call Control software includes a switchpar program 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.

For more information about manually copying and renaming binary and ASCII parameter files, refer to sections Section 4.2.3 through Section 4.2.5.

To use switchpar, run the following from the command line:

Under Windows NT:

switchpar <cty> <prt> <nmsroot>

Under UNIX:

switchpar <cty> <prt>

Where:

4.2.3 Adding Protocols for a Particular Country

To add protocols for a particular country, copy the binary parameters 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 to...

nccx<prt><cty>.pf

Windows NT:
\nms\ag\cfg\country

or

UNIX:
/opt/nms/ag/cfg/country

Windows NT:
\nms\ag\cfg

or

UNIX:
/opt/nms/ag/cfg

 nccx<prt>.pf

<prt><cty>.pf

 adi<prt>.pf

Where <prt> indicates the protocol and <cty> indicates the country where used.

4.2.4 Changing Default TCP Parameters

To change default TCP parameters:

  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: 

    


    
 Copy this file...
    

    		
 From this directory...
    

    		
 To this directory...
    

    		
 And rename to...
    


    
 nccx<prt><cty>.par
    

    


    Windows NT:
    \nms\ctaccess\cfg\country
    

 or
    


    UNIX:
    /opt/nms/ctaccess/cfg/country
    

    

    


    Windows NT:
    \nms\ctaccess\cfg
    

 or
    


    UNIX:
    /opt/nms/ctaccess/cfg
    

    

    		
 nccx<prt>.par
    


    
 nccxadi<cty>.par
    

    		
 nccxadi.par
    


    
 nccstart<cty>.par
    

    		
 nccstart.par
    



    


    

    

    

    




Where <prt> indicates the protocol and <cty> indicates the country where used.


    


  1. Load the specified parameters in one of the following ways:
    

      

    • Use ctdaemon to set system-wide parameters by typing:

      

      
ctdaemon -f <filename>
      
Any CT Access 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 CT Access Developer's Reference Manual for more information.
      
In your application, call the CT Access function 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. 

      

      
Note:  You must modify parameters before starting the specified TCP for the new parameter values to take effect. 

 

      


      


      WARNING:
      

      

      


      You may only change a subset of parameters for each CAS protocol without affecting regulatory approvals. 
      Chapters 6 - 18 list all parameters for each protocol and indicate which parameters may be edited. Editing other parameters may result in violations of country-specific regulations.
      

      

      


      


      

      

      


    

    

    

    4.2.5	 Changing Country Parameter Files
    

    


    To change the specified country for AG 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 to...
    


    
 nccx<prt><cty>.pf
    

    


    Windows NT:
    \nms\ag\cfg\country
    

 or
    


    UNIX:
    /opt/nms/ag/cfg/country
    

    

    


    Windows NT:
    \nms\ag\cfg
    

 or
    


    UNIX:
    /opt/nms/ag/cfg
    

    

    		
 nccx<prt>.pf
    


    


    nccxadi<cty>.pf
    

    

    		
 nccxadi.pf
    


    


    nccstart<cty>.pf
    

    

    		
 nccstart.pf
    


    


    <prt><cty>.pf
    

    

    		
 adi<prt>.pf
    



    


    

    

    

    


    Where <prt> indicates the protocol and <cty> indicates the country where used.
    

Note:  You can only use AG CAS protocols for one country at a time. The country used will be the last country who's protocols were loaded.

    

    

    4.3	 Starting CAS Protocols
    

    


    Once a CT Access context has been opened and the TCP parameters has been loaded, the application can start a TCP on that CTA context according to the loaded parameters (see Section 4.2). Applications start CAS protocols by invoking nccStartProtocol. Once a TCP has started on a CTA context, the application can use call control functions to place and answer calls on that CTA context.
    

Note:  To start a TCP from within an application, the TCP must have been downloaded to the AG board at system initialization time. agmon downloads all TCPs specified in the AG configuration file, ag.cfg. For more information about the AG configuration file, see the Chapter 3 of this manual and the AG Runtime Configuration and Developer's Manual.


    nccStartProtocol requires a TCP name as one of its arguments. Valid TCPs include: 

    


    
 TCP Name
    

    		
 Description
    


    
 lps0
    

    		
 Analog Loop Start
    


    
 ap20
    

    		
 Australian P2 TCP
    


    
 wnkx (x=0,1)
    

    		
 Digital and analog wink start (digital or analog) TCP
    


    
 euc0
    

    		
 European digital CAS TCP
    


    
 fgd0
    

    		
 Feature Group D TCP
    


    
 gds0
    

    		
 Ground Start TCP
    


    
 mfs0
    

    		
 MF-Socotel TCP (Spanish national CAS protocol)
    


    
 mfc0
    

    		
 MFC-R2 TCP
    


    
 ops0
    

    		
 Off-Premises Station TCP
    


    
 sta0
    

    		
 Operator Workstation TCP
    


    
 eam0
    

    		
 Pulsed E and M TCP
    


    
 ss50
    

    		
 Signaling System 5 TCP
    


    
 r150
    

    		
 System R 1.5 TCP (inbound calls)
    


    
 r151
    

    		
 System R 1.5 TCP (outbound calls)
    



    


    

    

    

    


    After the application calls nccStartProtocol, it will receive NCCEVN_STARTPROTOCOL_DONE. If the TCP is started successfully, the event value field contains CTA_REASON_FINISHED. Otherwise, the value field contains a reason code that describes the error that occurred.
    


    If your application terminates, all channels associated with the application are terminated, the TCP shuts down, and the bit pattern specified in the IdleCode statement in the AG configuration file is signaled on the line. 
    

    

    

    4.3.1	 Starting CAS Protocols with Resource Management
    

    


    On AG Quad boards that use DSP resource management, DSP functions started by the TCP (for example, DTMF detection) cannot be active while calls are in the Connected state. For this reason, when calling nccStartProtocol, the value of the NCC service parameter mediamask (in the NCC.X.ADI_START_PARMS structure) must be set to 0.
    


    If mediamask is not set to zero, the TCP does not start and the application receives the NCCEVN_STARTPROTOCOL_DONE event with the reason NCC_REASON_OUT_OF_RESOURCES. The application must then set mediamask to zero before starting the protocol again.
    

Note:  These restrictions only apply when the AG Quad board is configured with all four trunks enabled. If you are using the AG Dual variants, no special restrictions apply. 


    For a reference to NCC.X.ADI_START parameters and information about migrating from ADI to NCC call control parameters, refer to Appendix B.
    

    

    


    
 
    (Page 1 of 1 in this chapter)  Version
    


    
 



    
tech_support@nmss.com

    

Copyright © 1999, Natural MicroSystems, Inc.   All rights
reserved.