Sent: Monday, June 01, 2009 11:33
PM
Subject: Re: [Freeswitch-users] Make
current fails (build 13537)
NO its not a bad one at all. Its switch_nat_init(); in
switch_core.c since your network must be eating the packets its sending out to
detect if you're behind nat or not... and not getting an ICMP unreachable like
it should be getting... the joys of admins that block all ICMP like idiots.
ICMP has many uses... and outright blocking it is stupid. (This is my
assumption cuz its what makes sense in this case)
So you're getting hit by the nice retry/timeout loop in the natpmp
software we just added and possibly the upnp lib too.
So for now edit switch_core.c and comment out switch_nat_init();
I'm working my ass off to ensure that our users that do have to live in
these insane nat scenarios can do so without much if any pain. Most of which
uses SMB/Consumer grade routers which these two libs we added would allow us
to poke holes and setup stuff and make it painless as possible.
Soon you'll have an option in switch.conf.xml to turn it off.
Please next time don't be so demanding and calling builds brain dead ..
when in fact its trying to become more aware of its network config without
much user input.
/b
On Jun 1, 2009, at 5:24 PM, Nik Middleton wrote:
Well I can only
assume build 13537 is brain dead. Surely I shouldn’t have to edit a
whole bunch of configs to get it working. FS now takes 3 minutes to start,
with no indication as to what it’s looking for in the logs. That said, to
date ‘make current’ has always worked well for me. Guess I was bound
to hit a bad one eventually.
Still, it’s very
frustrating.