Forum Discussion

Jason_portsip's avatar
Jason_portsip
Copper Contributor
Aug 14, 2022

Teams doesn't reply ACK for 200 OK

Hi,

My SBC domain is sbc.portsip.io and resolved to 218.76.62.10, the SBC private IP is 192.168.0.11, and the TLS transport is 5078 for communicating with Teams, and used port 5069 on TCP for communication with backend PBX.

 

When I dialed from teams, and the PBX extension answered the call, SBC send the below 200 OK to teams, voice is good but the teams is not replied ACK to SBC cause the call is hangup after a while, where is wrong?

 

SIP/2.0 200 OK
Via: SIP/2.0/TLS 52.114.32.169:5061;branch=z9hG4bKb34e2036
Record-Route: <sip:AAAAAAEAAAAAAscTwKgAEGIwNTdkZTRiNDIzZGZhZmFmNzViMDAwZTE1MjY3OTlh@192.168.0.11:5069;transport=tcp;lr;drr>
Record-Route: <sip:7AcAAAIAAAAAAQFqNHIgqWRjYTM1OWQ2NDJjMmM4ODFhOGI0YjcwMmQ4YWEwYmJl@sbc.portsip.io:5078;transport=tls;lr;drr>
Record-Route: <sip:sip-du-a-as.pstnhub.microsoft.com:5061;transport=tls;lr>
Require: timer
Contact: <sip:sbc.portsip.io:5078;transport=tls>
To: <sip:+86101@sbc.portsip.io:5078;user=phone>;tag=2f928937
From: "Thomas Oliveri"<sip:+1001@sip.pstnhub.microsoft.com:5061;user=phone>;tag=6ce7fe294b6641e194ea839c798d6295
Call-ID: 677fb489e2ac5661b78a1339affa2029
CSeq: 1 INVITE
Session-Expires: 3600;refresher=uac
Accept-Language: en
Allow: REGISTER, INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, SUBSCRIBE, UPDATE, INFO, MESSAGE, PUBLISH
Content-Type: application/sdp
Server: PortSIP SBC v10.0.0.22
Supported: replaces, norefersub, tdialog, join, timer
User-Agent: PortSIP UC - Call Manager 16.0.0.175
X-Session-Id: 611040612304556032
X-Trunk-Name: Teams Direct Routing
X-CID: 2vaVDqa6gvIvCq5L7Nw_Fw..
Content-Length: 387
 
v=0
o=- 420019946 1 IN IP4 192.168.0.16
s=ps
c=IN IP4 218.76.62.10
t=0 0
m=audio 30006 RTP/SAVP 18 0 8 101
c=IN IP4 218.76.62.10
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=mid:audio
a=sendrecv
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:s4XvtaXKNh33jeaNbeFQk35Xw5d1nfForKnSIczO
Direct Routing
SBC
teams
  • Jason_portsip's avatar
    Jason_portsip
    Copper Contributor
    Aug 14, 2022
    OK, we have solved it.
    The problem is that we don't need to rewrite the Contact if the DR is present.
  • Pedro_vega's avatar
    Pedro_vega
    Copper Contributor
    Oct 13, 2023

    Jason_portsip  Hi Jason, could you share more details on this? I am facing this same issue with a especific SBC, I have compared all signaling whit other SBC that is not having this issue but there is no difference. I have a support ticket with microsoft support team, but no feedbac so far.

Resources