Polycom 3725-76302-001O manual Integrate RealPresence DMA and Lync, Required Information

Integrations with Other Systems

			Uses SVC
			cascading
			between Microsoft
Feature	Client	Server	AVMCU and	Comments
			Polycom MCU
Meet Now calls to a	Lync 2013	Lync 2013	Yes
VMR
Escalated conferences -	Lync 2013	Lync 2013	Yes
Lync client drag and
drop multi-party call
Direct point-to-point	Lync 2010	Lync 2010	No
Lync call to a VMR	Lync 2013	Lync 2013
DMA registered	Lync 2010	Lync 2010	No	If a Lync 2013 client, all
endpoint calling point	Lync 2013	Lync 2013		calls will be audio only.*
to point to a Lync client
	Lync 2010	Lync 2010	No	•	Endpoints that don’t
	Lync 2013	Lync 2013			support the SIP SDP
					multipart protocol will
Lync client calling point					fail to join the call.
to point to DMA				•	Some Polycom
registered endpoint					endpoints will join the
					call as audio only if
					dialed with a Lync
					2013 client.*
Presence enabled	Lync 2013	Lync 2013	No
VMRs

*The Lync 2010 client supports the H.263 video codec, but the Lync 2013 client does not. See the note on page 169.

Integrate RealPresence DMA and Lync 2013

Before integrating, gather required information from your Lync 2013 system administrator. If you need the RealPresence DMA system to automatically create conference contacts in Active Directory, ensure that your RealPresence DMA system is integrated with Microsoft Active Directory before continuing. Refer to the Polycom Unified Communications Deployment Guide for Microsoft Environments for more information on the preliminary network, port, Lync server, and DNS configuration steps needed to prepare the RealPresence DMA system and your environment for integration with Lync 2013.

Required Information

You should gather the following information before beginning the integration process:

●The Fully Qualified Domain Name (FQDN) of the RealPresence DMA system

●The SIP domain for conference contacts (used in the Contact SIP domain field on the Admin > Conference Manager > Conference Settings page)

●The FQDN of or IP address of the Lync pool (used in the Next hop address field on the Network > External SIP Peers > Add External SIP Peer dialog)

Polycom, Inc. 170