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....
So I can transfer a call to a queue when I enter the DDI of the queue, however, when I search for the Queue by name in the transfer box & hit transfer the original call stays with me, on hold, it doesn't get transferred to the queue.
Is this the same bug everybody else has?
Really frustrating having moved from a Cisco PBX where I could transfer to a 4 digit Hunt Group flawlessly.
TeamProMember
I have no issue transferring the call directly.
The issue only occurs when consulting first. We then have two separate calls and can't transfer the call after consulting.
Are you transferring calls to the Queue by entering the Queue name in the transfer box, or are you transferring to the Resource Account associated with the Queue please?
We can get it to work when transferring to the resource account, but you need to be an owner or member of the queue for it to be in the list of people to transfer to.