Cisco Cisco TelePresence Video Communication Server Expressway

Appendix 1 – Troubleshooting 

Calls between endpoints and OCS via the UC gateway where the Cisco AM GW is not involved 
consist of a single call with two call legs. 

 

Leg a) between the endpoint and Cisco VCS 

 

Leg b) between Cisco VCS and OCS 

 

Calls between endpoints and OCS via the UC gateway where the Cisco AM GW is involved consist of 
two calls and four call legs. 

 

Leg a) between the endpoint and Cisco VCS 

 

Leg b) between Cisco VCS and the Cisco AM GW 

 

Leg c) between the Cisco AM GW and Cisco VCS 

 

Leg d) between Cisco VCS and OCS 

 

Troubleshooting calls between Cisco VCS and OCS is very much the same as troubleshooting any 
Cisco VCS / OCS call scenario. See the Troubleshooting section in “Cisco VCS Deployment Guide - 
Microsoft OCS 2007 (R1 and R2) and Cisco VCS Control (X5)”. 

As a starting point, consider Search history and Status > Calls on the Cisco VCS. 

Check that the calls are being made as expected 

This will give the MOC client’s view of the call. 

This will provide OCS’s view of communications between OCS and Cisco VCS and OCS and MOC. 

As a starting point, consider Search history and Status > Calls on the Cisco VCS. 

Check that the calls are being made as expected 

The Event log (Maintenance > Logs > Event log) shows key events including incoming calls, 
connecting calls and disconnecting calls and error events. 

Note: the oldest event information is shown on page 1 – the opposite order to the event information on 
Cisco VCS where page 1 is the most recent information. 

The level of tracing (to save more or less information in the Event log) can be configured in the Event 
capture filter page (Maintenance > Logs > Event capture filter). 

Cisco VCS Deployment Guide: Microsoft OCS 2007 R2, Cisco VCS Control X5.1 
and Cisco AM GW 1.0 

Page 17 of 24