Cisco Cisco TelePresence Video Communication Server Expressway
Appendix 12 – Cisco TelePresence MCU configuration
Cisco VCS Deployment Guide: Microsoft Lync 2010 and Cisco VCS X6.1
Page 73 of 81
Appendix 12 – Cisco TelePresence MCU
configuration
configuration
MCU connectivity with Lync Server and Cisco VCS
MCUs must be registered to Cisco VCS in order for Lync callers to be able to join conferences.
OCS Relay
When OCS Relay is used, FindMe™ accounts can be set up for static conferences (for example if the
In-Call presence status of the conference is wanted). For Ad hoc conferences (for example those
created and used by Multiway™), a static route to the MCU’s domain must be set up in order that calls
can be routed to non FindMe™ destinations.
In-Call presence status of the conference is wanted). For Ad hoc conferences (for example those
created and used by Multiway™), a static route to the MCU’s domain must be set up in order that calls
can be routed to non FindMe™ destinations.
Configuration of Cisco VCS and MCUs registered to Cisco VCS
The configuration of both the Cisco VCS and the MCU documented in the ‘Cisco VCS Multiway™
deployment guide’ is the correct configuration for Cisco VCS and MCU when working with Lync Server
Please see that document for further details.
deployment guide’ is the correct configuration for Cisco VCS and MCU when working with Lync Server
Please see that document for further details.
Configuration of Lync Server to support Lync clients creating /
joining ad hoc conferences
joining ad hoc conferences
Ensure that Lync Server has a static domain route to the MCU’s domain.