Direct Routing failover behaviour and lack of recovery from MS Teams side

Hi, We have Direct Routing working fine towards two separate SBC's (each with own wildcard cert) and had calls routing from MS Teams to both of them randomly for the first test customer tenant. A...

failover

microsoft teams

recover

Resiliency

David_NOW_NZ
Apr 07, 2021
Hi Erik365Online

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

David_NOW_NZ

Copper Contributor

Apr 07, 2021

Hi Erik365Online

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