Known limitations

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

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


Ref # Limitation
16232 The Call-id is not logged on an administrative event when a Guest joins a conference and all Guests are muted.
16119 "License limit reached" alarms are not lowered as expected, even though an appropriate "Alarm lowered" message is logged.
16092 An alias clash on VMR creation via LDAP sync, where the clashing alias was manually configured, results in the VMR owner being repeatedly sent a VMR provisioning email after every sync. The workaround is to remove the manually configured alias.
15943 "Connectivity lost between nodes" alarms are not recorded in the alarm history (History & Logs > Alarm History).
14908 In deployments where the VMR Scheduling for Exchange feature is receiving consistently high levels of usage (i.e. more than 30 meeting requests per minute), the processing of emails by the equipment resource may be delayed. The workaround is to split users into several smaller groups, and create an individual Exchange Connector (with a different equipment resource mailbox) for each group of users.
13305 The G.719 codec is not currently supported for SIP.


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


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


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
16645 If a user who is connecting via a Skype meeting gateway session immediately disconnects the video conferencing call before the outbound gateway session connects, the call may cause a looping video connection in the Skype for Business meeting. This participant will be displayed in the Management Node and can be disconnected to resolve the issue.
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.
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.


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.

Infinity Connect web app

Ref # Limitation


Network connection interruptions of longer than 10 seconds may require Chrome participants to manually reconnect to a conference.
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.

Infinity Connect desktop client

Ref # Limitation
16068 Occasionally, if two Infinity Connect desktop clients are registered to Pexip Infinity using the same alias (user), then neither client will be able to successfully answer an incoming call.