thanks for the info. In my case, it doesn't matter what the source port is the router always rewrites the addresses. The only way to stop it doing that is to change the destination port (the server's port) to other than 5060. -benny On 7/25/08, Ondrej Sterbak <sterbo at email.cz> wrote: > On Fri, Jul 25, 2008 at 12:58, Benny Prijono <bennylp at pjsip.org> wrote: >> On Fri, Jul 25, 2008 at 11:53 AM, Ondrej Sterbak <sterbo at email.cz> wrote: >>> >>> OK, I will investigate this matter more and let you know about the >>> router(s) which could rewrite the headers. But do you have an idea why >>> the message sent by sipsak goes through without any change? >>> >> >> Does it have the same private IP as the sender's host? > Fine, I found out where was the difference between sending from sipsak > and from PJSUA. sipsak sent it from random port and PJSUA from 5060. > When I changed the sending port for sipsak to 5060 and turned on > symmetric routing (sipsak -vvv -i -S -l 5060 -f sipsak.msg -s > sip:example.com:5060) my router rewrites private addresses to public > as well. > > I forgot to write in earlier posts and didn't think that could cause > the problems that my router is standard old PC box running Gentoo > Linux as well. And that one rewrites the addresses. So it can be > either iptables, or dnsmasq, or kernel or something else... :/ > > Does anyone here has experiences with Linux routers rewriting IP > addresses in SIP (or maybe in any other protocol)? If so please let me > know where to look for the problem. > > Many thanks in advance! > > Ondrej > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >
