Jerry has already clarified in a previous reply that he is running SIP over
TCP, not UDP.
But he hasn't clarified on which machine he is applying the iptables header
rewrite rules (10.201, or 1.3?).
Either way though, it seems like a kludgy work-around. IMO, it'd be better to
focus on creati
Don't you want udp rather than tcp?
Have a look at the iptables stats to see if any packets are hitting your
rule.
Also I think the source port from your host will be 5068 so your replies
will be to the right port but you can double check
tcpdump is also very useful here
sudo tcpdump -i eth0
I'm by no means an iptables guru...
Not sure if it's necessary to enable forwarding via:
echo "1" > /proc/sys/net/ipv4/ip_forward
Also have you tried without the "POSTROUTING" rule?
I seem to recall that "iptables" is smart enough to correctly route
packets back out without that rule.
>
> Your correct. I forgot to mention that the other end IS using tcp.
So I have in my SIP trunk.
transport=tcp
So correct my iptables line was specifying "-p tcp"
I also set tcpenable=yes in sip.conf
Thanks.
Jerry
--
_
-- Ba
You're redirecting tcp, sip defaults to udp.
--
Sent from my cellphone.
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
Join the Asterisk Community at the 13th AstriCon, September 27-29, 2016
ht
Le 15/10/2016 à 18:17, Jerry Geis a écrit :
I have a host 192.168.1.3 that wants to run SIP on 5068 (long story).
My host is 192.168.10.201.
My host needs to stay on 5060 because of all the other devices I have
connected.
I tried putting port=5068 in my SIP extension definition but that did
not
