Supported Endpoints and Interoperability

Microsoft

Product Version Notes
Endpoints
Lync Room System (LRS)

Skype Room Systems (SRS) (project Rigel – e.g. Logitech SmartDock)

from first release
Microsoft Surface Hub from first release
Software Endpoints
Skype for Business 2016 client Windows and OSX See Received content can be slow to update.

See No video on Lync for Mac / Lync 2010 (RTV-based clients) in SfB/Lync meetings.

Skype for Business 2015 client Windows
Skype for Business Mobile iOS/Android/Windows
Lync 2013 desktop client Windows and OSX
Lync 2011 desktop client OSX
Lync 2010 desktop client Windows
Call Control
Skype for Business Server 2015
Lync Server 2010
2013

2016

Poly

Product Version Notes
Hardware Endpoints
Poly HDX series
(4000, 4500, 6000, 7000, 8000, 9000)
3.0 and above
Poly VSX series
(3000, 5000, 6000, 7000, 8000)
8.7.1 and above
Poly VVX series
(100, 200, 300, 400, 500, 600)
5.4 and above
Poly QDX 6000 4.0.2 and above
Poly RPX 200/400 Immersive Room* 2.6 and above
Poly OTX 300 Immersive Room* 5.1 and above
Poly TPX 306 Immersive Room* 3.1 and above
HP Halo Poly Rooms 3.0 and above
Poly RealPresence Group series
300/500/700
4.0.2 and above
Poly RealPresence Immersive Studio Room* 5.1 and above
Poly RealPresence Centro 5.1 and above
Poly RealPresence Debut 1.1 and above
Poly RealPresence Trio 5.4 and above
Software Endpoints
Poly RealPresence Desktop (Windows, OSX) and Mobile (iOS, Android) 2.3.0 and above
Poly CMA Desktop 5.2.5 and above
Infrastructure
Poly DMA 7000 6.1.2
Poly CMA 4000/5000 4.0 and above
Poly VBP 5300/6400 9.0 and above
Poly RMX/RPCS
(800s, 1500, 1800, 2000, 4000)
8.2.0 and above
VC-Connect can support the primary system in such a multi-screen system. The primary codec must support a protocol such as H.264, because VC-Connect does not support the TIP protocol. If all screens are required (or the primary codec does not support H.264), VC-Connect can act as a gateway into the MCU to which the multi-screen system is registered. This allows participants who cannot connect directly to that MCU (because, for example, they are using an endpoint such as Skype for Business that the MCU does not support) to connect via VC-Connect instead.

Cisco

Product Version Notes
Hardware Endpoints (VTC)
Cisco C series
(C20, C40, C60, C90)
TC4.2.1 and above See issues with endpoints running TC version 5.x or earlier.
Cisco DX series
(DX80)
10.2.3
Cisco E20 TE4.1.1 and above See Main video on a Cisco E20 freezes and no presentation is shown when a VMR participant starts presenting.
Cisco EX series
(EX60, EX90)
TC6.3 and above See issues with endpoints running TC version 5.x or earlier.
Cisco MX series
(MX200, MX300, MX700, MX800)
TC5.0 and above

CE8.0 and above

See issues with endpoints running TC version 5.x or earlier.
Cisco MXP series
(880 MXP, 990 MXP, 1000 MXP, 1500 MXP, 1700 MXP, 3000 MXP, 6000 MXP)
F8.3 and above See A Cisco MXP intermittently puts a call on hold immediately after resuming it.
Cisco Edge 75/85/95 MXP series F5.3 and above
Cisco SX series VTC systems

(SX10, SX20, SX80)

TC7.3.0 and above See issues with endpoints running TC version 5.x or earlier.
Cisco Video Phones 9951/9971 9.3 and above
Cisco TX 9000 Immersive Room* 6.1 and above
Cisco IX 5000 Immersive Room* 8.0 and above
Cisco Tandberg T1000 E5.3.1
Cisco Tandberg T150 L6.1
Software Endpoints
Cisco Jabber/Movi desktop client 4.4 and above
Cisco Jabber for Windows (via CUCM) 9.7 and above
Webex CMR 31.0 and above
Call Control
Cisco VCS Control

Cisco VCS Expressway

X7.2.1 and above
Cisco Unified Communications Manager (CUCM) 8.6.2 and above
Infrastructure
Cisco Codian 4200 series (4203, 4205, 4210, 4215, 4220) 4.3 and above
Cisco Codian 4500 series (4501, 4505, 4510, 4520) 4.3 and above
Cisco Codian 8400 series 4.5 and above
Cisco Codian 8500 series 4.3 and above
Cisco TelePresence Server (8700, 7010) 3.1
Cisco TelePresence MSE8000 MCU 4.1 and above
* VC-Connect can support the primary system in such a multi-screen system. The primary codec must support a protocol such as H.264, because VC-Connect does not support the TIP protocol. If all screens are required (or the primary codec does not support H.264), VC-Connect can act as a gateway into the MCU to which the multi-screen system is registered. This allows participants who cannot connect directly to that MCU (because, for example, they are using an endpoint such as Skype for Business that the MCU does not support) to connect via VC-Connect instead.

Other Manufacturers

Product Version Notes
Hardware Endpoints
Aethra Vega X5, X7 10.1.24, 12.1.7
AVer EVC series 1.08, 10.06, 10.10
AVer HVC 330 3.12, 3.14
Counterpath Bria 3.2.1, 3.5.5
Huawei TE series 1.1, 1.2
Huawei ViewPoint 9030 11.2
LifeSize Express 200, 220 4.8 and above
Lifesize Room 200, 220 4.8 and above
Lifesize Team 200, 220 4.8 and above
Lifesize Passport 4.8 and above
LifeSize Icon 600 1.1.4 and above
RadVision XT1000, XT4000, XT5000, XT240 8.3 and above
RadVision VC240 2.5 and above
Sony PCS-XG80 2.30 and above
Starleaf 1.8.2
Tely Labs 4.5.1 and above
Yealink VC-110 50.0 and above
Yealink VC-120 40.20 and above
Yealink VC400 30.0 and above
Yealink T49G 51.0 and above
Software Endpoints
LifeSize Softphone 8.1.12
Linphone 3.7, 3.8
Yealink VC Desktop 1.0 and above
Infrastructure
GNU Gatekeeper
LifeSize Media Server 5.2 and above
Magor SBC 102 and above
RadVision viaIP MCU 7.7.4 and above
RadVision viaIP Gateway (100, 400) 5.7.2
VidyoGateway 1.20.2, 3.2.0
Zoom Room Connector 1.0.1