Guest

Cisco Unified Contact Center Express

Agents Not Displayed on Cisco Supervisor Desktop

Document ID: 63307

Updated: Jan 31, 2013

   Print

Introduction

This document describes the steps to take when one of these problems occurs with agents in a Cisco IP Contact Center (IPCC) Express environment:

  1. Cisco Agent Desktop (CAD) agents who are logged in and processing calls possibly do not appear in Cisco Supervisor Desktop (CSD).

  2. CAD agents appear in CSD but then quickly disappear.

  3. CAD agents are unable to Chat with CSD users.

  4. Messages appear in the Event Viewer logs on the UCCX server. This is an example:

    Event Type:     Warning
    Event Source:     FCCServer
    Event Category:     None
    Event ID:     3
    Date:          1/21/2010
    Time:          2:01:52 PM
    User:          N/A
    Computer:     TACUCCX1
    Description:
    FCCS3008 Network communication error <COMM_FAILURE> sending message to 
       application <Agent1>.  
    The application will be logged out.

Prerequisites

Requirements

Readers of this document should have knowledge of these topics:

  • Cisco Customer Response Solutions (CRS)

  • Cisco Agent Desktop

  • Cisco Supervisor Desktop

Components Used

The information in this document is based on these software and hardware versions:

  • Cisco CRS version 3.x and later

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to the Cisco Technical Tips Conventions.

Problem

One of these problems occurs with agents in a Cisco IP Contact Center (IPCC) Express environment:

  1. Cisco Agent Desktop (CAD) agents who are logged in and processing calls possibly do not appear in Cisco Supervisor Desktop (CSD).

  2. CAD agents appear in CSD but then quickly disappear.

  3. CAD agents are unable to Chat with CSD users.

  4. Messages appear in the Event Viewer logs on the UCCX server:

    Event Type:     Warning
    Event Source:     FCCServer
    Event Category:     None
    Event ID:     3
    Date:          1/21/2010
    Time:          2:01:52 PM
    User:          N/A
    Computer:     TACUCCX1
    Description:
    FCCS3008 Network communication error <COMM_FAILURE> sending message to 
       application <Agent1>.  
    The application will be logged out.

Cause

CAD and CSD use a proprietary chat protocol in order to communicate agent states and chat messages in a client server architecture. These messages are sent and received by the Cisco Desktop Chat Service on the UCCX server and distributed to CAD and CSD users as necessary. If the Cisco Desktop Chat Service is unable to make a connection to the CAD and/or CSD applications over the ports used by this protocol, the previous symptoms are the result.

These ports must be open throughout the transit path in order for the Chat protocol to work correctly:

  • UCCX Server - TCP 59000

  • CAD - TCP 59020

  • CSD - TCP 59021

  • CAD (59020) ------ (59000) UCCX Server (59000) ------ (59021) CSD

Solution

Complete these steps in order to resolve this issue:

  1. If CAD is installed on a Citrix or Microsoft Terminal Services environment, make sure that the PostInstall.exe utility is configured for this deployment type. Complete these steps:

    1. On the Citrix or MTS server, open Program Files > Cisco > Desktop > bin > PostInstall.exe.

    2. Confirm that the IP addresses shown are those of the UCCX server(s).

    3. In the left panel, choose Thin Client Environment.

    4. Choose Yes in the panel on the right.

    5. Click Apply.

    6. Restart all CAD and CSD instances.

  2. If the UCCX version is 7.0(1), verify that the CAD application does not experience Cisco bug ID CSCtd75811 (registered customers only) .

    1. When these symptoms are present, open Windows Task Manager on the Cisco Agent Desktop PC.

    2. Click on the Processes tab.

    3. Check the Show processes from all users box.

    4. Sort the list of processes by Image Name.

    5. If multiple instances of agent.exe are present, upgrade UCCX to a version which contains the fix to Cisco bug ID CSCtd75811 (registered customers only) .

  3. If the UCCX version is 7.0(1), verify that the system path includes WebAdminLib.dll. To do so, choose Web CDA > Services Configuration > Enterprise Data > Fields. Complete the workaround mentioned in the CAD Troubleshooting Guide if this error is returned:

    CDAUI1000 Error while trying to load data. 
    Ensure that the system path includes the location of the WebAdminLib.dll.
  4. Verify that the Agent is assigned to the correct team in Web CDA > Personnel > Agents. Agents can appear to be assigned to different teams in Web CDA than AppAdmin because Directory Services are not synchronized. Manually synchronize Directory Services from the Web CDA > Services Configuration or restart the Cisco Desktop Sync Service from AppAdmin Control Center.

  5. Verify that all Desktop Services are running in AppAdmin Control Center. If any of these services show in a Stopped, Partial Service or Invalid state, contact Cisco Technical Assistance Center (TAC) for assistance. This is the list of services that should be running:

    • Cisco Desktop Call/Chat Service

    • Cisco Desktop Enterprise Service

    • Cisco Desktop LDAP Monitor Service

    • Cisco Desktop License and Resource Manager Service

    • Cisco Browser and IP Phone Agent Service - if you use CAD-BE or IPPA

    • Cisco Desktop Recording & Statistics Service

    • Cisco Desktop Sync Service

  6. Test connectivity over the previously mentioned ports between the UCCX server and CAD and the UCCX server and CSD.

    1. On the UCCX server, open a Command Prompt window.

    2. Start the CAD or CSD application on the client PC.

    3. Issue these commands and substitute the correct IP addresses:

      Telnet <CSD IP Address> 59021
              Telnet <CAD IP Address> 59020

      Note: A failure message is denoted with the appearance of this message in the Command Prompt Window.

      Connecting to 192.168.xxx.xxx Could not open a connection to host 
         on port 59000:Connect failed
    4. If no failure message is received, test connectivity from the CSD and CAD PCs to the UCCX server.

      1. On the CAD or CSD PC, open a Command Prompt window.

      2. Issue this command, and substitute the correct IP address of the master UCCX server:

        Telnet <UCCX IP Address> 59000
      3. If no failure message is received, monitor the open Telnet connection when these symptoms appear.

    5. If a failure message appears immediately or while you monitor the open Telnet connection, examine these:

      1. If antivirus software is running on the CAD or CSD PC, turn it off including real time scanning if applicable.

      2. If Windows Firewall is enabled, turn it off in the Windows Firewall section of the Control Panel.

      3. Verify that the above mentioned ports are not blocked via Group Policy.

      4. Verify that any network firewall in the transit path allows traffic over the previously mentioned ports.

      5. If CAD and CSD is reachable only over VPN, make sure the VPN headend and all other security devices allow traffic over the above mentioned ports.

      6. Verify Cisco Security Agent (CSA) does not block the previously mentioned ports if it is installed.

      7. Verify that the network ports in the transit path are free of errors.

      8. If the CAD or CSD PC has mutliple NICs and IP addresses, disable the unused NIC.

      9. Verify that no third party applications on the CAD or CSD PC conflict with the UCCX software and prevent communication on the previously mentioned ports. Perform these steps:

      1. To do so, build a test PC with the base version of the operating system installed such as Windows Vista, XP and so forth. Avoid the use of a pre-packaged corporate image.

      2. Install only CAD or CSD on this test PC.

      3. Test to see if the previously mentioned symptoms exist.

      4. If not, add each application on the production PC to the test PC incrementally, and test the CAD and CSD functionality between each installation.

Problem

Cisco Agent Desktop agent appears and disappears from the Cisco Supervisor Desktop

Intermittently Agent begins to disappear and appear on the Supervisor Desktop under Team Agent state Report.

Solution

This problem is caused when multiple threads do not exit correctly under Agent desktop PC. When the CHAT communication on TCP Port 59000 and 59020 between Client and Server has been lost due to network interruption/outage. CAD is unable to recover from this and creates multiple Agent.exe instances.

Exit out affected Cisco Agent Desktop application and launch CAD again.

Problem

PERERR_CM_REDIRECT_CALL_UNKNOWN_DESTINATION message

In PIM log, there is a PERERR_CM_REDIRECT_CALL_UNKNOWN_DESTINATION message. This happens when the agent does not pick up the call and the call goes back into queue, the agent becomes not ready then the Request operation failed error message appears.

Solution

Complete these steps in order to resolve this issue:

  1. Set FilterOutRecoveryOnTimerExpiry to1 and restart the services on the PG at this location:

    HKLM\SOFTWARE\Cisco Systems, Inc.\icm\<instance
    name>\PG1A\PG\CurrentVersion\JGWS\jgw1\JGWData\Dynamic
  2. Set cvp time out with this parameter: setRnaTimeOut *:15

Problem

Navigation errors

During the navigation of different pages of Cisco Desktop Administrator, one of these errors appears:

CDAUI1000 Error while trying to load data.
  Ensure that the system path includes the location of the WebAdminLib.dll

Or

The requested resource () is not available.

../63307/sup-dsktp-no-display-01.gif

Solution

Complete these steps in order to resolve the issue:

  1. In Control Panel, launch the System utility.

  2. On the Advanced tab, click Environment Variables.

  3. From the list of System Variables, choose Path and click Edit.

  4. In the variable value field, locate the C:\Program Files\Cisco\Desktop\bin string. Use cut and paste to move it to the beginning of the variable value string. This results in the DLL that is accessed from the correct location.

  5. Click OK and close System utility.

  6. Stop the Cisco Unified Node Manager.

  7. On the Unified CCX server, delete the teamadmin folder from these locations:

    • C:\Program Files\wfavvid\tomcat_appadmin\webapps

    • C:\Program Files\wfavvid\tomcat_appadmin\work\catalina\localhost

  8. Restart the Unified Node Manager, and wait two minutes.

    Note: After you complete these steps you should be able to access Cisco Desktop Administrator and navigate to the different pages.

Problem

Unable to see all agents on monitor and in log

You are unable to see all agents in the monitor screen and in the log, this error message appears:

2010-09-24 07:37:44.404 DEBUG [0xeec] FCCClientAPI::corbaInit: This client
is not running in Citrix/MTS mode. A static port number will be used.

2010-09-24 07:37:44.388 DEBUG [0xeec] FCCClientAPI::corbaInit: Unable to open
registry:HKEY_LOCAL_MACHINE\SOFTWARE\Spanlink\CAD\Chat Server API\Setup.Looking
 in LDAP.

This issue is documented in Cisco bug ID CSCsa19971 (registered customers only) .

Solution

Complete these steps in order to set the registry key on the Citrix server and resolve this error:

  1. Choose Start > Run and type regedit.

  2. Create the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Spanlink\Chat Server API\Setup .

  3. In that key, create a DWORD value named OmniOrbUsePort.

  4. Set the value to 0.

  5. Restart the Citrix server.

Problem

CAD agents are not displayed on CSD

The agents that up in CSD depends on the software communication. CAD software communicates to CSD about its state through UCCX. If communication breaks any where in this communication path, complete these steps in order to resolve the issue:

Note: This can occur because the sync is broken as the CSD shows no service after you choose the team.

Solution

  1. Stop the node manager.

  2. Restart the CTI manager in all the Cisco CallManager in the cluster.

  3. Start the node manager on the master IPCCX and wait until it appears.

  4. Start the node meager in the sub IPCCX.

Problem

Agents names do not appear in the supervisor desktop due to misconfigured ODBC

This can happen if ODBC DSN is created without any passwords. When you test the ODBC DSN, you need to enter the password and then test the connection. In this example, CTIOS Server tried to login without a password and thus ODBC connection failed. Since the ODBC connection failed, the SQL Queries in the CTIOS Registry was not done at all. .

Solution

First make sure the ODBC connection is set up correctly and works, and then restart the CTIOS Server in order to resolve this issue.

Problem

UCCX has 6 agents logged in, but only 4 appear in the Supervisor Desktop

The Cisco Supervisor Desktop shows six agents logged in under the Real Time Displays section of the application window, but only four of the six that are logged in show up in the Agents window.

../63307/sup-dsktp-no-display-02.gif

Solution

Two agents were logged out of the Cisco chat service because ports were blocked from the workstation to UCCX server. You need to verify that the ports are not blocked in order to resolve this issue.

Problem

Multiple Agent.exe Instances Created Cause CAD Agent to Disappear

Agents intermittently disappear and re-appear from CSD. CAD loses connectivity to the call/chat service and does not recover properly. Multiple instances of agent.exe appear on the agent PC processes list in Task Manager. Netstat on the agent PC shows multiple connections to the server.

Solution

The solution is to apply a fixed version of the Splkstd.dll file to each of the CAD desktops as a workaround for this issue. There are two solutions for this issue:

  1. Kill the agent.exe processes on the Task Manager and open CAD again, on the desktop computer of the agent. Then you see the agents on the Supervisor Desktop. This is a quick fix but not a permanent solution.

  2. On the workstation of the agent, choose C: > Program Files > Cisco > Desktop > bin directory. Then complete these steps:

    1. Rename the existing SplkStd.dll, for example SplkStd.old.

    2. Extract the patched SplkStd.dll file to the renamed path.

    3. Reboot the agent workstation.

Note: This is documented in the Cisco bug ID CSCtd75811 (registered customers only)

Problem

Agents do not appear on CSD

Agents do not appear on CSD at all.

Solution

Complete these steps in order to resolve this issue:

  1. In order to navigate to CDA, choose Start > Programs > Cisco > Desktop > Admin.

  2. Click on Call Center 1 and from the menu, choose Desktop Administrator > Side A.

  3. On the next window if you have not previously configure a password, just click on login (no password needed).

  4. Choose Services configuration > Synchronize Directory service and click on the Synchronize button.

  5. Restart the Cisco Desktop service.

Problem

Real time display in CSD does not update

The real time display in Cisco Supervisor Desktop does not update under the root Skill group area for any group. You are able to see agent details if you drill down into a specific group.

  1. Set the debug threshold on FCCserver and FCRasSvr in the 'C:/Program Files/Cisco/Desktop/config' folder on both the PGs. Ensure the debug threshold is set for the supervisor PC also.

  2. Once the Agent and Supervisor login and statistical display problem is observed, collect the FCCserver, Rascalserver, and Supervisor log and debug.

  3. In order to ensure that you can complete the sync, restart the Cisco Sync Service from Windows Services on both the PGs.

After the Cisco Sync Service has been restarted, check the logs:

Line 6781: 2012-06-25 09:42:37:111 INFO DESK1039 Error getting skill stats from 
enterprise server: <-20>.
        Line 6785: 2012-06-25 09:47:08:863 ERROR DESK3038 ChatAPI DropPresenceUser  
   failed.
Line 6889: 2012-06-25 09:47:15:570 ERROR LRMS2001 The LRM client failed to 
connect to any service.

2012-06-25 09:49:34:164 WARN FCCS3008 Network communication error <TRANSIENT>
sending message to application <AGENT_DESKTOP_012918>.  The application will be
logged out.

Note: Enter the netstat -p tcp -b -n command on the CAD server side in order to show which .exe uses these ports.

From the logs it was determined that CHAT and Enterprise services in UCCE use different ports than those mentioned when connected to the CAD clients:

  • Chat TCP 5900 to connect to the Agent TCP 37350 to connect to the Supervisor.

  • Enterprise TCP 59004 to connect to the Agent client.

In order to resolve this issue, restart the Cisco Enterprise Service. If that does not fix the issue, restart the PG servers.

Problem

Some Common issues were Agents not displayed

When more than 10 skills were assigned to an agent, sync replaced the data with that received in the last update from CTI. Supervisor would then only show what it had received in the most recent update from sync. So, in CSD kill Groups - Skill Agent Statistics Display report does not show correct agents for the skills selected on the left of the pan. This is documented in the Cisco bug ID CSCsm81553 (registered customers only) .

When a team or skill is chosen that contains no records, a supervisor would show all members of that team. Reports do work correctly after the sync patch is installed, when a valid team or skill is selected. This is documented in the Cisco bug ID CSCsm81587 (registered customers only) .

Related Information

Updated: Jan 31, 2013
Document ID: 63307