Owki, reading RFC-3261 again ;)
Imho Kamailio does what it is supposed to do, it forwards the packet to the first element in the Route header.
But as I received the BYE packet from sip:their_sbc , that one should have stripped itself out of the Route header, making everything just work, right?
Now I can hackishly fix it with a rewritehostport in the middle. But that will eventually not scale up that nicely. Ergo, does anyone have a good idea on how to e.g. have Kamailio in this situation ignore the first uri in the route header? Or am I still not getting it :) ?
thx !
BYE sip:05xxxxxx at my_kamailio http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users:5060;transport=udp SIP/2.0 Record-Route: sip:their_sbc;lr=on;ftag=as5716fec8 Via: SIP/2.0/UDP their_sbc;branch=z9hG4bK1ae8.269e4f67.0 Via: SIP/2.0/UDP their_internals:5060;received=their_internals;branch=z9hG4bK4f9044a7;rport=5060 Route: sip:their_sbc;lr=on;ftag=as5716fec8,<sip:36d0a5cfbaeb6b055d5bb02c32127b49_32123456789 at my_kamailio http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ;lr=on;ftag=as5716fec8> Max-Forwards: 69 From: "Some_Telecom" <sip:02xxxxxxxx at their_sbc http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>;tag=as5716fec8 To: <sip:05xxxxxx at their_sbc http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users:5060>;tag=U3FrFDm5Zr0KF Call-ID: 68fe6a470986bd087ce4ed860f603af6 at their_sbc http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users CSeq: 103 BYE User-Agent: Integrics Enswitch X-Asterisk-HangupCause: Normal Clearing X-Asterisk-HangupCauseCode: 16 Content-Length: 0 X-Enswitch-RURI: sip:05xxxxxx at my_kamailio http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users:5060;transport=udp X-Enswitch-Source: their_internals:5060
davy van de moere writes:
Imho Kamailio does what it is supposed to do, it forwards the packet to the first element in the Route header.
yes.
But as I received the BYE packet from sip:their_sbc , that one should have stripped itself out of the Route header, making everything just work, right?
yes, the previous sip proxy should have removed itself from the route header.
Now I can hackishly fix it with a rewritehostport in the middle. But that will eventually not scale up that nicely. Ergo, does anyone have a good idea on how to e.g. have Kamailio in this situation ignore the first uri in the route header? Or am I still not getting it :) ?
you are getting it and the only right fix is to fix the previous proxy that works incorrectly. it is very bad idea to start hacking around these kind of problems.
-- juha
Now I can hackishly fix it with a rewritehostport in the middle. But that
will eventually not scale up that nicely. Ergo, does anyone have a good
idea
on how to e.g. have Kamailio in this situation ignore the first uri in
the
route header? Or am I still not getting it :) ?
you are getting it and the only right fix is to fix the previous proxy that works incorrectly. it is very bad idea to start hacking around these kind of problems.
I was afraid so :) I'll push a bit on the other proxy supplier, and in the meanwhile force it to work with a rewritehostport.
Thx for your help
-
davy van de moere -
Juha Heinanen