Forum Discussion
Music on Hold in Teams & 4 seconds until Hold is in place for caller
Thank you for sharing, I would not say that there might be still missing infrastructures for some regions
😞
But what I see on our tenant is that they improved the time for transferring the call to the bot.
Still that ring to calling party which is put on hold and transferred to MoH bot is confusing but it is what it is.
A little update from our end on this issue. My IT Manager has put in a ticket about ensuring the correct zone is being used for the hold bot, as we are in Australia. They were quick to get the ticket underway but I haven't heard anything further in the meantime though.
What HAS made a difference, though, is that on my call queues I have opted in to the Conference Call option. This has increased the speed of answering by quite a few seconds, and we are now only having to press resume once and the caller is coming back straight away!
We just made sure we were using the protocols as in this instruction:
Thanks all for your assistance, it's great that we can work together to find solutions for these issues.
- GasmanzSep 17, 2020Brass Contributor
VickiFHL
We are still seeing on hold delays of 3-10 seconds for Teams Direct Routing calls to individual users.
I have also been talking to our SBC support about the transfer silence issue. They have advised that some Telcos actually inject their own MoH when Teams sends a re-invite after the user presses "Transfer" in the Teams client. The 2 largest Telcos in Australia (Telstra and Optus) do not inject their own MoH for re-invites they receive that have a=inactive or a=sendonly in the SDP. For these carriers and many others, you need the SBC to intercept these re-invites and inject a MoH audio stream on behalf of the Teams user.If injecting your own MoH at the SBC you may have an issue for blind transfers. Blind transfers start with a re-invite from Teams on first "transfer" button press, but then after you enter the phone number and press "transfer" a second time to complete the transfer, Teams sends a refer with no SDP to notify the SBC that a=sendrecv now. Could be that some SBCs are able to deal with this however.
It would be good if Teams actually acted more like a PBX and did this stuff on its own.