When we select Ring back if there's no answer the Teams Blind Transfer to a Call Queue fails

Valued Contributor

Hello Teams Community,

 

Please i need your help on this.

 

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

 

If you click the Transfer button to transfer the call to a Call Queue and select the "Ring back if there's no answer" option, Teams immediately calls back with the message that the call transfer failed. If you do not select the "Ring back 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?

 

IBN_2-1650554934574.png

 

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).

 

IBN_3-1650554981206.png

 

 

I’m able to reproduce the issue 100% of the time, an ex-colleague experiences the same issue on another tenant.

 

 

 
 

 

 

 

 

1 Reply

@IBN 

Since the community has not yet responded to your post, you might want to seek assistance with other resources that are focused on tech support:

 

  • Ask your IT manager to open a support case or call Microsoft using the support line you were given.  Other options for business subscription admins are listed here:

Get support | Microsoft Docs

https://support.serviceshub.microsoft.com/supportforbusiness/create