Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 1 – Troubleshooting
Cisco VCS Deployment Guide: CUCM v6.1, 7 and 8 with Cisco VCS X7.1 using a SIP trunk
Page 29 of 53
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
and 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
(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)
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)
If the search indicates:
Found: False
Reason: 480 Temporarily Not Available
this could be because the Cisco VCS Control’s zone links are not correctly set up. From the command
line execute:
line execute:
xcommand DefaultLinksAdd
to set up the required links for the Cisco VCS Control’s default zones; also check the links for other
zones that have been created.
zones that have been created.
Note: Each H.323 call will have two 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.