Hi Brian!

Thank you for your quick response. I ended up defining "local_ip_v4" at the top of vars.xml and set "bind_server_ip" to "local_ip_v4" as well. Is this the best way to go about selecting an IP address for FS to bind to?

In any case, even though it doesn't appear to affect operation, I am still getting this "IP change detected" somewhat periodically in my logs (running 1.0.4):

2009-08-14 01:30:21.215446 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.4]->[172.24.0.5] []->[]
2009-08-14 01:30:22.930551 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 02:00:21.226791 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.5]->[172.24.0.4] []->[]
2009-08-14 02:00:22.473798 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 02:10:21.255298 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.4]->[172.24.0.5] []->[]
2009-08-14 02:10:22.730414 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 02:20:21.279193 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.5]->[172.24.0.4] []->[]
2009-08-14 02:20:22.946537 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 02:30:21.297964 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.4]->[172.24.0.5] []->[]
2009-08-14 02:30:23.111418 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 02:40:21.333952 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.5]->[172.24.0.4] []->[]
2009-08-14 02:40:23.282789 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 02:50:21.362973 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.4]->[172.24.0.5] []->[]
2009-08-14 02:50:22.530569 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 03:20:21.409806 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.5]->[172.24.0.4] []->[]
2009-08-14 03:20:22.137788 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 03:30:21.414786 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.4]->[172.24.0.5] []->[]
2009-08-14 03:30:23.390800 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 03:50:21.422794 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.5]->[172.24.0.4] []->[]
2009-08-14 03:50:22.709792 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 04:00:21.422789 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.4]->[172.24.0.5] []->[]
2009-08-14 04:00:22.818539 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 05:00:21.2953 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.5]->[172.24.0.4] []->[]
2009-08-14 05:00:22.19405 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 05:10:21.29951 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.4]->[172.24.0.5] []->[]
2009-08-14 05:10:23.266294 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 05:50:21.98300 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.5]->[172.24.0.4] []->[]
2009-08-14 05:50:21.962418 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 06:00:21.125959 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.4]->[172.24.0.5] []->[]
2009-08-14 06:00:22.182413 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 06:50:21.238928 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.5]->[172.24.0.4] []->[]
2009-08-14 06:50:23.138401 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 07:00:21.246302 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.4]->[172.24.0.5] []->[]
2009-08-14 07:00:23.269782 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]
2009-08-14 08:00:21.373961 [INFO] mod_sofia.c:3232 IP change detected [172.24.0.5]->[172.24.0.4] []->[]
2009-08-14 08:00:22.503561 [NOTICE] sofia.c:1508 Adding Alias [172.24.0.5] for profile [internal]

Thanks!

Carlos

Brian West wrote: 
If you read the latest vars.xml I have clarified this:

   <!--
        THIS IS ONLY USED FOR DINGALING

        bind_server_ip

        Can be an ip address, a dns name, or "auto".
        This determines an ip address available on this host to bind.
        If you are separating RTP and SIP traffic, you will want to have
        use different addresses where this variable appears.
        Used by: dingaling.conf.xml
   -->
   <X-PRE-PROCESS cmd="set" data="bind_server_ip=auto"/>


So you'll need to open up the sip profile in sip_profiles and set the  
bind ip to exactly what you want.

Thanks,
Brian


On Aug 13, 2009, at 9:14 AM, Carlos S. Antunes wrote:

  
Hello!

First of all, I would like to express my thanks to all the  
developers of
Freeswitch.

I am testing Freeswitch on a Debian machine with physical network
interface with four virtual IP addresses. One of these IP addresses,
aliased as eth0:3, has been created specifically for Freeswitch.  I  
then
set bind_server_ip with the IP addresses associated with eth0:3. To my
surprise, however, tow things happen more or less randomly: 1) in
certain cases, Freeswitch binds to eth0:2 instead (with a different IP
address); and in another, although Freeswitch binds initially to  
eth0:3,
after a few hours it changes its mind and rebinds to eth0:2. Is this  
an
issue with bind_server_ip or am I missing some configuration detail?

Thanks!

Carlos

_______________________________________________
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