Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 1 – Troubleshooting
Cisco VCS Deployment Guide: Microsoft OCS 2007 R2, Lync 2010 and Cisco VCS X7.0
Page 73 of 104
Appendix 1 – Troubleshooting
Troubleshooting checklist for X7.x
If experiencing a problem with the OCS/Lync integration, it is recommended to go through the
following list when performing the initial faultfinding, to uncover any potential problems with the base
configuration and status of the deployment:
following list when performing the initial faultfinding, to uncover any potential problems with the base
configuration and status of the deployment:
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 OCS/Lync.
lowers the chances for interoperability issues between the video environment and OCS/Lync.
Ensure that all OCS/Lync gateway VCSs can successfully look up all OCS/Lync server A-record
FQDNs in DNS (this includes both Director and FEPs). This can be done using the
FQDNs in DNS (this includes both Director and FEPs). This can be done using the
Maintenance
> Tools > Network utilities > DNS Lookup
page on the VCS.
Ensure that all OCS/Lync servers can successfully look up all “OCS/Lync Gateway” VCS peer A-
record FQDNs and cluster FQDN in DNS. This can be done using the nslookup command-line
utility locally on each OCS/Lync server.
record FQDNs and cluster FQDN in DNS. This can be done using the nslookup command-line
utility locally on each OCS/Lync server.
If using B2BUA, verify that the B2BUA has connectivity both with the OCS/Lync environment and
the VCS (On the
the VCS (On the
Status > Applications > OCS/Lync B2BUA
page on the VC. Status = Alive is
the desired state for both), and, if using FindMe, that the B2BUA has successfully registered
FindMe accounts to OCS/Lync (on the
FindMe accounts to OCS/Lync (on the
Status > Applications > OCS/Lync users
page
Registration state = Registered and Subscription state = Subscribed are the desired states).
If using OCS Relay and a neighbor zone towards OCS/Lync, verify that the neighbor zone is up
(On the
(On the
Status > Zones
page on the VCS) and, if using FindMe, that OCS Relay has successfully
registered FindMe accounts to OCS/Lync (on the
Status > Applications > OCS Relay
page on
the VCS. Registration state = Registered and Subscription state = Subscribed are the desired
states).
states).
Problems connecting Cisco VCS Control local calls
Look at search history to check the applied transforms
1. Go to the
Search history
page (
Status > Search history
).
Search history entries report on any searches initiated from a SETUP/ARQ /LRQ in H323 and from an
INVITE/OPTIONS in SIP. The summary shows the source and destination call aliases, and whether the
destination alias was found.
INVITE/OPTIONS in SIP. The summary shows the source and destination call aliases, and whether the
destination alias was found.
2. Select the relevant search attempt. The search history for that search attempt shows:
•
the incoming call’s details
•
any transforms applied by admin or user policy or cpl
•
in priority order, zones which matched the required (transformed) destination, reporting on:
•
•
any transforms the zone may apply
•
found or not found status
•
if not found, the error code as seen in the zone’s search response
•
repeated until a zone is found that can accept the call, or all prioritized zone matches
have been attempted
have been attempted
(The search may be ‘not found’ due to lack of bandwidth or because the search from the zone resulted in
an H.323 rejection reason or a non 2xx response to a SIP request.)
an H.323 rejection reason or a non 2xx response to a SIP request.)
If the search indicates:
•
•
Found: False
•
Reason: 480 Temporarily Not Available