We have Edge and SE Server for Lync 2013 and in the same topology a Skype for Business Standard Edition Server. Users homed on the new Server cannot join external conferences.

Client sends BYE after 10 seconds, with this message

ms-client-diagnostics: 52527;reason="Tearing down session due to failure while dialing in"

Any help?

Hi

Have you configured the SfB server to use the 2013 edge pool?

thanks

Yes of course. I can use SfB for everything except conferences hosted somewhere outside. I can use it from home etc. - everything works.  Did not find anything about diagnostic code 52527 at all.

Thanks

Johann

Hi,

Would you please tell us the issue happen with the conference hosted by federated partners or for users who (belong for your corporation) external the corporation?

If the issue happen for federation partners, please double if the SFB Server choose the Edge Server 2013 as the next hop to access external network, and the users who homed in SFB Server enable federation function as well.

If the issue happen for the users who external the corporation,  make sure the there is no port limitation for SFB Server.

Best Regards,
Eason Huang

Hi,

thanks for this detailed statement.

The issue happens whenever one of our users is hosted on SfB and is invited from anyone outside (e.g. federated Partner) to a conference. Federation is enabled for all users, Edge 2013 is assigned as next hop for both Lync and SfB Server. Users can communicate via federation - only external conferences are failing.

SIP communication at the Client:

In parallel there are some NOTIFY Messages coming from the external site.

Hi,

Base on your description above, the issue happen with federated partner.

If it is the case, the issue may happen on the Edge Server side.

Conferencing Media Establishment (Federated):  CustomerA IS federated with CustomerB. CustomerB creates a Lync meeting and sends it to CustomerA. CustomerA joins the meeting.

1. Customer A is joining using the Lync 2010 client CustomerA (attendee) will connect to CustomerA's Edge then to CustomerB's (organizer) Edge and finally onto the MCU provisioned for the meeting from the organizer pool
   1. Calling Party (attendee) <-> CallingPartyEdge (attendee Edge) <-> CalledPartyEdge (organizer) <-> MCU (organizer)
2. Customer A is joining using the Lync 2013 client - CustomerA will try to tunnel media traffic to its own Edge which will then do FTURN with CustomerB's Edge. If the FTURN is successful, the media will be between CompanyA's Edge and CompanyB's Edge on 3478 -3478 for audio and 50k source to 443 destination for desktop sharing. If FTURN fails then media between the Edge servers will try to use 50k range ports.
   1. Calling Party (attendee) <-> CalledParty (AV MCU) - Unlikely, but possible. The non-Federated user would have to be internal to the network where the conference is hosted
   2. Calling Party (attendee) <-> CallingPartyEdge<->CalledParty (AV MCU) - Very unlikely. Would mean the AV MCU can directly connect to 50k of the attendee Edge
   3. Calling Party (attendee) <-> CallingPartyEdge<->CalledPartyEdge<-> AV MCU (organizer) - FTURN this is the most common scenario that would work.
   4. Calling Party (attendee) <->CalledPartyEdge<-> AV MCU (organizer) - If attendee can connect directly to 50k of the AV MCU Edge

So please check if the 50,000-59,999 ports open on both Edge Servers external interface for your corporation and the partner corporation.

Best Regards,
Eason Huang

Edge ports are open - otherwise it also would not work with users registered on Lync 2013 server. The problem happens only with users registered on Skype for Business server. Both are using the same client.