POLYCOM – LYNC integration: RealPresence connect (part 1)

Part 1: Architecture and requirements 

I will try to explain how to configure the servers to realize the configuration of the new Polycom option: the RealPrecense Connect.

First, I found many information in the official Polycom documentation :(http://supportdocs.polycom.com/PolycomService/support/global/documents/support/strategic_partner_solutions/Polycom_Unified_Communications_Deployment_Guide_for_Microsoft_Environments_us.pdf) but I want to give more details not obvious (for me J) in this guide.

The RealPresence Connect is an amazing feature which provides the users to schedule a video conference with outlook. This conference will be easely reached from Lync client or from a video room system.

Lync or web participants just have to click on the link when the video room’s users have to call the conference ID.

Let’s begin the technical part!

The target architecture:

Requirements:

Microsoft Lync 2013 Server -> 5.0.8308.577
RMX: 8.4
DMA: 6.1


The RMX must be connected with the front end. You can register it with the DMA (H.323) in order to use it with the Polycom infrastructure only.

The configuration has two steps:

                    1-      Register the RMX in the lync infrastructure

                    2-      Configure the SIP trunk between the DMA and the front end

Two others parts will describe this steps.

 Again, I recommend to following the Polycom document for this configuration. I just want to specify some points.

POLYCOM – LYNC integration: RealPresence connect (part 3)

Part 3 DMA Configuration:

I haven’t faced any issue for the DMA integration. The entire lync configuration is well explained in the Polycom documentation. You can erase the static route to the RMX for the one to the DMA. After that, this is exactly the same process than the RMX. I'll just present some screenshots to have another a view of this integration.

The certificate part is very similar than the RMX. First, you upload the root certificate. After, with the certificate request, you can generate the DMA’s certificate on your PKI.

Configuration of the external SIP Peer

Next hop address: FQDN of the Lync FE

Destination network: sip domain

RMX connection

As I said before, the RMX not has to be registered on the DMA but it must be knonw by the DMA.

The registration is Inactive because the RMX is registered to the Lync FE in SIP and H.323 is disabled. The new logo which appeared means your RMX is configure to support cascaded conferences with Lync.

 Dial Rules

Resolve to Lync Conference ID: Will match when using RealPresence Connect.

Lync Server Rule: Will match when a video endpoint call a Lync user.

For the RealPresence Connect, only the first rule is needed. 

Your configuration is ready !