Re: [sr-dev] [kamailio/kamailio] Wrong Record-Route and Via header fields when TCP is used (#2033)

Bingo! It works correct once I reversed the 'listen' parameters order as you suggested: ``` INVITE sip:2601@192.168.0.178:47566;transport=tcp SIP/2.0 Record-Route: <sip:192.168.9.103;transport=tcp;r2=on;lr;did=18b.c921> Record-Route: <sip:10.28.80.1;transport=tcp;r2=on;lr;did=18b.c921> Via: SIP/2.0/TCP 192.168.9.103;branch=z9hG4bK25a.491f2e3a37e082ce56aae708a46851e9.0;i=3 Via: SIP/2.0/TCP 10.28.80.47:5060;rport=49394;branch=z9hG4bK2cde1541 ``` But, obviously, the same problem appears for calls in the opposite direction: ``` INVITE sip:2600@cust1.cpbxmt3.in.xorcom.com SIP/2.0 Record-Route: <sip:192.168.9.103;transport=tcp;lr;did=30f.9df1> Via: SIP/2.0/TCP 192.168.9.103;branch=z9hG4bKb8cf.41e31318f7016a84b9f0615135a326b8.0;i=1 Via: SIP/2.0/TCP 192.168.0.178;received=192.168.0.178;rport=47566;branch=z9hG4bKikbzlczg ```` I have mhomed=1 in my configuration. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2033#issuecomment-521565159