Cisco Cisco IP Contact Center Release 4.6.2 Release Note

•  For the IP Tab, do not Enable IP Routing. 
•  For the NETBEUI Tab, allow access to “This Computer Only”. 

2. Open 

Computer Management > Local User and Groups > Users. 

  Double-click on the Administrator account. 
  Select Allow Access on the Dial In tab. 

Note: Routing and Remote Access Service is not supported on Windows 2000 Professional. Any 
Peripheral Gateway used with RRAS must run Windows 2000 Server. 

  

Create a Software directory and load folders, as detailed on the 3

rd

 Party Host 

Form 

 Add Persistent Static Routes as detailed on 3

rd

 Party Host Form 

For geographically distributed central controller sites, the CallRouters and Loggers have a Private IP WAN 
connection, used to communicate between side A and side B. Windows only allows one “default gateway” for 
each machine, which sends the Private Network traffic to the Visible Network. You need to add a set of Static 
Routes to the CallRouter and Logger systems on both sides of the system to direct this traffic to the Private 
Network. 

1.  On CallRouter A and Logger A:  

route add <network number> mask <subnet mask> <gateway IP> -p 
 

Example: route add 192.168.142.64 mask 255.255.255.192 192.168.141.126 –p 

 

Where: 
The network number of the remote Private Network is 192.168.142.64  
The subnet mask for this remote network is 255.255.255.192 
The local Private Network Adaptor Card’s IP Address is 192.168.141.126  

 

(-p sets the route as persistent) 

 

2.  On CallRouter B and Logger B:  

Example: route add 192.168.141.64 mask 255.255.255.192 192.168.142.126 –p 

 Configure Telnet Security as detailed on 3

rd

 Party Host Form 

Windows 2000 provides a Microsoft standard Telnet utility that comes pre-configured to allow users to start 
connections without logging into the domain for account validation. To help secure the ICM systems, set this to 
require users to login using Telnet by using the Windows Registry Editor. 

1.  Run the file regedit32.exe. Expand HKEY_Local_Machine\Software\Microsoft\Telnetserver\1.0. 

2.  Set NTLM to ZERO (0) to require users to login. 

3.  Set the Telnet Service to Autostart and Stopped/Started. 

Note: The Domain Controllers/DNS Servers do NOT have to be co-located with the ICM Loggers.   They 
may be installed on separate servers.