Media Bypass

%3CLINGO-SUB%20id%3D%22lingo-sub-332940%22%20slang%3D%22en-US%22%3ERe%3A%20Media%20Bypass%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-332940%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20input..%20Just%20to%20update..Proxy%20Relay%20was%20added%20in%20the%20supported%20media%20section%20on%20the%20SBC.%20Turned%20this%20off%20and%20all%20was%20fine....%20Its%20a%20little%20frustrating%20given%20the%20length%20of%20time%20we%20have%20been%20playing%20with%20it...%20But%20this%20seems%20to%20work%20for%20us%20now...%20Calls%20flowing%20like%20a%20champ!%20Now%20the%20fun%20REALLY%20begins!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331558%22%20slang%3D%22en-US%22%3ERe%3A%20Media%20Bypass%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331558%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20it%20is%20some%20configuration%20error%2C%20not%20Media%20Bypass.%20Media%20Bypass%20is%20not%20used%20or%20supported%20for%20Direct%20Routing%20yet.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E488%20could%20be%20that%20the%20phone%20numbers%20you%20send%20in%20the%20SIP%20INVITE%20is%20not%20formated%20the%20way%20that%20Teams%20want%20it%2C%20you%20should%20check%20the%20fields%20for%20to%2C%20from%2C%20contact%20and%20p-asserted-identity.%20It%20could%20also%20be%20codec%20problem%2C%20so%20that%20your%20SBC%20and%20Teams%20don't%20use%20the%20same%20codecs.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20should%20check%20the%20SIP%20logs%20at%20your%20SBC%20to%20start%20with%2C%20there%20you%20will%20be%20able%20to%20see%20more%20about%20the%20488%20error%20and%20what%20caused%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20couldn't%20see%20your%20image%20that%20you%20sent.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%2FLinus%20Cansby%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-667052%22%20slang%3D%22en-US%22%3ERe%3A%20Media%20Bypass%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-667052%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F260731%22%20target%3D%22_blank%22%3E%40WelshViking%3C%2FA%3E%26nbsp%3BCould%20you%20tell%20me%20where%20is%20the%20SBC%20section.%20I%20haven%C2%B4t%20found%20the%20field%20%22proxy%20relay%22%26nbsp%3B%20on%20the%20output%20of%20cmdlet%20%22get-csonlinepstngateway%22.%20Actually%20we%20are%20facing%20a%20similar%20problem%2C%20but%20in%20our%20case%20is%20about%20outgoing%20call%2C%20when%20the%20call%20is%20put%20on%20hold%2C%20the%20call%20is%20dropped.%20We%20have%20seen%20a%20488%20message%20with%20text%20message%20%22back%20to%20back%20bypass%20offer%20was%20declined%20by%20peer%22.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331545%22%20slang%3D%22en-US%22%3EMedia%20Bypass%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331545%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20had%20some%20severe%20teething%20problems%20deploying%20direct%20routing%20with%20our%20SBC.%26nbsp%3B%20we%20now%20have%20a%20successful%20connection%20when%20calling%20into%20teams...%20but%20not%20when%20calling%20out.%26nbsp%3B%20When%20calling%20out%20the%20call%20is%20disconnected%20after%203%20seconds%20with%20a%20response%20code%20488.%20looking%20at%20the%20report%20in%20teams%20the%20only%20difference%20is%3A%3C%2FP%3E%3CP%3Esuccessful%20call%3A%3C%2FP%3E%3CP%3EWhere%20as%20a%20failed%20call%20shows%20FAILED%20in%20these%20fields...%26nbsp%3B%20%26nbsp%3BIs%20this%20a%20media%20bypass%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-331545%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-673824%22%20slang%3D%22en-US%22%3ERe%3A%20Media%20Bypass%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-673824%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F354250%22%20target%3D%22_blank%22%3E%40Jesus_Ortiz%3C%2FA%3E%26nbsp%3B%20this%20was%20on%20the%20SBC%20itself%20not%20on%20within%20the%20365%20environment%2C%20sorry%2C%20i%20should%20have%20made%20that%20clear.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
WelshViking
Contributor

We have had some severe teething problems deploying direct routing with our SBC.  we now have a successful connection when calling into teams... but not when calling out.  When calling out the call is disconnected after 3 seconds with a response code 488. looking at the report in teams the only difference is:

successful call:

image.pngWhere as a failed call shows FAILED in these fields...   Is this a media bypass issue?

 

 

 

 

 

4 Replies

Hi,

 

I think it is some configuration error, not Media Bypass. Media Bypass is not used or supported for Direct Routing yet.

 

488 could be that the phone numbers you send in the SIP INVITE is not formated the way that Teams want it, you should check the fields for to, from, contact and p-asserted-identity. It could also be codec problem, so that your SBC and Teams don't use the same codecs.

 

You should check the SIP logs at your SBC to start with, there you will be able to see more about the 488 error and what caused it.

 

I couldn't see your image that you sent.

 

/Linus Cansby

Thanks for the input.. Just to update..Proxy Relay was added in the supported media section on the SBC. Turned this off and all was fine.... Its a little frustrating given the length of time we have been playing with it... But this seems to work for us now... Calls flowing like a champ! Now the fun REALLY begins!

@WelshViking Could you tell me where is the SBC section. I haven´t found the field "proxy relay"  on the output of cmdlet "get-csonlinepstngateway". Actually we are facing a similar problem, but in our case is about outgoing call, when the call is put on hold, the call is dropped. We have seen a 488 message with text message "back to back bypass offer was declined by peer".

@Jesus_Ortiz  this was on the SBC itself not on within the 365 environment, sorry, i should have made that clear. 

Related Conversations