Cisco Cisco Administrative Workstation Release Note

Workstation(s) must be running. The ICM software loads an  “ICM Service Control” tool on the desktop of 
each server used to control the services loaded on that machine.  Start the services in the following order: 

•  Logger A   
•  CallRouter A 
•  CallRouter B 

• 

Logger B

 

Each service starts several process windows on the task bar of the local machine, each one an ICM 
program associated with the service.  As each node starts up, it looks for the other server components and 
attempts to register with them.  If you completed the ICM Setup and network testing successfully, no major 
errors should occur. 

 

 
Verify that the ICM Processes have no errors: 
 CallRouters: 

o 

Router: UP and synchronized with peer 

o 

Ccagent: [will be in service but not be connected to any peripheral gateways] 

o 

Rtsvr: [no connectivity to AW at this time] 

Loggers: 

o 

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

o 

Replication: [no connectivity to AW HDS at this time] 

o 

Campaign Manager: [you see errors, no BA Dialer setup at this time] 

Complete Setup on all Admin Workstations (see 

). 

When the Admin Workstation software loads using ICM Setup, it creates specific domain level groups and 
accounts in the ICM domain it is loaded into.   

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 (

). 

Apply these hot fixes 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.). 

1. Click 

Start > Run, enter ICMDBA and click OK. 

2.  Expand Tree under the AW Hostname. 

3. Highlight 

<cus_awdb>. 

4.  Select Expand from the Database menu. 

5.  Highlight C Drive. 

6.  Expand Data to 500MB. Click OK. 

7. Click 

Start on Expand DB window. Click OK. Close when complete. 

8.  Select Expand from the Database menu. 

9.  Select Log (C drive is automatically highlighted). 

10.  Expand the Log to 200MB. Click OK. 

11. Click Start on the Expand the database window. Click OK. Close when complete. 

12.  Close the ICMDBA. 

13. Click Start > Programs > Microsoft SQL Server > Enterprise Manager. 

14.  Expand the Server Tree and Highlight the Databases folder under the Server name. 

15.  Double-click on the ICM Database in right panel, now in the <cus_awdb> Properties Window.