You are here: Installation > Release notes > Known limitations

Known limitations

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

Pexip

Ref #

Limitation

8250 Outbound calls that do not accept all offered media streams from Pexip Infinity may fail if a subsequent empty re-INVITE causes a mix of encrypted and non-encrypted streams to be offered.
8247 Occasionally, a backplane between nodes may temporarily lose connectivity when the IPsec connection is rekeyed.
8211 If an endpoint does not signal specific H.264 packetization mode support when setting up an H.323 call, Pexip Infinity will ignore all H.264 capabilities.
7906 If a caller dials into a Virtual Reception and enters the number of the conference they want to join, but there are insufficient 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.
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.
6001 An Infinity Connect Host participant who has joined a Host-PIN-protected conference as control-only (and there are no other Host participants) cannot use the green telephone icon next to a participant's name in the roster to let a Guest participant (who is waiting to join) into the conference. The workaround is to use the Start conference option, which will let in all Guest participants.
4312 Occasionally, group chat messages may not be displayed to Infinity Connect Web App participants who are using Internet Explorer.

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.

Microsoft

Ref #

Limitation

8240 Conferencing Nodes deployed in Microsoft Azure which are upgraded to v14 may not boot after upgrade. The workaround is to redeploy the node.
8237 Lync / Skype for Business clients that are connected to a VMR may lose their connection if a Lync/SfB client is presenting content and then a second Lync/SfB client starts presenting a PowerPoint file.
5951 If a Virtual Auditorium is configured with different layouts for Guest view and Host view, and that Virtual Auditorium is then gatewayed into a Lync / Skype for Business meeting, the Virtual Auditorium call may be dropped. The workaround is to configure the same layout for Guest view and Host view within a Virtual Auditorium.
5100 If a Conferencing Node being used as a gateway into a Lync meeting is near processor capacity and another endpoint in the 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 Lync/Skype for Business through the Pexip Distributed 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 Lync clients not previously connected may not be properly retained by the VMR. To resolve, re-send the message.

4195

Participants connected via the Pexip Distributed Gateway into the AV-MCU may not receive presentation content from Lync participants. This occurs if the 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

8133 When viewing the live platform status and conference status graphs in a Microsoft Edge browser, if there are any labels that contain a hyphen or dash the graph will not render correctly, and zooming or panning within the graph will leave traces of the label.