Teams Direct routing - no BYE message from Teams

%3CLINGO-SUB%20id%3D%22lingo-sub-3002164%22%20slang%3D%22en-US%22%3ETeams%20Direct%20routing%20-%20no%20BYE%20message%20from%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3002164%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20following%20problem%20with%20Direct%20Routing%20SBC%3A%20call%20is%20established%20between%20mobile%20phone%20and%20Teams%20via%20SBC.%20Teams%20side%20ends%20the%20call%2C%20but%20this%20signaling%20(SIP%20BYE)%20never%20reaches%20mobile%20phone.%20On%20mobile%20phone%20call%20remains%20ongoing%2C%20and%20will%20remain%20until%20mobile%20phone%20hangs%20up.%3C%2FP%3E%3CP%3EIn%20our%20solution%20SBC%20is%20implemented%20as%20VM%20at%20Microsoft%20Azure.%26nbsp%3BAnalysis%20so%20far%20showed%20that%20such%20BYE%20message%20never%20reaches%20SBC.%20Problem%20is%20sporadic%2C%20but%20can%20be%20provoked%20rather%20easily%3A%201%20out%20of%2010-15%20test%20calls%20results%20with%20such%20behavior.%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%2C%20had%20anyone%20faced%20the%20same%20problem%20with%20Direct%20routing%3F%20Any%20hints%20for%20the%20solution%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EProblem%20tickets%20were%20opened%20against%20Microsoft%20Teams%20and%20against%20Microsoft%20Azure%2C%20but%20no%20results%20yet.%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%2C%26nbsp%3B%3C%2FP%3E%3CP%3EMaja%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3002164%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3004082%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Direct%20routing%20-%20no%20BYE%20message%20from%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3004082%22%20slang%3D%22en-US%22%3EI%20can't%20say%20I've%20seen%20that.%20Does%20it%20only%20happen%20with%20calls%20to%20mobile%20phones%3F%20Is%20it%20to%20a%20specific%20number%2C%20or%20all%20calls%3F%20Out%20of%20curiosity%2C%20what%20SBC%3F%20Do%20you%20have%20a%20copy%20of%20the%20sip%20trace%3F%3C%2FLINGO-BODY%3E
New Contributor

Hi, 

We have a following problem with Direct Routing SBC: call is established between mobile phone and Teams via SBC. Teams side ends the call, but this signaling (SIP BYE) never reaches mobile phone. On mobile phone call remains ongoing, and will remain until mobile phone hangs up.

In our solution SBC is implemented as VM at Microsoft Azure. Analysis so far showed that such BYE message never reaches SBC. Problem is sporadic, but can be provoked rather easily: 1 out of 10-15 test calls results with such behavior. 

Please, had anyone faced the same problem with Direct routing? Any hints for the solution?  

Problem tickets were opened against Microsoft Teams and against Microsoft Azure, but no results yet. 

Best regards, 

Maja

 

3 Replies
I can't say I've seen that. Does it only happen with calls to mobile phones? Is it to a specific number, or all calls? Out of curiosity, what SBC? Do you have a copy of the sip trace?
Same here for 100% of the calls. Scenario is when calling from external to Teams client. When the Teams side disconnects the BYE message never reached our on-prem Avaya SBC. We don't use Media Bypass. Setup is straight forward with only 1 SBC , 1 route pattern and 1 policy.

This must be something within the Teams environment. Any one any thoughts?

Thanks in advance.
Jacco
We are using Metaswitch SBC (now also Microsoft company), but the problem should not be at SBC. Based on our experience, testing with real Metasw. SBC is not showing this behavior. Problem is present only if SBC is deployed as VM, so this looks like Azure problem.
The issue is not related to any specific number.
SIP trace taken at SBC looks like normal SIP call, except BYE sent from mobile is rejected from MS Teams with 481 Call Leg/Transaction Does Not Exist. This is I believe also correct, because from Teams point of view, call was already released at that point.