Forum Discussion
Jonny Marlborough
Aug 11, 2020Brass Contributor
Delay transferring out from auto attendant
We have been testing Teams with Direct Routing trunks provided by a carrier partner. All inbound and outbound calls direct to/from Teams users connect without issue. We are using the Teams apps on Wi...
YouGotServered
Sep 15, 2021Brass Contributor
So, I think our issue is the same, or at least has the same causes as yours.
Essentially, our ideal call flow is Auto attendant > call queue > receptionist.
Unfortunately the handoff from AA to CQ takes a solid 5 seconds. Add that to the initial connection from the caller to AA (about 1 second) and then the handoff from the CQ to the receptionist (about another 2 seconds) and you have a SOLID 7+ second delay from the time someone dials to the time they talk to someone even if the receptionist answers IMMEDIATELY.
Clients have complained that it takes way too long, and they aren't wrong.
Is my issue the same as yours?
Has Microsoft finished the fix for this yet?
Essentially, our ideal call flow is Auto attendant > call queue > receptionist.
Unfortunately the handoff from AA to CQ takes a solid 5 seconds. Add that to the initial connection from the caller to AA (about 1 second) and then the handoff from the CQ to the receptionist (about another 2 seconds) and you have a SOLID 7+ second delay from the time someone dials to the time they talk to someone even if the receptionist answers IMMEDIATELY.
Clients have complained that it takes way too long, and they aren't wrong.
Is my issue the same as yours?
Has Microsoft finished the fix for this yet?
Jonny Marlborough
Sep 20, 2021Brass Contributor
That sounds like the same issue we have. I've not tested in a while but I've not seen any announcement that it has been fixed yet, and from people's testing in this thread it seems to still be a problem.
- _PeterL_Oct 11, 2021Copper ContributorIs your tenancy in a different region to the call queue members? (this was my scenario and I was getting the delay - we managed to resolve using some other SBCs and essentially relaying the call from SBC to SBC so that it breaks out in the same region as our tenancy.)
- YouGotServeredOct 11, 2021Brass Contributor
_PeterL_ Ours is all the same region.
Sadly due to this issue and the continual Teams outage (like the one last week due to a bad update that MS had to rollback due to lack of good QA), we have been instructed to look for a replacement ASAP.
Microsoft's horrendous and slow support is not acceptable for something as critical as phones, ESPECIALLY when we've had 3 outages in the past 6 months (NOT including the bandwidth.com DDoS attack which I can't blame MS for). Our clients want a vendor that they can actually call and get resolutions from instead of essentially throwing a ticket into a volcano. Most of our Teams issues have gone unresolved with support. We've been told to wait months for resolutions that never come.
Teams is a good platform, but not for traditional calling I'm afraid.