Hey Ray, Thanks for the response. I agree that this is a strange scenario - there seems to be some problem with the DHCP server in the environmnet, because of which, after lease time expiry, it sometimes doesn't provide back the IP to the device. I assume this triggers a interface down scenario in the device, causing the " loose ethX and FS to all available interfaces" scenario. I have a couple of questions though: 1. " loose ethX and you are binding FS to all available interfaces" - Is FS binding to available interfaces part configurable? Can I ask freeswitch not to bind to loop back interface if eth0 goes down? 2. Keeping in mind that this is a strange scenario, should FS still behave this way? I mean, once the device has got back the right IP, I wonder why the internal profile has not been loaded back? Thanks again mate! On Wed, May 15, 2013 at 6:19 PM, info <raimund.sacherer@logitravel.com>wrote:
On Tue, May 14, 2013 at 10:31 AM, Siri MM <sirimmfs@gmail.com> wrote:
Hello All,
I am facing an issue with freeswitch installed on my device. For some reason, IP address on my device sometimes seems to be 'fluctuating' between the actual Static IP, and 127.0.0.1. Freeswitch is able to detect this change everytime, and reconfigure accordingly. However, during one such occassion, it hasn't brought up the internal profile, and isn't binding to port 5060. No other program uses this port on my device.
Working log: http://pastebin.freeswitch.org/20912
Not-working log: http://pastebin.freeswitch.org/20915
Would appreciate any inputs
Thanks!
Hi Siri,
I am a bit mystified as to how things are supposed to work if (how?) your IP get's switched between static and 127.0.0.1 (again, how?) This feels just wrong on so many levels :-)
127.0.0.1 normally is bound to the loopback interface, which, on linux, is called lo your other IP should be bound to an eth0 interface, or an internal ip and and the static IP on a router with some sort of NAT or port redirection. AFAIK linux should not allow you bind 127.0.0.1 to eth0 if it is allready bound to lo, so my best guess would be that you loose ethX and you are binding FS to all available interfaces...
Alas, I don't know how to answer, because even if there should be a problem bringing up the internal profile on such a "switch", my guess is that that's probably *not* the problem you should be looking to fix for right now.
Especially since, if somehow the IP really get's switched to 127.0.0.1, you will be talking only to yourself and I do not see how this should create a working setup (unless you use only an internal sip/(pri|bri) card or some USB channelbanks/gprs sticks, etc. and you only will be doing robocalls or automated IVR's ...
Well, sorry mate that I can't help you more, but this really is a strange szenario,
best regards, Ray
_________________________________________________________________________ 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