Forum Discussion
Teams devices (deskphones) Throwing 488 error regarding media bypass
Have a Direct routing setup that is using media bypass.
Calls using PC client or web client are fine.
Calls using any model\mfg of Teams phone throws the following every 10 minutes and then the call drops on the 3rd event. Primarily looking at Poly CCX500 but have tried Yealink MP58 and Audiocodes C450HD as well. Updating to latest firmware and Teams app in TAC doesn't fix it.
"488 Not Acceptable Here
REASON: Q.850;cause=79;text="15cfcbd7-1ab7-4d79-9957-85344e485f29;BackToBackBypass offer was declined by Peer" "
I have tickets open with Microsoft and Poly. No one seems to know what is going on.
Any one else seeing the same behavior?
6 Replies
DayneJake
I'm just receiving the same reply from Microsoft when a re-invite from PSTN (Proximus) is relayed back by AudioCodes SBC to Microsoft cloud.
Interestingly this only affects native Teams clients, browser-based Teams clients work fine. The reason must be that browser-based clients do not support media bypass.Not all calls fail, currently what I know are emergency test calls to 117 in Belgium, after entering a DTMF digit. I could not get other numbers to fail yet.
The re-invite looks completely normal, with public IP in the SDP "c=" parameter.
I need to open a ticket at Microsoft.Hi, is there already an update or a solution provided by Microsoft. It looks like we have a similar behaviour in our environment.
Marco1187 I am facing similar issue in our environment but instead of 488 Un-acceptable media, we are getting 491 Gone here. We have raised case with microsoft, but no luck.
- We turned off Media Bypass on the SBC and also in TAC. The call does not drop and we do not see the 488. Microsoft still working on the ticket.
We have seen similars, but those has appeared in very begin of the calls. And we have asked from the SIP trunk provider why this is happening. We are still in middle of that. But have you asked from your SIP trunk operator of this? Which SBC you are having? And is it really phone which is sending that SIP message?
- The 488 is coming from the Microsoft leg of the traffic in the SBC syslogs. This only happens when using a Teams phone device. When using a PC client or Web client, a 200 ok response is issued.
