Cisco Cisco IPCC Web Option Release Note

The Node Form worksheet lists the NIC interfaces first, although, for the Sprint and MCI NIC, there is no 
additional platform or specific services to start (they are co-resident in the ICM CallRouter). The ICM 
Setup program requires the ID values when the CallRouter is set up. When the services start on the 
CallRouter, these ID values are validated against the ICM configuration database and rejected if they do 
not match. 

Also, you must configure an ICM Gateway for each CICM Instance on the NAM for connectivity from the 
NAM CIC process to the CICM INCRP NIC. 

Typically, PG’s associated with the NAM Domain are IVR/ISN PG’s. 

Complete the setup on all Peripheral Gateways (see 

). 

Cisco provides specific hot fixes to major releases and service packs of the ICM software to address 
service-impacting issues.  You can download hot fixes from Cisco’s Web site (

) 

and apply them after the initial load of the software. The hot fix installation process only applies fixes 
required for the specific software module (CallRouter, Logger, type of PG, etc.). 

Once the ICM configuration database is set up with the appropriate peripherals, you can start the PG 
services using the Cisco Service Control application on the desktop of the PG. If the local peripheral 
(IVR/ISN) is not available to connect to the PG, “disable” it in the PG setup. Testing only proves that the 
PG communications layer is set up properly and that it can talk to the CallRouters and obtain configuration 
information. 

Verify that the ICM Processes have no errors: 

o 

CallRouters: 

o 

Router: UP and synchronized with peer 

o 

Ccagent: connected to all configured peripheral gateways 

o 

Rtsvr: feed activated to AW 

o 

Loggers: 

o 

Logger: connected to its respective database and synchronized with peer – MDS is in 
service 

o 

Admin Workstation: 

o 

Updateaw: displays “waiting for new work” 

o 

Iseman: listen thread waiting for client connection 

o 

Peripheral Gateways: 

o 

Mdsproc: inservice 

o 

Pgagent: inservice and active to one side of central controller 

o 

[peripheral] PIMs: disabled on node form – PIM windows do not exist 

 

Install First Domain Controller Server for CICM Child Domain 

Install DNS Server on First Domain Controller for CICM Child Domain 

Install Additional Domain Controller 

Install and Configure DNS on Additional Domain Controller 

Configure Active Directory Sites 

Assign Global Catalog and FSMO Roles and Configure Time Source