[Freeswitch-users] bind_server_ip issue

[Brian West]

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 at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org