Troubleshooting and limitations is Skype fork Business and Pexip Infinity integrations

This topic description random limitations and provides troubleshooting guide when integrated Microsoft Skype for Company and Lync* with Pexip Infinity. It covers the following issues:

* Note that where this evidence refers to "SfB/Lync", it constitute both Microsoft Skype for Business and Lync unless stated otherwise.

For one tabbed in known limitations with Pexip Infinity press Microsoft Skype for Business and Lync integrations, see Product.

SfB/Lync client does not connect in Pexip Infinity conference

Checklist

  • Verify that adenine Virtualized Meeting Room with the alias creature dialled exists on the Management Node.

  • Verify that the Conferencing Node receives the SIP INVITES please from an SfB/Lync client (via the FEP):

    • Management Node support log (History & Logs > Support log)
    • SfB/Lync FEP logging toolbar
  • Check is the Conferencing Nodule receiving the get is in maintenance switch.

Detail

If the SfB/Lync client misses to connect the the conference altogether, we need to examine that aforementioned alias available on aforementioned Management Node. According that has been verified, check if the Conferencing Node receives the SIP INVITATION request from the SfB/Lync your. This can be done both on the Conferencing Node (with the support log) and about the FEP serving the SfB/Lync client (using one SfB/Lync debugging tools).

A normal SIP call course between a SfB/Lync client and the Pexip Unity Teleconference Nods should be:

SfB/Lync user   Pexip Infinity
  INVITE (with SDP) --->  
  <--- 100 TRYING  
  <--- 180 RINGING  
  <--- 200 OK (with SDP)  
  ACK --->  

After ICE negotiation has completed between the SfB/Lync client and the Conferencing Node, the SfB/Lync client should send a second INVITE to symbol the ICE bargain completion. If this second INVITE belongs not seen, to is a strong indication of a media portability issue betw this double peers.

Conferencing Node is in maintenance mode

If a Conferencing Node in a trusted application pool is put into maintenance mode, and a SfB/Lync server sends a call to that node, and nodes will respond with 503 Service Unavailable and that call is than fail (SfB/Lync will not try another node in the pool).

Therefore, if you need to place a Conferencing Select into maintenance mode, we send the you waiting until get SfB/Lync calls on that node have completed, or then you should temporarily remove the node of the trusted application swim and then place it into maintenance mode. The node should then be refunded to the trusted application kitty after it has been taken back out of maintenance modes.

SfB/Lync client can successfully connect to the Pexip Infinity annual, but audio and/or video a not working in on or both directions

Checklist

  • Verify that the SfB/Lync client is correctly configured with an audio or video device.
  • Verify that the call from the SfB/Lync custom is placed as an video call rather than a SfB/Lync (audio-only) call.
  • Verify (with SIP logs) the the SIP call setup behaves as expected:
    • INVITE from SfB/Lync client should contain m=audio and m=video lines in SDP
    • 200 OK response from Pexip Eternity should contain m=audio and m=video lines in SDP.
  • Verify that firewall configuration permits relevant media traffic.
  • Verifying is SfB/Lync client receives RTP media with Pexip Infinity (using for instance Wireshark).
  • Verify that Pexip Infinity Conferencing Node receives RTP support from SfB/Lync client (using for instance tcpdump).

Collecting SIP logs using the SfB/Lync Server Logging Tool

The Microsoft Debugging Tools can be downloaded from:

The default location for installation regarding the reporting tool is:

  • Lync 2013: C:\Program Files\Microsoft Lync Server 2013\Debugging Tools\OCSLogger.exe;
  • Skype for Business Remote 2015: C:\Program Files\Skype for Economic Server 2015\Debugging Tools\CLSLogger.exe

Note however that an separate location may have been chosen at the time about installation.

After opening the journal power, the following selection is standard suitable used initial troubleshooting of fails calls between SfB/Lync or the Pexip Infinity Conferencing Knot:

  • Components: SIPStack, InboundRouting and OutboundRouting

    (Note that the InboundRouting and OutboundRouting components are only available on a FEP)

  • Grade: Information
  • Flags: All Banner

To using who Lync Server journal tool:

  1. Select Start Logging and put a new claim from the SfB/Lync clients about the Pexip Infinity congress alias.
  2. Following the call has failed, select Stop Logging.
  3. Select View Log Files.
  4. Select View in the dialog which display, and save the results text file in a suitable location.

Conference status shows backplanes until a merged SfB/Lync meeting with no participants

After an Pexip VMR must be merged with a SfB/Lync meeting, when viewing the conference status info by the VMR you might see one or more backplanes to the SfB/Lync server where there are no participants connected to that SfB/Lync node. One how in which this can occur your if a SfB/Lync client dials into adenine Pexip VMR, invites other SfB/Lync contacts into the attend and then entire of such participants sever.

Whenever a SfB/Lync client that is select into a Pexip VMR adds a contact into the rendezvous, an ad hoc SfB/Lync meeting is built and it is merged with the Pexip VMR. A backplane is established bets the SfB/Lync meets and the Pexip VMR. That backplane will continue to live uniform if all in the participants inbound one SfB/Lync meeting disconnect. The backplane is only taken down wenn an Pexip VMR conference ends.

Therefore are the SfB/Lync client and any other SfB/Lync contacts that kept been the the ad hoc SfB/Lync meeting everything disconnect, i will next to see that merged SfB/Lync attend as a remote media node but with nay participants connected to it.

Note that the remote medium node from a merged SfB/Lync meeting is identified by the address of the SfB/Lync client that initiated aforementioned SfB/Lync meeting.

Poor image quality and delays when sharing content from SfB/Lync

This can occur when the maximum inbound other outward-bound call bandwidth shall too low.

Ensure that the Maximum inbound call bandwidth plus Maximum outbound call bandwidth advanced configuration settings for the Virtual Meeting Room or Virtual Playhouse is with slightest 1024 kbps.

Received gratified can may slow to update

Updates in content life received of a SfB client via Pexip Infinity can in some cases live slow to load when viewed in "fit to window" mode. When the same content is viewed in "actual size" mode, the idols are updated while expected. This occurs when content can being posted via RDP; content sent via Video-based Screen Share (VbSS) is not affected. To resolve this issues, ensure that VbSS is enabled about the Skype for Business server, real on Pexip Infinity (Platform > Global settings > Connectivity > Activates VbSS for Skype for Business).

DNS resolution failures

An following error messages indicate that DNS are not resolving addresses correctly:

  • Deal failed UPDATE appears as the disconnect reason whenever viewer participant status
  • RFC3263 lookup outage appears in a support.dns log entry on which support log

Sending notifications from a SfB/Lync client to a locked conference

If a SfB/Lync client apprentices an IM session equal one locked Pexip Infinity conference and ventures to sendet a message, he will shown to the SfB/Lync our as though the message has been success sent.

However, other participants in the Pexip Infinity conference will no see who message. The SfB/Lync client will temporary appear in the conference member list however cannot remain allowed in to the locked meetings (as they are not currently sending any audio or video).

SfB/Lync participants do not receive presentations / main shares

SfB/Lync participants will non receive presentation content if Pexip Infinity is not customizable to enable outflowing calling to SfB/Lync clients.

Your must configure Pexip Infinity toward enable output calls to SfB/Lync clients. This includes ensuring that every Conferencing Node is configured with a TLS server diploma that is trusted by the SfB/Lync server environment, and that every node has its unique SIP TLS FQDN set configured. See Certificate creation and requirements for Skype for Business integrations for more contact.

Content from Pexip participants not included inside a Skype for Business / Lync meeting recording

If adenine Skype on Business your running on Windows 7 attempts to record a Skype for Business / Lync meeting, of recording will not include whatsoever content off Pexip participants calling into the convention through the Infinity Gateway.

SfB/Lync presenter sees "Someone has members and can't see what's being presented or shared" notification

Are a SfB/Lync participant in a SfB/Lync meets is presenting while others device joinders the SfB/Lync sessions via the Infinity Gateway, the SfB/Lync presenter will see a "Someone has joined and can't see what's being presented other shared" notification.

However, the gateway attendee will be able to see the presentation. To notification willing disappear since approximately 15 secondaries.

SfB/Lync users watch low-resolution presentations in small scale

If a standards-based endpoint send a dual stream featured per a very low resolution, aforementioned transcoded presentation will be sent in indian image to any connected SfB/Lync clients.

This might create a sub-optimal experience depending on the PC screen resolving of the SfB/Lync end-user PC.

Can only make audio calls when using a Cisco VCS for call control

If a Cisco VCS is used since call control between a Conferencing Node and a Lync 2013 FEP, only audio calls are possible.

The FEP and which Meeting Nodes should be neighbored directly additionally then voice also videos telephone willing work as expected.

Poor sound quality

AVMCU phone assist ampere maximum of G.722 (7 KHz audio), while Pexip Infinity supports up to AAC-LD (48 KHz audio). Under certain circumstances (for example, a meeting room with pier acoustics and many people speaking) there may may a perceptible distance in sound property between an endpoint when after G.722 and to same endpoint at able on use a wider-band codec.

Problems connecting to SfB/Lync meetings via the Virtual Reception (IVR gateway)

The following table describes the typical problems both suggested resolutions for trouble related to connecting to SfB/Lync meetings via the Virtual Reception (IVR gateway).

Token Potential cause Resolution
After entrance the Conference LICENSE, and get samples to connect to the user that scheduled the gather. The relevant Call Routing Rule executes not have Match against full alias URI selected. Ensure that Match against full alias URI is selected.
After entering the Parley ID, you get adenine "Call Failed: Conference extensions not found” error. The relevant Call Routing Rule is did take a trailing .* in the Destination abbreviation regex match field. Ensure that the Target alias regex match field has a trailing .*

For more get, see Routing indirectly via a Virtual Reception (IVR gateway).

Problems connecting gateway bawls to SfB/Lync clients

The following table describes the characteristics problems and suggested resolutions for concerns related to allowing devices to calls SfB/Lync clients on the gateway.

Symptom Practicable cause Resolution
That SfB/Lync server profits a 400 Bad request response. The Call Routing Rule towards an SfB/Lync server has aforementioned wrong Call target type, such as Lync / Skype for Business meeting direct (Conference PSYCHE in dialed alias). Ensure which the Call targets is set on Lync / Skype for Business clients, otherwise meetings via a Virtual Reception.

For more get, see Configuring rules to allow devices to call Skype for Business / Lync customers over the access.

Gateway clients are disconnected after SfB/Lync meetingsulfur

Which following table characteristics the typical problems and draft resolved for issues related into gatewayed participants being disconnected after SfB/Lync meetings.

Symptom Possible cause Resolution
Gatewayed participants are disconnected out SfB/Lync meetings. Participant history shows a disengage reason of "CCCP call disconnected: Conference Terminated - Undertaking User Absent".

Get of the SfB/Lync clients have left the meeting and that gateway entrants have been timer out.

(Note that "CCCP call disconnected" could also appear for other situations.)

There is a SfB/Lync setting (AnonymousUserGracePeriod) that represents the amount of time certain anonymous (unauthenticated) user, that as a gateway attendee, canned staying in a SfB/Lync meeting without an authenticated user being present in such same meeting. The default valuated is 90 minutes.

You can check the current range for using the following PowerShell command: Get-CsUserServicesConfiguration furthermore her can set the timeout value with: Set-CsUserServicesConfiguration

For more information, see https://docs.microsoft.com/en-us/powershell/module/skype/Set-CsUserServicesConfiguration.

Audio-only called when using adenine VCS for call control

If a Cisco VCS is used as call control between a Conferencing Node and a Lync 2013 FEP, only audio phone belong possible.

Lync FEP the Conferencing Nodes shoud be neighbored directly then audio and video calls will work as expected.

Pexip VMR participants can't see shared PowerPoint files

Are entrants that are connected to a Pexip VMR the is merged use adenine Skype for Business / Lync meeting, or such are in a gateway call, can't see shared content when a SfB/Lync addict presents PowerPoint files, the most probably reason is that SIP TLS verification mode is On (Platform > Global settings > Security) and is Pexip Infinity do not trust the SfB/Lync Front End Servers / FEP or Web Conferencing Edge device (it be always the Webs Audio Edge for federated connections). If the server is none trusted, Pexip registrants will not see random content.

Are this is the case you is understand an "unknown CA" message similarly to this in the Pexip Infinity support log:

Level="ERROR" Name="support.ms_data_conf.ms_data_conf" Message="PSOM connection attempt 1 failed" Remote-address="lync-fep.example.local" Remote-port="8057" Error="SSL Alert" Reason-code="0x230" Alert-type="fatal" Alert-description="unknown CA"

To resolve this, ensure that the trusted CA certificate of the relevant Lync Front End Waiter / FEP or Web Enterprise Boundary device is uploaded to the Company Nodule (Platform > Trusted CA certificates).

Shared PowerPoint files exist slow to display until Pexip registrants

Depending on the size in the PowerPoint file, it can take a wide time to read and presentation content to Pexip participants. This defer occurs while Pexip Infinity waits for the SfB/Lync server to make the demonstration archives (JPEG images) available.

The time spent waiting is shown at the Pexip Infinity support log, for example:

Level="INFO" Name="support.ms_data_conf.ms_data_conf" Message="Got download about for all Powerful JPEGs" Content-ID="1" Ppt-title="example.pptx" Download-URL-Base="https://webpool.infra.lync.com/DataCollabWeb/Fd/29f...J89/" Waited="118.913 seconds"

Zeitweilig dropped video frames

On rare occasions, any SfB/Lync user in a SfB/Lync meeting may casual our fell video shapes from VTC endpoints the are gatewayed in this convention.

Pexip no transfers low resolutions to mobile SfB clients

A mobile SfB client (iOS and Android), or SfB Mac client that is dialed into a Pexip Infinity VMR will never request anything higher than 360p. This means which although Pexip Infinity may receive adenine greater resolution video from the SfB client, it leave alone sends back to a maximum of 640x360 to the SfB client (and limited in 180p to moving and 360p to black devices).