Cisco Cisco Expressway
Appendix 1: Troubleshooting
Checklist
If you are experiencing a problem with the Microsoft integration, we recommend that you go through the following list
when performing the initial faultfinding. It will help to uncover any potential problems with the base configuration and
status of the deployment:
when performing the initial faultfinding. It will help to uncover any potential problems with the base configuration and
status of the deployment:
■
Check the Event Log (Status > Logs > Event Log) on Expressway
■
Enable logging on FE Server
■
Enable debug on Microsoft Client
■
Ensure that video endpoints and infrastructure devices are running up-to-date software. Doing so lowers the
chances for interoperability issues between the video environment and Microsoft.
chances for interoperability issues between the video environment and Microsoft.
■
Ensure that all Gateway Expressways can successfully look up all Microsoft Server A-record FQDNs in DNS
(this includes both Director and FE Servers). You can use Maintenance > Tools > Network utilities > DNS
lookup on the Expressway.
(this includes both Director and FE Servers). You can use Maintenance > Tools > Network utilities > DNS
lookup on the Expressway.
■
Ensure that all Microsoft servers can successfully look up all Gateway Expressway peer A-record FQDNs and
cluster FQDN in DNS. You can use the nslookup command-line utility locally on each Microsoft Server.
cluster FQDN in DNS. You can use the nslookup command-line utility locally on each Microsoft Server.
■
Verify that the B2BUA has connectivity both with the Microsoft environment and the Expressway (on the
Status > Applications > Microsoft interoperability page, Status = Alive is the desired state for both).
Status > Applications > Microsoft interoperability page, Status = Alive is the desired state for both).
Tracing Calls
Tracing calls at SIP / H.323 level
1.
Go to Maintenance > Diagnostics > Diagnostic logging.
2.
Optionally, select Take tcpdump while logging.
3.
Click Start new log.
4.
(Optional) Enter some Marker text and click Add marker.
—
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.
This helps to subsequently identify the relevant sections in the downloaded diagnostic log file.
—
You can add as many markers as required, at any time while the diagnostic logging is in progress.
—
Marker text is added to the log with a "
DEBUG_MARKER
" tag.
5.
Reproduce the system issue you want to trace in the diagnostic log.
6.
Click Stop logging.
7.
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).
archive (the exact wording depends on your browser).
Microsoft Problems
Run the Lync Server ‘Best Practices Analyzer’ to help identify configurations that may be incorrect on Lync Server.
.
53
Cisco Expressway with Microsoft Infrastructure Deployment Guide
Appendix 1: Troubleshooting