Forum Discussion
Jonny Marlborough
Aug 11, 2020Brass Contributor
Delay transferring out from auto attendant
We have been testing Teams with Direct Routing trunks provided by a carrier partner. All inbound and outbound calls direct to/from Teams users connect without issue. We are using the Teams apps on Wi...
zilmar
Jan 07, 2021Copper Contributor
We also have exactly the same problem.
An Anynode from TE-System is used as the SBC.
From my point of view it seems to be a problem on Microsoft side.
I have opened a Premier Support ticket on 11.11.2020. So far there is no solution.
Michael Milad-Said
Feb 15, 2021Brass Contributor
Hi zilmar
Did Microsoft end up confirming it is an issue?
I have seen a new option GenerateRingingWhileLocatingUser under Set-CsOnlinePSTNGateway (SkypeForBusiness) | Microsoft Docs and New-CsOnlinePSTNGateway (SkypeForBusiness) | Microsoft Docs but unable to set via Powershell (I've even downloaded the latest Teams Preview Module - 1.1.11).
This sounds like it should resolve the issue and from the following link is $true by default Connect your Session Border Controller (SBC) to Direct Routing - Microsoft Teams | Microsoft Docs
Not sure if it's something MS is still working on and hasn't been deployed to all tenants.
Michael
- zilmarFeb 16, 2021Copper Contributor
Last week I received this reply confirming the problem.
As you know additional internal resources were involved on the reported issue as well we did reached out to our Product Group and from there they confirmed that they are aware of that behavior and they are working on fixing the behavior and reduce the delay significantly.
Call routing time justified by the hops in call AA => CQ => CQ agent, It can take up to 10 seconds if tenant is US and user accounts Europe locations.
During that call routing time if no greeting is configured on AA (is the case per screenshots presented).
For avoiding the silence admins can configure Greetings and Music on hold.
Set up an auto attendant for Microsoft Teams - Microsoft Teams | Microsoft Docs
Create a call queue in Microsoft Teams - Microsoft Teams | Microsoft DocsThe delay in call routing is being fixed by the Product Group.
Unfortunately the fix for this may be rolled by March end (there is no definite ETA currently). After the fix is done the delay should be reduced significantly.- Michael Milad-SaidFeb 17, 2021Brass Contributor
Hi zilmar ,
Ok thanks for the info.
I had initially raised a support ticket with Anynode and they mention the below solution as a temporary fix for the silence. I've tested this and it works ok (replace Australia with your respective Country ringback tone)
Hope it works for you 🙂
One more thing though:
On the SIP Node on which the incoming call is received, you could configure an Australian Ringback Tone from anynode's own Media Sources, if you like.
- Inbound_Node_configure_Ringback_tone.PNG
Note: In version 4.0.6 this can be found under Media Sources, but in the latest version 4.2 this was now renamed into Tones and Announcement. Also the layout looks a bit different now, but the undelying software architecture has not changed.
This Ringback tone will not resolve the "~5 second delay" issue (after the 200 OK), but it may alleviate the observed symptoms somewhat. At least the caller should hear a ringback tone then as long as the transferred call is still in the 180 Ringing state. After the ICE peer negotiation finished successfully and anynode receives the final 200 OK, the Ringback tone would then stop to be played, of course.- GeoffRichApr 08, 2021Copper ContributorWe are experiencing the same delays discussed here. Has there been any developments/improvements/releases since Feb?