I have enabled auto-nat only for the external profile (port 5080), but FreeSWITCH also maps SIP port for the internal one: freeswitch@internal> show nat_map port,proto,proto_num,sticky 5060,udp,0,0 5060,tcp,1,0 5080,udp,0,0 5080,tcp,1,0 4 total. Is this intended or just a bug? - Dmitry Bely
only works on one profile. Not designed to work with more than one. /b On Feb 22, 2011, at 6:58 AM, Dmitry Bely wrote:
I have enabled auto-nat only for the external profile (port 5080), but FreeSWITCH also maps SIP port for the internal one:
freeswitch@internal> show nat_map port,proto,proto_num,sticky 5060,udp,0,0 5060,tcp,1,0 5080,udp,0,0 5080,tcp,1,0
4 total.
Is this intended or just a bug?
- Dmitry Bely
On Wed, Feb 23, 2011 at 1:01 AM, Brian West <brian@freeswitch.org> wrote:
only works on one profile. Not designed to work with more than one.
It's a bit strange as FreeSWITCH default configs contain 2 profiles (internal and external), Auto-nat is not designed for the default configuration? I still think it should be fixed. Then you have internal profile: <param name="ext-sip-ip" value="auto"/> <param name="sip-port" value="5060"/> external profile: <param name="ext-sip-ip" value="auto-nat"/> <param name="sip-port" value="5080"/> you don't expect that port 5060 is silently exposed to the Internet.
On Feb 22, 2011, at 6:58 AM, Dmitry Bely wrote:
I have enabled auto-nat only for the external profile (port 5080), but FreeSWITCH also maps SIP port for the internal one:
freeswitch@internal> show nat_map port,proto,proto_num,sticky 5060,udp,0,0 5060,tcp,1,0 5080,udp,0,0 5080,tcp,1,0
4 total.
Is this intended or just a bug?
- Dmitry Bely
participants (2)
-
Brian West
-
Dmitry Bely