Option	Description
`-H`	Print valid command line options.
`-p` protocol	Specifies the protocol to run. Default = `nocc`.
`-l` ipaddress	Local IP address.
`-d` ipaddress	Destination IP address.
`-t` #	TX board number (starts with board 1).
`-r` ipaddress	Router IP address.
`-v` filename	AG TRAU program (vocoder) file name.
`-e` type	Encoding type.

Option	Description
`-H`	Print valid command line options.
`-p` protocol	Specifies the protocol to run. Default = `nocc`.
`-l` ipaddress	Local IP address.
`-d` ipaddress	Destination IP address.
`-t` #	TX board number (starts with board 1).
`-r` ipaddress	Router IP address.
`-v` filename	AG TRAU program (vocoder) file name.
`-e` type	Encoding type.

Option	Description
`-H`	Print valid command line options.
`-p` isd0	Specifies the protocol to run. Default = `nocc`.
`-l` ipaddress	Local IP address.
`-d` ipaddress	Destination IP address.
`-t` #	TX board number (starts with board 1).
`-r` ipaddress	Router IP address.
`-v` filename	AG TRAU program (vocoder) file name.
`-e` type	Encoding type.

(Page 1 of 1 in this chapter)

Chapter 6

Demonstration Programs

6.1 TRAU Exerciser Demonstration Program

6.2 Fusion Demonstration Programs

: 6.2.1 Fusion AG-8 Demonstration
: 6.2.2 Fusion AG-T1/E1 Demonstration
: 6.2.3 Fusion AG-T1/E1 ISDN Demonstration

6.3 The Sample Gateway Program

: 6.3.1 Gateway Program
: 6.3.2 Port Count
: 6.3.3 Using the Sample Gateway Program with Net

6.4 Sample Gateway Program Session Control

: 6.4.1 PSTN Half Call Control in the Sample Gateway
: 6.4.2 IP Half Call Control in the Sample Gateway

6.1 TRAU Exerciser Demonstration Program

The TRAU Exerciser (trauxsr) demonstrates the ability of AG-RT task processors to perform processing operations on AG-RT daughterboards.
To run the trauxsr program, follow the steps below: Edit one of the provided agmon configuration files to match your system's hardware configuration (indicate system-specific board addresses and interrupts). Sample files (fusionag8.cfg, fusione1.cfg, and fusiont1.cfg) are provided in the directory nms\ag\cfg. Compile the file trauxsr.c with a C/C++ compiler such as nmake. Run agmon with the customized ag.cfg. Run trauxsr.exe.
For additional information about the TRAU Exerciser program, refer to the Fusion AG TRAU Developer's Reference Manual. For more information about running agmon, refer to the AG Runtime Configuration and Developer's Manual.

6.2 Fusion Demonstration Programs

Fusion includes a variety of demonstration programs for different system configurations. To test a Fusion gateway, run a demonstration program on two separate Fusion host systems located at different points on a packet network.
Available Fusion demonstration programs include:

Command File

Location

demo.cmd

nms\fusion\samples\ag8

demo.cmd

nms\fusion\samples\agt1

demoisdn.cmd

nms\fusion\samples\agt1
To run a Fusion demonstration program, run the demonstration command file appropriate for the host system configuration. Each program performs the following: Initializes and loads the AG boards with agmon (the demoisdn.cmd program also initializes AG ISDN). Initializes the TX board. Responds to calls received by the AG line interface board(s). Routes calls over the packet network. Note: The default configuration assumes you are linking to a TX board with QUICC32 (all TX 3000 boards come with QUICC32). If you are not using a TX board with QUICC32, modify the make file to compile and link with a non-QUICC32 TX board.

Command File	Location
`demo.cmd`	`nms\fusion\samples\ag8`
`demo.cmd`	`nms\fusion\samples\agt1`
demoisdn.cmd	`nms\fusion\samples\agt1`

6.2.1 Fusion AG-8 Demonstration Program

Procedure

To run demo: 1. From the command line prompt, navigate to the following directory: nms\fusion\samples\ag8. 2. Option Description -H Print valid command line options. -p protocol Specifies the protocol to run. Default = nocc. -l ipaddress Local IP address. -d ipaddress Destination IP address. -t # TX board number (starts with board 1). -r ipaddress Router IP address. -v filename AG TRAU program (vocoder) file name. -e type Encoding type. Modify any of the following in the demo.cmd file: 3. Enter the following at the command line: demo 4. Press the ESC key to exit the program.

Notes

All incoming calls are routed to the destination IP address through the TX board. Up to three AG-8s are supported. AG-8 lines 0..7 on board 1 map to virtual ports 1..8 on the TX board. AG-8 lines 0..7 on board 2 map to virtual ports 9..16 on the TX board. AG-8 lines 0..7 on board 3 map to virtual ports 17..24 on the TX board.
For more information about AG TRAU types and program file names, refer to the Fusion AG TRAU Developer's Reference Manual. For specific Fusion gateway hardware and software requirements, refer to the Fusion Installation Manual.

6.2.2 Fusion AG-T1/E1 Demonstration Program

Name

demo

Purpose

Processes and encodes incoming PCM calls, and send network-ready GSM, G.723.1 or G.711 streams to the TX board.

Usage

demo

Description

Receives, switches, performs onboard echo cancellation, and encodes up to 24 channels of PCM data and on host systems that use an AG-T1 line interface board.
Before running the demonstration program, complete the following tasks: 1. Make sure your TX board is installed and configured as a network interface card (see Fusion Installation Manual). Record the TX board's IP address and Default Router address. 2. Update the demo.cmd file with the TX Board's IP address and Default Router address, and the IP address of the destination machine. 3. Verify the AG board addresses in the agisdnti.cfg or agisdnei.cfg file (depending on your board configuration). You may need to change these addresses to reflect the settings on your AG-T1 board address switches. 4. Compile the demonstration program: Change directory to \nms\fusion\samples\ag-T1E1\src. Enter nmake /a. (you may use another C\C++ compiler)

Procedure

To run demo.cmd: 1. From the command line prompt, navigate to the following directory: nms\fusion\samples\ag-E1T1. 2. Option Description -H Print valid command line options. -p protocol Specifies the protocol to run. Default = nocc. -l ipaddress Local IP address. -d ipaddress Destination IP address. -t # TX board number (starts with board 1). -r ipaddress Router IP address. -v filename AG TRAU program (vocoder) file name. -e type Encoding type. Modify any of the following in the demo.cmd file: 3. Enter the following at the command line: demo. 4. Press the ESC key to exit the program.

Notes

All incoming calls from the T1 are routed to the destination IP address on the TX board.
For more information about AG TRAU types and program file names, refer to the Fusion AG TRAU Developer's Reference Manual. For specific Fusion gateway hardware and software requirements, refer to the Fusion Installation Manual.

6.2.3 Fusion AG-T1/E1 ISDN Demonstration Program

Name

demoisdn

Purpose

Processes and encodes incoming PCM calls, and uses ISDN to send network-ready GSM, G.723.1 or G.711 streams to the TX board.

Usage

demoisdn

Description

Automatically runs the AG ISDN demonstration program isdncta. Receives, switches, performs onboard echo cancellation, and encodes up to 24 channels of PCM data and on systems that use an AG-T1 line interface board. Note: For more information about the AG ISDN demonstration program isdncta, refer to the AG ISDN for Natural Call Control Manual.
Before running the demonstration program, complete the following tasks: 1. Make sure your TX board is installed and configured as a network interface card (refer to the Fusion Installation Manual). Record the TX board's IP address and Default Router address. 2. Update the demoisdn.cmd file with the TX Board's IP address and Default Router address, and the IP address of the destination machine. 3. Verify the AG board addresses in the agti.cfg or agei.cfg file (depending on your board configuration). You may need to change these addresses to reflect the settings on your AG-T1 board address switches. 4. Compile the AG ISDN demonstration program isdncta. Change directory to \nms\ctaccess\demos\isdncta. Enter nmake /a. (you may use another C\C++ compiler) 5. Compile the demonstration program: Change directory to \nms\fusion\samples\T1E1\src. Enter nmake /a. (you may use another C\C++ compiler)

Procedure

To run demoisdn: 1. From the command line prompt, navigate to the following directory: nms\fusion\samples\ag-E1T1. 2. Option Description -H Print valid command line options. -p isd0 Specifies the protocol to run. Default = nocc. -l ipaddress Local IP address. -d ipaddress Destination IP address. -t # TX board number (starts with board 1). -r ipaddress Router IP address. -v filename AG TRAU program (vocoder) file name. -e type Encoding type. Modify any of the following in the demoisdn.cmd file: 3. Enter the following at the command line: demo 4. Press the ESC key to exit the program.

Notes

All incoming calls from the T1 are routed to the destination IP address on the TX board.
For more information about AG TRAU types and program file names, refer to the Fusion AG TRAU Developer's Reference Manual. For specific Fusion gateway hardware and software requirements, refer to the Fusion Installation Manual.

6.3 The Sample Gateway Program

The NMS Sample Gateway program runs on a host system that uses the AG-T1 board with an AG-RT daughterboard and a TX network interface board.
The top level project for the Sample Gateway Program is named gwsampleapp.dsp and is found in nms\fusion\samples\gwsample\gwsampleapp. This project opens the GwSampleApp project as well as all of the projects (DLLs) associated with it. The Sample Gateway program is made up of six sub-projects: Project Function GwSampleApp Provides the user interface for the application. SessCtrl Coordinates call setup between the other DLL/modules in the system. LanCS Manages IP call control (by default, it uses the Fusion H.323 stack). RtpMgr Manages the TX board and its resources. AdTran Manages the address translation database and provides an addresse lookup service to SessCtrl. AgMgr Manages PSTN call control as well as AG Board resources. Figure 23. Sample Gateway Program Components
The entire project can be built at a command prompt by executing the MakeAll.bat file located in the nms\fusion\samples\gwsample directory. This batch file builds the debug release of the application. To execute Sample Gateway program, run the demo.cmd file located in nms\fusion\samples\gwsample. Note: This application requires the Fusion H.323 Protocol Stack, and the G.723 vocoder. It also requires that the TX board is configured as a Network Adapter. This is accomplished by invoking the Network icon located in the Windows NT Control Panel. For specific instructions on how to set the TX board as a network interface card, refer to the Fusion Installation Manual.

Project	Function
GwSampleApp	Provides the user interface for the application.
SessCtrl	Coordinates call setup between the other DLL/modules in the system.
LanCS	Manages IP call control (by default, it uses the Fusion H.323 stack).
RtpMgr	Manages the TX board and its resources.
AdTran	Manages the address translation database and provides an addresse lookup service to SessCtrl.
AgMgr	Manages PSTN call control as well as AG Board resources.

6.3.1 Gateway Program Configuration

The nms\fusion\gwsample\bin directory contains text files that configure the GwSampleApp application. When you build this project, these files are copied from the Config directory to both gwsample\gwsampleapp and gwsample\gwsampleapp\debug. The Sample Gateway program includes the following configuration files.

Configuration File

Description

config.val

The Fusion H323 call stack configuration file. This file specifies the capability set and channel characteristics for the H.323 sessions. The format for this file can be found in the H.323 Programmer's Guide and Reference.

adtranDB.cfg

The address translation database. This file is used to associate the packet network endpoints with telephone numbers on the local exchange. For inbound PSTN calls, the called party number is looked up in the AdTranDB.cfg file and its associated IP address is used for the IP side of the call. The format for this file is found in the header of the adtrandb.cfg file.

gwsample.cfg

Configuration file containing the vocoder filename. This file is downloaded to the AG-RTdaughterboard during initialization. The vocoder filename can be changed through the GwSample User Interface by clicking on the Vocoder button. This action replaces the text string in gwsample.cfg. You must exit and restart the GwSampleApp program in order to load a new vocoder file.

Note: The Sample Gateway program also generates a log file of trace information regarding the program's activity. This file is named gwstrace.log and it is located in nms\fusion\gwsample\bin\config.
When executing the GwSampleApp from the demo.cmd script, the configuration files are referenced from nms\fusion\gwsample\gwsampleapp. When executing the GwSampleApp from within Microsoft Developer's Studio, the configuration files are referenced from nms\fusion\gwsample\gwsampleapp\debug. Changes to these configuration files should first be made in the nms\fusion\gwsample\bin directory, and then copied to nms\fusion\gwsample\gwsampleapp and nms\fusion\gwsample\gwsampleapp\debug directories.

Configuration File	Description
`config.val`	The Fusion H323 call stack configuration file. This file specifies the capability set and channel characteristics for the H.323 sessions. The format for this file can be found in the H.323 Programmer's Guide and Reference.
`adtranDB.cfg`	The address translation database. This file is used to associate the packet network endpoints with telephone numbers on the local exchange. For inbound PSTN calls, the called party number is looked up in the `AdTranDB.cfg` file and its associated IP address is used for the IP side of the call. The format for this file is found in the header of the `adtrandb.cfg` file.
`gwsample.cfg`	Configuration file containing the vocoder filename. This file is downloaded to the AG-RTdaughterboard during initialization. The vocoder filename can be changed through the GwSample User Interface by clicking on the Vocoder button. This action replaces the text string in `gwsample.cfg`. You must exit and restart the GwSampleApp program in order to load a new vocoder file.

6.3.2 Port Count Limits

Currently the maximum number of calls that can be opened on the Gateway is 10. This is a limitation of the sample application. The call count can be increased by modifying the XXX_MAX_CALLS #define entry in the main header file of each of the sub-projects.

6.3.3 Using the Sample Gateway Program with Net Meeting

This application has been tested with Microsoft Net Meeting version 2.1. If you are running Net Meeting on Windows/NT 4.0, install Service Pack 3 for proper audio performance on Net Meeting. Net Meeting-to-Gateway Calls
Net Meeting Microphone sensitivity and Speaker Volume settings can effect audio quality. If either the microphone or speaker slide bar is set too high, acoustic coupling between the speaker and microphone can result in an echo heard at the `other end' of the call. Double-Talk on Net Meeting-to-Gateway Calls
The vocoder Input Gain setting can be adjusted to a level that prevents a possibility of choppy audio heard (at the client side only). Tests have shown that this condition can occur during double-talk, when both talkers are talking at the same time. During double-talk, it appears that choppy audio is a result of Net Meeting's internal audio processing. By increasing the Vocoder Input Gain, higher amplitude audio is sent from the Gateway to Net Meeting. Tests have shown that this hotter audio helps to reduce this choppy audio condition during double-talk. Additionally, this effect can be reduced by lowering the Net Meeting microphone sensitivity (with the slide bar). The G723.1 vocoder default input gain (+6dB, 0x800) and output gain (-3dB, 0x2D4) values worked well in NMS lab environments. Other gain values may have to be set to accommodate your specific environment.
This choppy audio condition (during double-talk) does not occur with gateway-to-gateway connections.

6.4 Sample Gateway Program Session Control

As Figure 23 shows, the Session Control Module sets up connections and negotiates sessions between PSTN (WAN) and packet network (LAN) half-calls based on the states of the respective calls: Figure 24. Fusion Sample Gateway Program State Machine

6.4.1 PSTN Half Call Control in the Sample Gateway Program

Figure 25 shows the sequence for connecting calls from the PSTN side of the gateway:
Figure 25. Connecting Calls from the PSTN Side of the Gateway
Figure 26 shows the sequence for disconnecting calls from the PSTN side of the gateway: Figure 26. Disconnecting Calls from the PSTN Side of the Gateway

6.4.2 IP Half Call Control in the Sample Gateway Program

Figure 27 shows the sequence for connecting calls from the IP/packet network side of the gateway: Figure 27. Connecting Calls from the IP Side of the Gateway


Figure 28 shows the sequence for disconnecting calls from the IP/packet network side of the gateway: Figure 28. Disconnecting Calls from the IP Side of the Gateway

(Page 1 of 1 in this chapter)

tech_support@nmss.com