Cisco Cisco TelePresence Video Communication Server Expressway
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.
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. Go to
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.
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 VCS
Control used to route the call.
Control used to route the call.
Check for errors in the Event Log
Check the Event Log (
Status > Logs > Event Log
).
Tracing calls
Tracing calls at SIP / H.323 level
1. Go to
Maintenance > Diagnostics > Diagnostic logging
.
2. Optionally, select Take tcpdump while logging.
3. Click Start new log.
4. (Optional) Enter some Marker text and click Add marker.
l
The marker facility can be used to add comment text to the log file before certain activities are
performed. This helps to subsequently identify the relevant sections in the downloaded diagnostic log
file.
performed. This helps to subsequently identify the relevant sections in the downloaded diagnostic log
file.
l
You can add as many markers as required, at any time while the diagnostic logging is in progress.
l
Marker text is added to the log with a "DEBUG_MARKER" tag.
5. Reproduce the system issue you want to trace in the diagnostic log.
6. Click Stop logging.
7. Click Download log to save the diagnostic log to your local file system. You are prompted to save the file
(the exact wording depends on your browser).
8. If appropriate, click Download tcpdump to also download the tcpdump file to your local file system.
Presence not observed as expected
Presence Server status
n
Go to
Status > Applications > Presence > Publishers
to check who is providing presence information to
the VCS Presence Server.
n
Go to
Status > Applications > Presence > Presentities
to check whose presence is being watched for
(on domains handled by VCS Presence Server).
n
Go to
Status > Applications > Presence > Subscribers
to check who is watching for presence (of one
or more entities in domains handled by VCS Presence Server):
Microsoft Lync and Cisco VCS Deployment Guide (X8.1)
Page 55 of 76
Appendix 1: Troubleshooting