2.1 Introduction

2.2 Modifying the CT Access Configuration File

2.2.1 Sample CT Access Configuration File

2.3 Configuring NaturalConference

2.4 Modifying the Board Configuration File

2.4.1 Sample Board Configuration Files

2.4.2 Sample Board Configuration Files for AG 2000/400

OAM Configuration File

agmon Configuration File

2.4.3 Sample Board Configuration Files for AG 4000/1600

OAM Configuration File

agmon Configuration File

2.5 Setting Up the NaturalConference Configuration File

2.5.1 Customizing a cnf.cfg For Your System

2.5.2 NaturalConference Configuration File Structure

2.5.3 NaturalConference Configuration File Statements

Using Flags

2.5.4 Sample NaturalConference Configuration File for AG2000/400

2.5.5 Sample NaturalConference Configuration File for AG4000/1600

2.6 Verifying NaturalConference

2.6.1 Verifying the NaturalConference Installation

2.6.2 Verifying the NaturalConference Configuration

2.6.3 Receiving Calls and Adding Callers to a Conference

2.1 Introduction

Before you develop applications using NaturalConference, you must configure NaturalConference for your system. Follow these steps:

1. Ensure that the the CT Access configuration file includes NaturalConference components, as described in Section 2.2, Modifying the CT Access Configuration File.

2. Modify the board configuration file to include NaturalConference components, as described in Section 2.4, Modifying the Board Configuration File.

3. Create the NaturalConference configuration file, as described in Section 2.5, Setting Up the NaturalConference Configuration File.

2.2 Modifying the CT Access Configuration File

The ctdaemon uses the CT Access configuration file (cta.cfg). If you use ctdaemon as part of your application environment, define all CT Access services that the application uses by specifying the service and service manager names in the CT Access configuration file. You must also modify the cta.cfg if the application will use tracing for any of its CT Access services, including the NaturalConference (CNF) service.

You can develop and run a NaturalConference application without using CT Access Server (ctdaemon). If you do not use CT Access Server (ctdaemon), make sure that the application's CT Access services and service managers are explicitly defined in your application code.

For more information about ctdaemon and the CT Access development environment, see the CT Access Developer's Reference Manual.

Note: To use OAM, the CT Access Server (ctdaemon) must be running.

A NaturalConference application typically uses the following services:

This service...	With this service manager...	Provides the...
CNF	CNFMGR	NaturalConference API
NCC	ADIMGR for AG boards	CT Access call control API
ADI	ADIMGR for AG boards	Older CT Access call control API
SWI	SWIMGR	Switching API
OAM	OAMMGR	Functions for configuring, monitoring, and testing boards. For versions of CT Access 4.0 and later.

Note: The Natural Call Control (NCC) service API is the new standard call control API for NMS products. The NCC service provides an extended and enhanced version of the call control portion of the ADI service API. If your application currently uses the ADI service for call control, consider migrating to the NCC service for better performance, new features, and more control over your application's call control functionality.

The default cta.cfg file includes the NCC and ADI services (see the sample cta.cfg in Section 2.2.1). If the CNF service is not listed in the cta.cfg, edit the file as follows:

1. Stop ctdaemon and any other programs running CT Access.

2. Add the following line for the CNF service:
   Service = cnf, cnfmgr

3. Save and close the cta.cfg.

4. Restart ctdaemon.

The cta.cfg file is located in the following directories:

Windows NT: \nms\ctaccess\cfg
UNIX: /opt/nms/ctaccess/cfg

2.2.1 Sample CT Access Configuration File

For details about the CT Access configuration file, see the CT Access Developer's Reference Manual. The following code excerpt is an example of a CT Access configuration file that includes the CNF service. The CNF service is shown in bold:

#==========================================================================
# cta.cfg
#
# This is an example of a file that specifies CT Access configuration.
# It allows you to:
#   - specify generic operational settings that apply to CTA Server,
#     ctdaemon,and all CTA applications.
#     Note: these settings can be overwritten by CTA application via 
#           ctaInitialize.
#   - specify application specific settings
#   - specify CTA Server and ctdaemon specific settings
#   - redefine service specific parameter defaults
#
#==========================================================================



#==========================================================================
# CT Access System Configuration (ctasys)
#
# Valid options are:
#   Service = name, dll        - tells the daemon about available "services"
#                              - tells the CT Access server what "services" 
#                                to export
#
# Note: NCC should always precede ADI when both services are listed.
#==========================================================================
[ctasys]
Service = ncc, adimgr
Service = adi, adimgr
Service = dtm, adimgr
Service = ppx, ppxmgr
Service = swi, swimgr
Service = vce, vcemgr
Service = oam, oammgr
Service = cnf, cnfmgr


#==========================================================================

2.3 Configuring NaturalConference

NaturalConference requires appropriate declarations in two different configuration files:

Configuration File	Description
Board configuration file	· Contains board information such as board address, interrupt, and CT Bus clocking. · Contains sections for declaring DSP functionality and associated DSP files to be loaded on each board. The NaturalConference DSP file must be declared in this file. · The board configuration utility reads and interprets this file and performs the board loading and configuration.
NaturalConference configuration file (cnf.cfg)	· Contains the conferencing resource declaration. · NaturalConference uses this information to create and manage conferencing resources. If the NaturalConference configuration file does not exist, or if it does not contain a valid declaration consistent with the board configuration file's content, NaturalConference will not be able to open any conferencing resources.

Figure 6 illustrates how NaturalConference uses the configuration files:

Figure 6. Board & NaturalConference Configuration File Usage

Refer to Section 2.4 for further information about the DSP file and the syntaxes that you must use for NaturalConference.

Refer to Section 2.5 for further information about syntaxes in the cnf.cfg file.

2.4 Modifying the Board Configuration File

NaturalConference uses dedicated DSPs. These DSPs cannot be used with other features such as IVR, Fax, or NMS Fusion. Dedicating a DSP to NaturalConference can reduce the number of ports available for use with IVR. The number of IVR and NaturalConference ports available simultaneously depends on the particular model of AG 2000 board, AG 4000 board, or AG 4000C board installed in (and the configuration of) your computer.

To declare DSPs as conferencing resources, associate DSPs with a NaturalConference DSP file in the board configuration file. Depending on your system configuration and the capabilities required for NaturalConference, specify one of the following DSP files:

File	Description	Capabilities
ag2conf.c54	Default mu-law configuration	Supports echo canceller, DTMF clamping, and tone clamping.
ag2confa.c54	Default A-law configuration	Supports echo canceller, DTMF clamping, and tone clamping.
ag2conf1.c54	Default mu-law configuration	Does not support echo canceller, DTMF clamping, or tone clamping.
ag2conf1a.c54	Default A-law configuration	Does not support echo canceller, DTMF clamping, or tone clamping.

The DSP files are located in the following directories:

Windows NT : \nms\ag\load
UNIX: /opt/nms/ag/load

Refer to Chapter 3 for additional information on the DSP files.

Follow this procedure to declare DSPs for use by NaturalConference:

1. Open the board configuration file.

2. For each board you want NaturalConference to use, add the following keyword and parameter:

   Boards configured with OAM	Boards configured with agmon
   DSP.C5x[n].Image = ag2confx.c54	AG2DSPIMAGE n = ag2confx.c54

   ...where n is the DSP number and x is one of the available NaturalConference DSP files. Alternately, the keyword and parameter can specify a range of DSPs, instead of a single one:
   Note: See Section 2.4.2 for sample board configuration files.
3. Save the modifications.

4. Create a NaturalConference configuration file, as described in Section 2.5.

5. Run the board configuration utility to load or reload the board. If the configuration utility succeeds without error messages, NaturalConference should work according to the resources declared in the NaturalConference configuration file.

Refer to your board-specific installation and developer's manual for a complete description of configuration file keywords.

2.4.1 Sample Board Configuration Files

Use the sample board configuration files provided with NaturalConference as models. Choose one that corresponds to the hardware installed on your system. The following table lists sample configuration files for some of the AG 2000 boards and AG 4000 boards that support NaturalConference.

For OAM, the files are located in the following directories:

Windows NT:\nms\ag\cfg
UNIX: /opt/nms/ag/cfg

For agmon, the files are located in the following directories:

Windows NT:\nms\ag\cfg\agmon
UNIX: /opt/nms/ag/cfg/agmon

Board	Sample OAM Configuration File	Sample agmon Configuration File	Description
AG 2000/200	agpi2cnf_200.cfg	ag2cnf_200.cfg	Eight analog ports in mu-law with one conferencing resource.
AG 2000/200	agpi2cnfa_200.cfg	ag2cnfa_200.cfg	Eight analog ports in A-law with one conferencing resource.
AG 2000/400	agpi2cnf_400.cfg	ag2cnf_400.cfg	Eight analog ports in mu-law with three conferencing resources.
AG 2000/400	agpi2cnfa_400.cfg	ag2cnfa_400.cfg	Eight analog ports in A-law with three conferencing resources.
AG 4000/1600	agpi4cnf_1600.cfg	ag4cnf_1600.cfg	56 ports in mu-law with 9 conferencing resources.
AG 4000/1600	agpi4cnfa_1600.cfg	ag4cnfa_1600.cfg	56 ports in A-law with 9 conferencing resources.
AG 4000/1600	agpi4cnf_2t1_1600.cfg	ag4cnf_2t1_1600.cfg	Two T1 trunks running ISDN in mu-law with nine conferencing resources.
AG 4000/1600	agpi4cnf_2e1_1600.cfg	ag4cnf_2e1_1600.cfg	Two E1 trunks running ISDN in A-law with seven conferencing resources.

Note: If you have an AG 4000C board, use the sample configuration files for the AG 4000 boards.

2.4.2 Sample Board Configuration Files for AG 2000/400

The following sample configuration files set up an AG 2000/400 board running 8 loopstart protocols for an analog interface in mu-law, capable of handling 48 to 96 conferencing ports on 3 DSPs.

OAM Configuration File

##################################################################
#       agpi2cnf_400.cfg
#
#  This model of board configuration file must be used with
#  an AG2000/400 with eight LoopStart interfaces configured in mu-Law. 
#  One DSP is used for IVR. Three conferencing resources are defined.
#
##

Clocking.HBus.ClockSource = OSC
Clocking.HBus.ClockMode = STANDALONE

# Protocols definition
TCPFiles[0] = nocc.tcp    # "no trunk control" protocol
TCPFiles[1] = lps0.tcp    # Loopstart protocol

# Slac Files Definition
#NetworkInterface.Analog[0..7].ConfigFile = a2usasl6.slc
#NetworkInterface.Analog[0..7].ConfigFile = a2eurlsc.slc
#NetworkInterface.Analog[0..7].ConfigFile = a2jpnsl6.slc

# Default Modules activated
DSP.C5x.DSPFiles[0] = callp
DSP.C5x.DSPFiles[1] = dtmf
DSP.C5x.DSPFiles[2] = mf
DSP.C5x.DSPFiles[3] = ptf
DSP.C5x.DSPFiles[4] = signal
DSP.C5x.DSPFiles[5] = tone
DSP.C5x.DSPFiles[6] = voice
DSP.C5x.DSPFiles[7] = rvoice
#DSP.C5x.DSPFiles[8] = wave
#DSP.C5x.DSPFiles[9] = oki

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

XLaw = MU-LAW

###########################################################################
#                                                                         #
# To use NaturalConference with an existing AG2000 configuration file     #
# and have three conferencing resources using three DSPs, add the         #
# following line.                                                         #
###########################################################################
DSP.C5x[1..3].Image = ag2conf.c54

agmon Configuration File

##################################################################
#       ag2cnf_400.cfg
#
#      --- Alliance Generation Configuration ---
#
#  Boot AG2000
#
##################################################################
[AGBOARD]

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

# Uncomment the appropriate Trunk Control Protocol(s)

 TCP = nocc.tcp           # "no trunk control" protocol
 TCP = lps0.tcp           # Loopstart protocol

# Uncomment the appropriate DSP functions

# DSP (.m54) files to link in
 AG2DSPFile = callp.m54
 AG2DSPFile = dtmf.m54
 AG2DSPFile = mf.m54
 AG2DSPFile = ptf.m54
 AG2DSPFile = signal.m54
 AG2DSPFile = tone.m54

 AG2DSPFile = voice.m54
# AG2DSPFile = wave.m54
# AG2DSPFile = oki.m54
 AG2DSPFile = rvoice.m54

 RunModule = gtp.leo
 RunModule = voice.leo
 RunModule = svc.leo

 IdleCode   = mu-LAW

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

 Board 0
  PCIBUS = 0
  PCISLOT = 15
  ClockRef = OSC # Change to OSC for standalone operation
  EnableMvip = NO # Change to YES if there is an MVIP bus




###########################################################################
#                                                                         #
# To use NaturalConference with an existing AG 2000 configuration file    #
# and have three conferencing resources using three DSPs, add the         #
# following line to the Board section.                                    #
#                                                                         #
###########################################################################
  AG2DSPIMAGE 1..3 = ag2conf.c54

 End Board

# Uncomment for second board.
# Board 1
#  PCIBUS = 1
#  PCISLOT = 7
  
#  ClockRef = OSC # Change to OSC for standalone operation
#  EnableMvip = NO # Change to YES if there is an MVIP bus
# End Board


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

                                                     

2.4.3 Sample Board Configuration Files for AG 4000/1600

The following sample configuration files set up an AG 4000/1600 board running 2 T1 interfaces with AG ISDN, capable of handling 144 to 288 conferencing ports on 9 DSPs.

OAM Configuration File

##################################################################
##                        agpi4cnf_2t1_1600.cfg
#
# Sample configuration file for AG4000 running two T1 interfaces with AG
# ISDN and using nine resources of NaturalConference
#
##

Clocking.HBus.ClockSource = NETWORK
Clocking.HBus.ClockSourceNetwork = 1
Clocking.HBus.ClockMode = STANDALONE

NetworkInterface.T1E1[0..3].SignalingType = PRI
NetworkInterface.T1E1[0..3].D_Channel = ISDN
NetworkInterface.T1E1[0..3].LineCode = AMI
NetworkInterface.T1E1[0..3].FrameType = ESF    # Extended SuperFrame 

# Protocols
TCPFiles[0] = nocc.tcp    # "no trunk control" protocol
TCPFiles[1] = isd0.tcp

# Default Modules activated
DSP.C5x.DSPFiles[0] = callp
DSP.C5x.DSPFiles[1] = dtmf
DSP.C5x.DSPFiles[2] = mf
DSP.C5x.DSPFiles[3] = ptf
DSP.C5x.DSPFiles[4] = signal
DSP.C5x.DSPFiles[5] = tone
DSP.C5x.DSPFiles[6] = voice
DSP.C5x.DSPFiles[7] = rvoice
#DSP.C5x.DSPFiles[8] = wave
#DSP.C5x.DSPFiles[9] = oki

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

#   Uncomment the appropriate leo file

DLMFiles[3] = isdn4ess.leo  # use with "AT&T 4ESS"
#DLMFiles[3] = isdn5ess.leo  # use with "AT&T 5ESS"
#DLMFiles[3] = isdndms.leo   # use with "Northern Telecom DMS100"
#DLMFiles[3] = isdnhkt.leo   # use with "Hong Kong Telephone"
#DLMFiles[3] = isdnntt.leo   # use with "Nippon Telegraph Telephone"
#DLMFiles[3] = isdnni2.leo   # use with "US National ISDN 2"
#DLMFiles[3] = isdntwn.leo   # use with "Taiwanese Operator"

#DLMFiles[3] = imgt.leo      # use with "AT&T 4ESS"/"AT&T 5ESS"/"DMS100"

XLaw =MU-LAW

###########################################################################
#                                                                         #
# To use NaturalConference with an existing AG4000 configuration file     #
# and have nine conferencing resources, add the following line.           #
#                                                                         #
###########################################################################
DSP.C5x[7..15].Image = ag2conf.c54

agmon Configuration File

########################################################################
#                        ag4cnf_2t1_1600.cfg
#
#      --- Alliance Generation Configuration --
#
# Sample configuration file for AG 4000 running two T1 interfaces with AG
# ISDN and using nine resources of NaturalConference
########################################################################

[AGBOARD]

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


 TCP = nocc.tcp             # "no trunk control" protocol
 TCP = isd0.tcp

#   Uncomment the appropriate DSP functions

# DSP (.m54) files to link in
 AG2DSPFile = callp.m54
 AG2DSPFile = dtmf.m54
 AG2DSPFile = mf.m54
 AG2DSPFile = ptf.m54
 AG2DSPFile = signal.m54
 AG2DSPFile = tone.m54

 AG2DSPFile = voice.m54
# AG2DSPFile = wave.m54
# AG2DSPFile = oki.m54
 AG2DSPFile = rvoice.m54

 RunModule = gtp.leo
 RunModule = voice.leo
 RunModule = svc.leo

#   Uncomment the appropriate leo file

 RunModule = isdn4ess.leo   # use with "AT&T 4ESS"
# RunModule = isdn5ess.leo  # use with "AT&T 5ESS"
# RunModule = isdndms.leo   # use with "Northern Telecom DMS100"
# RunModule = isdnhkt.leo   # use with "Hong Kong Telephone"
# RunModule = isdnntt.leo   # use with "Nippon Telegraph Telephone"
# RunModule = isdnni2.leo   # use with "US National ISDN 2"
# RunModule = isdntwn.leo   # use with "Taiwanese Operator"

# RunModule = imgt.leo      # use with "AT&T 4ESS"/"AT&T 5ESS"/"DMS100"

 IdleCode = MU-LAW

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

 Board 0
   PCIBUS = 1               # Use blocate to determine PCIBUS and PCISLOT
   PCISLOT = 6

   ClockRef = NET1    
   EnableMvip = NO          # Change to YES if there is an MVIP bus
   DIGITALMODE = PRI
   LINECODE = AMI
   FRAMETYPE = ESF          # Extended SuperFrame 

###########################################################################
#                                                                         #
# To use NaturalConference with an existing AG 4000 configuration file    #
# and have nine conferencing resources using nine DSPs, add the following #
# line to the Board section.                                              #
#                                                                         #
###########################################################################
  AG2DSPIMAGE 7..15 = ag2conf.c54

 End Board

#   Uncomment the following for a second board

# Board 1
#   PCIBUS = 1
#   PCISLOT = 14
#   ClockRef = NET1          # Change to MVIP if there is an MVIP bus
#   EnableMvip = NO          # Change to YES if there is an MVIP bus
#   DIGITALMODE = PRI
#   LINECODE = AMI
#   FRAMETYPE = ESF          # Extended SuperFrame 
# End Board

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

2.5 Setting Up the NaturalConference Configuration File

After modifying the board configuration file, create a NaturalConference configuration file (cnf.cfg) to declare conferencing resources.

Use the NaturalConference configuration file to assign DSPs from a given board to a numbered conferencing resource. A NaturalConference application can open this resource using cnfOpenResource.

You can also use the cnf.cfg to

• Disable the resource capabilities that you do not need, potentially increasing the number of members supported on a given resource.

• Add a new conferencing resource without having to modify your application. You can take advantage of the new resource by using cnfGetResourceList to retrieve a list of available resources.

• Assign a conferencing resource to a new DSP without having to recompile the application.

2.5.1 Customizing a cnf.cfg For Your System

The easiest way to create a cnf.cfg file for your system is to modify one of the sample files installed with NaturalConference. The sample files are installed in the following directories:

• Windows NT: \nms\ctaccess\cfg

• UNIX: /opt/nms/ctaccess/cfg

The sample configuration files for NaturalConference are:

Board	NaturalConference Configuration File	Corresponding OAM Configuration File	Corresponding agmon Configuration File	Description
AG 2000/200	cnf_ag2_200.cfg	agpi2cnf_200.cfg & agpi2cnfa_200.cfg	ag2cnf_200.cfg & ag2cnfa_200.cfg	One conferencing resource.
AG 2000/400	cnf_ag2_400.cfg	agpi2cnf_400.cfg & agpi2cnfa_400.cfg	ag2cnf_400.cfg & ag2cnfa_400.cfg	Three conferencing resources.
AG 4000/1600	cnf_ag4_1600.cfg	agpi4cnf_1600.cfg & agpi4cnfa_1600.cfg	ag4cnf_1600.cfg & ag4cnfa_1600.cfg	Nine conferencing resources.
AG 4000/1600	cnf_ag4_2t1_1600.cfg	agpi4cnf_2t1_1600.cfg	ag4cnf_2t1_1600.cfg	Nine conferencing resources.
AG 4000/1600	cnf_ag4_2e1_1600.cfg	agpi4cnf_2e1_1600.cfg	ag4cnf_2e1_1600.cfg	Seven conferencing resources.

Note: If you have an AG 4000C board, use the sample configuration files for the AG 4000 boards.

2.5.2 NaturalConference Configuration File Structure

The NaturalConference configuration file begins with a [CONFERENCING] section. Statements in this section are global statements that apply to all resources defined in the file.

Each conferencing resource is defined in a [Resource n] section. Statements in this section are local statements that apply only to the designated resource. The numbering of a resource is user-defined and may be defined in an unordered fashion. Valid resource numbers are from 0 to 4095.

A statement has the general syntax keyword = value. Not all keywords can be used in global statements.

White space, such as indentations or a space around an equals sign, is ignored but is useful for clarity. The pound sign (#) and semicolon (;) are both comment delimiters. NaturalConference ignores any text that follows a comment delimiter character on the same line. Case is ignored for Windows NT but is important for file names for UNIX-based operating systems.

Following is an excerpt from a typical NaturalConference configuration file:

[CONFERENCING] # Start of active region

Flags = NO_ECHO_CANCEL # Common statements

[Resource 0] # Start of a resource-specific section for Resource 0

  Board = 0   # Resource-specific statements 
  BoardType = AG2000
  DSP = 3
  Flags = NO_DTMF_CLAMPING


[Resource 1] # Start of a resource-specific section for Resource 1

  Board = 1   # Resource-specific statements 
  BoardType = AG4000
    DSP = 10

# EOF (End of active regions)

2.5.3 NaturalConference Configuration File Statements

The following table summarizes the NaturalConference configuration file statements. Brackets ([ ]) signify an optional value. A vertical bar ( | ) signifies a choice of more than one value.

Keyword	Global	Local	Allowed Values	Specifies...	Mandatory?
Board	x	x	0..n	The board number as defined in the board configuration file. Every board in the system must have a unique board number.	Yes
BoardType	x	x	AG2000 AG4000 AG4000C	The type of board.	Yes
DSP		x	[dsp1[..dspn]]	The DSP number to be used by this resource. Note: You can assign only 1 DSP to a resource.	Yes
Flags	x	x	NO_ECHO_CANCEL | NO_DTMF_CLAMPING | NO_TONE_CLAMPING	The capabilities the application will not use.	No

Using Flags

The Flags statement is optional. Use this statement to specify the capabilities the application will not use. By disabling certain capabilities you free up system resources, making it possible to increase the number of members supported on a given conferencing resource. If you do not specify any flags, all capabilities currently supported by the loaded DSP module are available. Applications cannot dynamically activate a capability at the conference or member level if the capability has been disabled in the configuration file.

Flags that you specify in the [CONFERENCING] section apply to every conferencing resource declared in the configuration file. For example:

[CONFERENCING]
Flags = NO_DTMF_CLAMPING 

[RESOURCE 0]
Flags = NO_ECHO_CANCEL | NO_TONE_CLAMPING

The resulting flags for resource 0 are NO_DTMF_CLAMPING | NO_ECHO_CANCEL | NO_TONE_CLAMPING.

2.5.4 Sample NaturalConference Configuration File for AG2000/400

The following sample NaturalConference configuration file defines three conferencing resources on Board 0:

###########################################################################
#       cnf_ag2_400.cfg
#
#      --- NaturalConference Configuration File --
#
# Sample configuration file for AG 2000 running eight Loop Start Interfaces
# and using three resources of NaturalConference.
#
# This file is associated with the board configuration files ag2cnf_400.cfg
# and ag2cnfa_400.cfg installed in the \nms\ag\cfg directory.
#
###########################################################################

[CONFERENCING]

# Flags = NO_ECHO_CANCEL | NO_DTMF_CLAMPING

[RESOURCE 0]

Board = 0
BoardType = AG2000
DSP = 1

[RESOURCE 1]

Board = 0
BoardType = AG2000
DSP = 2

[RESOURCE 2]

Board = 0
BoardType = AG2000
DSP = 3

2.5.5 Sample NaturalConference Configuration File for AG4000/1600

The following sample NaturalConference configuration file defines nine conferencing resources on Board 0:

########################################################################
#                        cnf_ag4_2t1_1600.cfg
#
#      --- NaturalConference Configuration File --
#
# Sample configuration file for AG 4000 running 2 T1 trunks (48 ports)
# and using 9 resources of NaturalConference (144 conferencing ports)
#
# This file is associated with the board configuration file
# ag4cnf_2t1_1600.cfg installed in the \nms\ag\cfg directory.
#
########################################################################

[CONFERENCING]

Flags = NO_ECHO_CANCEL

[RESOURCE 0]

Board = 0
BoardType = AG4000
DSP = 7

[RESOURCE 1]

Board = 0
BoardType = AG4000
DSP = 8

[RESOURCE 2]

Board = 0
BoardType = AG4000
DSP = 9

[RESOURCE 3]

Board = 0
BoardType = AG4000
DSP = 10



[RESOURCE 4]

Board = 0
BoardType = AG4000
DSP = 11

[RESOURCE 5]

Board = 0
BoardType = AG4000
DSP = 12

[RESOURCE 6]

Board = 0
BoardType = AG4000
DSP = 13

[RESOURCE 7]

Board = 0
BoardType = AG4000
DSP = 14

[RESOURCE 8]

Board = 0
BoardType = AG4000
DSP = 15

2.6 Verifying NaturalConference

After you install and configure NaturalConference, verify that the system is operational before you continue.

Before running the NaturalConference verification procedures described in this section, make sure that

• CT Access is properly installed.

• NaturalConference is properly installed and the CNF service is defined in the CT Access configuration file as described in Section 2.2.

• Your system hardware includes at least one AG 2000 board, AG 4000 board, or AG 4000C board that supports NaturalConference.

• The board is initialized and operating correctly.

To verify that NaturalConference is operational,

• Verify that the NaturalConference software can be successfully loaded.

• Verify the NaturalConference configuration.

• Test your system's ability to receive calls and add them to a conference.

2.6.1 Verifying the NaturalConference Installation

Use the CT Access version checker utility, ctavers, to verify that the NaturalConference software can be successfully loaded. ctavers verifies that all the CT Access libraries defined in the CT Access configuration file (cta.cfg) are accessible.

See Section 2.2 for more information about the CT Access configuration file.

To run ctavers, from the command line enter the following command:
ctavers

ctavers displays a list of all the installed CT Access components. Verify that NaturalConference is installed. The NaturalConference statements are shown in bold in the following example:

CT Access Version Checker Utility  V.5 (Sep 12 2000)

CT Access Release:             4.01
CT Access Compatibility Level: 2
CTA: DISPATCHER      v 4.01 Sep 12 2000 compat: expdisp=1  expapi=2
Mgr: ADIMGR          v 1.02 Sep 12 2000 compat: reqdisp=1
Mgr: PPXMGR          v 1.00 Sep 12 2000 compat: reqdisp=1
Mgr: SWIMGR          v 1.00 Sep 12 2000 compat: reqdisp=1
Mgr: VCEMGR          v 1.00 Sep 12 2000 compat: reqdisp=1
Mgr: OAMMGR          v 1.01 Sep 12 2000 compat: reqdisp=1
Mgr: CNFMGR          v 1.02 Sep 14 2000 compat: reqdisp=1
Svc: NCC   (ADIMGR ) v 1.00 Sep 12 2000 compat: reqdisp=1  expapi=1 expspi=1
Svc: ADI   (ADIMGR ) v 1.60 Sep 12 2000 compat: reqdisp=1  expapi=1 expspi=1
Svc: DTM   (ADIMGR ) v 1.00 Sep 12 2000 compat: reqdisp=1  expapi=0 expspi=0
Svc: PPX   (PPXMGR ) v 1.00 Sep 12 2000 compat: reqdisp=1  expapi=0 expspi=0
Svc: SWI   (SWIMGR ) v 1.00 Sep 12 2000 compat: reqdisp=1  expapi=0 expspi=0
Svc: VCE   (VCEMGR ) v 1.00 Sep 12 2000 compat: reqdisp=1  expapi=0 expspi=0
Svc: OAM   (OAMMGR ) v 1.01 Sep 12 2000 compat: reqdisp=1  expapi=1 expspi=1
Svc: isdn  (ADIMGR ) v 1.00 Sep 12 2000 compat: reqdisp=1  expapi=1 expspi=0
Svc: imgt  (ADIMGR ) v 1.00 Sep 12 2000 compat: reqdisp=1  expapi=1 expspi=0
Svc: CNF   (CNFMGR ) v 1.02 Sep 14 2000 compat: reqdisp=1  expapi=1 expspi=1

2.6.2 Verifying the NaturalConference Configuration

Use the NaturalConference utility, cnfinfo, to verify that the NaturalConference software is properly configured. cnfinfo checks all the boards currently loaded on your system and opens all the resources defined in the NaturalConference configuration file (cnf.cfg).

See Section 2.5 for more information about the NaturalConference configuration file.

To run cnfinfo, from the command line enter the following command:
cnfinfo

cnfinfo displays a list of the installed boards and the defined resources, including the maximum number of members with all capabilities, and the maximum number of members with all capabilities except echo canceller or DTMF clamping. You can evaluate how many NaturalConference ports are available when using the capabilities of each resource.

For example:

2.6.3 Receiving Calls and Adding Callers to a Conference

Use the NaturalConference sample program, cnfjoin, to test your system's ability to receive calls and add them to a conference.

cnfjoin opens the first conferencing resource available and opens a designated number of channels for call control. When cnfjoin receives a call, it immediately adds the caller to a conference. All callers are added to the same conference. When a caller disconnects, it is removed from the conference and another caller can take its place.

The cnfjoin program is based on NCC and can be used either with ISDN, CAS, or analog protocols.

Note: To use cnfjoin, call control and all conferencing resources must reside on the same board. If you are using the default configuration files provided by the installation, your system is properly configured to use cnfjoin, since these files configure call control and conferencing on the same board.

For more information about cnfjoin, refer to Chapter 7.