Jul 21 2021 02:15 AM
Hello all,
since a while I experience a changed behaviour when receiving calls in case I'm busy on another call/meeting. The option "Busy on busy is available when in a call" in Teams Calling Policies is set to "Enabled" and assigned to the users.
Teams Direct Routing is configured with an Audiocodes Mediant VE 7.20A.258.661. Everything works as expected except missed call notifications on busy.
Past (probably a few weeks ago)
Today
SBC
I deleted the Teams client cache on Windows but this did not make a difference.
I can reproduce the issue everytime. I can reproduce it in other Teams Direct Routing deployments as well.
So, did this behaviour change? Is it a Teams (client) bug? Is anyone else experiencing this changed behaviour?
I wrote a blog about an issue last year where the behaviour for missed notifications on the Teams Clients was different. Call loops after enabling busy on busy for Microsoft Teams Calling with Audiocodes Mediant – Erik's ...
The documentation does not state anything regarding missed call notifications in case of a call is rejected due to busy on busy is enabled as far as I could see. Set up policies - Microsoft Teams | Microsoft Docs
Best Regards
Erik
Jul 21 2021 05:47 AM
Jul 21 2021 10:52 AM
Hi @GerkensM,
Thank you!
I 'd guess that something was changed due to new / changed busy options. True, as you said, since a while you can not only just enable/disable busy on busy, you can also select "unanswered" which uses the user's unanswered setting.
Best Regards,
Erik
Jul 22 2021 11:49 PM
Jul 23 2021 01:36 AM
Jul 23 2021 02:31 AM
SolutionJul 23 2021 06:25 AM
Jul 29 2021 03:18 AM
Jul 23 2021 02:31 AM
Solution