Manual

Appendix 1 - Troubleshooting

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.

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.

(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

it is likely that the Cisco VCS’s zone links are not correctly set up. From the command line execute:

xcommand DefaultLinksAdd

to set up the required links for Cisco VCS default zones. Also check the links for other zones that have

been created.

Not

e: Each H.323 call will have 2 entries in the Search History:

 An ARQ to see if the endpoint can be found.

 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.

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

Go to the Call history page (Status > Call 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.

2. Select the relevant call attempt.

The entry shows the incoming and outgoing call leg details, the call’s status and the zones that the Cisco

VCS Control used to route the call.

Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2 Page 64 of 92