MS Teams Direct routing Help required | Call from MS teams to outbound doesn't hangup when far end hangs up

[lodperera]

We are developing SBC(using asterisk<-- don't shame we've got it working as our main dev guy is an asterisk worshipper) for MS teams direct routing multi tenant.

We have come across an issue where when a call is placed from the msteams to outbound. The call can answer and speak. But if it hangs up from the far end, then the call doesn't hangup from msteams side.

We could see that we are NOT receiving a response for our BYE signal.


So I'm thinking maybe we have the BYE headers incorrect. So I';m here to ask for another person who has msteams working to make a call outbound from msteams then hangup from far end. if it hangs up on msteams then great. Can that person share the SIP trace with me so i could figure out what we are doing wrong?



I have attached my ones and SIP header changes that we did but for no avail we didn;t receive any SIP reply for the BYE. Adding Contact and Record-Route headers does not work
Following are 3 tests with different headers.

No hangup and no 200 response:

<--- Transmitting SIP request (702 bytes) to TLS:52.114.16.74:5061 ---> BYE sip:api-du-a-euwe.pstnhub.microsoft.com:443;x-i=44b10908-b64c-470c-9c7b-a464d7e90e3b;x-c=2668ecc86de551178ca3f444962b2a3e/d/8/460cc2238b95483488bc5c03eec07b12 SIP/2.0 Via: SIP/2.0/TLS OUR.SBC.IP:5061;rport;branch=z9hG4bKPjf8eebee6-5559-44aa-899a-6d3844717e19;alias From: <sip:+61104@testdemo.OUR.SBC.DMN;user=phone>;tag=a081c337-263f-441c-afe4-a63bca81db6c To: "Ralph Lauren" <sip:+102@sip.pstnhub.microsoft.com;user=phone>;tag=d405e1c20d434d9094c13ddbde9b4fff Call-ID: 2668ecc86de551178ca3f444962b2a3e CSeq: 31603 BYE Route: <sip:sip-du-a-au.pstnhub.microsoft.com:5061;transport=tls;lr> Reason: Q.850;cause=16 Max-Forwards: 70 User-Agent: LocalCom SBC Content-Length: 0


BYE sip:api-du-a-euwe.pstnhub.microsoft.com:443;x-i=e2feb2d9-26d4-4258-b73b-968a3709f349;x-c=5c2c5112909b5b95b3ea74838e0df29f/d/8/f0b46e4ad8dd4b07b7f1d0ca05948202 SIP/2.0 Via: SIP/2.0/TLS OUR.SBC.IP:5061;rport;branch=z9hG4bKPj53fe93bc-3f56-48b0-b8ad-4723188c213c;alias From: <sip:104@testdemo.OUR.SBC.DMN>;tag=e8058cc5-7dc2-4689-a697-c0ab6d6d1103 To: "Ralph Lauren" <sip:102@sip.pstnhub.microsoft.com>;tag=44918744aed546b68471ada352b63295 Call-ID: 5c2c5112909b5b95b3ea74838e0df29f CSeq: 30127 BYE Route: <sip:sip-du-a-au.pstnhub.microsoft.com:5061;transport=tls;lr> Reason: Q.850;cause=16 Max-Forwards: 70 User-Agent: LocalCom SBC Content-Length: 0



BYE sip:api-du-a-euno.pstnhub.microsoft.com:443;x-i=639399ee-fbe6-4e5f-807e-1759d50bac35;x-c=da1ff5f49a775e4899f8484718110052/d/8/698ba64f3b1b425eaa84b4559cf9f89b SIP/2.0 Via: SIP/2.0/TLS OUR.SBC.IP:5061;rport;branch=z9hG4bKPje86b4d94-29a9-46f9-8382-9234cd2165c9;alias From: <sip:104@testdemo.OUR.SBC.DMN>;tag=b5588b68-ff0e-478e-a056-ca6d008c2335 To: "Ralph Lauren" <sip:102@testdemo.OUR.SBC.DMN>;tag=f7bedddc0eff4dd99355c2454ca3219d Call-ID: da1ff5f49a775e4899f8484718110052 CSeq: 32447 BYE Route: <sip:sip-du-a-au.pstnhub.microsoft.com:5061;transport=tls;lr> Reason: Q.850;cause=16 Max-Forwards: 70 User-Agent: LocalCom SBC Content-Length: 0




@DigitalDaz I think you have a working msteams? Please help me by sharing a SIP trace

 

[lodperera]

@robvandenbulk

I saw you have a working direct routing with ms teams and kamilio mentioned in this forum.

I'm stuck with above issue and would like to get a sip trace when the far end(PSTN) side hangup the call, our BYE message doesn't receive a reply tried close to 8 different headers and info in those headers but cannot quite work it out what we are missing in our BYE message.

Because of this issue when far end hangs up the ms teams call keeps on going.

Would you be kind enough to help a stranger?

 

[DigitalDaz]

I haven't touched teams for ages but why is your RURI what appears to be an https api endpoint?

 

[robvandenbulk]

@robvandenbulk

I saw you have a working direct routing with ms teams and kamilio mentioned in this forum.

I'm stuck with above issue and would like to get a sip trace when the far end(PSTN) side hangup the call, our BYE message doesn't receive a reply tried close to 8 different headers and info in those headers but cannot quite work it out what we are missing in our BYE message.

Because of this issue when far end hangs up the ms teams call keeps on going.

Would you be kind enough to help a stranger?

Are you still working on it? sorry for long replay.

 

[lodperera]

@robvandenbulk @DigitalDaz

Thank you for replies. I appreciate it.


I ended up putting a job on upwork and a good samaritan send me the BYE packet capture for $150


But the two BYE signals looks the same, we cannot understand what changes in header affects the routing. For now we have paused the project as working on other pressing things. We havent been lucky to get any MS teams sales so this SBC project has become less important overnight. :-|

 

[lodperera]

I haven't touched teams for ages but why is your RURI what appears to be an https api endpoint?

>Route: <sip:sip-du-a-au.pstnhub.microsoft.com:5061;transport=tls;lr>

I guess you mean above?
I think microsoft inserts that header when you are using multi tenant method.