Table of Contents Index NMS Glossary Previous Page Next Page Version


Chapter 6

Demonstration Programs


6.1 Introduction
6.2 Preparing to Run the Demonstration Programs
6.2.1 Building the Demonstration Programs
6.2.2 Setting Up the Required Configuration Files
AG 4000 Board Keyword File
CX 2000 Board Keyword File
System Configuration File
PPX Configuration File
6.3 Booting the System
6.4 CX 2000 Call Center Demonstration Program: cdicc
6.5 PBX Demonstration Program: cdipbx

6.1 IntroductionTop of Page

This chapter presents the demonstration programs supplied with the CDI service:
Program

Description

cdicc

Demonstrates a call center application using the CDI service, with mixed board support in a single application.

cdipbx

Demonstrates a PBX application using the CDI service.

CT Access is shipped with source code for all demonstration programs. Each demonstration program is shipped as source and makefiles.

Before you start the demonstration programs, ensure that:

Refer to the specific product installation manual for more information on installing and starting each of these.

6.2 Preparing to Run the Demonstration ProgramsTop of Page

cdicc and cdipbx require the following setup:

This section describes how to set up and run the demonstration programs. The setup for running the demonstration programs is summarized in the following steps:

  1. Build the demonstration programs.

    
    
  2. Set up the board keyword and system configuration files.

    
    
  3. Boot the system.

    
    
  4. Run the demonstration programs.

6.2.1 Building the Demonstration ProgramsTop of Page

As a prerequisite for using the demonstration programs, build the ccclib component, then build the executables for the demonstration programs. To do this, go to a command prompt and issue the appropriate make command for your operating system (for example, nmake for Windows NT).
To Compile

Go to This Directory

ccclib

Windows NT: \nms\ctaccess\demos\ccclib

UNIX: /opt/nms/ctaccess/demos/ccclib

cdipbx

Windows NT: \nms\ctaccess\demos\cdipbx

UNIX: /opt/nms/ctaccess/demos/cdipbx

cdicc

Windows NT: \nms\ctaccess\demos\cdicc

UNIX: /opt/nms/ctaccess/demos/cdicc

Note: It is assumed that the NMS software was loaded in directory \nms (on UNIX, the path is /opt/nms).

6.2.2 Setting Up the Required Configuration FilesTop of Page

Make sure that you have the correct board keyword and system configuration files in the proper directories. Create board keyword files for the AG board and the CX 2000 or CX 2000C board. Also, create an oamsys.cfg system configuration file specifying these board keyword files, and then use oamsys to boot the boards. For more information about configuring your boards, refer to the CX 2000 and CX 2000C Installation and Developer's Manual, the AG 4000 Installation and Developer's Manual, and the OAM System User's Manual.

In additon, you need a configuration file for the Point-to-Point Switching (PPX) service to run the demonstration programs.

AG 4000 Board Keyword FileTop of Page

The AG 4000 keyword file resides in \nms\ag\cfg on Windows NT (/opt/nms/ag/cfg on UNIX), and is called agpi4000.cfg. The AG 4000 keyword file for this example follows:

#
#
#       AG Plugin-in Config File for AG 4000
#

 Clocking.HBus.ClockSource = OSC
 Clocking.HBus.ClockMode = MASTER_A

# TCP files are shipped with the AG-CAS sub-package of Natural Access.
# Be sure that you installed the protocols that are specified below before
# trying to start a board with this configuration file.
 TCPFiles[0] = nocc.tcp           # "no trunk control" protocol
 TCPFiles[1] = wnk0.tcp           # 2-way wink protocol

# DSP (.m54) files to link in

 DSP.C5x.DSPFiles = callp.m54 dtmf.m54 mf.m54 ptf.m54 tone.m54 voice.m54 signal.m54

 DLMFiles[0] = gtp.leo
 DLMFiles[1] = voice.leo
 DLMFiles[2] = svc.leo

#--------------------------------------------------------------------------
# Other default settings may be found in your AG 4000 Installation and 
# Developer's Manual.
#--------------------------------------------------------------------------

 XLaw = MU-LAW

CX 2000 Board Keyword FileTop of Page

The CX 2000 board keyword file resides \nms\cx\cfg on Windows NT (/opt/nms/cx/cfg on UNIX), and is called cx2000.cfg. The CX 2000 keyword file for this example follows:

  #
  #  Standalone operation
  #
#Clocking.HBus.ClockMode   = STANDALONE
#Clocking.HBus.ClockSource = OSC

  #
  #  Master the CT Bus (drive clock A)
  #
#Clocking.HBus.ClockMode   = MASTER_A
#Clocking.HBus.ClockSource = OSC

  #
  #  Slave to the CT Bus (slave from clock A)
  #
Clocking.HBus.ClockMode   = SLAVE
Clocking.HBus.ClockSource = A_CLOCK
SwitchConnection          = YES

System Configuration FileTop of Page

When your board keyword file(s) are complete, create a system configuration file describing the overall configuration of your system, and assigning a board keyword file to each board. oamsys creates records in the OAM database for your boards based on this file.

The system configuration file is typically named oamsys.cfg. By default, oamsys looks for a file with this name when it starts up.

The Bus and Slot values in the system configuration file are required to identify the PCI bus and slot for each board. Obtain these values using the pciscan utility, by entering the following at a command prompt:

pciscan

pciscan displays information on the boards that are configured in the system, including the Bus and Slot values.

Once you have used pciscan to obtain these values, you can verify them by causing pciscan to blink an LED on each board. For example, assume the utility indicated that there was a board at bus 2, slot 10 and another board at bus 2, slot 14. To determine which bus/slot combination contains the AG 4000 board, choose a bus/slot combination and use them as arguments (separated by a space) to the pciscan utility. For example:

pciscan 2 10

The utility flashes the the blue hot swap LED on the CX 2000C board (or the Board Locate LED on a CX 2000 board) in the given bus/slot combination. If the LED flashes on the AG 4000 board, then use this bus/slot information in your configuration file for Bus and Slot.

This is an example of a system configuration file (oamsys.cfg) for two boards (CX 2000C and AG 4000C) configured in a system:

#-------------------------------------------------------
# oamsys.cfg
# This is the default OAM system configuration file,
# used by the oamsys tool. It describes all the NMS 
# boards in a chassis.
#
# Each board is has its own section in this file.
# Each is delimited by a user-defined board name in 
# square brackets. All board names and numbers must 
# be unique.   
#
# You will need to modify the bus and slot numbers 
# for each board to match your chassis configuration.
# You may also need to add more board sections if you
# have more boards in your chassis.
#----------------------------------------------

    #-------------------------------------------------------------
    # Logical board number, physical bus, physical slot
    # 
    #------------------------------------------------------------

[Board0]
  Product = AG_4000C_T1
  Number = 0
# This assumes that pciscan located this board on pci bus 2, slot 10
# Make the appropriate changes for your configuration
  Bus = 2
  Slot = 10
  File = agpi4000.cfg

[Board1]
  Product = CX 2000C-48
  Number = 1
# This assumes that pciscan located this board on pci bus 2, slot 14
# Make the appropriate changes for your configuration
  Bus    = 2
  Slot   = 14
  File   = cx2000.cfg



PPX Configuration FileTop of Page

The Point-to-Point Switching (PPX) service requires its own configuration file, which it uses when it is started. This service must be started by the user. The PPX configuration file (ppx.cfg) must reside in \nms\ctaccess\cfg (/opt/nms/ctaccess/cfg under UNIX). The ppx.cfg file needed to support the demonstration program configuration follows:

#                       ppx.cfg
#
#          --- Point-to-Point Switching Service ---
#          ---        Configuration             ---
#
#   This file defines to the point-to-point switching service
#   the available bus, timeslots, and switches it may use for
#   establishing connection paths.
#   
#   This configuration file contains example switch definitions
#   for the various NMS boards. Use this as a guide for
#   configuring the PPX service to your particular hardware
#   configuration.
#
#   Some Reminders:
#       - All switch numbers must be unique.
#       - The "DeviceNumber" is the board number established 
#         during H/W configuration.
#       - The PPX service speaks MVIP-95, not MVIP-90.
#    
#
[PPX]
Fabric
        IdleCode = MU_LAW     # Default idle pattern [ MU_LAW | A_LAW ]
        
        Bus H100                        # H100 bus
            CTBUS:0..15:0..31
            CTBUS:16..23:0..63
            CTBUS:24..31:0..127
        End Bus

        Bus MVIP_90                     # MVIP-90 bus
            Bus H100 (CTBUS:0..15:0..31)
        End Bus

        Switch 0                       # AG4000
             SwitchType = HMIC
             DeviceName = "agsw"
             DeviceNumber = 0
             Bus H100 ()
             Inputs
                 LOCAL:0..14(2):0..23     # Trunk (or ..29 for Es)
                 LOCAL:16..18(2):0..127   # DSP
                 LOCAL:20..26(2):0         # HDLC
             End Inputs
             Outputs
                 LOCAL:1..15(2):0..23     # Trunk (or ..29 for Es)
                 LOCAL:17..19(2):0..127   # DSP
                LOCAL:21..27(2):0          # HDLC
             End Outputs
         End Switch

         Switch 1                        # CX2000
            SwitchType = HMIC
            DeviceName = "cxsw"
            DeviceNumber = 1
            Bus H100 ()               
            Inputs                  
                LOCAL:0..2(2):0..47      # 48 station interfaces
                LOCAL:4..6(2):0..47      # Limited DSP
            End Inputs
            Outputs                     
                LOCAL:1..3(2):0..47      # 48 station interfaces
                LOCAL:5..7(2):0..47      # Limited DSP
            End Outputs
        End Switch                           
End Fabric

6.3 Booting the SystemTop of Page

Once all the board keyword files have been edited and placed in the proper directories, boot the AG and CX boards using the following procedure:

  1. Start the Hot Swap Manager service (CompactPCI only). For more information, see the OAM System User's Manual.

    
    If this service was already started, proceed to step 2.
  2. Start the PPX Service (Point-to-Point Switching). For more information, see the Point-to-Point Switching Service Developer's Reference Manual.

    
    If this service is not listed, install the PPX service by entering the following at a command prompt:
    ppxservicecfg -install
  3. Configure and boot the AG and CX boards in the OAM database by entering the following at the prompt:

    
    oamsys
At this point, both boards should be booted and ready to execute the demonstration programs as outlined in the following sections.

6.4 CX 2000 Call Center Demonstration Program: cdiccTop of Page

Name

cdicc

Purpose

Demonstrates:

Usage

cdicc [options]

where options include:

Options

Description

-B [sw:]dev

T1 board [PPX switch number:] and board device number (oamsys.cfg board number). Default = 0:0.

-b [sw:]dev

CX 2000 or CX 2000C board [PPX switch number:] and board device number (oamsys.cfg board number). Default = 1:0.

-T n

T1 trunk/span number. Default = 1. The values are one-based.

-C n

T1 channel/slot number on trunk/span. Default = 0.
Value is zero-based.

-c n

CX 2000 or CX 2000C channel/slot number. Default = 0.
Value is zero-based.

-o n

0 = inbound call center demonstration.
1 = outbound call center demonstration (default).

-d n

Number to dial for outbound demo. Default = 5551212.

For example, enter -B0:0 -b1:1 -C0 -c0 -T1 -o1 -d2711100 for Outbound Demo. Enter -B0:0 -b1:1 -C0 -c0 -T1 -o0 for Inbound Demo.

Note: The demonstration uses the wnk0 protocol.

Featured Functions

cdiDisableBattery, cdiEnableBattery, cdiStartSignalDetector, cdiStartTimer, cdiStartTones, cdiStopSignalDetector, cdiStopTimer, cdiStopTones

Description

Performs the functions of a simple call center with two call center application modes: Inbound and Outbound. Depending on the -o command line flag, the demonstration program does the following:

The demonstration program performs all initial switching to voice and signaling DSPs, switching of caller and agent, and subsequent reconnection of DSPs using the Point-to-Point Switching Service (PPX).

Procedure

The following procedure assumes that you are using an AG 4000 board and a CX 2000 or CX 2000C board with a 2500-type telephone connected to one of the lines. cdicc can be run in conjunction with the cdipbx demonstration program to provide the function of the PSTN. Both demonstration programs can share one set of T1 and CX 2000 or CX 2000C boards.

The demonstration configuration is as follows:
chap6a.gif

Figure 4. cdicc Demonstration Program Configuration


To run cdicc:

  1. Configure the boards as described in Section 6.2.

    
    
  2. Boot the boards as described in Section 6.3.

    
    
  3. Connect a 24-port cable to the top 24-port connector on rear I/O connector of the CX 2000 or CX 2000C and to a 24-port telephone jack breakout box.

    
    
  4. Plug a telephone into Port 1 of the breakout box and another telephone into Port 11 of the breakout box.

    
    
  5. Place a T1 loopback cable into T1 and T2 of the AG board.

Inbound

  1. Navigate to the following directory:

    
    \nms\ctaccess\demos\cdicc  (Windows NT) 
    opt/nms/ctaccess/demos/cdicc (UNIX)
  2. Start cdicc by entering:

    
    cdicc -B0:0 -b1:1 -T2 -C0 -c10 -o0
    The application automatically detects the T1 board type and sets stream values accordingly. The call center agent phone, connected to Port 11 (-c10), does not have a dial tone.
  3. In another command prompt window, navigate to the following directory:

    
    \nms\ctaccess\demos\cdipbx  (Windows NT) 
    opt/nms/ctaccess/demos/cdipbx (UNIX)
  4. Start cdipbx by entering:

    
    cdipbx -B0:0 -b1:1 -T1 -C0 -c0 -N1 -n1 -x101 
    The customer phone, connected to Port 1 (-c0), has a dial tone.
  5. Take the customer handset attached to the cdipbx demonstration (station in port 1) off-hook and dial a 7-digit number to access the T1 of the cdicc demonstration.

    
    You hear a prompt welcoming you to the CX 2000 Call Center and you are prompted for a 4-digit account number.
  6. Key in any four digits on the phone's DTMF keypad.

    
    You then hear three additional prompts asking you to hold, to continue to hold, and providing a short description of the CX  2000 or CX 2000C board. 
    If the agent handset remains on-hook, these three prompts continue playing over and over as a set.
  7. Take the agent handset off-hook.

    
    When the customer hears a complete prompt set, the agent handset  hears a call indication tone and the customer will hear a ring-back tone.
    Immediately after the tones are played, the customer and the agent are connected and can begin to talk.
  8. Hang up each handset.

Outbound

  1. Navigate to the following directory:

    
    \nms\ctaccess\demos\cdicc  (Windows NT) 
    opt/nms/ctaccess/demos/cdicc (UNIX)
  2. Start cdicc by entering the following:

    
    cdicc -B0:0 -b1:1 -T2 -C0 -c10 -o1 -d2711101
    The application automatically detects the T1 board type and sets stream values accordingly. The call center agent phone, connected to Port 11 (-c10), does not have a dial tone.
  3. In another command prompt window, navigate to the following directory:

    
    \nms\ctaccess\demos\cdipbx  (Windows NT) 
    opt/nms/ctaccess/demos/cdipbx (UNIX)
  4. Start cdipbx by entering the following:

    
    cdipbx -B0:0 -b1:1 -T1 -C0 -c0 -N1 -n1 -x101 
    The customer phone, connected to Port 1 (-c0), has a dial tone.
  5. After starting both instances of the demonstration programs, pick up the agent's station attached to the CX 2000 or CX 2000C.

    
    The Predictive Dialer function in the demonstration program automatically dials the phone number indicated in the -d option on the specified T1 channel.
    The agent handset hears a call indication tone and the customer's phone rings.
    When the customer answers, the agent and the customer are connected and can begin to talk.
  6. Hang up each handset.

6.5 PBX Demonstration Program: cdipbxTop of Page

Name

cdipbx

Purpose

Demonstrates:

Usage

cdipbx [options]

where options are:
Options

Description

-B [sw:]dev

T1 board [PPX switch number:] and board device number (oamsys.cfg board number). Default = 0:0.

-b [sw:]dev

CX 2000 or CX 2000C board [PPX switch number:] and board device number (oamsys.cfg board number). Default = 1:0.

-T n

T1 trunk/span number. Default = 1. The values are one-based.

-C n

T1 channel/slot number on trunk/span. Default = 0.
Value is zero-based.

-c n

CX 2000 or CX 2000C channel/slot number. Default = 0.
Value is zero-based.

-N n

Number of T1 channels. Default = 1.

-n n

Number of phone channels (CX 2000 or CX 2000C ports).
Default = 1.

-x n

Base extension number (3 or 4 digits). Default = 100.

For example, cdipbx -B0:0 -b1:1 -T1 -C0 -c0 -N1 -n5 -x101

Featured Functions

cdiDisableBattery, cdiEnableBattery, cdiStartSignalDetector, cdiStartTimer, cdiStartTones, cdiStopSignalDetector, cdiStopTimer, cdiStopTones

Description

This demonstration program simulates the functions of a PBX. It can be used in standalone mode with a single CX 2000 or CX 2000C or in conjunction with the Call Center demonstration. In the CX 2000-only mode, calls can be made to local phone extensions only. The local phone extensions are governed by the -x option.

When used with the Call Center demonstration, the PBX demonstration provides local and off-premises calls.

Procedure

CX 2000-only Mode

The CX 2000-only Mode uses only the CX 2000 or CX 2000C board.

To run cdipbx:

  1. Configure the boards as described in Section 6.2.

    
    
  2. Boot the boards as described in Section 6.3.

    
    
  3. Connect a 24-port cable to the top 24-port connector on rear I/O connector of the CX 2000 or CX 2000C and to a 24-port telephone jack breakout box.

    
    
  4. Plug a telephone into Port 1 of the breakout box and another telephone into Port 5 of the breakout box.

    
    Note:  The configuration specified for the cdipbx is different from that used in the cdicc demonstration.
    
    
  5. Navigate to the following directory:

    
    \nms\ctaccess\demos\cdipbx  (Windows NT) 
    opt/nms/ctaccess/demos/cdipbx (UNIX)
  6. At a command prompt, enter the following:

    
    cdipbx -b1:1 -c0 -n5 -x101
    This sets up the PBX demonstration program to use the first 5 ports of the CX 2000 or CX 2000C. The -c0 option causes the demo to start with CX2000 port 0. The -n5 option causes the demo to use 5 consecutive ports. The first port's extension number is 101 (-x101). This instance of the PBX demonstration supports extensions 101 through 105. If you plug phones into ports 1 through 5 of the breakout box, you can dial any of the extensions in the range 101 through 105.
  7. Pick up the handset attached to Port 1 of the breakout box and dial the three digit extension 105.

    
    
  8. The phone plugged into Port 5 of the breakout box begins to ring. When it does, pick up the handset and begin to converse.

    
    
  9. Hang up each handset.

Running cdipbx with cdicc

The PBX demonstration can be run in conjunction with the Call Center demonstration. Expanding on the Standalone Mode example, you can run the demonstration to place calls both local and off-premises.

Note: The command line setup for the PBX demonstration is similar to the outbound mode of the Call Center demonstration.

To run cdipbx:

  1. Configure the boards as described in Section 6.2.

    
    
  2. Boot the boards as described in Section 6.3.

    
    
  3. Connect a 24-port cable to the top 24-port connector on rear I/O connector of the CX 2000 or CX 2000C and to a 24-port telephone jack breakout box.

    
    
  4. Plug a telephone into Port 1 of the breakout box and another telephone into Port 11 of the breakout box.

    
    
  5. Place a T1 loopback cable into T1 and T2 of the AG board.

    
    
  6. Navigate to the following directory:

    
    \nms\ctaccess\demos\cdipbx  (Windows NT) 
    opt/nms/ctaccess/demos/cdipbx (UNIX)
  7. At a command prompt, enter the following:

    
    cdipbx -B0:0 -b1:1 -T1 -C0 -c0 -N1 -n5 -x101
    This sets up the PBX demonstration to use the first 5 ports of the CX 2000 or CX 2000C as well as enabling Trunk 1 (-B0:0 -T1). The -c0 option causes the demo to start with CX2000 port 0. The -n5 option causes the demo to use 5 consecutive ports. The first port's extension number is 101 (-x101). This instance of the PBX demonstration supports extensions 101 through 105. If you plug phones into ports 1 through 5 of the breakout box, you can dial any of the extensions in the range 101 through 105.
    The -N1 option indicates you are using only 1 of the T1 channels.
  8. Start the Call Center demonstration in another command prompt window in either Inbound or Outbound mode and follow the steps in Section 6.4.



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 © 2000, Natural MicroSystems, Inc. All rights reserved.