Cisco Cisco Unified CRM Connector 7.5 Installation Guide

 

94  

the side A and side B host names and ports.  In a simplex 
environment, only configure side A. 

3.  You will need to know the peripheral type.  If you are 

implementing a multi-site that has different ACD types you will 
need to capture all peripheral types. 

4.  You will need to know the peripheral ID for the ACD (PIM).  If 

multiple peripherals are implemented you will need to record each 
peripheral ID. 

5.  For Nortel Meridian and Symposium sites AND for multiple 

peripheral sites configured as a single CRM Connector instance 
you will need a list of agent DNs and their associated ACD DN 
and the Peripheral ID for the agents and ACDs.  

6.  You should use meaningful channel names, even if you are only 

configuring one instance.  You will need to assign both a module 
name AND a channel name.   You will need to define a unique 
module and channel names for each CRM Connector instance. 

If you are using a text editor, backup the current config.ini file.  It is good 
practice to always edit a copy of a file to guard against accidental changes 
that affect your system’s operation. 

Use the Administration Tool if you have installed it, or simply navigate to 
the config.ini file and open it with a text editor. 

This may already be configured, because the default config.ini file 
includes the module class and module definitions for the CRM Connector.  
Also the CRM Connector Server implementation chapter included these 
definitions in the sample config.ini.  However we will repeat those steps 
here. 

1.  In the module manager create the module class definition for the 

CRM Connector.  This is: 

. 

2.  In the module manager create this module instance, based on the 

module manager class:  

. 

Note:  If you implemented the NULL CTI connector you will need to 
comment out its module instance.  It is good practice to comment out the 
module class definition for unused components but this is not required. 

Warning:  If you have duplicate instance definitions with the same 
module name configured the first defined instance will be implemented.  
Therefore given the following lines in this order,