Forum Discussion
Consult then transfer to call queue is not working
I have just been on with a support rep, and I think they found an answer....
you have to assign a DDI to the call queue, then you should be able to transfer a call to it.
there is allegedly documentation around this which I am waiting for, and also a site where I can request a feature from Microsoft - one can hope 🙂
this does seem odd where a purely sip based PBX in the cloud requires DDI to be assigned.
Hope this helps
I have had to do some creative work where I assigned the DDI but diverted the DDI on the sip trunk to the main number - I don't want to be woken in the night with a caller asking about their hospital appointment just because the put the wrong DDI on their paperwork....
Lars86 Microsoft rep has told me it's a known issue. Please up vote it here: https://microsoftteams.uservoice.com/forums/908686-bug-reports/suggestions/41005159-call-consult-and-transfer-to-a-call-queue-transf
They expect a big release half december where they are aiming to fix this issue..
Hopefully! That is what they promised in April.
Thorsten StiebigAny news regarding this issue?
I opened a ticket in November and Microsoft sent me the documentation on how to transfer a call. *rolleyes*
Today after 2 months they told me that there is no problem on the Microsoft side. I'm a bit furious, because I referred to this discussion and they did not even bother to read it.
In the steps recording I clearly stated where the transfer button disappears. I can reproduce this behavior using the resource account name to transfer the call to, so I don't even leave the Teams-environment.
Even so Microsoft insists that there is a problem on the side of our telephony provider.This is nonsense what Microsoft told you. It is a known issue at Microsoft side and all people with direct Routing have the same issue. It is stupid to say that all phone providers are the problem. I have no informations that this is working at any phone Provider. I have the official statement from microsoft that this is an error on Microsoft side and that it should solved to the end of 2020. I have still the same issue and we are now in january 2021. I will reopen my Ticket and will ask when we could receive a solution.
Regards
Thorsten
