Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 1 - Troubleshooting
Cisco TelePresence Multiway Deployment Guide (Cisco VCS X7.2 and Conductor XC1.2)
Page 23 of 35
Appendix 1 - Troubleshooting
Problems connecting Cisco VCS Control local calls
Look at ‘Search History’ to check the applied transforms
Search history entries report on any searches initiated from a SETUP/ARQ/LRQ in H323 and from an
INVITE/OPTIONS in SIP.
INVITE/OPTIONS in SIP.
1. Go to
Status > Search history
.
The summary shows the source and destination call aliases, and whether the destination alias
was found.
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, the zones that 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.
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.)
zone resulted in an H.323 rejection reason or a non 2xx response to a SIP request.)
3. If the Search indicates:
•
Found: False
•
Reason: 480 Temporarily Not Available
it is likely that the VCS’s zone links are not correctly set up. From the command line execute:
xcommand DefaultLinksAdd
to set up the required links for VCS default zones; also check the links for other zones that have
been created.
been created.
Each H.323 call will have 2 entries in the Search history:
•
•
the first for an ARQ to see if the endpoint can be found
•
the second for the SETUP to actually route the call
The ARQ search does not worry about links or link bandwidth, and so if links do not exist or link
bandwidth is insufficient it may still pass, even though the SETUP search will subsequently fail.
bandwidth is insufficient it may still pass, even though the SETUP search will subsequently fail.
Each SIP call will usually only have a single Search history entry:
•
•
for the SIP INVITE
Look at ‘Call History’ to check how the call progressed
1. Select
Status > Calls > History
.
The summary shows the source and destination call aliases, the call duration and whether the call
is a SIP, H.323 or SIP< -- >H.323 interworking call.
is a SIP, H.323 or SIP< -- >H.323 interworking call.
2. Select the relevant call attempt.
The entry will show the incoming and outgoing call leg details, the call’s status and the zones that
the Cisco VCS Control used to route the call.
the Cisco VCS Control used to route the call.