Cisco TelePresence

Interoperability Database

Warning - In preview mode

We endeavor to make our Cisco TelePresence products interoperable with all relevant standards-based equipment. Although it is not possible to test all scenarios, the testing on which this data is based covers most common functions of the listed endpoints and infrastructure.

The following pages describe the software releases that were tested for interoperability with Cisco TelePresence products. The results are grouped by product range. It is not possible to guarantee that all the models listed in the Product(s) column have been tested with the specified software release, although to the best of our knowledge we believe that all such models are interoperable with the associated software release. The absence of a device or release does not imply a lack of interoperability.

Cisco TelePresence Video Communication Server (VCS) software version X8.9

Show data for version: X8.9X8.8X8.7X8.6, X8.7X8.6X8.5.1X8.5X8.2.1X8.2X8.1.1X7.2.2X7.2X7.1X7.0.1X7.0

Cisco TelePresence

Product(s) Software releaseComments
Cisco TelePresence Conductor XC4.0

No issues found.

Cisco TelePresence Conductor XC4.1

No issues found.

Cisco TelePresence Conductor XC4.2

No issues found.

Cisco TelePresence IX5000 and IX5200 8.1.2

We do not support registration of IX5000 and IX5200 endpoints to VCS.

Cisco TelePresence Management Suite (TMS) 15.0

No issues found.

Cisco TelePresence MCU Series products 4.5

No issues found.

Cisco TelePresence Server 4.2

No issues found.

Cisco TelePresence SX Series CE 8.1

No issues found.

Cisco TelePresence SX Series CE 8.0

No issues found.

Cisco TelePresence Systems C/SX/EX/MX/Profile Series T.C 7.3.5

No issues found.

Cisco VCS X8.9

Traversal zone connections between a Cisco VCS and a Cisco Expressway are not supported. (Applies to all versions of both products).

Cisco

Product(s) Software releaseComments
Cisco DX Series 10.2.5

Hold/resume from Skype for Business, in a call initiated by DX80 to Skype for Business, failed in one test environment. The issue was not observed in calls initiated by Skype for Business to DX80. The issue was not reproducible when the same test was repeated in another environment.

Cisco IP Phone 7800 Series 11.5.1

When a 7800/8800 Series endpoint using MRA receives a call, with Single Number Reach set up to an external mobile device, the endpoint might continue to ring even if the call is answered on the mobile device.

Cisco Jabber 11.7

No issues found.

Cisco Prime Collaboration Assurance 10.5.1

Not supported.

Cisco Unified Communications Manager 11.5

No issues found.

Cisco Unified Communications Manager IM and Presence Service 11.5

No issues found.

Cisco VCS X8.9

In third-party calls, where more than one H.264 payload is offered with different profiles, all subsequent H.264 payloads are treated as duplicate and removed. If the first H.264 profile is not baseline, this may lead to the call negotiating H.263 for video channels.

Jabber Guest 10.6.8.11

No issues found.

Avaya

Product(s) Software releaseComments
Scopia PathFinder Server 8.3.3

No issues found.

Scopia XT Executive 240 8.3.5
  • When Expressway interworks H.323 calls between this endpoint and LifeSize SIP endpoints, the calls are set up with one-way audio, but they have two-way video.
  • On Avaya H.323 calls that Expressway interworks to SIP we do not support the DTMF (RFC2833 or H.245 AlphaNumeric) Avaya uses. We only support H.245-signal for DTMF on the H.323 side of interworking.

LifeSize

Product(s) Software releaseComments
Icon 600 LS_RM3_2.10.0 (1981)
  • When VCS interworks calls between this endpoint (SIP) and Avaya Scopia XT Executive 240 (H.323), the calls are set up with one-way audio, but they have two-way video.
  • When a call is made to an Icon 600, within 20 seconds of its initial registration the call may be rejected with a 503 service unavailable error. You must restart the endpoint to address this issue.
  • If an Icon 600 endpoint is behind a NAT/firewall, and a SIP call is made where media has to route across it, the receiving endpoint will not be able to present to the Icon 600. The Icon 600 does not send out any packet to open the NAT/firewall. As a result, media sent from the VCS to the Icon 600's RTP port is blocked on the NAT/firewall.
Room 220 LS_RM2_5.0.4(7)

When VCS interworks calls between this endpoint (SIP) and Avaya Scopia XT Executive 240 (H.323), the calls are set up with one-way audio, but they have two-way video.

Microsoft

Product(s) Software releaseComments
Lync for Mac client 2011

Not supported.

Lync for Windows client 2013

Lync 2013 clients are interoperable with Cisco VCS (in the Gateway VCS deployment), when they are in a Lync 2013 or Skype for Business 2015 Server environment.

Lync Server 2010

No issues found with Lync Server 2010 for AV calls between interoperable clients.

Screen sharing from interoperable Lync clients is not supported with Lync Server 2010 and Gateway VCS deployments.

Lync Server 2013

The following clients are supported:

  • Lync 2013 9Windows desktop, native client).
  • Skype for Business 2015 (Windows desktop, native client).
  • Skype for Business 2016 (Windows desktop, native client).

AV calls and screen sharing from interoperable Microsoft clients are supported with Cisco TelePresence endpoints behind the Gateway VCS. The  versions supported are as follows:

  • TC Series endpoints version 7.2 and later.
  • CE Series endpoints version 8.0.
  • DX Series endpoints version 10.2(5).

AV calls and screen sharing from interoperable Microsoft clients are supported with Cisco TelePresence bridges behind the Gateway VCS. The supported platforms and tested versions are as follows:

  • MCU 5300 Series and MCU MSE 8510, version 4.5.
  • TS 8710 and Multiparty Media 310/320, version 4.2.

The MCU platforms above do not revoke the floor when the Lync user stops sharing their screen. See CSCux48258.

The following conferencing bridges do not work with screen sharing from Lync in the Gateway VCS deployment:

  • Cisco TelePresence MCU 4200 Series.
  • Cisco TelePresence MCU 4500 Serie.

The following endpoints do not work with screen sharing from Lync in the Gateway VCS deployment:

  • Cisco Jabber.
  • Cisco Jabber Video for TelePresence.
Skype for Business Mobile versions

Lync 2013 mobile versions are not supported.

Skype for Business mobile versions are interoperable with Cisco VCS on Skype for Business 2015 Server with the following limitations:

  • Call hold/resume does not work as expected between Skype for Business mobile versions and Cisco endpoints.
  • Call transfer between Cisco endpoints and Skype for Business mobile versions is not supported.
  • Audio-only calls from Cisco endpoints to Skype for Business (iOS mobile) are not supported.
Skype for Business Server 2015

The following clients are supported:

  • Lync 2013 (Windows desktop, native client).
  • Skype for Business 2015 (Windows desktop, native client).
  • Skype for Business 2016 (Windows desktop, native client).

We do not support the following clients in calls to MCU bridges. We do support them in other call scenarios, including calls to TelePresence Server bridges:

  • Skype for Business (iOS mobile).
  • Skype for Business (Android mobile).
  • We do not support Skype for Business (Windows mobile).

Mobile versions of Skype for Business cannot share their screens.

Lync 2013 mobile versions are not supported.

AV calls and screen sharing from interoperable Microsoft clients are supported with Cisco TelePresence endpoints behind the Gateway VCS. The versions supported are as follows:

  • TC Series endpoints version 7.2 and later.
  • CE Series endpoints version 8.0.
  • DX Series endpoints version 10.2(5).

The following endpoints do not work with screen sharing from Microsoft in the Gateway VCS deployment:

  • Cisco Jabber.
  • Cisco Jabber Video for TelePresence.

The following conferencing bridges do not work with screen sharing from Microsoft in the Gateway VCS deployment:

  • Cisco TelePresence MCU 4200 Series.
  • Cisco TelePresence MCU 4500 Series.

The following MCU platforms do not revoke the floor when the Lync user stops sharing their screen. See CSCux48258.

  • MCU 5300 Series.
  • MCU MSE 8510, version 4.5.
Skype for Business Windows client 2015/2016

Skype for Business 2015 and 2016 clients are interoperable with Cisco VCS (in the Gateway VCS deployment), when they are in a Lync 2013 or Skype for Business 2015 Server environment.

Polycom

Product(s) Software releaseComments
HDX 9000 3.1.9

No issues found.

RealPresence Group 300 5.1.2

When this endpoint receives a call from Avaya Scopia XT Executive 240 with sips: contact, it generates a malformed Warning header in the 480 response. This issue is logged with Polycom as GS-27082.

RealPresence Group 300 4.3.0
  • When this endpoint receives a call from Avaya Scopia XT Executive 240 with sips: contact, it generates a malformed Warning header in the 480 response. This issue is logged with Polycom as GS-27082.
  • Polycom GroupSeries endpoint cannot decode media encrypted by B2BUA. This issue is resolved in version 5.0.0 of the RealPresence Group Series software.
RealPresence Group 310 5.1.2

When this endpoint receives a call from Avaya Scopia XT Executive 240 with sips: contact, it generates a malformed Warning header in the 480 response. This issue is logged with Polycom as GS-27082.