Shorewall users - Jan 2006 - How to portforward for voip

I am still having trouble with portforwarding.

The Shorewall users have sudgested the flowing


DNAT    net     loc:192.168.3.240       tcp     5060
DNAT    net     loc:192.168.3.240       udp     5060:5065
DNAT    net     loc:192.168.3.240       udp     8000:8020 8000:8020
DNAT    net     loc:192.168.3.240       udp     16384:23384 16384:23384

As far as I can tell line 1 is not needed as voip does not need tcp ?

I was on http://www.bandwidth.com/tools/voipTest this site said that  
sip port 5060 was blocked.


Thanks again


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

On Wednesday 11 January 2006 03:26, Philip Immoos wrote:
> I am still having trouble with portforwarding.
>
> The Shorewall users have sudgested the flowing
>
>
> DNAT    net     loc:192.168.3.240       tcp     5060
> DNAT    net     loc:192.168.3.240       udp     5060:5065
> DNAT    net     loc:192.168.3.240       udp     8000:8020 8000:8020
> DNAT    net     loc:192.168.3.240       udp     16384:23384 16384:23384
>
> As far as I can tell line 1 is not needed as voip does not need tcp ?
>
> I was on http://www.bandwidth.com/tools/voipTest this site said that
> sip port 5060 was blocked.
Then it is time to start debugging; use the DNAT debugging guide in Shorewall 
FAQs 1a and 1b to determine what is happening.

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net
PGP Public Key   \ https://lists.shorewall.net/teastep.pgp.key