Teams Blind Transfer to a Call Queue fails when you select "Ring back if there's no Answer"

Question

Hi

Please i have a colleague who is having this issue. I need your assistance to get it resolved.

Teams Blind Transfer to a Call Queue fails when you select the "Ringback if there's no answer" option. If you click the Transfer button to transfer the call to a Call Queue and select the "Ringback if there's no answer" option, Teams immediately calls back with the message that the call transfer failed.

If you do not select the "Ringback if there's no answer" option, the transfer to the Call Queue works. The "Ring back if there's no answer" option works when you transfer to a user.

It looks like, when the "Ring back if there's no answer" option is selected, Teams does not even send a SIP REFER to transfer the call.

Is this a known issue?

Answer 1

I've filed case 33074057 and Microsoft has confirmed the issue:

"the current issue you are facing is a known one and can be replicated in different organizations as it is not possible to use safe transfers (Ringback if there's no answer) with non-user accounts such as CQs and AAs"

I've filed a feedback request to make this immediately obvious as opposed to let the user try and fail (could use some votes):

https://feedbackportal.microsoft.com/feedback/idea/0954a64c-8e54-ed11-a81b-000d3a7e4185