# Verifying NaturalConference

After you install and configure NaturalConference, verify that the system is operational:

- Verify that the NaturalConference software is successfully loaded.

- Verify the NaturalConference configuration.

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

## Verifying the NaturalConference installation

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

To run ctavers, enter the following command:

ctavers

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

H:\>ctavers -x cnf,cnfmgr
Natural Access Version Checker Utility V.5 (Jun 29 2001)
Natural Access Release: 4.03
Natural Access Compatibility Level: 2
CTA: DISPATCHER v 4.03 Jun 29 2001 compat: expdisp=1 expap
Mgr: CNFMGR v 2.00 Jul 17 2001 compat: reqdisp=1
Svc: CNF (CNFMGR ) v 2.00 Jul 17 2001 compat: reqdisp=1 expap

## 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). Refer to Setting up the NaturalConference configuration file for more information.

To run cnfinfo, 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:

H:\>cnfinfo
CNFINFO: NaturalConference Utility V2.0 (Jul 25 2001)
| Rs/Bd |
| 0/0 |
|--------------------------|-----------|
|Features | 0x20ff |
|Full | 24 |
|Wo (E) | 24 |
|Wo (D) | 24 |
|Wo (T) | 24 |
|Wo (Co) | 50 |
|Wo (E & D) | 24 |
|Wo (E & T) | 24 |
|Wo (E & Co) | 64 |
|Wo (D & T) | 24 |
|Wo (D & Co) | 50 |
|Wo (T & Co) | 50 |
|Wo (E & D & T) | 24 |
|Wo (E & D & Co) | 64 |
|Wo (E & T & Co) | 64 |
|Wo (D & T & Co) | 60 |
|Wo (E & D & T & Co) | 64 |
|--------------------------|---------- |
------------------------------------------------------------------------
(Type "cnfinfo -a" to have details on the abbreviations used in this table)
Board CNF Resources CNF Ports
----- ------------- ---------
0 1 24

## 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 conference 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 Natural Call Control (NCC) and can be used either with ISDN, CAS, or analog protocols.

To use cnfjoin, call control and all conference 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, refer to cnfjoin overview.