Cisco Cisco Administrative Workstation Release Note

o 

Enter peripheral.hostport=42027 

o 

Enter peripheral.hostname2=icmcuspg1b (be sure to uncomment) 

o 

Enter peipheral.hostport2=43027 (be sure to uncomment) 

o 

SAVE and CLOSE file 

8. Open 

the 

blender.properties file (from the directory C:\CiscoMB\servlet\Properties\Blender) with a 

text editor and make the following edits:  

Note: these setting vary according to peripheral types. 

[example] 

o 

Uncomment “service1=service.fwgw.properties” 

9.  Open the firewallgatewayFG.properties file with a text editor (located in the 

C:\CiscoMB\servlet\Properties directory) and make the following edits:   

Note: These setting vary according to whether or not you have duplex PG’s. 

[example] 

10.  Replace <connectionname> (appears throughout) with the name of the connection to Media Blender 

that you created on the collaboration server during the 

 steps.  For example: cmb1. 

11.  Enter the Primary and Secondary CTI Server hostnames, where indicated by <primaryhostname> and 

<backuphostname>. 

12.  Enter the Primary and Secondary CTI Server ports, where indicated by <primaryserverport> and 

<backupserverport>. 

13.  Save and Close. 

 

To Start Media Blender: 

1.  Open the Browser and enter the URL http:\\<media blender hostname>. 

2.  For the user name, enter Administrator (with capital A).  

3.  For the password, enter <Win2K Admin login password>. 

4.  Click on the Server Administration link. 

5.  In the left frame, click on Media Blender > Server > Start > Shutdown. 

6.  In the right frame, click Start. 

7.  In the left frame, select Media Blender > Service > Firewall Gateway > Start > Stop. 

8.  In the right frame, click Start. 

 
Verify that these ICM Processes have no errors: 

o 

CallRouters: 

o 

Router: running and synchronized with its peer 

o 

Ccagent: connected to all configured peripheral gateways 

o 

Rtsvr: feed activated to the AW 

o 

Loggers: 

o 

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

o 

CampaignManager: the process is running on the logger and connected to the Blended 
Agent Dialer. 

o 

Admin Workstation: 

o 

Updateaw: Displays “waiting for new work” 

o 

Iseman: the listen thread is waiting for a client connection 

o 

Cms_jserver: the cmsnode.exe process is active. The event helper message shows CCS 
and CEM running.  

o 

Cmsnode: the initialization is complete 

o 

Peripheral Gateways: 

o 

Generic (IPCC & VRU) PG 

  Mdsproc: in service