<p></p>
<p>Hello guys,</p>
<p>My kamailio version is:</p>
<p>version: kamailio 5.1.1 (x86_64/linux)<br>
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES<br>
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB<br>
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.</p>
<p>I am facing a strange bug with TM in case of negative replies.</p>
<p>A party sends the invite<br>
B party connects the call<br>
B party after a few time sends in dialog invite with t38 media.<br>
A party rejects the in-dialog invite with 488<br>
Kamailio send ACK to A party(since it is an ACK for negative replies it is build in each hop)<br>
The problem in this case is that the ACK sent by kamailio to A party has the callid of kamailio - B party.<br>
Since it has a different callid the A party does not recognize the ACK.</p>
<p>How can I resolve this issue?</p>
<p>Thanks and regards,<br>
Rafael</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/kamailio/kamailio/issues/2525">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABO7UZP27K2XSZXZ54RTHMTSL72YBANCNFSM4S25QO7Q">unsubscribe</a>.<img src="https://github.com/notifications/beacon/ABO7UZPMYIFL7BUSG6OSBBTSL72YBA5CNFSM4S25QO72YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4K2YLXYQ.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/kamailio/kamailio/issues/2525",
"url": "https://github.com/kamailio/kamailio/issues/2525",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>