Polycom 7000 manual Automatic Contact Creation and Configuration

Integrations with Other Systems

Note: Polycom RealConnect™requires Polycom MCUs

Polycom RealConnect™ scheduled conferences require that the RealPresence DMA system manage at least one Polycom MCU that supports Lync 2013. Non-Polycom MCUs are not supported.

Polycom RealConnect™ uses Microsoft Outlook meeting invitations to deliver conference information to participants. When you schedule a conference with Outlook, you can configure the Outlook meeting invitation to include Lync conference IDs in meeting invitations as plain text, in addition to the automatically included “Join Lync Meeting” hypertext link. When they receive the meeting invitation, users of Lync clients can click the link, and users of non-Lync endpoints can dial the plain-text Lync conference ID.

When non-Lync endpoints dial the meeting ID in the meeting invitation, the incoming call is acted on by the Dial to RealConnectTM conference 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.

In a superclustered configuration, endpoints can connect to a RealConnectTM conference from any cluster in the supercluster, but the call will be routed through the supercluster to the cluster that is hosting the RealConnectTM conference.

For information on configuring Microsoft Outlook and Microsoft Lync 2013 to support Polycom RealConnect™, refer to the Polycom Unified Communications in a Microsoft Environment Solution Deployment Guide.

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.

Active Directory Service Account Permissions

If you integrate 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 should have full permissions to add, change, and delete entries in the OU where the conference contacts are stored. The account should also have full administrative permissions for Lync administration to manipulate these contacts.

Polycom, Inc. 169