MS Teams Direct Routing - Internal call transfer failure

Hi all, My organisation is planning a move to direct routing. We have an AudioCodes VE SBC. I've been working on this for awhile and got everything to a pretty decent state. I've come across ...

microsoft teams

Matej_Maric

Copper Contributor

Aug 01, 2019

obviously we dont use same vendor SBC but standard wise logic should remain the same

Lt_Flash

Copper Contributor

Aug 02, 2019

Matej_Maric

Here's my INVITE packet, I had to remove triangle brackets to make post clear:

INVITE sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:7709b36f-1f10-4b1c-8a0f-9c0e5390c86c SIP/2.0

Via: SIP/2.0/TLS X.X.X.X:5061;branch=z9hG4bKf26f.503bdc4.0;i=54849946

From: "XXXXXXX";tag=a1d8a1ca-d330-4251-811d-35fa1a797c64&;

To: sip:sip.pstnhub.microsoft.com:5061;transport=tls;x-m=8:orgid:7709b36f-1f10-4b1c-8a0f-9c0e5390c86c

Call-ID: 1fa2f0d0-ba41-4e4d-83be-fbef9d0739c6

CSeq: 10432 INVITE

Allow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REFER

Supported: 100rel, timer, replaces, norefersub

Session-Expires: 1800

Min-SE: 90

Max-Forwards: 69

Content-Type: application/sdp

Content-Length: 346

Contact: sip:gateway@sbc.xxx.xxx.com:5061;transport=TLS

Forum Discussion

MS Teams Direct Routing - Internal call transfer failure

Resources