Resiliency
3 TopicsDirect 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. All good. sbc1.domain.nz sbc2.domain.nz We then wanted to understand the failover performance and recovery handling if we were to lose a regional SBC and so we performed the following test. - Perform calls from MS Teams to PSTN and calls routing towards both SBC1 and SBC2 randomly as both SBC's are within customer tenant voice route as defined below. New-CsOnlineVoiceRoute -identity "unrestricted.voiceroute" -NumberPattern ".*" -OnlinePstnGatewayList cust-tenant1.sbc1.domain.nz, cust-tenant1.sbc2.domain.nz -Priority 1 -OnlinePstnUsages "NZ.PU" - We then shutdown the SBC public interface for sbc1.domain.nz and calls were routed from MS Teams to sbc2.domain.nz interface only, as expected - We then shutdown the SBC public interface for sbc2.domain.nz and calls continued to try and route towards sbc2.domain.nz, even though OPTIONS had been failing for a while towards this interface from MS Teams. - We then activated the SBC public interface for sbc1.domain.nz. OPTIONs were sent and ACK from sbc1 to MS Teams OK. However MS Teams never started to send OPTION's to this sbc1. - We waited for 30 mins and there was no change. - We then activated the SBC public interface for sbc2.domain.nz. OPTION's were quickly established in both directions and calls started working from MS Teams towards this sbc2 quite quickly. - It has now been 4 days and I am still unable to get MS Teams to send OPTION's messages to sbc1. The MS teams admin portal shows the "SIP Options Status" for sbc1 as "Warning" "There is a problem with the SIP OPTIONS. The Session Border Controller exists in our database (your administrator created it using the command New-CSOnlinePSTNGateway). But we have difficulties determining SIP Options status. Please check in 15 minutes." I have tried the following to recover this situation. 1. Deleted the sbc1 from msteams admin portal for 24 hours and recreated. No difference. 2. Change the SIP Port used for sbc1. No difference. My observations are as follows :- 1. MS Teams appears to only try and recover SIP OPTIONS for the "last" SBC that was working. 2. Other SBC's that failed prior to last working SBC are not recovered from MS Teams side. 3. Don't perform this kind of controlled failure when everything is working fine .. you will regret it 🙂 If anyone has any advice on how we can get sbc1 working normally again (i.e. get MS Teams to sned OPTIONS towards it) .. your help would be appreciated. Thanks DavidSolved6.5KViews0likes3CommentsTech Accelerator: Mastering Azure and AI adoption
Join us to learn about the essential guidance, resources, products and tooling you need to accelerate your next Azure and AI project or enhance your existing Azure deployments. Get in-depth technical guidance from Microsoft experts to enhance the reliability, security and ongoing performance of your Azure workloads. Learn more about AMD products and solutions to accelerate cloud adoption. Browse our exciting two-day agenda. Click on the session names you're interested in for the ability to Add to calendar. Select Attend to let us know you're coming. Tuesday, February 11, 2025 7:30 a.m. PST - Best practices for secure and reliable Azure projects 8:00 a.m. PST - Govern, manage and secure your AI deployments 9:00 a.m. PST - How to run a successful Azure migration project 10:00 a.m. PST - Advance cloud infrastructure: Essentials with AMD on Azure Wednesday, February 12, 2025 7:30 a.m. PST - Essentials to build and modernize AI applications on Azure 8:30 a.m. PST - Proactively design, deploy & monitor resilient Azure workloads 9:30 a.m. PST - Cloud platform security in an evolving threat landscape Don't miss out! Register for the VIP experience to receive event reminders and exclusive post-event content, including access to session presentations.5.7KViews6likes4CommentsHow to Check Database Availability from the Application Tier
First published on MSDN on Jan 29, 2017 Reviewed by: Mike Weiner, Murshed ZamanA fundamental part of ensuring application resiliency to failures is being able to tell if the application database(s) are available at any given point in time.4KViews1like0Comments