I'll provide cleaner SIP traces in future.  Meanwhile if you can bear with the 
existing examples I'll use the Frame numbers to point a couple of things out.

The only difference in the config file between working and nonworking is 
commenting out these two lines:

`loadmodule "topos.so"
modparam("topos", "db_url", DBURL)
`
As for the NAT handling, I've tested with a minimally modified default 4.4.5 
kamailio.cfg which does use set_contact_alias().

In badcall-sanitized.txt, Frame 12 is expected, however Frame 13 is a duplicate 
that's missing the Contact: header.  That seems like a bug.  This doesn't 
happen in goodcall-sanitized.txt.

Without knowing how modules interact with the core of Kamailio, I'm wondering 
if topos.so and nathelper.so might be working on the packet in the wrong order 
causing the NAT processes to see the encoded headers rather than decoded and 
thus not act as it should.

Like I mentioned, everything goes to the right place without topos loaded.

-- 
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/1005#issuecomment-281817939
_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

Reply via email to