(Page 1 of 1 in this chapter) Version

Chapter 3

Editing the AG Configuration File

3.1 Introduction
3.2 AG Configuration File Summary
3.3 Creating an AG Configuration File
3.3.1 Assigning an AG 2000 Board Number
3.3.2 Determining PCI Bus and Slot Location
3.3.3 Interrupts
3.3.4 DSP Files
3.3.5 .leo Files
3.3.6 Configuring a Standalone AG 2000 Board
3.3.7 Enabling Telephony Bus Switching
3.3.8 Telephony Bus Clocking
3.3.9 Enabling Echo Cancellation
3.3.10 QSLAC Files
3.3.11 Trunk Control Programs
3.3.12 QSLAC Files and TCPs for Loop Start
3.3.13 QSLAC Files and TCPs for Subscriber Loop
3.3.14 QSLAC Files and TCPs for DID
3.4 Running agmon
3.5 Sample AG Configuration Files
3.5.1 AG 2000 With LS Without H.100 Connectivity
3.5.2 Two AG 2000 LS With H.100 Connectivity
3.5.3 AG 2000 DID Without H.100 Connectivity
3.5.4 AG 2000 Subscriber Loop Without H.100 Connectivity

3.1 Introduction

The AG configuration file lists the types, locations, and roles of each of the AG boards. It also describes which software modules will be loaded to the board's memory. The AG board initialization utility, agmon, takes the AG configuration file as input, configures the boards as described in the file, and downloads runtime files.

This chapter:

Refer to the AG Runtime Configuration and Developer's Manual for the AG configuration file format and details about AG configuration file keywords.

3.2 AG Configuration File Summary

The following table summarizes the AG configuration file statements that are related to the AG 2000 board. For detailed information about these statements (including default values), refer to the AG Runtime Configuration and Developer's Manual.
Keyword

 Allowed Values

 Description

 Mandatory?

AG2DSPImage

 [dsp1[..dspn]] = filename

 Specifies a pre-linked DSP image file (for developers who develop their own DSP images).

 No

AG2DSP_Lib

 filename

 DSP library file.

 No

AG2DSP_Loader

 filename

 Module to load DSP functions.

 No

AG2DSP_OS

 [dsp1[..dspn]] = filename

 Defines DSP operating system used.

 No

AG2DSPFile

 filename

 Installs a DSP file. The naming convention for
AG 2000 DSP files is filename.m54. Refer to Section 3.3.4, DSP Files for a list and description of the DSP files that are shipped.

 No

AG2TaskProcessor

 [dsp1..[dspn]] = dsp_func1, dsp_func2

 Configures DSPs.

 No

Board

 boardnum [..endboard] | ALL

 Beginning of section defining configuration of one or more boards.

 Yes

ClockRef

 MVIP | H100 | OSC | SEC8K

 Configures the telephony bus clock.

 Only if EnableMVIP or DriveSec8K statement is present.

Diagnostics

 level

 Determines diagnostics level
(0 - 3) at board initialization time.

 No

EnableMVIP

 YES | NO

 Determines whether board is electrically connected to the MVIP bus or H.100 bus.

 No

End Board

Ends section defining the configuration of one or more boards.

 No

IdleCode

 MU-LAW | A-LAW | evencode [,oddcode]

 Defines voice encoding and bit pattern transmitted to network interface.

 No

LoadFile

 filename

 Defines boot loader.

 No

PCIbus

 busnum

 Defines the PCI bus location of the board.

 Yes

PCIslot

 slotnum

 Defines the slot location of the board on the PCI bus.

 Yes

Qslac

 Qslac [m[..n]] = filename.slc

 Specifies country-specific configuration file for line interfaces.

The default QSLAC file can be overriden on a board-wide or port-by-port basis using the QSLAC statement.

m, n optionally specifies a port or a range of ports.

· If a QSLAC file is not specified, all ports use the default file.

· If a QSLAC file is specified but no ports are specified, all ports use the specified QSLAC file.

· If a QSLAC file is specified and certain ports are specified, the specified ports use the specified QSLAC file. Any other ports not listed use the default QSLAC file.

Refer to Section 3.3.10, QSLAC Files.

 Not mandatory in the United States. Outside of the United States, it is mandatory for loop start. This is commonly added during the AG CAS Protocol installation.

ReportFile

 filename

 Defines configuration log file name.

 No

RunFile

 filename

 Specifies the runtime software to be transferred to the board.

 No

RunModule

 filename

 Specifies a runtime component to be transferred to the board.

 Yes

TCP

 filename

 Downloads trunk control program.

 Yes

3.3 Creating an AG Configuration File

The easiest way to create an AG configuration file for your system is to modify or combine the contents of the sample files installed with CT Access. These files are installed in one of the following directories:

The sample configuration file shipped with CT Access for the AG 2000 board is aglps.cfg for the loop start protocols and ag2000.cfg for others.

The file you create should be named ag.cfg. This is the filename agmon looks for by default. agmon uses the following algorithm to search for this file:

If you have two or more different boards, you can combine the sample configuration files. For example, if you are using an AG 2000 board and an AG Quad T board, begin by combining the aglps.cfg and agqt1.cfg files.

Group the statements into three categories: common, range-specific, and board-specific.

3.3.1 Assigning an AG 2000 Board Number

Each AG 2000 board is identified by a board number. The board number is assigned in the AG configuration file.

You do not configure the address or interrupt vector of PCI boards; instead it is automatically configured by the PC. To identify a board on the PCI bus, you specify the PCI bus number and PCI slot number on the bus. For example:

Board 0
  PCIbus = 0
  PCIslot = 2
  # other board specific configuration
End Board
When developing applications using CT Access, you open the ADI service specifying the PCI board, stream, and timeslot.

3.3.2 Determining PCI Bus and Slot Location

If you do not know the PCI bus and slot location of your AG 2000 board, use the AG board locate utility, blocate. blocate displays a list of all AG 2000 boards on the PCI bus with their corresponding PCI bus, slot number, and interrupt assignment.

Note: When invoking blocate, agmon should not be running.

To run blocate, enter the following at the command prompt:

  blocate
The following will be displayed:

  Thu Aug 13 15:51:22      There was 1 NMS PCI card detected

  BUS  SLOT  INTERRUPT
  00  14  0xf
If you have more than one PCI board in your system, blocate lists all boards and their assignments. To determine the location of a specific board, use blocate to associate the PCI bus assignment to a physical board by flashing an LED on the board.

To flash the LED on a board, call blocate with the PCI bus and PCI slot locations. For example:

  blocate 0 14
The following will be displayed:

  Flashing LED for NMS PCI board on bus 0 slot 14
The blocate LED will flash on the board located on PCI bus 0 in PCI slot 14.

Refer to Appendix D for more information about the blocate utility.

3.3.3 Interrupts

For AG 2000 boards on the PCI bus, the system chooses which interrupt is used. The system may choose to share one interrupt across several boards, or it may choose to allocate a single interrupt per board. The system may even choose to share interrupts between NMS PCI boards and boards from other vendors.

For AG 2000 boards on the PCI bus, the Interrupt keyword in the AG configuration file is ignored.
WARNING:

The system BIOS for every computer system which supports a combination of PCI slots and ISA slots provides some mechanism for assigning interrupts to either the ISA slots or to the PCI and plug-n-play slots.

It is critical that all interrupts which are assigned to the PCI slots are NOT used by any ISA boards.

Failure to abide by this restriction will cause the AG 2000 board to malfunction. It is recommended that you make a complete list of all interrupts in use by ISA boards before configuring an AG 2000 board.




agmon will fail to initialize a PCI board if a board on the ISA bus uses the interrupt assigned to the PCI board. The board locate utility, blocate, will correctly identify the PCI board, regardless of interrupt conflicts.






3.3.4	 DSP Files





Functions running on AG 2000 boards are specified with DSP files. The default DSP files are loaded. The default DSP files include: callp, dtmf, mf, ptf, signal, and tone. The non-default DSP files required for each AG 2000 board must be specified in the AG configuration file.



CT Access includes the following DSP files: 





 DSP File



 Description




 adsir(_j).m54



 Contain the caller ID function which decodes the modem burst that occurs between the first and second rings on a loop start line. In addition, it contains the FSK data receiver. (_j) is the Japanese variant.




 adsix(_j).m54



 Contains the FSK data transmitter. (_j) is the Japanese variant.




 callp.m54



 Contains voice and tone detectors used for call progress detection. Use for any outgoing or two-way trunk protocol, and for call progress analysis.




 dtmf.m54



 Contains the DTMF receiver and an energy/silence detector. Use dtmf.m54 for DTMF detection.




 dtmfe.m54



 A variant of dtmf.dsp, optimized for use with the echo canceller (echo.dsp). It yields better talk-off resistance but requires the echo canceller to achieve the best cut through performance.




 echo.m54



 Contains the echo cancellation function. The echo canceller removes reflected transmit channel energy from the incoming signal, which improves DTMF detection and voice recognition while playing.


 Note: Substitute dtmfe.dsp for dtmf.dsp when using the echo canceller.




 g726.m54



 Contains ITU G.726 ADPCM play and record functions. G.726 is a standard for 32 kbit/s speech coding.


 These functions require considerably more DSP processing time than the functions in voice.dsp.


 g6726.dsp is required if you start play/record with an encoding type of ADI_ENCODE_G726.




 ima.m54



 Contains IMA ADPCM play and record functions. IMA is a standard for 32 kbit/s speech encoding.




 mf.m54



 Contains the multi-frequency receiver which is required for any trunk protocol (TCP) that uses MF signaling, and required by the MF detector.




 ptf.m54



 Contains precise tone filters. Used as the cleardown detector by loop start protocols.




 oki.m54



 Contains play and record functions for OKI ADPCM speech encoding, at 24 kbit/s or 32 kbit/s (used to play/record compatible voice files).




 rvoice.m54



 Contains PCM play and record functions.


 rvoice.m54 is required to play or record with an encoding of ADI_ENCODE_MULAW, ADI_ENCODE_ALAW, or ADI_ENCODE_PCM8M16.




 signal.m54



 Contains signaling, ring detector, and pulse functions. These are "out of band" functions which typically operate on the MVIP signaling stream. This file is required for:


·	 Any trunk protocol except NOCC


·	 The signal detector


·	 Sending a pulse




 tone.m54



 Contains the tone generation function. This file is required for any trunk protocol except NOCC. It is also required for generating tones, generating DTMF tones, MF tones, initiating dialing, and for generating a beep tone with any second record function.




 voice.m54



 Contains NMS ADPCM play and record functions. The compressed speech is in a framed format with 20 milliseconds of data per frame. Speech is compressed to 16, 24, or 32 kbit/s or stored as uncompressed mu-law or A-law (64 kbit/s). This file is required to play or record with encoding values of ADI_ENCODE_NMS_16, ADI_ENCODE_NMS_24, ADI_ENCODE_NMS_32, or ADI_ENCODE_NMS_64.




 wave.m54



 Contains play and record functions for PCM speech in formats commonly used in WAVE files, including 8 and 16 bit 11 kHz sampling.


















For non-standard or custom configurations, the AG2DSPImage or AG2TaskProcessor keywords in the ag.cfg file can be used to identify which DSP files to load onto each DSP processor. All DSP processors that have not been explicitly configured with an AG2DSPImage or AG2TaskProcessor keyword will be loaded with all of the default DSP files and all DSP files identified with the AG2DSPFile keyword in the ag.cfg file. The default DSP files include: callp, dtmf, mf, ptf, signal, and tone.



The AG Runtime Configuration and Developer's Manual provides details about the DSP resources available on each AG 2000 board and the DSP requirements for each ADI service function. Refer to this manual to estimate the DSP requirements for your application, and for instructions for re-configuring DSP resources if necessary.






3.3.5	 .leo Files





A .leo (loadable extensible object) file is a run module, a modular extension to the core file. The core file, along with the run modules, comprise the software that runs on the board's coprocessor. Previously, standard run modules were packaged with the core file in a single file called the run file.



The following .leo files are included with AG 2000: 





 File



 Description




 svc.leo



 DSP function manager.




 gtp.leo



 Trunk protocol engine.




 voice.leo



 Play and record manager.



















3.3.6	 Configuring a Standalone AG 2000 Board





For a standalone AG 2000 board, H.100 connectivity should be disabled in the AG configuration file (EnableMVIP=NO). 



Automatic default connections are made on AG 2000 boards to connect the voice and signaling information to DSP resources. This provides the trunk channels with the necessary processing resources. However, you cannot reroute the channels to other boards or other external resources.



See Section 5.4, Default Connections, for the default connections made when setting EnableMVIP=NO.






3.3.7	 Enabling Telephony Bus Switching





When you set EnableMVIP=YES, telephony bus switching is enabled. No switch connections are made automatically. To control switching, use the CT Access Switching service. Refer to the Switching Service Developer's Reference Manual for more information.



The AG 2000 board defaults to MVIP-90 compatibility mode. This configures:




To change the clock speed of the bus, use the Switching service. Stream speeds are set in groups of four (i.e., streams 0..3, 4..7, 8..11, etc.).






3.3.8	 Telephony Bus Clocking





In a system, one board drives the bus clock signals. The board that drives the bus clocks is called the bus clock master. All the timing signals are passed across the bus from the clock master. The clock master derives its clock from the telephone network or an on-board oscillator. In a system connected to digital network trunks, the bus clock master should take its clock source from a digital trunk.



All other boards (clock slaves) reference their clocks from the bus. Refer to Getting Started With MVIP Switching for more information on telephony bus clocking.



Some telephony board models can act as the clock master, while others cannot. (To determine the capabilities of other boards, see the documentation for each specific board.) An AG 2000 board can act as either a clock master or as a clock slave. 



In a system with both H.100 boards and MVIP-90 boards, it is recommended that one of the H.100 boards be configured as the clock master.


Note:  In order to use the clock fallback features in an MC1 system, the MC1 board must be configured as the MVIP bus clock master. In an MC1 system, AG 2000 boards are configured as clock slaves to the MVIP-90 bus (ClockRef=MVIP). In this configuration, some H.100 bus streams are configured in MVIP-90 compatibility mode (clocked at 2 MHz) and are limited to 32 timeslots. Refer to the MC1 board documentation for more information.


The system clocking is configured by the keyword ClockRef in the AG configuration file.



If telephony bus switching is enabled (EnableMVIP=YES), set the ClockRef statement for each board to indicate whether the board will be the telephony bus clock master or a clock slave and to specify the clock source.



The ClockRef options are: 





 Value



 Description




 MVIP



 Causes the board to act as a clock slave to the MVIP-90 bus by deriving the local clock from the bus. Another board must drive the clock on the MVIP-90 bus.


 Note: Should typically not be used on an H.100 board except in a mixed H.100 and MVIP-90 system where an MC1 board is the bus clock master.




 H100



 Causes the board to act as a clock slave to the H.100 bus by deriving the local clock from the bus. Another H.100 board must drive the clock on the H.100 bus. 




 OSC



 Causes the board to drive the bus clock using the on-board oscillator.
Setting ClockRef to OSC for a board makes that board the clock master.


 If the clock master is an H.100 board, it will drive both the H.100 bus clocks and the MVIP-90 bus clocks. This setting is only used when there are no digital connections to the telephone network. (The on-board oscillator is accurate to 50 ppm (parts per million) and does not meet the requirements for a Stratum 4 clock.)


 ClockRef should be set to MVIP or H100 for all other boards on the bus.




 SEC8K



 Causes the AG 2000 board to derive the local clock from the CT_NETREF clock on the H.100 bus. Setting ClockRef to SEC8K for a board makes the board the clock master. ClockRef should be set to MVIP or H100 for all other boards on the bus.


 Some earlier models of the AG 2000 board cannot derive its clock from SEC8K. Contact NMS Developer Support for more information.


















When a system is configured with a mix of MVIP-90 and H.100 boards, it is recommended that one of the H.100 boards be configured as the bus master. If the system contains digital trunk interfaces (T1 or E1), generally, one of the digital trunks is chosen as the clock reference for the system. If the digital trunk interface cards are MVIP-90 cards, the following configuration is recommended: The digital card should generate SEC8K. The AG 2000 should derive its timing from SEC8K and be bus master. The digital card slaves to the AG 2000 board.


Note:  For the earlier versions of the AG 2000 board which can not derive its timing from SEC8K, they must be configured to slave from the MVIP bus (ClockRef = MVIP).





3.3.9	 Enabling Echo Cancellation





Echo cancellation improves the input signal-to-noise ratio during play which improves the performance of operations such as tone detection and speech recognition.



To enable echo cancellation:


    


  1. Include the following statement in the AG configuration file:
    

    
AG2DSPFILE = echo.m54
    

  2. Restart agmon to re-initialize the AG board with echo cancellation.
    

    

  3. Set the appropriate ADI service parameters in your application and in your system.
    

    
To enable echo cancellation with the board's default settings, set the parameter ADI_START_PARMS.echocancel.mode equal to 1. 



Refer to the ADI Service Developer's Manual for more information on configuring echo cancellation on the AG 2000 board.






3.3.10	 QSLAC Files





The QSLACs (Quad Subscriber Line Audio - Processing Circuit) on an AG 2000 board control:




There are two QSLACs on an AG 2000 board. The first QSLAC services ports
0 - 3. The second QSLAC services ports 4 - 7. Each port can be configured separately; the configuration is contained in a QSLAC file. Each QSLAC file is customized for a specific line interface signaling module and for a certain country's 2 wire return loss requirements.



For information on QSLAC files and AG 2000 E&M boards, refer to Chapter 7.



Through the CT Access Switching service, you can control (per port):




Refer to Chapter 6 for more information on controlling the gain.


 Naming Conventions for QSLAC Files



All QSLAC files have an extension of .slc. All QSLAC files adhere to the following naming convention:



pp cty ss i.slc 





 Where...



 Represents the...




 pp



 Two-position NMS product field:


 a2 = AG 2000 board


 q3 = QX 2000/80-4L


 q4 = QX 2000/100-4L


 w8 = WTI-8 board




 cty



 Three-position ISO country code or region code.




 ss



 Two-position signaling type:


 ls = loop start


 dd = DID


 sl = subscriber loop




 i



 One position line impedance field:


 6 = 600 ohm


 9 = 900 ohm


 n = for lines longer than 2000 feet


 c = complex (used in some international markets)
















For example, a2usals6.slc represents the AG 2000 board/USA/loop start/
600 ohm line QSLAC file.



The Natural Access installation program configures the system for the QSLAC file that is intended for your country. Do not change the configuration unless you are confident that a change is required and is allowed by the regulatory agencies.



For more information about QSLAC files, refer to the AG CAS for Natural Call Control Installation and Developer's Manual.



If the default file is not used, an entry will be made in the error log file at boot time. If echo cancellation is enabled, there is no benefit in changing from the default QSLAC file.


 Sample AG Configuration File for Loading QSLAC Files



The following code excerpt is a sample Boards section of an ag.cfg file that loads the QSLAC file. This example overrides the default from 600 Ohms to 900 Ohms.


Note:  The Natural Access installation or the AG CAS Protocol installation will install an aglps.cfg file that is correct for the country that you have selected if you have installed loop start TCPs.

#--------- BOARDS section ----------

 Board 0
  PCIBUS = 0     
  PCISLOT = 19
 

   ClockRef = OSC        # OSC for standalone operation
   EnableMvip = YES      # YES if there is an MVIP bus
   Qslac = a2usals9.slc

End Board

# -------------------------------



If there are multiple QSLAC statements in the configuration file that involve the same port, the last statement supersedes previous settings for that port. For example:


Board 0
  PCIBUS = 1
  PCISLOT = 5
  RunModule = gtp.leo
  RunModule = voice.leo
  RunModule = svc.leo

  Qslac = a2usals9.slc   # Override the default file for all ports
                         # with a2usals9.slc

  ClockRef = OSC        # Change to OSC for standalone operation
  EnableMvip = Yes      # Change to YES if there is an MVIP bus
 End Board
Board 1
  PCIBUS = 1
  PCISLOT = 6
  RunModule = gtp.leo
  RunModule = voice.leo
  RunModule = svc.leo

  Qslac 0..3 = a2usals6.slc   # Override the default file for ports
                              # 0, 1, 2 ,3 with a2usals6.slc

  Qslac 4..5 = a2usalsn.slc   # Override the default file for ports
                              # 4 and 5 with a2usalsn.slc

                              # Ports 6 and 7 receive default file
                              # a2usals6.slc

  ClockRef = MVIP        # Change to OSC for standalone operation
  EnableMvip = Yes       # Change to YES if there is an MVIP bus
 End Board


 Board 2
  PCIBUS = 1
  PCISLOT = 7
  RunModule = gtp.leo
  RunModule = voice.leo
  RunModule = svc.leo


  Qslac      = a2usals9.slc          # Override the default file for all
          # ports with a2usals9.slc

  Qslac 2..4 = a2usals6.slc          # Override the last setting 
          # (a2usals9.slc) for ports 2, 3, 4,
          # with a2usals6.slc

  Qslac 7    = a2usalsn.slc          # Override the last setting
          # (a2uasls9.slc)for port 7 with
          # a2usalsn.slc

  ClockRef = MVIP        # Change to OSC for standalone operation
  EnableMvip = Yes       # Change to YES if there is an MVIP bus
 End Board





3.3.11	 Trunk Control Programs





Trunk control programs (TCPs) perform all the signaling tasks necessary to interface with the telephony protocol used on the line or trunk. TCPs are loaded onto an AG 2000 board at board initialization. After a TCP has been loaded to the AG 2000 board, the application must start up its protocol before it can use the TCP to perform call control on a specific port.






3.3.12	 QSLAC Files and TCPs for Loop Start





The following table lists the QSLAC files for loop start which may be selected for the United States and Canada: 





 File



 Description




 a2usals6.slc



 This is the default file that is used when you have a 600 ohm PBX.




 a2usals9.slc



 Optimizes performance interfacing to a 900 ohm PBX.




 a2usalsn.slc



 Optimizes performance interfacing to long lines (> 2000 feet).


















Other QSLAC files are used in other parts of the world. Either the Natural Access installation or the AG CAS protocol installation will configure the correct files for the countries that are supported.



For European countries that are not supported, use the a2eurlsc.slc file. Refer to the AG CAS for Natural Call Control Installation and Developer's Manual for information on changing network tone descriptions.



The following table lists the TCPs that are applicable to the AG 2000 loop start boards: 





 Trunk Control Program



 Description




 nocc.tcp



 No call control.




 lps0.tcp



 Loop start on AG 2000.



















3.3.13	 QSLAC Files and TCPs for Subscriber Loop





The following table lists the QSLAC files for subscriber loop which may be selected for the United States: 





 File



 Description




 a2usasl6.slc



 This is the default file that is used when you have a 600 ohm telephone.




 a2usasl9.slc



 Optimizes performance interfacing to a 900 ohm device.

















The following table lists the TCPs that are applicable to the AG 2000 subscriber loop boards: 





 Trunk Control Program



 Description




 sta0.tcp



 Subscriber loop on AG 2000.




 nocc.tcp



 No call control.



















3.3.14	 QSLAC Files and TCPs for DID





The following table lists the QSLAC files for DID which may be selected for the United States: 





 File



 Description




 a2usadd6.slc



 This is the default file that is used when you have a 600 ohm trunk.




 a2usadd9.slc



 Optimizes performance interfacing to a 900 ohm trunk.

















The following table lists the TCPs that are applicable to the AG 2000 DID boards: 





 Trunk Control Program



 Description




 wnk1.tcp



 Inbound wink start protocol. (You may also use wnk0.tcp.)




 nocc.tcp



 No call control.



















3.4	 Running agmon





When your AG configuration file is complete, invoke agmon to initialize and configure your boards as described in the file. agmon interprets your AG configuration file and loads the appropriate files to the AG boards. If the initialization is successful, agmon monitors for errors until you terminate it. (For more information about agmon, refer to the AG Runtime Configuration and Developer's Manual.)


Note:  In UNIX, agmon must be left running at all times. In Windows NT, you can use the F3 key to stop monitoring, but leave the AG boards running. However, agmon should be left running at all times so that errors are captured if they occur.


agmon creates two files, ag.rpt and agerror.log. These files can be found in the agmon startup directory in Windows NT, and in /var/opt/nms/ag in UNIX. 





 File



 Description




 ag.rpt



 Contains a summary of the board configuration, including which files were loaded, and any errors that occurred in loading.




 agerror.log



 An error log file. Any errors displayed in the agmon session are appended to the file. The file remains open for one second after an error is written.



















3.5	 Sample AG Configuration Files





The following sections are listings of sample ag.cfg files for different system configurations using AG 2000 boards. Sample AG configuration files for AG 2000 E&M boards are in Chapter 7.






3.5.1	 AG 2000 With LS Without H.100 Connectivity





The following sample AG configuration file describes one AG 2000 LS board using a loop start protocol, without H.100 connectivity:


[AGBOARD]

#---------- COMMON section --------

  TCP = nocc.tcp       # no call control protocol
  TCP = lps0.tcp       # loop start protocol

  AG2DspFile = tone.m54       # Beep, tone generation, dial
  AG2DspFile = callp.m54       # Call Progress detection
  AG2DspFile = signal.m54       # Out-of-band channel associated
          signaling
  AG2DspFile = dtmf.m54       # DTMF and silence/energy detectors
  AG2DspFile = voice.m54       # NMS ADPCM play and record
  AG2DspFile = ptf.m54       # Cleardown and precise tone detection

  RunFile = AG2000.cor
  RunModule = gtp.leo
  RunModule = svc.leo
  RunModule = voice.leo

  ClockRef   = OSC
  EnableMvip = No
  IdleCode   = mu-LAW

#--------- BOARDS section ----------

 Board 0
  PCIBUS = 0
  PCISLOT = 19
 End Board





3.5.2	 Two AG 2000 LS With H.100 Connectivity





The following is a sample configuration file for two AG 2000 LS boards with H.100 connectivity. One AG 2000 board is the clock master that drives the MVIP clock. No H.100 connections are made by agmon because EnableMvip is set to YES. All line-interface-to-DSP-resource connections must be made by the application(s).


[AGBOARD]
#------------ COMMON section ---------

  AG2DspFile = voice.m54
  AG2DspFile = signal.m54
  AG2DspFile = dtmf.m54
  AG2DspFile = callp.m54
  AG2DspFile = tone.m54
  AG2DspFile = ptf.m54

  TCP = lps0.tcp

  RunFile = AG2000.cor
  RunModule = gtp.leo
  RunModule = svc.leo
  RunModule = voice.leo

  IdleCode = MU-LAW
  EnableMvip = YES

#--------- BOARDS section ---------
Board 0
  PCIBUS = 0
  PCISLOT = 19
  ClockRef = OSC
End Board

Board 1
  PCIBUS = 0
  PCISLOT = 20
  ClockRef = H100
End Board





3.5.3	 AG 2000 DID Without H.100 Connectivity





The following sample AG configuration file describes one AG 2000 DID board using a DID protocol, without H.100 connectivity:


[AGBOARD]

#---------- COMMON section --------

  TCP = nocc.tcp       # no call control protocol
  TCP = wnk1.tcp       # inbound wink start protocol

  AG2DspFile = tone.m54       # Beep, tone generation, dial
  AG2DspFile = callp.m54       # Call Progress detection
  AG2DspFile = signal.m54       # Out-of-band channel associated
          signaling
  AG2DspFile = dtmf.m54       # DTMF and silence/energy detectors
  AG2DspFile = voice.m54       # NMS ADPCM play and record
  AG2DspFile = ptf.m54       # Cleardown and precise tone detection

  RunFile = AG2000.cor
  RunModule = gtp.leo
  RunModule = svc.leo
  RunModule = voice.leo

  ClockRef   = OSC
  EnableMvip = No
  IdleCode   = mu-LAW

#--------- BOARDS section ----------

 Board 0
  PCIBUS = 0
  PCISLOT = 19
 End Board





Note:  You may also use wnk0.tcp.








3.5.4	 AG 2000 Subscriber Loop Without H.100 Connectivity





The following sample AG configuration file describes one AG 2000 subscriber loop board using a subscriber loop protocol, without H.100 connectivity:


[AGBOARD]

#---------- COMMON section --------

  TCP = nocc.tcp       # no call control protocol
  TCP = sta0.tcp       # subscriber loop protocol

  AG2DspFile = tone.m54       # Beep, tone generation, dial
  AG2DspFile = callp.m54       # Call Progress detection
  AG2DspFile = signal.m54       # Out-of-band channel associated
          signaling
  AG2DspFile = dtmf.m54       # DTMF and silence/energy detectors
  AG2DspFile = voice.m54       # NMS ADPCM play and record
  AG2DspFile = ptf.m54       # Cleardown and precise tone detection

  RunFile = AG2000.cor
  RunModule = gtp.leo
  RunModule = svc.leo
  RunModule = voice.leo

  ClockRef   = OSC
  EnableMvip = No
  IdleCode   = mu-LAW

#--------- BOARDS section ----------

 Board 0
  PCIBUS = 0
  PCISLOT = 19
 End Board














 
    (Page 1 of 1 in this chapter)  Version




 




tech_support@nmss.com



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