Forum Discussion
Direct Routing failover behaviour and lack of recovery from MS Teams side
Thanks for your suggestions.
It seems to have sprung back to life today after I deleted the SBC and recreated it (yesterday evening) using powershell commands below. Not sure how long it took to come back to life after this change but I will look back through SBC verbose logs to try and determine that. It didnt come back straight away.
Remove-CsOnlinePSTNGateway
New-CsOnlinePSTNGateway
Prior to this, I had tried disabling the sbc in admin portal for 12 hours and then re-enabling it, but this did not help. Therefore it looks like if you (or anyone) get yourself in this situation, the delete and recreation of SBC using powershell appears to be the way to fix it.
Cheers
David
Hi David_NOW_NZ
I'm also operating two geographical dispersed SBCs and can turn off one of two for maintenance without any issues after maintenance is done it get's back to work.
I'd try to disable and re-enable some basic sbc settings.
Did you also try to disable and enable it again in the Teams Admin Center after you re-created sbc1?
Did you also check the SIP options settings in the sbc1 settings in the Teams Admin Center? Maybe try to disable and re-enable it?
I'd also re-check the firewall rules if there is one in front of the public interface of sbc1, just to be sure that all the (new) Teams Phone System Signaling IPs can reach the public interface ip of sbc1. Plan Direct Routing - Microsoft Teams | Microsoft Docs
Thanks for your suggestions.
It seems to have sprung back to life today after I deleted the SBC and recreated it (yesterday evening) using powershell commands below. Not sure how long it took to come back to life after this change but I will look back through SBC verbose logs to try and determine that. It didnt come back straight away.
Remove-CsOnlinePSTNGateway
New-CsOnlinePSTNGateway
Prior to this, I had tried disabling the sbc in admin portal for 12 hours and then re-enabling it, but this did not help. Therefore it looks like if you (or anyone) get yourself in this situation, the delete and recreation of SBC using powershell appears to be the way to fix it.
Cheers
David