Contributed by Praveen Alampally and Arundeep Nagaraj, Cisco TAC Engineers.
Prerequisites
Requirements
Cisco recommends that you have knowledge of these topics:
- Webex Contact Center (formerly Customer Journey Platform (CJP))
- Contact Center and Voice Over Internetworking Protocol (VoIP)
Note: This document is targeted towards customers and partners, who have deployed Webex Contact Center to their network infrastructure.
Components Used
This document is not restricted to specific software or hardware versions.
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, ensure that you understand the potential impact of any command.
Collect Generic Information for all Webex Contact Center Issues
Problem Description - Gather complete information bout the exact issue. Include information, such as how many users are affected, the exact timestamp, and so on.
Setup Type - Is this a new deployment?
Configuration Changes - Any recent changes on the Webex Contact Center Dashboard or the network?
Business Impact - Define the exact business impact. Associate it to a number, if possible. For example, this issue impacts 20 agents, 9 out of 10 calls to the call center fail, and so on.
Tenant Name - This is found on the top right corner of the Dashboard page.
Tenant Name
Customer Org ID: If Deployed through Control Hub
Common Issues
Type of Issue | Description | Details | Data to Collect |
Inbound Call Failures | These are related to the inbound calls, where the caller dials into the system and experiences Interactive Voice Response (IVR) treatment for self-service, before their interaction with agents. |
|
|
Outbound Call Failures | These are related to the outbound calls, where the agent establishes the outbound call from Applet. The first call leg is established on the agent's phone. After the agent's leg is established, the call is attempted to the external party. |
|
|
Call Quality Issues | Webex Contact Center allows endpoint agnostic Automatic Call Distribution (ACD) to agents. The agent's phone can be a mobile phone, desk phone, or a third-party soft client. When call quality issues occur, it needs investigation from all the parties involved in the call flow. The best practice is to report the call quality issue within 24 hours as the quality metrics of the call are logged for 24 hours. We need multiple examples due to the nature of the issue and multiple parties involved in the call flow. |
|
|
Agent Applet / Desktop Issues |
Agent Applet (AP) is the web user interface (UI) for the agents to perform day-to-day operations on Voice, Email, Chat, etc. If agent session loses connectivity for more than 120 seconds, they are logged out. If multiple browser tabs / windows or desktop applications are in use, they can attribut to the poor performance of the Agent Applet / Desktop. |
|
|
Multimedia Issues - Chat | Chat is part of the MultiMedia (MM) Omni-Channel feature of Webex Contact Center. Ensure that Chat is enabled for the Tenant and the agents are assigned to the associated queue in MMAdmin. |
|
|
Multimedia Issues - Email | Email is part of the MultiMedia (MM) OmniChannel feature of Webex Contact Center. Ensure that Email is enabled for the Tenant and the agents are assigned to the associated queue in MMAdmin. |
|
|
Reporting Issues (Analyzer or Legacy) | Real-Time Reports and Historical Reports constitute Legacy Reports of Webex Contact Center. Analyzer is the newest reporting solution available, whoch can be customized to a great extent. The data between Analyzer and Legacy Reports do not match exactly as the data is computed differently. There are multiple customization options available for Sandard Reporting. |
|
|
Capture Browser Logs
Browser logs are a great source of information to help understand a browser's behavior. There are times when TAC asks you to provide browser logs to understand the communication and data exchange between the Agent Desktop and the server. Browser logs constitute Console logs and Network logs.
Enable timestamps on your browser
Before you collect the browser's logs (or console logs) from Chrome or Firefox, enable timestamps on your browser. This helps to synchronize client and server timings.
Enable timestamps and preserve logs upon navigation.
Chrome
- From the menu bar, choose View > Developer > Developer Tools.
- Click the Customize and Control Dev Tools button (3 vertical dots).
- Click Settings.
- Under Preferences, check these checkboxes:
- Log XML HTTP Requests
- Show timestamps
- Preserve log upon navigation
Firefox
- From the menu bar choose Tools > Web Developer > Toggle Tools.
- Clock Customize Developer Tools and Get Help.
- Click Settings (the cog button)
- Check the Enable timestamps check box.
Collect Console Logs
The console gives you information about a page, while that page is opened. Ultimately, the messages you see in the console, either come from the web developers, who built the page, or the browser itself. When someone logs a message to the console, they can indicate the importance, or severity level of the message.
Chrome or Firefox
- Open the Developer Tools (right-click anywhere on the browser and choos Inspect).
- Perform the steps of the scenario to capture.
- Navigate to the Console Tab.
- Based on your browser:
- Right-click and choose Save as (notepad tex file).
- Right-click and choose Select All. Right-click and choose Copy.
- - Paste that into a text file. - Attach the text files to your support ticket.
Internet Explorer (IE)
- Press the F12 key to open the Developer Tools Widows.
- In the Console tab, enter the AgentSDK.EnableIE11DebugLogging(true) command to enable extra logging.
- Perform the steps of the scenario to capture.
- From the Console tab, right-clock and choose Copy All.
- Enter the AgentSDK.EnableIE11DebugLogging(false) command to disable extra logging:
Collect Hyper Text Transfer Protocol Archive format (HAR) Logs
The HTTP Archive format, or HAR, is a JSON-format archive for logging of a web browser's interaction with a site.
Chrome of Firefox
- Open Google Chrome and navigate to the page where the issue occurs.
- Open the Developer Tools (right-clock anywhere on the browser and choose inspect).
- Look for a round Record button (
) in the upper-left corner of the Network tab; red indicates recording is in progress and grey indicates it is disabled.
- Check the Preserve log check box.
- Click the Clear button (
) to clear out any previous logs from the Network tab.
- Perform the steps of the scenario to capture.
- Right-clock anywhere on the grid of network requests, choose Save as HAR with Content or Save all as HAR, and save the file to your computer.
How to generate a HAR on Microsoft Edge or Miscrosoft Internet Explorer
- Browse the URL where you wish to start the capture.
- Navigate to Developer Tools (use F!@ as a shortcut) and click the Network tab.
- Perform the steps of the scenario to capture.
- Click Export as HAR.
- Click Save As... to save the HAR file (or Extensible Markup Language (XML) if you use an older version of Internet Explorer.