Alex,
Are you sure this is not a bug with the other endpoint (the other side of the call)? The end-to-end ACK for the 200 OK would have to originate from it and Kamailio would merely be relaying it. Is it possible that it is in fact that UA which is ignoring the To tag in the 200 OK from 1.1.1.1?
-- Alex
Alex R.S.M wrote:
Hi,
I made a simple SIP test call. The end point reply to kamailio with 180, 200 messages. The end point includes "tag=1_1555_t58918_125k" in TO field of these messages. However, kamailio reply with ACK message that includes a random tag (tag=5f08ae5f) in TO field. This tag is not the same as the one sent by the end point:
1.1.1.1 end-point ip address 2.2.2.2 kamailio ip address
INVITE From: sip:1.1.1.1@2.2.2.2;tag=snl-1226930829-1404351227071264-11 To: sip:14078789913@x.x.x.x;user=phone Call-ID: 9280396221-9479318750707221-11-7604239022
180 From: sip:1.1.1.1@2.2.2.2;tag=snl-1226930829-1404351227071264-11 To: sip:14078789913@x.x.x.x;user=phone;*tag=1_1555_t58918_125k* Call-ID: 9280396221-9479318750707221-11-7604239022
200 From: sip:1.1.1.1@2.2.2.2;tag=snl-1226930829-1404351227071264-11 To: sip:14078789913@x.x.x.x;user=phone;*tag=1_1555_t58918_125k* Call-ID: 9280396221-9479318750707221-11-7604239022
ACK From: sip:1.1.1.1@2.2.2.2;tag=snl-1226930829-1404351227071264-11 To: sip:14078789913@2.2.2.2;user=phone;*tag=5f08ae5f* Call-ID: 9280396221-9479318750707221-11-7604239022
How can I force it to send the correct tag?