3.1 Introduction

3.2 Managing Resources

3.2.1 Managing Available Members

3.2.2 Resource Management Example

3.2.3 Using DSP Files for Resource Management

3.3 Configuration Examples

3.1 Introduction

This chapter explains how to configure the boards in your system to optimize the performance of a NaturalConference application. The following boards support NaturalConference:

• AG 2000

• AG 4000

• AG 4000C

NaturalConference uses dedicated DSPs (these DSPs cannot be used with other features such as IVR, Fax, or Fusion). Dedicating a DSP to NaturalConference can reduce the number of ports available for use with interactive voice response (IVR). The number of IVR and NaturalConference ports concurrently available depends on the model of board installed in (and the configuration of) your computer.

3.2 Managing Resources

The number of members in a conference is limited by the number of members that a resource can support. You can increase the number of members in a conference by

• Chaining conferences at the application level. For more information on chaining conferences, refer to Section 7.2, cnfjoin.

• Disabling capabilities, either at the resource level or at the application level. The following sections describe how to disable capabilities.
  Note: In release 1.0, you can assign only 1 DSP to a resource.

The number of members a resource can support ranges from 16 to 61, depending on the capabilities set for each conference (DTMF clamping, tone clamping, and echo cancellation are MIPS-requiring features). The following table lists examples of conference configurations:

Capabilities Defined	Members Supported
All capabilities	16
All capabilities except echo cancellation and tone clamping	32
All capabilities except echo cancellation, tone clamping, and DTMF clamping. Requires special firmware (ag2conf1(a).c54).	61

For more details on the number of members that a resource can support, refer to the readme_cnf.txt.

Note: The echo cancellation module delivered with NaturalConference is based on a 10 ms window length with an adapt time of 200 ms. This module is similar to the standard echo cancellation module (echo.m54) used with the IVR port. Refer to the board-specific installation and developer's manual for more information on echo.m54.

3.2.1 Managing Available Members

You can manage the available members for a conference in the following ways:

• Use cnfGetResourceInfo to determine how many members you can add to a conference. This function gives you the maximum number of members the resource can accept if using the full capabilities of the resource, as well as the number of members available for a new conference.

• If you know before opening the resource that you will never use certain capabilities, disable the capabilities in the cnf.cfg by using the Flags keyword as described in Section 2.5.3. The information retrieved by cnfGetResourceInfo will be closer to your needs.

• If you intend to create a conference using fewer capabilities than the resource allows, specify the unused capabilities for this resource in the CNF_CONFERENCE_PARMS structure when you create the conference. When the conference is created, you may have more available members on this resource than you expected. Then you can invoke cnfResizeConference to increase the number of available members. If you resize your conference progressively (adding one member each time) you will reach the real limit of the resource.

3.2.2 Resource Management Example

The following example illustrates resource management:

1. A call to cnfGetResourceInfo indicates that the resource can handle 6 members with full capabilities.

2. Because the application does not require echo cancellation, the keyword flags=NO_ECHO_CANCEL is specified in the cnf.cfg to configure the resource. The resource is opened and cnfGetResourceInfo is invoked, indicating that the number of available members has increased to 12.

3. A new conference with full capabilities and 4 members is created, reducing the number of available members to 8.

4. When a second conference with no DTMF clamping and 4 members is created, the number of available members is only reduced by 2 (to 6 available members).

3.2.3 Using DSP Files for Resource Management

Depending on your system configuration and the capabilities required for NaturalConference, load one of the following DSP files:

Load this DSP File...	If...
ag2conf(a).c54	You need the maximum capabilities, including echo cancellation, tone clamping, and DTMF clamping. This module gives you 16-32 available members per conference. This is the recommended DSP file for NaturalConference applications. Note: Disabling these capabilities in the cnf.cfg will not increase the number of available members per conference to more than 32.
ag2conf1(a).c54	You do not need tone clamping, DTMF clamping, and echo cancellation. This module gives you 61 available members per conference.

The DSP files are located in the following directories:

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

3.3 Configuration Examples

This section presents examples of AG 2000 board and AG 4000 board DSP and resource configurations for using NaturalConference to develop a voice, fax, and conferencing application.

Refer to the board-specfic installation and developer's manual for additional information on configuring DSPs for IVR.

These configurations assume the following:

• IVR requires:

  Capabilities	MIPS	DSP Modules
  Echo cancellation (16 ms window length, 400 ms adapt time)	3.63	echo.m54
  DTMF and silence detector	1.94	dtmf.m54
  Call progress	1.06 (AG 2000 only)	callp.m54
  Precise tone filter (2 single freq or 1 tone pair)	1.25	ptf.m54
  NMS record 32 kbps	3.38	voice.m54
  	Total: 11.26 MIPS per channel

  For a 100 MIPS device (90 MIPS effectively), the required number of IVR channels is 8 (90 divided by 11.26 and rounded to the nearest whole number).

• FAX could be used either in reception or transmission in V17, V27, or V29, requiring 8 channels per DSP.

• NaturalConference can support 16 members per DSP with all capabilities activated.

Following are the sample board configurations:

Board Name	Number of Channels	Number of NaturalConference Ports
AG2000/200-8L	8 IVR channels	16 ports of NaturalConference with echo cancellation, DTMF clamping, and tone clamping.
AG2000/200-8L	none 1	32 to 64 ports of NaturalConference.
AG2000/400-8L	8 IVR channels and 8 FAX channels	32 ports of NaturalConference with echo cancellation, DTMF clamping, and tone clamping.
AG2000/400-8L	none 1	48 to 96 ports of NaturalConference 2.
AG4000/400-1T	none 1	64 to 128 ports of NaturalConference.
AG4000/800-2T	24 IVR channels and 24 FAX channels (1 trunk)	16 ports of NaturalConference with echo cancellation and DTMF clamping.
AG4000/1600-2T	48 IVR channels and 48 FAX channels (2 T1 trunks)	48 ports of NaturalConference with echo cancellation and DTMF clamping.
AG4000/3200-4T	96 IVR channels and 96 FAX channels (4 T1 trunks)	112 ports of NaturalConference with echo cancellation and DTMF clamping.
AG4000/4000-4E	120 IVR channels and 120 FAX channels (4 E1 trunks)	144 ports of NaturalConference with echo cancellation and DTMF clamping.

1 When using a dedicated conferencing resource board. 2 Due to memory limitations of the coprocessor program of the AG 2000 board.