Oct 06 2020 03:12 PM
Oct 06 2020 03:12 PM
Wondering if anyone faced similar issues or can point me in the right direction.
* Client answers call queue
* Client tries to "consult and transfer" or "transfer" and before you can even search for a user to transfer/consult it will disconnect the call
* As a work around we have been parking incoming calls
* we're using Direct routing, ticket open with MSFt and our SBC provider but it's a slow process with fingers pointing back at each other...
* i have tested by calling client direct via teams using email and transfr
Oct 06 2020 03:34 PM
Oct 06 2020 06:12 PM
Thanks Henry, I signed into teams as the client on my PC and did some testing from my mobile, issue continues so proves Network infrastructure not at fault as we use teams within our business no problems.
Oddly only half the calls seem to drop during the "transfer" or "consult and transfer" and sometimes it even works the first time, then you resume call and hit transfer again and call drops.
Checked the call logs for the user, attached debug excel file and overview shows response code: N/A along with some other odd info I couldn't find any details for which looks suspicious
Cnd_Skype_ResultDetail: Trouter client failed to deliver Http message.
I have forward this onto MSFT ticket which they can hopefully make sense of.
Oct 30 2020 04:15 AM
we are facing the same issue. Is there any feedback from support in the meantime?
Which SBC are you using?
Dec 17 2020 01:06 AM
Is there any fix being rolled out for this issue yet? It's a known problem but doesn't seem to be being resolved? Our MD is questioning why we purchased teams licenses if the most simple thing of transferring a call isn't going to work
Dec 17 2020 07:36 AM
In our case it was the wrong position of our REFER rule. Has to be first entry in Call Routing Table "from MS Teams". We are using Ribbon SBC 1K Version 9.
May 04 2021 01:03 PM
Facing similar issues with Direct Routing and Microsoft customers. This needs to be fixed!
Jun 17 2021 09:22 AM
Jul 14 2021 07:37 AM
I've had the same issue reported to me today by one of our employees. They tried to 'consult and transfer', but no-one answered, and when trying to resume the call, the line just dropped?
We are using pure Microsoft cloud Teams, no other 3rd parties involved.
Yet another Teams bug, I really don't understand why Microsoft persist in adding fancy features that hardly anyone uses rather than ironing out the bugs in the box standard features?