Polycom 7000 manual Lync and non-Lync Endpoint Collaboration

icon is

Integrations with Other Systems

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.

Note: Point to point calls between Polycom endpoints and Lync 2013 clients

When you register a Polycom endpoint to a RealPresence DMA system and make a point to point call to a Lync 2013 client, the conference may not have video because the H.261 and H.263 video codecs are not supported by the Lync 2013 client. As a workaround for Polycom HDX and RealPresence Group Series endpoints, register the endpoint to the Lync 2013 server before starting the conference. This workaround requires an RTV option key or Lync Interoperability License.

Note: Point to point calls between Polycom endpoints and Lync 2010 clients

If you add a SIP endpoint on the Network > Endpoints page using the Address of record format <name>@<IP address> and call the endpoint using a Lync 2010 client, the endpoint will not hang up when the call is terminated from the Lync 2010 client. As a workaround, use an Address of record with the format <name>@<SIP domain> when adding the endpoint.

Considerations and Requirements for Lync 2013 Integration

●For the latest software version requirements and interoperability information, consult the Polycom Unified Communications in a Microsoft Environment Release Notes.

●The following Virtual Entry Queue (VEQ) call scenarios are not supported:

Calls to a Virtual Entry Queue (VEQ) from a Lync client

A non-Lync endpoint connecting to a VEQ and entering a Lync conference ID when prompted

●The Lync AVMCU doesn’t support incoming calls dialed from a RealPresence DMA system VMR.

●Conference mode configurations of SVC-only and Mixed AVC and SVC are not supported in RealPresence DMA system and Lync 2013 cascaded conferences. Any conference that requires Lync AVMCU connectivity must use conference templates with AVC only as the configured Conference mode.

●You need Lync-capable Polycom MCUs to take advantage of Polycom RealConnectTM functionality.

Non-Polycom MCUs are not supported. If your Polycom MCU is Lync 2013 capable, the

displayed next to the MCU name on the Network > MCU > MCUs page. If no MCUs that support Lync 2013 are available, the cascaded RealConnectTM conference won’t start. Refer to your MCU documentation for more information.

●The Transfer Call feature of the Lync client is currently not supported when the MCU hosting the call is configured to use ICE or encryption.

Polycom, Inc. 170