[Freeswitch-users] Port mapping disabled warning in Freeswitch log

[Rupa Schomaker]

On Tue, Apr 19, 2011 at 3:31 PM, Stephen Wilde <wstephen80 at gmail.com> wrote:
> Ok, thank you Rupa.
> My doubt was: why FS try to add a nat port mapping when there is no nat?
> But if this is only a log problem, then ok, I'll do a git pull.
> Stephen
>

The log is informational.  I guess you could call it an impedance
mismatch between the caller and the callee. The function that calls
the mapping function doesn't know or care if nat is setup.  The called
mapping function logs a warning (now info) saying "hey dummy, nat
isn't setup so I'm not going to do a nat map".

So lowering to info is the easiest, maybe even debug is more
appropriate.  I can be easily convinced of that.

-- 
-Rupa