Apparently the MetaSwitch guys incorrectly interpret `Privacy: none`
as `Privacy: id`.

ref: RFC 3325
Reported-by: Stéphane Alnet <stephane@shimaore.net>

FS-6817 #resolve

Fix dates in RPM changelog that cause complaints on newer RPM build
software

When we specifically release all limits on a channel we destroy the
hash table stored in the "limit_hash" private channel data but we
don't destroy the private data as it will be reclaimed as part of the
session.  If limit increment is called after the limit release we can
reuse that channel private, but we need to check whether the hash
table is null first.  Fortunately this makes the code look better
anyway.

FS-6775 #resolve
FS-6783 #resolve

This reverts commit e2b1ee26.

This reverts commit 99d0f134.

calculate jitter percentage in jitterbuffer to factor into conditions for reducing the size when in adaptave mode