Realconnect For Lync 2013 - Polycom realpresence 1800 Administrator's Manual

RealConnect for Lync 2013

RealConnect for Microsoft Lync requires that a conference call be scheduled and that Lync clients receive
an Online Meeting invite containing the dial-in conferencing ID.
To connect to a scheduled Online Meeting:
» Click the Join Lync Meeting link in the Online Meeting invite.
A call to the AVMCU is initiated. The RealPresence Platform obtains the Lync conference SIP URI is
obtained. The SIP URI is used to create an ad hoc Virtual Meeting Room (VMR) which is assigned
the same number as the Lync conference ID. The VMR then dials into the Online Meeting and
connects as a Lync Client.
Should the RealConnect-ed Collaboration Server fail, the DMA containing the VMR to which both MCUs
were connected, is capable of recreating the conference on an alternate Collaboration Server.
To achieve this, the (original) Collaboration Server provides the DMA with the AVMCU Focus (SIP) URI as
part of the conference information, even for Ad-Hoc conferences.
In addition, two additional values are passed via the XML API from the Collaboration Server to the DMA
within the conference information, to enable proper termination of the recreated conference (as explained
in the conference termination below):
● The original AVMCU conference type - scheduled (AVMCU), scheduled (PCM), Ad-Hoc, or none
(meaning non-AVMCU conference).
● The value of the "To" field in the original invitation.
Cascading Conference Reestablishment Process
1 Once the DMA detects a Collaboration Server failure (via XML API or ping), it disconnects all the
Collaboration Server SIP connections (legs) except the SIP connection to the AVMCU.
2 The DMA recreates the conference on an alternate Collaboration Server, and passes to it (via XML
API) the AVMCU Focus URI, the conference type, and the value of the original "To" field in the
Microsoft invite, as preserved from the original conference.
3 The Collaboration Server uses the Focus URI to recreate the cascading link to the AVMCU, and
recreates the conference using the conference type retained from the original conference.
4 The Collaboration Server uses the original "To" field value to create SIP sessions to the "leftover"
SIP connections from the AVMCU to the original Collaboration Server in order to disconnect them.
Reestablished Cascading Conference Termination
Once all the Collaboration Server participants are disconnected, the Collaboration Server uses the retained
conference type to determine whether or not the cascading link to the AVMCU should be disconnected:
● For scheduled conferences - The cascading link is disconnected.
● For Ad-Hoc conferences - The cascading link is not disconnected.
Polycom®, Inc.
Appendix H - Deployment Into Microsoft Environments
1012