jun yang yj13535428...@gmail.com wrote:
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
i add
X-PRE-PROCESS cmd=set data=local_ip_v4=0.0.0.0/
before
X-PRE-PROCESS cmd=set data=domain=$${local_ip_v4}/
and it has no effect all the same.
is that something wrong.
2009/9/11 Jason White ja...@jasonjgw.net
jun yang yj13535428...@gmail.com wrote:
when freeswitch start ,it auto bind to
when i set local_ip_v4 to 0.0.0.0 i see the info below:
2009-09-11 20:22:27.15625 [WARNING] sofia.c:2291 Invalid IP 0.0.0.0 replaced
with 218.21.105.133
2009-09-11 20:22:27.15625 [WARNING] sofia.c:2300 Invalid IP 0.0.0.0 replaced
with 218.21.105.133
2009-09-11 20:22:27.15625 [NOTICE] sofia.c:1509
i also found that:
2009/7/17 Raul Fragoso raul at etellicom.com
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users:
* 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
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.
sip in general cannot properly support binding to 0.0.0.0 for a UAS, there
is no easy way for the sip stack to know which traffic is for which host and
all of the outbound traffic will appear to go out a single interface when no
specific binding is made.
running each ip on it's own profile is the
thanks for the info that it is a sip problem.
seems it should be doc in wiki to explain that how to configure freeswitch
so that client can connect from any interface,
cause not everyone play with freeswitch is a sip guru.
so thanks any way, i should learn more with sip and freeswitch.