Again, I would say block the ports at your router. Or block them with a host-based firewall on the server. On Tue, Jan 11, 2011 at 12:22 PM, Alex Wang <hadyn_whx@hotmail.com> wrote:
Hi Brian
I think you misunderstood me on this, what I want to say is not every PBX will face to the public, even in the commercial environment, the PBX may not need open 5060-5080 to the public, but the sip session will need upnp to automatically map the port. My question is how to handle this kind of situation. Just -nonat and map all the other port?
Thanks
Alex On Tue, 11 Jan 2011 11:06:56 -0600 Brian West <brian@freeswitch.org> wrote:
start FreeSWITCH with -nonat .. I can NOT and will NOT change in the way it works. If you want to manage your mappings yourself do so... I'm not going to cripple the autonat to not AUTO nat.
/b
On Jan 11, 2011, at 9:09 AM, Rupa Schomaker wrote:
Hmmm... I didn't put anything in the nat_map code to allow some parts of the sofia profile to participate in the nat mapping while others do not.
Brian, do you have any ideas?
Alex, I'd suggest just blocking ports 5060-5080 on the firewall. The port blocking *should* take precedence over the upnp maps.
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- -Rupa