Home

3PIP Phone + Teams Meeting + SFB Server 2015

%3CLINGO-SUB%20id%3D%22lingo-sub-783942%22%20slang%3D%22en-US%22%3E3PIP%20Phone%20%2B%20Teams%20Meeting%20%2B%20SFB%20Server%202015%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-783942%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20is%20expected%20behavior%20with%203PIP%20phones%20(registered%20to%20SFB%20Server%202015)%20with%20a%20Teams%20meeting%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20say%20that%20if%20the%20phone%20is%20registered%20to%20SFB%20O%20_%20it%20will%20happily%20join%20a%20teams%20meeting%20(from%20the%20calendar%20meeting%20invite)%3C%2FP%3E%3CP%3EWhen%20the%20phone%20is%20register%20to%20SFB%20Server%20_%20it%20fails%20(from%20the%20same%20calendar%20meeting%20invite)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20SIP%20trace%20I%20see%20the%20following%20error%20on%20the%20SFB%20Server%20_%20%22Start-Line%3A%20SIP%2F2.0%20413%20Request%20entity%20too%20large%22%3C%2FP%3E%3CP%3Eie%20the%20phone%20on%20clicking%20_%20%22Join%22%20button%20sends%20an%20invite%20to%20the%20SFB%20Server%3C%2FP%3E%3CP%3EThe%20server%20responds%20with%20the%20413%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F125284i0336739A9FF09134%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20project%20intent%20was%20to%20move%20to%20%22SFB%20with%20Teams%20Collaboration%20and%20Meetings%22.%3C%2FP%3E%3CP%3EKeeping%20telephony%20on%20SFB%20server%20but%20using%20Teams%20for%20meetings%20etc.%20However%20this%20issue%20is%20a%20bit%20%22awkward%22%20if%20the%20phones%20can't%20join%20meetings%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-783942%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMeetings%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-789473%22%20slang%3D%22en-US%22%3ERe%3A%203PIP%20Phone%20%2B%20Teams%20Meeting%20%2B%20SFB%20Server%202015%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-789473%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F61235%22%20target%3D%22_blank%22%3E%40Alistair%20Keay%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20might%20want%20to%20check%20out%20the%20following%3A%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Fimaucblog.com%2Farchive%2F2018%2F07%2F06%2F3rd-party-ip-phones-and-teams-conference-join%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fimaucblog.com%2Farchive%2F2018%2F07%2F06%2F3rd-party-ip-phones-and-teams-conference-join%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20guessing%20that%2C%20for%20SfB%20Online%20homed%20meetings%2C%20there%20is%20an%20additional%20process%20occurring%20that's%20creating%20the%20SfB%20legacy%20meeting%20join%20URI%20that%20the%203PIP%20phone%20understands%20and%20is%20able%20to%20join%20the%20Teams%20meeting%20via%20an%20interop%20(SIP)%20gateway.%20On-prem%20SfB%20Server%20won't%20have%20the%20smarts%20to%20do%20this%20which%20is%20why%20it's%20not%20working%20in%20your%20%22Meetings%20First%22%20scenario%20where%20you're%20trying%20to%20use%20on-prem%20SfB%20Server%202015%20for%20calls%20and%20Teams%20for%20meetings%20(again%20guessing%20here%2C%20but%20makes%20sense).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDamien%3C%2FP%3E%3CP%3Edmunified.com%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-790760%22%20slang%3D%22en-US%22%3ERe%3A%203PIP%20Phone%20%2B%20Teams%20Meeting%20%2B%20SFB%20Server%202015%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-790760%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F62969%22%20target%3D%22_blank%22%3E%40Damien%20Margaritis%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%20for%20the%20reply.%3C%2FP%3E%3CP%3EI%20have%20had%20it%20confirmed%20that%20a%20yealink%20registered%20to%20sfb%20server%202019%20works.%3C%2FP%3E%3CP%3EI%20will%20do%20a%20bit%20more%20testing.%20(Ie%20try%20another%202015%20pool%20patched%20to%20the%20latest%20etc)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1072827%22%20slang%3D%22en-US%22%3ERe%3A%203PIP%20Phone%20%2B%20Teams%20Meeting%20%2B%20SFB%20Server%202015%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1072827%22%20slang%3D%22en-US%22%3E%3CP%3EI%20raised%20an%20MS%20case%20and%20the%20answer%20is%20that%20this%20is%20currently%20expected%20behaviour.%3C%2FP%3E%3CP%3Eie%20if%20the%20user%20sending%20the%20Teams%20meeting%20invite%20(Teams%20for%20Collab%20%2B%20Meetings%20or%20Islands)%20also%20has%20an%20SFB%20Server%20account%20then%20this%20will%20fail%3C%2FP%3E%3CP%3EApparently%20a%20fix%20is%20due%20shortly%20(I%20was%20told%20end%20of%20the%20year%202019)%20_%20the%20fix%20sounds%20like%20removing%20the%20option%20frmo%20a%203PIP%20phone%20to%20join%20the%20Teams%20meeting%20_%20which%20is%20fair%20enough%20if%20not%20ideall%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Alistair Keay
Occasional Contributor

What is expected behavior with 3PIP phones (registered to SFB Server 2015) with a Teams meeting? 

 

When I say that if the phone is registered to SFB O _ it will happily join a teams meeting (from the calendar meeting invite)

When the phone is register to SFB Server _ it fails (from the same calendar meeting invite)

 

In the SIP trace I see the following error on the SFB Server _ "Start-Line: SIP/2.0 413 Request entity too large"

ie the phone on clicking _ "Join" button sends an invite to the SFB Server

The server responds with the 413

clipboard_image_0.png

 

 

The project intent was to move to "SFB with Teams Collaboration and Meetings".

Keeping telephony on SFB server but using Teams for meetings etc. However this issue is a bit "awkward" if the phones can't join meetings

3 Replies

Hi @Alistair Keay,

 

You might want to check out the following: http://imaucblog.com/archive/2018/07/06/3rd-party-ip-phones-and-teams-conference-join/

 

I'm guessing that, for SfB Online homed meetings, there is an additional process occurring that's creating the SfB legacy meeting join URI that the 3PIP phone understands and is able to join the Teams meeting via an interop (SIP) gateway. On-prem SfB Server won't have the smarts to do this which is why it's not working in your "Meetings First" scenario where you're trying to use on-prem SfB Server 2015 for calls and Teams for meetings (again guessing here, but makes sense).

 

Cheers,

 

Damien

dmunified.com

Highlighted

@Damien Margaritis 

thanks for the reply.

I have had it confirmed that a yealink registered to sfb server 2019 works.

I will do a bit more testing. (Ie try another 2015 pool patched to the latest etc)

 

Regards

 

 

I raised an MS case and the answer is that this is currently expected behaviour.

ie if the user sending the Teams meeting invite (Teams for Collab + Meetings or Islands) also has an SFB Server account then this will fail

Apparently a fix is due shortly (I was told end of the year 2019) _ the fix sounds like removing the option frmo a 3PIP phone to join the Teams meeting _ which is fair enough if not ideall

 

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
50 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
32 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
15 Replies
Dev channel update to 80.0.355.1 is live
josh_bodner in Discussions on
67 Replies