CID: 1211948 fix memory leak of decoded iks message in function parse_plain_auth_message in mod_rayo

FS-6506 --resolve Technically when you are not using groups you do not add a <users> tag inside <domain> you just put several <user> tags in <domain> This patch will consume an extraneous <users> tag and move on making it work either way.

sofia is treating all notify sending as if they were natted rather than when nat is detected.  This causes issues on some polycoms that use strange ports in their contact for getting notifies that do not match the port the calls come from

Correction to commit 0ba59aa6 using the correct variable in tel uri param parsing for mod_sofia

FS-4779 FS-6467 the behaviour from 4479 is now masked behind the param 3pcc-reinvite-bridged-on-ack FS-6467 please test master

This seems to be a paradox when running a perl script from a session then executing perl again on the same session from a different thread.
I fixed it by converting any execution of perl in the execute_on_* family of operators to only run background mode which is to store the command in the session stack to be executed only by the session thread instead of on the spot by the outide thread.  changing the execute_on_answer to perl::/path/to/script.pl would also eliminate the crash in code that has not been updated with this patch.

This is just a limitation of embedded perl we have to live with.

Expanding on 05263818 to support boolean tel url params in mod_sofia

Conflicts:
	src/mod/applications/mod_conference/mod_conference.c

We were calling switch_epoch_time_now() twice for no good reason.

This allows building mod_soundtouch in clang as clang doesn't support
gcc's -fcheck-new.

These haven't been touched in years; they can't possibly still be
applicable.

We already had uuid_answer and uuid_pre_answer, so we might as well
add uuid_ring_ready.

Automated leak detectors find leaked memory on shutdown.  Cleaning up
after ourselves on shutdown eliminates noise from these reports.

The rc variable here was always initialized but the compiler couldn't
see that because of the lack of an unconditional else clause.

On start DTMF packets we were showing the last write timestamp as a
signed value when it's an unsigned value, which could result in it
appearing incongruous with later packets where the value was displayed
correctly.

The net effect here is the code looks more "regular" and reads more
linearly.

Previously we would continue considering phrase actions even after
receiving a break action; we would only break on the next input
clause.  It appears the intent here was to break before the next
action.

If we get SWITCH_STATUS_BREAK then we didn't get
SWITCH_STATUS_SUCCESS.