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 Connect web app see the Connect web app release notes.

Pexip Infinity

Ref # Limitation
37183 The "Use SSH Authorized Keys from cloud service" setting (a new option introduced in version 34) on Conferencing and Management Nodes has no effect. SSH Authorized keys are always fetched from the cloud service in the same way as previous versions of Pexip Infinity.

30756

Under certain circumstances, when a Conferencing Node is handling WebRTC calls that include presentation, the observed media load may exceed 100%.

27534

A Connect app that is paired to another video device (such as a SIP endpoint) cannot be used to connect to a Media Playback Service.
24424 Only 3 of the assigned DNS servers will be used by the Management Node or by a Conferencing Node (as configured in its associated system location).

19176

Changing the IP address of the Management Node and then manually rebooting before completing the installation wizard may result in failed connectivity to Conferencing Nodes. To work around this, you must ensure that you re-run and fully complete the installation wizard after changing the Management Node configuration.

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.
15943 "Connectivity lost between nodes" alarms are not recorded in the alarm history (History & Logs > Alarm History).

13305

The G.719 codec is not currently supported for SIP.
12218 In some call scenarios that take a long time for the call setup to complete (for example calls that involve ICE, a Conferencing Node behind static NAT, and where the client is also behind a NAT) any audio prompts (such as requests to enter a PIN) may be played too early and the client may not hear all of the message.

7906

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.

6739

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.

5601

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.

Pexip Teams Connector

Ref # Limitation
35285 Participants connected via Azure Communication Services (ACS) will not see video from participants joining via CVI as "trusted". We are working with Microsoft to address the issue that these participants are filtered out. A temporary workaround is to configure your system so that CVI participants connect as normal/untrusted guests, and ensure that someone admits them from the lobby. Please contact your Pexip authorized support representative for assistance and refer to issue #35285.
34367 A Microsoft Teams Room that joins a VMR as a Guest is not treated as a Guest. For example, it will not be muted if "mute all Guests" is triggered.
27854 In a large Teams meeting you may see a discrepancy in the participant count on Pexip versus that which is reported on the Teams side. We are working with Microsoft to resolve this.

Cisco

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.

Poly/Polycom

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

Microsoft Skype for Business and Lync

Ref # Limitation

17210

RDP presentation content from a Skype for Business meeting may sometimes take several seconds to render on VTC devices that are gatewayed into that meeting. One workaround is to use Video-based Screen Sharing (VbSS) instead of RDP for content sharing. If you must use RDP then you can configure your system to adjust the bandwidth used for RDP presentation which will reduce the delay in rendering the RDP content for the VTC device — contact your Pexip authorized support representative for configuration details.

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.

5100

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.

4926

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

4812

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.

4195

Participants connected via the Infinity 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.

VMR Scheduling for Exchange

Ref # Limitation
19530 When using Microsoft's OWA with Office 365 account, join instructions that use the <style> element will not be added, even though the "Success" message is displayed to the user.
16602

In some circumstances, users are not able to obtain a VMR for a meeting if an existing meeting invitation is being edited and has previously had a VMR assigned. This may happen if a user has previously activated the add-in when editing an invitation but then discarded their changes, or if the user has removed the information added to the invitation when the add-in was previously activated. By default, users will see a message "VMR already assigned".