Cisco Cisco Administrative Workstation Release Note

ICM Process Testing In The Staging
Environment

The sample test cases in this section allow you to validate the ICM inter-process communications and fault
tolerance in the Staging Environment. When you install the system in the Production Environment, the
Routing Application and Scripting are configured. At that time, begin Application Testing.

Table 1

Sample Test 1-RTTEST

Test Number:

Test Title:

RTTEST

Test Purpose:

Verify the current state of all ICM Central Site Processes and that all devices (PG’s and
Peripherals) are identified correctly by each CallRouter.

Test Setup:

All ICM Services start in full Duplex Mode – Run RTTEST on each CallRouter

Procedure:

Run: Rttest /system <CallRouterHostname> /cust <instance name> /node routera

Rttest: status

Take a screen shot of the results and append to the Staging Report

Quit to exit out of the command prompt when you are finished on each CallRouter

Expected Results:

All configured processes are OK as seen by CallRouters

Pass:

Fail:

All configured physical controllers are communicating (CFO) with CallRouters

Pass:

Fail:

All configure/in-service Peripherals are properly identified by that CallRouter
and are online

Pass:

Fail:

Passed: (initial)

Failed: (initial)

Reason for Failure:

Remarks:

C Signifies that the ICM peripheral gateway server successfully downloaded a configuration from the

ICM call router.

F Signifies that the ICM peripheral gateway is fully configured and that the configuration is valid.

O Signifies that the ICM PG is on lineand that it is communicating with the ICM call router

Peripherals are not online (O), since there are no live peripherals in the Staging Environment. The test is

re-run in Production.

Table 2

Sample Test 2-ICM Process Logs

Release 6.0(0) Staging on Windows 2000

104