You can NOT bind to 0.0.0.0 you can however use ${local_ip_v4} and if
the IP changes sofia will bounce the profile and update the IP.
/b
On Sep 11, 2009, at 7:55 AM, jun yang wrote:
i also found that:
2009/7/17 Raul Fragoso <raul at etellicom.com>:
> You can not do that with a single profile. Each profile is bound
to only
> one local IP, so if you need to bind to more than one you will
have to
> create a new profile and set the specific sip-ip/rtp-ip params for
them.
>
but cann't understand how to do..
2009/9/11 jun yang <yj13535428...@gmail.com>
the os have three ip, one public ipv4 with adsl which is dynamic
assigned every time, two lan ip in diffrent scope, 192.169.0.2 ,
192.168.5.2.
when freeswitch start ,it auto bind to the pubic ip, so the lan user
cann't connect to freeswitch use lan ip.
i have setting
<X-PRE-PROCESS cmd="set" data="bind_server_ip=0.0.0.0"/>
but have no effect, freeswitch also auto bind to the public ip.
any help is thanks.
_______________________________________________
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
