This can be done both on the Conferencing Node (with the support log) and on the FEP serving the SfB/Lync client (using the SfB/Lync debugging tools).Ī normal SIP call flow between a SfB/Lync client and the Pexip Infinity Conferencing Node should be: SfB/Lync clientĪfter ICE negotiation has completed between the SfB/Lync client and the Conferencing Node, the SfB/Lync client should send a second INVITE to signal the ICE negotiation completion. After that has been verified, check if the Conferencing Node receives the SIP INVITE request from the SfB/Lync client. If the SfB/Lync client fails to connect to the conference altogether, we need to verify that the alias exists on the Management Node.
Content from Pexip participants not included in a Skype for Business / Lync meeting recording.SfB/Lync participants do not receive presentations / content sharing.Sending messages from a SfB/Lync client to a locked conference.Poor image quality and delays when sharing content from SfB/Lync.
Conference status shows backplanes to a merged SfB/Lync meeting with no participants.Collecting SIP logs using the SfB/Lync Server Logging Tool.SfB/Lync client can successfully connect to the Pexip Infinity conference, but audio and/or video is not working in one or both directions.SfB/Lync client does not connect to Pexip Infinity conference.This topic describes any limitations and provides troubleshooting guidance when integrating Microsoft Skype for Business and Lync* with Pexip Infinity.