Cisco Cisco Expressway
3. (Optional) Enter some Marker text and click Add marker.
l
The marker facility can be used to add comment text to the log file before certain activities are
performed. This helps to subsequently identify the relevant sections in the downloaded diagnostic log
file.
performed. This helps to subsequently identify the relevant sections in the downloaded diagnostic log
file.
l
You can add as many markers as required, at any time while the diagnostic logging is in progress.
l
Marker text is added to the log with a "DEBUG_MARKER" tag.
4. Reproduce the system issue you want to trace in the diagnostic log.
5. Click Stop logging.
6. Click Download log to save the diagnostic log to your local file system. You are prompted to save the file
(the exact wording depends on 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.
Checking DNS records
You can use the Expressway's DNS lookup tool (
Maintenance > Tools > Network utilities > DNS
lookup
) to assist in troubleshooting system issues. The SRV record lookup includes those specific to
H.323, SIP, Unified Communications and TURN services.
Note that performing the DNS lookup from the Expressway-C will return the view from within the enterprise,
and that performing it on the Expressway-E will return what is visible from within the DMZ which is not
necessarily the same set of records available to endpoints in the public internet.
and that performing it on the Expressway-E will return what is visible from within the DMZ which is not
necessarily the same set of records available to endpoints in the public internet.
The DNS lookup includes the following SRV services that are used for Unified Communications:
n
_collab-edge._tls
n
_collab-edge._tcp
n
_cuplogin._tcp
n
_cisco-uds._tcp
Checking call status
Call status information can be displayed for both current and completed calls:
n
Current calls: the
Call status
page (
Status > Calls > Calls
) lists all the calls currently passing through
the Expressway.
n
Completed calls: the
Call history
page (
Status > Calls > History
) 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 Expressway was last restarted.
the Expressway was last restarted.
If the 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.
is limited to the most recent 500 calls per peer.
Mobile and remote access calls have different component characteristics depending on whether the call is
being viewed on the Expressway-C or Expressway-E:
being viewed on the Expressway-C or Expressway-E:
n
On an Expressway-C, a Unified CM remote session will have 3 components (as it uses the Encryption
B2BUA to enforce media encryption). One of the Expressway components will route the call through one of
the automatically generated neighbor zones (with a name prefixed by either CEtcp or CEtls) between
Expressway and Unified CM.
B2BUA to enforce media encryption). One of the Expressway components will route the call through one of
the automatically generated neighbor zones (with a name prefixed by either CEtcp or CEtls) between
Expressway and Unified CM.
Unified Communications: Mobile and Remote Access via Cisco Expressway Deployment Guide (X8.1.1)
Page 31 of 36
Appendix 1: Troubleshooting