Cisco Cisco Expressway
Appendix 1: Troubleshooting
Troubleshooting checklist
If you are experiencing a problem with the Lync 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:
list when performing the initial faultfinding. It will help to uncover any potential problems with the base
configuration and status of the deployment:
n
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 Lync.
the chances for interoperability issues between the video environment and Lync.
n
Ensure that all "Lync gateway" Expressways can successfully look up all Lync Server A-record FQDNs in
DNS (this includes both Director and FEPs). You can use
DNS (this includes both Director and FEPs). You can use
Maintenance > Tools > Network utilities >
DNS lookup
on the Expressway.
n
Ensure that all Lync servers can successfully look up all “Lync gateway” Expressway peer A-record
FQDNs and cluster FQDN in DNS. You can use the nslookup command-line utility locally on each Lync
Server.
FQDNs and cluster FQDN in DNS. You can use the nslookup command-line utility locally on each Lync
Server.
n
Verify that the B2BUA has connectivity both with the Lync environment and the Expressway (on the
Status > Applications > Lync B2BUA
page, Status = Alive is the desired state for both).
Check for errors in the Event Log
Check the Event Log (
Status > Logs > Event Log
).
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.
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.
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 to your local file system. You are prompted to save the file
(the exact wording depends on your browser).
8. If appropriate, click Download tcpdump to also download the tcpdump file to your local file system.
Microsoft Lync and Cisco Expressway Deployment Guide (X8.1)
Page 47 of 63
Appendix 1: Troubleshooting