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....
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
ThorstenAlso still the same problems on our side!
Really bad this is taking so long... hope they come with the fix soon!
Going to check if i can find my ticket number and also going to reopen it.
Today I get the following answer from Microsoft on my reopened ticket: In my reopened ticket I pointed to this discussion ...
"
As I can see that the issue which you have reported and which is mentioned on the shared article, still remains a known issue for Microsoft. Our engineering team is actively working on it but unfortunately, we will do not a fix for the issue yet nor an ETA to share with you.
Consult then transfer is available for the user since the release of multiwindow calling and meetings to Global Availability. That being said, consult and transfer does not work in the context of transferring to CQs.
Ref: https://support.microsoft.com/en-us/office/transfer-a-call-in-teams-b7f40f14-e083-46b9-b739-68038c8f73a0
There were few issues related to Consult then Transfers which were resolved by disabling the New Meeting Experience in Teams Client Settings. I would suggest you can also try this workaround and check if it works for your environment. Please feel free to reach us back if need status detail in future.
We regret the inconvenience caused to you.
"
..... unbelievable.
Today I was a participant at the Teams Community Day ... I get in contact with another participant who had the same issue ... he said he could solve this with some changes on his SBC. I will get those detail informations in the next days ... but I can not really beleive that changes on the SBC can solve this issue because the call will not left microsoft environment when we select "consult then transfer" ...
I will let you know up to date
regards
Thorsten