General Techniques
Alarms and Status Messages
When troubleshooting, first check if any alarms have been raised (Action column. Check the alarms on both Cisco Expressway-C and Cisco Expressway-E.
). If alarms exist, follow the instructions in theNext, review the status summary and configuration information (Cisco Expressway-C and Cisco Expressway-E. If any required configuration is missing or invalid, an error message and a link to the relevant configuration page is shown.
). Check the status page on bothYou may see invalid services or errors if you change the following items on Cisco Expressway, for which a system restart is required to be sure the configuration changes take effect:
-
Server or CA certificates
-
DNS configuration
-
Domain configuration
Use the Collaboration Solutions Analyzer
Procedure
Step 1 |
Use the CollabEdge validator tool to validate your MRA deployment. It simulates a Jabber client sign in process and provides feedback on the result. |
Step 2 |
If the CollabEdge validator cannot identify the issue, we suggest that you collect logs from the Cisco Expressway while attempting to sign in. Then use the log analysis component in the CSA to analyze the logs. |
Diagnostic Logs
Jabber for Windows Diagnostic Logs
The Jabber for Windows log file is saved as csf-unified.log under C:\Users\<UserID>\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Logs.
Configure Cisco Expressway Diagnostic Log Levels
Before you begin
Procedure
Step 1 |
Go to . |
Step 2 |
Select the recommended logs for the problem you are experiencing. You can find these using the Log Advisor Tool: https://logadvisor.cisco.com/logadvisor/collaboration/unifiedcommunications/mra. |
Step 3 |
Click Set to debug. |
Create a Diagnostic Log Capture
Procedure
Step 1 |
Go to . |
Step 2 |
(Optional) Select Take tcpdump while logging. |
Step 3 |
Click Start new log. |
Step 4 |
(Optional) Enter some Marker text and click Add marker.
|
Step 5 |
Reproduce the system issue you want to trace in the diagnostic log. |
Step 6 |
Click Stop logging. |
Step 7 |
Click Collect log. |
Step 8 |
When the log collection completes, click Download log to save the diagnostic log archive to your local file system. You are prompted to save the archive (the exact wording depends on your browser). |
After You Create Logs
If you want to download the logs again, you can re-collect them by using the Collect log button. If the button is grayed out, first refresh the page in your browser.
After you have completed your diagnostic logging, return to the Support Log configuration page and reset the modified logging modules back to INFO level.
Check DNS Records
Procedure
Go to .The SRV record lookup includes those specific to H.323, SIP, Unified Communications and TURN services.
The DNS lookup includes the following SRV services that are used for Unified Communications:
|
Check that the Cisco Expressway-E is Reachable
Procedure
Ensure that the FQDN of the Cisco Expressway-E is resolvable in the public DNS. The FQDN is configured at and is built as <System host name>.<Domain name>. |
Check Call Status
Call status information can be displayed for both current and completed calls.
The same set of call status information is also shown on the Calls by registration page (accessed via the Registration details page).
If the Cisco Expressway is part of a cluster, all calls that apply to any peer in the cluster are shown, although the list is limited to the most recent 500 calls per peer.
Procedure
Step 1 |
If you wish to get information about the current calls, go to the Call status page ( ). The Call status page lists all the calls currently taking place to or from devices registered with the Cisco Expressway, or that are passing through the Cisco Expressway. |
Step 2 |
If you wish to get information about the completed calls, go to the Call history page ( ). The Call history page lists all the calls that are no longer active. The list is limited to the most recent 500 calls, and only includes calls that have taken place since the Cisco Expressway was last restarted. |
Mobile and Remote Access Call Identification
The call status and call history pages show all call types—Unified CM remote sessions (if Mobile and Remote Access is enabled) as well as Cisco Expressway RMS sessions.
To distinguish between the call types, you must drill down into the call components. Mobile and Remote Access calls have different component characteristics depending on whether the call is being viewed on the Cisco Expressway-C or Cisco Expressway-E:
-
On the Cisco Expressway-C, a Unified CM remote session has three components (as it uses the B2BUA to enforce media encryption). One of the Cisco Expressway components routes the call through one of the automatically generated neighbor zones (with a name prefixed by either CEtcp or CEtls) between Cisco Expressway and Unified CM.
-
On the Cisco Expressway-E, there is one component and that routes the call through the CollaborationEdgeZone.
If both endpoints are outside of the enterprise (that is, off premises), you will see this treated as two separate calls.
Rich Media Sessions (Cisco Expressway Only)
If your system has a rich media session key installed and thus supports business-to-business calls, and interworked or gatewayed calls to third-party solutions and so on, those calls are also listed on the call status and call history pages.
Devices Registered to Unified CM via Cisco Expressway
Identify Devices in Unified CM
Procedure
Step 1 |
In Unified CM, go to and click Find. |
Step 2 |
Check the IP Address column. Devices that are registered via Cisco Expressway will display the IP Address of the Cisco Expressway-C it is registered through. |
Identify Provisioning Sessions in Cisco Expressway-C
Procedure
Step 1 |
In Cisco Expressway-C, go to . |
Step 2 |
In the Advanced status information section, click View provisioning sessions. This shows a list of all current and recent (shown in red) provisioning sessions. |
Ensure that Cisco Expressway-C is Synchronized to Unified CM
Changes to Unified CM cluster or node configuration can lead to communication problems between Unified CM and Cisco Expressway-C. This includes changes to the following items:
-
Number of nodes within a Unified CM cluster
-
Host name or IP address of an existing node
-
Listening port numbers
-
Security parameters
-
Phone security profiles
You must ensure that any such changes are reflected in the Cisco Expressway-C. To do this:
Procedure
Step 1 |
On Cisco Expressway, go to . |
Step 2 |
Rediscover all Unified CM and IM and Presence Service nodes. |
Check MRA Authentication Status and Tokens
Procedure
Step 1 |
(Optional) To check and clear standard (non-refresh) OAuth user tokens, go to .This could help identify problems with a particular user's OAuth access. |
Step 2 |
(Optional) To check statistics for MRA authentication, go to .Any unexpected requests or responses on this page could help identify configuration or authorization issues. |