Cisco Cisco Expressway
Appendix 1: Troubleshooting
Problems connecting Expressway-C 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.
2. Select the relevant search attempt.
The search history for that search attempt shows:
n
the incoming call’s details
n
any transforms applied by admin or user policy or CPL
n
and in priority order, zones which matched the required (transformed) destination, reporting on:
l
any transforms the zone may apply
l
found or not found status
l
if not found, the error code as seen in the zone’s search response
l
repeated until a zone is found that can accept the call, or all 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)
(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:
n
Found: False
n
Reason: 480 Temporarily Not Available
this could be because the Expressway zone links are not correctly set up. From the command line execute
xcommand DefaultLinksAdd
xcommand DefaultLinksAdd
to set up the required links for the Expressway's default zones; also check
the links for other zones that have been created.
Note that each H.323 call will have two entries in the search history:
n
The first for an ARQ to see if the endpoint can be found.
n
The second for the Setup to actually route the call.
The ARQ search does not depend on 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.
insufficient it may still pass, even though the Setup search will subsequently fail.
Each SIP call will usually have only a single search history entry for the SIP INVITE.
Look at call history to check how the call progressed
1. Go to
Status > Calls > History
.
The summary shows the source and destination call aliases, call duration and protocol (including any
interworking).
interworking).
2. Select the relevant call attempt and then the relevant call components.
This shows the incoming and outgoing call leg details and the zone and subzone routing.
Cisco Unified Communications Manager with Cisco Expressway (SIP Trunk) Deployment Guide (X8.6)
Page 26 of 37
Appendix 1: Troubleshooting