Cisco Cisco E-Mail Manager Unity Integration Option Release Note

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

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

11. Click Start on Expand Database window. Click OK and close the window. 

12. Close 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. You are now in the <cus_awdb> Properties Window. 

o 

On the Data Files Tab: 

  Check Autogrow and set the File Growth to 10%. 
  Set the Maximum File Size to [use the following calculation]. 

{80% of free disk space}/{number of ICM database files and aw logs on this 
disk}+{database file current size} 

example: {4GB * .80}/{2}+{.5GB}=2.1GB 

o 

On the Transaction Log Tab: 

  Check Autogrow and set the File Growth to 10%. 
  Set Maximum File Size to [use the following calculation]. 

{80% of free disk space}/{number of ICM database files and aw logs on this 
disk}+{database file current size} 

Example: {4GB * .80}/{2}+{.2GB}=1.8GB 

 

Start the Distributor Service within Cisco Service Control.  

Verify that the ICM Processes have no errors: 

o 

CallRouters: 

o 

Router: running and synchronized with peer 

o 

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

o 

Rtsvr: feed activated to AW 

o 

Loggers: 

o 

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

o 

Admin Workstation: 

o 

Updateaw: displays “waiting for new work” 

o 

Iseman: listen thread waiting for client connection 

Before starting the ICM Services on the SS7 Gateways, NICs and Peripheral Gateways, you need to 
configure them in the ICM using the NIC and PG Explorer tools. The 

 should 

indicate the values and setting changes required during the setup of these nodes.  

In order to properly run ICM Setup for the NICs and PG’s, you need to pre-plan the Logical and Peripheral 
ID numbers, as they are required data elements to complete the setup program. The ICM automatically 
generates ID numbers from the Explorer tools, so you need to set them up in the Explorers in the exact 
order you planned them using the Node Form. 

If the ID numbers are not generated in the proper sequence, you can correct them in the Peripheral 
Gateway machines by re-running setup locally. They must match the ICM configuration database to the 
value in the PG’s registry, or the ICM CallRouter rejects the connection request.