A community member has associated this post with a similar question:
Teams Blind Transfer to a Call Queue fails when you select "Ring back if there's no Answer"

Only moderators can edit this content.

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

IBN 4,331

Hello Teams Community

Please i need your help on this issue.

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?

Yuki Sun-MSFT 40,856 Reputation points

2022-04-17T06:45:41.957+00:00

Hi @IBN ,

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.

I tried searching around but so far haven't seen any official statement or other similar reports about this issue. Given this, you may have a look at the Service health page in the Microsoft 365 admin center and see if there's any relative issue of Teams in your tenant.
Yuki Sun-MSFT 40,856 Reputation points

2022-04-20T09:19:01.243+00:00

Hi @IBN ,

Just checking in to follow up with this issue. Should there is any update or you are still looking for help on this, feel free to post back.
IBN 4,331 Reputation points

2022-04-21T15:22:57.793+00:00

Thank you for your email.

We are indeed using a direct routing setup which should be configured correctly.

The health dashboard for direct routing shows 2 warnings (certificate about to expire) but we still have some time for renewal (see screenshot below).

I’m able to reproduce the issue 100% of the time, an ex-colleague experiences the same issue on another tenant.
Yuki Sun-MSFT 40,856 Reputation points

2022-04-25T09:40:46.133+00:00

Hi @IBN ,

The health dashboard for direct routing shows 2 warnings (certificate about to expire) but we still have some time for renewal (see screenshot below).

This doesn't seem to be the issue.

Then I tried searching further and found this link which discusses a similar situation. As mentioned there. it's suggested to refer to the article below and see if more clues can be found for further investigation:
Monitor and troubleshoot Direct Routing