Appendix H - Deployment Into Microsoft Environments
Polycom®, Inc. 984
Lync 2013 SVC Connectivity to RealPresence
Collaboration Servers
Microsoft’s H.264 SVC codec has replaced RTV as the preferred codec for enabling video calls between
Lync 2013 clients (endpoints) and Polycom endpoints, in the same as manner as RTV replaced H.263 as
the preferred codec in previous versions. For backward compatibility, RTV is still supported for both Lync
2010 and 2013.
Although similar, the Microsoft H.264 SVC codec is not compatible with, and should not be confused with
Polycom’s standards-based H.264 and SVC implementation.
The Collaboration Server considers Lync 2010 and H.264 SVC Lync 2013 clients to be AVC endpoints. The
administrator must set the Conferencing Mode in the Conference Profile to CP (Continuous Presence) to
enable H.264 SVC Lync clients to connect to the conference.
Deployment Architectures
Two Deployment Architectures are presented as examples. Both require that a Polycom RealPresence
Distributed Media Application (DMA) System 7000 be configured as part of the solution.
Although Cisco legacy endpoints are inter-operable with Collaboration Server (RMX) 1800-0, the MCU is
not supported for integration into third-party and partner environments.
● Deployment Architecture 1 - RealPresence Hosted Conferences (Direct)
Both Lync clients and Standards-based video endpoints connect directly to the same conference
hosted only on the Polycom RealPresence Collaboration Server.
● Deployment Architecture 2 - RealConnect Cascaded Conferences
Lync clients connect to a conference on the Lync 2013 AVMCU while Standards-based video
endpoints content to a separate conference on the Polycom RealPresence Collaboration Server. The
two MCUs are cascaded together to form a single conference including all participants.
Note: Collaboration Server (RMX) 1800-0
Collaboration Server (RMX) 1800-0, is not supported for integration into third-party and partner
environments.