You'll have to do the manual assignments of your IP's in each profile.  You can't depend on the automatic stuff we have in our default configs.  

hint sip-ip and rtp-ip need to be set for each profile to the proper values.

/b

On Feb 7, 2012, at 10:40 AM, rico-freeswitch@ricozome.net wrote:

Hi guys,

I'm facing a stupid issue on a fresh installed Debian Squeeze (amd64)
server with two NICs, and FreeSwitch bottstraped from Git tree :

- eth0 is connected to the local LAN (172.16.96.3/24)
- eth1 is connected to Internet and have a public IP address.
To be exact, eth0 is on a DMZ, but anyway, it's a RFC1918 address.

FS is :
FreeSWITCH Version 1.0.head (git-d2c9fb5 2012-02-06 14-12-22 -0600)

The problem is when I start the server with its default config,
mod_sofia automatically binds into the public IP address, and nothing
listens on the local IP address !

thougth the CLI, I get this :
freeswitch@internal> sofia status
                    Name   Type
 Data State
=================================================================================================
          194.79.xxx.xxx  alias
internal ALIASED
                internal profile
sip:mod_sofia@194.79.xxx.xxx:5060 RUNNING (0)
           internal-ipv6 profile
sip:mod_sofia@[::1]:5060 RUNNING (0)
                external profile
sip:mod_sofia@194.79.xxx.xxx:5080 RUNNING (0)
   external::example.com gateway
sip:joeuser@example.com NOREG
=================================================================================================
3 profiles 1 alias
freeswitch@internal> eval ${local_ip_v4}
194.79.xxx.xxx

I have to precise it is my first attemps to install FS, and I'm
discovering the software, so I may forget something... But I didn't
found a way to force FS to link "internal" profile with the local IP
address.
I also could modify sip_profiles/internal.xml and hardcode the correct
IP address, but my feeling is it's not the right way, and I guess it
would probably have some side effects on the setup ?

Last, I tried both old 1.0.6 branch and lastest Git tree, both with
compiled packages "ala" Debian way, and bootstraped, and I always got
the same behavior...

So my question is simple : is this normal, ? and how should I handle FS
setup with mutiple NICs ?

Thanks for your help,

--
Eric Belhomme

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com

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

-- 
Brian West 
FreeSWITCH Solutions, LLC
Phone: +1 (918) 420-9266 
Fax:   +1 (918) 420-9267
brian@freeswitch.org
http://www.freeswitch.org