According Jeff Lenk, Windows Visual Studio doesn't understand that
people use the char type for non-null-terminated byte arrays, so it
throws a warning about this that causes the build to fail on Windows.

As the initial value for the ZID doesn't really matter here one iota,
just null-terminate it on Windows.

libzrtp's sas_is_verified field is a uint32_t, but zrtp_verified_set
expects a uint8_t.  This is a boolean field, so it doesn't matter one
way or the other.  gcc doesn't care, but Windows Visual Studio
apparently throws a warning about this.

The callback here receives both zrtp_protocol_event_t and
zrtp_security_event_t events.  The latter is numbered contiguously to
the former.  Still, it's a bit confusing to have to pick one as a
type, but apparently this fixes a warning on Visual Studio on Windows.

Thanks to Jeff Lenk.

...to satisfy Windows Visual Studio.  Thanks to Jeff Lenk.

Brian and I talked about this and concurred on the reversion here.
Part of the point of the ZRTP pass-through mode code is that it allows
two legs to have a ZRTP-enabled call even if FS doesn't have ZRTP.

This reverts commit f0aa4ab3.

It appears that libzrtp would prevent a non-passive client from
enrolling with a PBX because of a broken license mode comparison.

Thanks to Ivo Kutts for the report.

FS-4223 --resolve

FS-4220 --resolve i refactored this into a general cross platform function and use it everywhere else we try to set affinity

Some modules like mod_java drop files in there during install that
should be installed with the module rather than with FS.

add inbound-reg-in-new-thread sofia param to launch a new thread to process each new inbound register when using heavier backends

FS-4183 here is a start, it still needs some work but here are the basic components, initially I am using the algorithim we use to generate artifical silence (static) and using one of those values to sleep a certian number of microseconds plus the cumulative bytes of events but i bet there is still some predictability in there so it needs some more

Debian expects all copyright information to be in one place, so we
copy the license details to debian/copyright and remove the COPYING
files when we install components.