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.

We're breaking out of the loop here anyway, so setting done to true is
useless.

We were leaking memory when break_on_match was set or when we received
back SWITCH_STATUS_BREAK from a callee as we were failing to free
field_expanded_alloc.

If pattern is null we're setting it to a non-null value, so this
branch will always be taken.

Use `git diff -w` or `git log -p -w` to see what's going on in this
commit.

In the event of a memory error, we were trying to free a null pointer
while leaking the allocation for field_expanded_alloc.

These variables aren't used outside of this for loop, so they should
be declared within it.

I found a problem here but it may not completely match your expectations.
I reviewed the RFC 4028 and checked against the code and I discovered we should not be putting a Min-SE in any response at all besides a 422:

section 5:

   The Min-SE header field MUST NOT be used in responses except for
   those with a 422 response code.  It indicates the minimum value of
   the session interval that the server is willing to accept.

I corrected this problem and implemented the 422 response so if you request a value lower than the minimum specified for the profile.
If the value is equal or higher to the minimum, it will be reflected in the Session-Expires header in the response and no Min-SE will be present.

FS-5997 regression from commit 70accd9f this caused some attended transfers to calls with multiple targets to get the abondoned channels to be stuck on write lock

FS-6447 --resolve return subscriber-absent platform-code 20 if <dial> is attempted to user that is not registered

Prior to this commit, if anything at all went wrong in
switch_ivr_phrase_macro_event() we would generate a warning like this:

  [WARNING] switch_ivr_play_say.c:348 Macro [macro_name]: 'pattern_name' did not match any patterns

This is clearly misleading.  The natural thing to do on seeing that
message is to verify that the language files are there, and that the
pattern really does exist in that macro.  But none of that was usually
the problem.  The message would be generated if the language wasn't
found, or if the channel had gone away, for example.

With this commit, we verify that we actually tried looking for the
pattern before displaying the warning about the pattern not matching.