We were making a copy of the fifo name and stripping any domain name,
but then not using the value.

Reduce number of local variables where possible; consolidate lines.

This marker value is only used in one place.

If getting the DB handle failed during the load or reload of the
configuration, we would leak the XML structure we just allocated for
the configuration.

The goal here is to describe theory.  We want to illuminate what the
code is trying to do and what the core concepts are.

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)