Table of Contents Index NMS Glossary Previous Page Next Page Version

Chapter 3

Loading and Starting CAS TCPs

3.1 Introduction
3.2 Using Country-Specific Parameters
3.2.1 Before Configuring TCPs
3.2.2 Changing Parameter Files with switchpar
3.2.3 Adding Protocols for a Particular Country
3.2.4 Changing Default TCP Parameters
3.2.5 Changing Country Parameter Files
3.3 Starting CAS Protocols
3.3.1 CAS Protocols with Managed DSP Resources

3.1 IntroductionTop of Page

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

This chapter describes:

3.2 Using Country-Specific Parameters Top of Page

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

NMS 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:

3.2.1 Before Configuring TCPsTop of Page

Before configuring a TCP:

3.2.2 Changing Parameter Files with switchparTop of Page

NMS 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 3.2.3 through Section 3.2.5.

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

Under Windows NT or Windows 2000:

switchpar cty prt nmsroot

Under UNIX:

switchpar cty prt

Where:

3.2.3 Adding Protocols for a Particular CountryTop of Page

To manually 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...

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

prtcty.pf

 adiprt.pf

...where prt indicates the protocol and cty indicates the country where used.

3.2.4 Changing Default TCP ParametersTop of Page

To manually 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...
    


    
 nccxprtcty.par
    

    


    Windows:
    \nms\ctaccess\cfg\country
    

 or
    


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

    

    


    Windows:
    \nms\ctaccess\cfg
    

 or
    


    UNIX:
    /opt/nms/ctaccess/cfg
    

    

    		
 nccxprt.par
    


    
 nccxadicty.par
    

    		
 nccxadi.par
    


    
 nccstartcty.par
    

    		
 nccstart.par
    



    


    

    

    

    




...where prt indicates the protocol and cty indicates the country where used.


    


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

      

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

      

      
ctdaemon -f filename
      
...where filename can be one of the above 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 Natural 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 Natural Access Developer's Reference Manual for more information.
      

    • In your application, call the Natural 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. 

Note:  Use this procedure for systems running in command line mode in Windows NT or Windows 2000 and other operating systems. When running as a Windows service, copy the modified parameters to cta.cfg. Then restart the service.

 

        


        


        WARNING:
        
chap3a.gif
        

        

        


        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.
        

        

        


        


        

        

        


      

      

      

      3.2.5 Changing Country Parameter FilesTop of Page
      

      


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


      
 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
      


      


      nccxadicty.pf
      

      

      		
 nccxadi.pf
      


      


      nccstartcty.pf
      

      

      		
 nccstart.pf
      


      


      prtcty.pf
      

      

      		
 adiprt.pf
      



      


      

      

      

      


      ...where prt indicates the protocol and cty indicates the country where used.
      

Note:  You can only use NMS CAS protocols for one country at a time. The country used will be the last country whose protocols were loaded.

      

      

      3.3 Starting CAS ProtocolsTop of Page
      

      


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

Note:  To start a TCP from within an application, the TCP must have been downloaded to the board at system initialization. The configuration utility downloads all TCPs specified in the configuration file. For more information about the configuration file, see Chapter 2 of this manual.


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

      


      
 TCP Name
      

      		
 Description
      


      
 ap20
      

      		
 Australian P2 TCP
      


      
 eam0
      

      		
 Pulsed E and M TCP
      


      
 euc0
      

      		
 European digital CAS TCP
      


      
 fgd0
      

      		
 Feature Group D TCP
      


      
 gds0
      

      		
 Digital Ground Start TCP
      


      
 lps0
      

      		
 Loop Start (analog or digital) TCP
      


      
 mfc0
      

      		
 MFC-R2 TCP
      


      
 mfs0
      

      		
 MF-Socotel TCP (Spanish national CAS protocol)
      


      
 ops0
      

      		
 Off-Premises Station TCP
      


      
 r150
      

      		
 System R 1.5 TCP (inbound calls)
      


      
 r151
      

      		
 System R 1.5 TCP (outbound calls)
      


      
 ss50
      

      		
 Signaling System 5 TCP
      


      
 sta0
      

      		
 Operator Workstation TCP
      


      
 wnkx (x=0,1)
      

      		
 Digital and analog wink start (digital or analog) TCP
      



      


      

      

      

      


      


      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. 
      

      

      

      3.3.1 CAS Protocols with Managed DSP ResourcesTop of Page
      

      


      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 A.
      


      For information about managing DSP resources on CG 6000 boards, see the CG  6000C Installation and Developer's Manual.
      


      

      

      


      
 
Table of Contents Index NMS Glossary Previous Page Next Page Version
      


      
 



      
Want to send us feedback on our documentation?  Email: Tech_Pubs@nmss.com

      

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