Known limitations

These are the known limitations in the current release of Pexip Infinity.

For a list of known limitations in the current release of the Infinity Connect clients, see Infinity Connect release notes.


Ref # Limitation
15649 Calls may occasionally be dropped in some deployment environments that experience intermittent degradation of storage IO performance.
15102 You cannot upload a theme ZIP if you zip the folder containing the custom files. To upload the files you must zip the files directly within the folder.
13305 The G.719 codec is not currently supported for SIP.
12929 The "Insufficient video licenses" screen is sometimes shown for the first 1-2 seconds of an RTMP stream.
12878 Infinity Connect calls may be dropped if the client sends a token refresh request to a different Proxying Edge Node from the proxying node that handled the original connection request, if Enable restricted routing for Proxying Edge Nodes is enabled and there is no direct connectivity between the two proxying nodes. The workaround for this is to disable Global Settings > Enable restricted routing for Proxying Edge Nodes.
12314 In the Participant Details for RTMP streams, the bandwidth is reported as 2000 kbps, even when the bandwidth has been limited to a lower value.
10337 Pexip Infinity will only latch for incoming media once, unless there has been a re-INVITE. This means that in some cases, when the NAT binding at the client has timed out and the source port has changed, Pexip Infinity will continue to send presentation media to the old port.


If a caller dials into a Virtual Reception and enters the number of the conference they want to join, but there are insufficient hardware resources available to join the caller to that conference, the caller is disconnected from the Virtual Reception.


Any changes made to VMR configuration — such as updating the participant limit — while the conference is ongoing do not take immediate effect, and may result in conference separation (i.e. new participants will join a separate VMR from those that are currently connected). All participants must disconnect from the conference for the change to take effect.


When changing the certificates in a chain, a reboot of the associated Conferencing Nodes may be required if the changes do not produce the desired effect.


Occasionally, group chat messages may not be displayed to Infinity Connect web app participants who are using Internet Explorer.


Ref # Limitation
4142 If the presentation channel already active from an MXP is taken by another connected participant, the MXP may not properly receive presentation content.


Ref # Limitation
13541 When a Polycom Trio is registered to Skype for Business, and has dialed in to Pexip Infinity, it will receive presentation as main video from Pexip Infinity. However, when the same endpoint is dialed out to from Pexip Infinity, it will receive presentation as RDP.


Microsoft Skype for Business and Lync

Ref # Limitation
15103 VTCs that are gatewayed into a Skype for Business meeting may experience slow loading of RDP presentation frames from other participants in that meeting, if the Pexip administrator has configured a low "Maximum inbound call bandwidth" limit on the gateway rule used for routing VTCs into Skype for Business meetings. The workaround is to remove the "Maximum inbound call bandwidth" limit on the rule.
13201 When a Skype for Business client is presenting PowerPoint slides in a Skype for Business meeting, sometimes only the first slide is sent to standards-based endpoints that are gatewayed into that meeting.
13026 At certain window sizes the video shown by a Skype for Business / Lync client may appear to pulse. Changing the size of the window resolves the issue.
9390 If a Skype for Business client running on Windows 7 attempts to record a Skype for Business / Lync meeting, the recording will not include any content from Pexip participants calling into the meeting through the Pexip Distributed Gateway.
8171 If a Lync 2010 client in a call with Pexip Infinity puts the call on hold, video does not properly resume when the call is resumed.


If a Conferencing Node being used as a gateway into a SfB/Lync meeting is near processor capacity and another endpoint in the SfB/Lync meeting starts sending content, a participant may be inadvertently disconnected from the conference. To resolve this, the endpoint can dial back into the conference.


Participants calling into Skype for Business / Lync through the Pexip Distributed Gateway may experience inconsistent call rejection messages if a Conferencing Node is placed into maintenance mode.


In some instances, one of two messages sent to a VMR from two SfB/Lync clients not previously connected may not be properly retained by the VMR. To resolve, re-send the message.


Participants connected via the Pexip Distributed Gateway into a SfB/Lync meeting may not receive presentation content from SfB/Lync participants. This occurs if the SfB/Lync user has a screen resolution where the width is an odd number of pixels, such as a resolution of 1437x758. If this occurs, one workaround is for the user to share an application rather than their full desktop.

Microsoft Edge browsers

Ref # Limitation
6411 Microsoft Edge browsers (which are WebRTC-compatible) cannot currently use STUN and thus cannot send media to Pexip Infinity via a TURN server. This means that Microsoft Edge users connecting to a conference from outside your network (via a reverse proxy) will not be able to send or receive audio/video.

Chrome browsers

Ref # Limitation
10545 Network connection interruptions of longer than 10 seconds may require Chrome participants to manually reconnect to a conference.

Safari browsers

Ref # Limitation
16136 Media in the Infinity Connect web app does not work in Safari on iOS 12.2.
16129 Switching camera on Desktop Safari v12.1 may lead to blank video being sent.