Cisco Cisco Unified CRM Connector 7.5 Installation Guide
96
Save the AssociatedDNsFile
After you have edited the AssociatedDNsFile to map your agent’s DN
information save the file. Be sure to save the file in the same location and
name you configured in the config.ini file or change the config.ini file for
a new location.
information save the file. Be sure to save the file in the same location and
name you configured in the config.ini file or change the config.ini file for
a new location.
Table 5-3: AssociatedDNsFile Header Abbreviations
Header Abbreviation
Meaning
PrimDN
Agent Primary DN
PosID
Agent Position ID
PeriphID Peripheral
ID
Table 5-4: AssociatedDNsFile
PrimDN - PosID - PeriphID
============================
1003 - 2003 - 5007
1003 - 2003 - 5007
1004 - 2004 - 5007
9005 - 3006 - 5003
1007 - 2007 - 5007
1007 - 2007 - 5007
Confirming the CRM Connector Configuration
After you have configured your CRM Connector you will need to test it.
Without an application, you will not be able to test CTI command
execution, but you can verify that the connector is properly configured,
connected to the CTI Server and monitoring the associated peripherals.
Without an application, you will not be able to test CTI command
execution, but you can verify that the connector is properly configured,
connected to the CTI Server and monitoring the associated peripherals.
Step 1: Start the CRM Connector Server
After changing the config.ini and activating the new configuration file, if
you are using the Administration Tool, you will need to restart the CRM
Connector Server to apply and activate the changes. You may use the
Administration Tool for this or if you are not using the administration tool,
use the services control of the Computer Management console to stop and
then start the CMService.
you are using the Administration Tool, you will need to restart the CRM
Connector Server to apply and activate the changes. You may use the
Administration Tool for this or if you are not using the administration tool,
use the services control of the Computer Management console to stop and
then start the CMService.
Step 2: Check the CTIModule log files.
The CTIModule log file will show the startup sequence for the CRM
Connector. Error! Reference source not found. below shows an
annotated startup sequence for a UICM connection with a Definity
peripheral. The last line shows that the CRM Connector is “working” with
the Definity.
Connector. Error! Reference source not found. below shows an
annotated startup sequence for a UICM connection with a Definity
peripheral. The last line shows that the CRM Connector is “working” with
the Definity.
Example 5-4: Annotated CRM Connector Startup Failure below shows a
failed startup: the CRM Connector cannot communicate with the CTI
Server because the port configuration is wrong. This also shows that if the
connection fails or is lost the CRM Connector will try to establish or re-
establish the connection at regular intervals.
failed startup: the CRM Connector cannot communicate with the CTI
Server because the port configuration is wrong. This also shows that if the
connection fails or is lost the CRM Connector will try to establish or re-
establish the connection at regular intervals.
Example 5-5: CRM Connector Monitors Agent Extension and Login Logs
below shows log snippets that show the monitoring of agent extensions,
agent ACD log in sequence and receiving a queued call.
below shows log snippets that show the monitoring of agent extensions,
agent ACD log in sequence and receiving a queued call.