Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum In-Reply-To: <camgknjxpm_6h4v0uextqv1gm-u3w-ac0tptwwe9e9ok37dd...@mail.gmail.com> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <61409> Message-ID: <[email protected]>
[quote title=Tony Graziano wrote on Sat, 09 July 2011 06:37]and to be a little more picky about "why" port forwarding does not actually change the destination of the sip message.when you have an invite to port 5060 and forward it to port 5080 in your firewall, the original sip message and header is stills saying port 5060. so unless you have a way to intercept and rewrite the actual sip messages, finding an itsp that can send you calls on port 5080 might actually be easier. this was my original assumption also. including some really bad results when I tried to use iptables to do this. but... i guess sipx isn't picky, since a simple firewall that will PAT, inbound udp 5060, to the sipx box on port 5080, seems to work just fine. -- -- Michael Scheidell, CTO SECNAP Network Security Corp _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
