I second that. the PIX has SIP fixup which allows RTP traffic to pass dynamically based on SDP information, so you don't need to create a rule for the RTP range - just allow SIP UDP 5060.<br><br>
<div><span class="gmail_quote">On 4/25/07, <b class="gmail_sendername">Tzafrir Cohen</b> <<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Tue, Apr 24, 2007 at 11:04:53PM -0400, Lee Jenkins wrote:<br>> Noah Miller wrote:<br><br>> >SIP:
<br>> >TCP and UDP port 5060 (signalling) - can be changed in sip.conf<br>> >UDP ports 10000-20000 (RTP stream) - can be changed in rtp.conf<br>> ><br><br>Yes. See rtp.conf (at least on your side).<br><br>
Also, if the firewall understands SIP, it may be smart enough to open<br>the ports for the relevant RTP ports upon the beginning of a SIP<br>session. So consider trying not to open any port for RTP.<br><br>--<br> Tzafrir Cohen
<br>icq#16849755 <a href="mailto:jabber:tzafrir@jabber.org">jabber:tzafrir@jabber.org</a><br>+972-50-7952406 mailto:<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a><br><a href="http://www.xorcom.com">
http://www.xorcom.com</a> <a href="http://iax:guest@local.xorcom.com/tzafrir">iax:guest@local.xorcom.com/tzafrir</a><br>_______________________________________________<br>--Bandwidth and Colocation provided by <a href="http://Easynews.com">
Easynews.com</a> --<br><br>asterisk-users mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users
</a><br></blockquote></div><br>