(Page 1 of 1 in this chapter)

Chapter 2

Protocol Software Package Overview

This chapter: Discusses the components of the software included in the protocol software package Explains how to use each component

The protocol software package for a given country contains the following: One or more readme files A trunk control program (TCP) A country-specific binary parameter file An editable (ASCII) protocol-specific parameter file, used to set changeable values for specific TCP parameters Sample country-specific agmon configuration files A demonstration program with source code and make files

readme files provide: Last-minute information that does not appear in other documentation Directory paths to program and configuration files

A trunk control program (TCP) is a script that is run by the on-board processor to implement a telephone protocol. TCPs are able to both receive and place calls on both one-way and two-way trunks. Digital CAS TCPs include the following: Protocol TCP File Name MFC-R2 mfc0.tcp Pulsed E and M eam0.tcp European Digital CAS euc0.tcp International Wink Start iwk0.tcp Signalling System 5 ss5.tcp System R1.5 (inbound calls) r150.tcp System R1.5 (outbound calls) r151.tcp

Country-specific parameter files contain all of the parameters that allow TCPs to adapt to local implementations. Parameter files come in two forms: A binary parameter file that contains the complete set of country-specific parameters and default values. This file is named prtcty.pf, where prt is the three character mnemonic indicating the name of the protocol (for example mfc for MFC-R2 TCPs), and cty is the three character code of the target country. For example, the code for Italian European Digital CAS binary parameter file would be eucita.pf and can be found in nms\ag\cfg\country. This file is also installed as adiprt.pf in the directory nms\ag\cfg. This is the active version of the file for a given protocol (the last country installed is loaded with CT Access applications). An ASCII parameter file that contains a subset of the country specific parameters that users can change without effecting the regulatory approvals in the target country. This file is named adiprt.par, where prt is the three character mnemonic indicating the name of the protocol (for example mfc for MFC-R2 TCPs).

AG configuration files contain information that determines how agmon sets up AG boards. These files also contain country-specific information for different protocols.
Like the parameter file, AG configuration files are installed into the directory nms\ag\cfg for Windows NT and OS/2 systems or opt/nms/ag/cfg for Unix systems: agprt.cfg, where prt is the three-letter mnemonic indicating the protocol (e.g., mfc for MFC-R2 protocols, eam for Pulsed E and M protocols, euc for European Digital CAS TCPs, iwk for International Wink Start protocols or mfs for MF Socotel protocols). Like adiprt.pf, this file is overwritten whenever a package for another country is installed (for example, ageam.cfg or ageuc.cfg). This means that this file always applies to the most recent country to have been installed. agprtcty.cfg, where prt is the three-letter mnemonic indicating the protocol (e.g., mfc for MFC-R2 protocols, eam for Pulsed E and M protocols, or euc for European Digital CAS TCPs). cty is a three-letter country code. Like prtcty.pf, multiple agprtcty.cfg files are stored on your system. Each one is specific to a different country.
For general information about the AG configuration file, refer to the AG Runtime Configuration and Developer's Manual. For information about configuring this file for your protocol setup, refer to Chapter 4 of this manual.

The demonstration program package includes source code file, makefile, voice files, and an executable file. This program uses the TCP to dial or receive a call. The demonstration program is described in detail in Chapter 8.

(Page 1 of 1 in this chapter)