Interoperability

We endeavor to make Pexip Infinity interoperable with all relevant standards-based devices. These tables list the devices and software versions with which Pexip Infinity is known to work, along with any known issues. Note however that these lists are not exhaustive - the absence of a device or specific version does not imply a lack of interoperability.

We welcome your feedback on any known issues with any of the mentioned devices or software versions, and we would also like to hear of any other devices that you have used with Pexip Infinity. Please send your comments to your Pexip authorized support representative.

For a list of more general system issues and how to resolve them, see Troubleshooting the Pexip Infinity platform.

In this topic:

Cisco
Microsoft
Google
Poly / Polycom
Other manufacturers
Hypervisors
Browser video support

Cisco

Product	Version	Notes
Hardware endpoints (VTC)
Cisco Webex Room series (Room, Room Kit) Webex Board Series Webex Desk Series	CE9.x and above RoomOS 10 and above
Cisco C series (C20, C40, C60, C90)	TC7.1 and above	See issues with TC7.1.4, and TC5.x or earlier.
Cisco DX series (DX70, DX80)	CE8.0 and above 9.7.1 and above
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. H.323 calls cannot be placed via a Virtual Reception if FECC is enabled on the Pexip Infinity platform and the call media is routed via a VCS.
Cisco EX series (EX60, EX90)	TC7.1 and above	See issues with TC7.1.4, and TC5.x or earlier.
Cisco MX series (MX200, MX300, MX700, MX800)	TC7.1 and above CE8.0 and above	See issues with TC7.1.4, and TC5.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 CE8.0 and above
Cisco Video Phones 9951/9971	9.3 and above
Cisco TX 9000 Immersive Room * Pexip Infinity can support the primary system in such a multi-screen system. The primary codec must support a protocol such as H.264, because Pexip Infinity does not support the TIP protocol. If all screens are required (or the primary codec does not support H.264), Pexip Infinity 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 Pexip Infinity instead.	6.1 and above
Cisco IX 5000 Immersive Room * Pexip Infinity can support the primary system in such a multi-screen system. The primary codec must support a protocol such as H.264, because Pexip Infinity does not support the TIP protocol. If all screens are required (or the primary codec does not support H.264), Pexip Infinity 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 Pexip Infinity instead.	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	Calls to Pexip Infinity that have been interworked from H.323 to SIP by Cisco VCS version 7 or lower will fail to start presentation.
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
* Pexip Infinity can support the primary system in such a multi-screen system. The primary codec must support a protocol such as H.264, because Pexip Infinity does not support the TIP protocol. If all screens are required (or the primary codec does not support H.264), Pexip Infinity 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 Pexip Infinity instead.

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 macOS	See Received content can be slow to update. See Troubleshooting and limitations with Skype for Business and Pexip Infinity integrations.
Skype for Business 2015 client	Windows
Skype for Business Mobile	iOS/Android/Windows
Lync 2013 desktop client	Windows and macOS
Call control
Microsoft Teams		Pexip Infinity can gateway calls from any supported device into a Microsoft Teams conference.
Skype for Business Server	2015
Lync Server	2013

Google

Product	Version	Notes
Call control
Google Meet		Pexip Infinity can gateway calls from any supported device into a Google Meet call.

Poly / Polycom

Product	Version	Notes
Hardware endpoints
Polycom HDX series (4000, 4500, 6000, 7000, 8000, 9000)	3.0 and above
Polycom VSX series (3000, 5000, 6000, 7000, 8000)	8.7.1 and above
Polycom VVX series (100, 200, 300, 400, 500, 600)	5.4 and above
Polycom QDX 6000	4.0.2 and above
Polycom RPX 200/400 Immersive Room * Pexip Infinity can support the primary system in such a multi-screen system. The primary codec must support a protocol such as H.264, because Pexip Infinity does not support the TIP protocol. If all screens are required (or the primary codec does not support H.264), Pexip Infinity 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 Pexip Infinity instead.	2.6 and above
Polycom OTX 300 Immersive Room * Pexip Infinity can support the primary system in such a multi-screen system. The primary codec must support a protocol such as H.264, because Pexip Infinity does not support the TIP protocol. If all screens are required (or the primary codec does not support H.264), Pexip Infinity 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 Pexip Infinity instead.	5.1 and above	Pexip Infinity does not support G.719 audio from Poly OTX devices. The workaround is to disable the G.719 codec on Pexip Infinity.
Polycom TPX 306 Immersive Room * Pexip Infinity can support the primary system in such a multi-screen system. The primary codec must support a protocol such as H.264, because Pexip Infinity does not support the TIP protocol. If all screens are required (or the primary codec does not support H.264), Pexip Infinity 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 Pexip Infinity instead.	3.1 and above
HP Halo Polycom Rooms	3.0 and above
Polycom RealPresence Group series 300/500/700	4.0.2 and above (5.0.0 and above required for One-Touch Join)
Polycom RealPresence Immersive Studio Room * Pexip Infinity can support the primary system in such a multi-screen system. The primary codec must support a protocol such as H.264, because Pexip Infinity does not support the TIP protocol. If all screens are required (or the primary codec does not support H.264), Pexip Infinity 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 Pexip Infinity instead.	5.1 and above
Polycom RealPresence Centro	5.1 and above
Polycom RealPresence Debut	1.1 and above
Polycom RealPresence Trio	5.4 and above
Poly Studio X series	3.0.1 and above	Calls that are encrypted using Diffie-Hellmann 2048 are not supported.
Poly G7500 series	3.0.1 and above
Software endpoints
Polycom RealPresence Desktop (Windows, macOS) and Mobile (iOS, Android)	2.3.0 and above
Polycom CMA Desktop	5.2.5 and above
Infrastructure
Polycom DMA 7000	6.1.2
Polycom CMA 4000/5000	4.0 and above
Polycom VBP 5300/6400	9.0 and above
Polycom RMX/RPCS (800s, 1500, 1800, 2000, 4000)	8.2.0 and above
Service
RealConnect	n/a	Calling to the RealConnect service is only supported over SIP. Pexip does not support H.323 calls to this service.
* Pexip Infinity can support the primary system in such a multi-screen system. The primary codec must support a protocol such as H.264, because Pexip Infinity does not support the TIP protocol. If all screens are required (or the primary codec does not support H.264), Pexip Infinity 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 Pexip Infinity instead.

Other manufacturers

Product	Version	Notes
Hardware endpoints
Aethra Vega X5, X7	10.1.24, 12.1.7
AVer EVC 100, 130, 150	01.16.02 and above
AVer EVC 170	30.00.12 and above
AVer EVC 300, 310, 350, 900, 910, 950	10.16.01 and above
AVer HVC 330	3.12, 3.14
AVer SVC 100, 500	20.04.29 and above
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	FECC does not work correctly with v3.4.0
RadVision XT1000, XT4000, XT5000, XT240	8.3 and above
RadVision VC240	2.5 and above
Sony PCS-XG80	2.30 and above
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

Hypervisors

For more information, see Supported hypervisors.

Product	Version	Notes
Microsoft Hyper-V	Microsoft Hyper-V Server 2019
VMware ESXi	6.7, 7.0 and 8.0
KVM Open Source	Linux 3.10.0 or later QEMU 1.5.0 or later

Product

Version

Notes

Microsoft Hyper-V

Microsoft Hyper-V Server 2019

VMware ESXi

6.7, 7.0 and 8.0

KVM Open Source

Linux 3.10.0 or later

QEMU 1.5.0 or later

Browser video support

For more information, see About the Connect web app.

Product	Version	OS
Google Chrome WebRTC (VP8/VP9/H.264)	126 and later (64-bit version only)	Windows, Linux, macOS, iOS, Android
Mozilla Firefox	128 and later	Windows, Linux, macOS, iOS
Microsoft Edge	126 and later	Windows, iOS
Apple Safari	15.4 and later	macOS, iOS
Notes: We strongly recommend using the latest publicly-released version (i.e. "stable version" or "supported release") of a browser. RTMP media streaming is also supported in all browsers. Instant Messaging to and from Skype for Business / Lync clients is supported in all browsers.