Polycom 3725-76302-001O manual Automatic Contact Creation and Configuration

Integrations with Other Systems

When non-Lync endpoints dial the meeting ID in the meeting invitation, the incoming call is acted on by the Dial by Lync Conference ID dial rule. This dial rule causes the RealPresence DMA system to search any configured and selected SIP peers for a matching Lync conference. If the conference ID isn’t resolved on a Lync server, the system continues to resolve the conference ID using the next dial rule in the list. If the conference ID is resolved on a Lync server, the hosting Lync server gives the RealPresence DMA system information about the conference in question. The RealPresence DMA system dynamically creates a VMR and starts a conference on a Lync-capable MCU, passing the Lync conference information to the MCU. The MCU builds a cascade link between the newly created conference and the conference hosted on the Lync AVMCU. Lync clients and non-Lync endpoints can now interact in the conference.

Automatic Contact Creation and Configuration

You can configure the RealPresence DMA system to create and manage a corresponding Polycom conference contact in Active Directory whenever users create a new VMR. The RealPresence DMA system communicates with the Lync server to ensure the new contact it is enabled for Lync functionality. This allows the system to publish presence updates to the conference contact; Lync clients display a status of Available, Busy, or Offline for the conference contact in the client’s contact list.

Note: Lync client contact creation delay

When you manually or automatically create a VMR or group of VMRs, allow up to 10 minutes for the newly created conference contact(s) to appear in the Lync client contact list.

Note: Required permissions for Active Directory service account

If you are integrating the RealPresence DMA system with Lync 2013 and plan to use the automatic conference contact creation feature, note that the required Active Directory service account permissions have changed from previous releases. The service account should have full permissions to add, change, and delete entries in the OU where the conference contacts are stored, along with full administrative permissions for Lync administration to manipulate these contacts.

Lync and non-Lync Endpoint Collaboration

Callers with Lync clients and non-Lync endpoints can join the same conference in several ways. See the Microsoft Lync documentation for more details on specific call flows.

●Users of Lync 2013 clients can select a Polycom conference contact in the contact list and drag it to an ongoing Lync 2013 conversation window, starting a video call.

●Users of Lync 2013 clients can start a Lync conference by selecting the (Show Menu) icon and choosing Meet Now. After starting the conference, users can invite more attendees to the conference or drag a Polycom conference contact into the conversation window to add the participant.

●Users of Lync clients can right-click a Polycom conference contact in the contact list and choose Start a video call.

●Users of Lync clients and other endpoints can use a Microsoft Outlook meeting invitation to connect to a Lync conference. Non-Lync endpoints can dial the included conference ID, and Lync clients can click the “Join Lync Meeting” link included in the invitation.

Polycom, Inc. 168