If FS is not behind NAT, then every call generates at least three
INFO-level log messages:

  [INFO] switch_nat.c:589 NAT port mapping disabled

This is useless noise.  The message is only interesting if you do have
NAT enabled but mapping disabled, which might indicate a configuration
issue.

With this change, we just skip the entire nat_add_mapping function if
the NAT system isn't initialized or we're not behind NAT.

Store some initial details about the channel separately so we can
preserve them across e.g. transfers and display them with show
channels.

With this commit, we store the original caller ID (name and number)
and IP address, and the call destination, dialplan, and context.

FS-4296 --resolve

Thanks-to: Mariusz Czułada <manieq.net@gmail.com>

Revert "FS-4296 --resolve initial calling/called nums in 'show channels'"

This reverts commit b08138d0.

Store initial caller and destination numbers in 'channels' table,
so `show channels` can display it.

Patch provided by Mariusz Czułada <manieq.net@gmail.com>

back off locking contention on sql queues when they are nearly full to allow the system to recover from an attack

Since we're all about WebRTC, We should compile and enable OPUS by default to lower the number of steps to complete a WebRTC setup

FS-6482 Commit 7e15c938 broke MWI for device having no transport parameters (plain UDP connection)

Right now mod_java fails to build on sid and jessie.  We have a
possible solution, but we'll just disable the build of the module
while we test and verify.

Ken noticed a build error.  We need to use the system ldap library
anyway, so we'll just drop mod_ldap here until we make that change.

Previously we would detect the missing LDNS system library at
configure time, but would only break during the build of mod_enum.

With this change, if mod_enum is enabled in modules.conf and the
system doesn't have a usable LDNS library we break during configure.

CID:1215198 don't set variables that are not used, and clean up the bail out usage condition to be more sane

The correct fix is to use gcc-4.7 or newer.  If the compiler borked
this, one should trust nothing else it produces.

Revert "FS-6524,FS-6494: the compiler for rpi seems to be strangely
mis-optimizing this if/else block. Yes, its already set to this value,
but without the else block, it 'magically' hits the if blocks above,
unless you sleep, print a log, or add the else"

This reverts commit 1ca1d637.

Introduced in commit e6ac87f5.

FS-6524,FS-6494: the compiler for rpi seems to be strangely mis-optimizing this if/else block. Yes, its already set to this value, but without the else block, it 'magically' hits the if blocks above, unless you sleep, print a log, or add the else

Release session R/W Lock

add heartbeat_fire_on_set variable to fire heartbeat instantly when its first enabled (legacy behavior)

We received the reply and signaled the condition
earlier then started to wait for it

We were using the libopus directory itself rather than a file within
it as a makefile target.  This is a bad idea as make will see the
target as updated whenever files are created in or removed from the
directory.  Since running configure creates and removes files, the
target will always appear dirty.

The effect was that when mod_opus was enabled in FS make would always
cause libopus to be reconfigured.

We'll target instead the configure file in libopus as that's the first
thing we need anyway.

sofia_glue_get_url_from_contact to strdup the value so before
overwriting the value signal to sofia that we have finished with the
raw header.