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

mod_skinny: fix behavior of transfer when target extension falls through to voicemail - keep bridge from dropping out during that operation

We're already avoiding it on sid and jessie; now we're hitting build
failures with it on wheezy.

ref: FS-6811

* Honor the timer name variable

* Added mod_bert::in_sync event when the stream is in sync

* Added BERT stats channel variables

* Check if the channel is going down when out of sync to avoid flagging it
  as out of sync, if the channel is going down it is expected to have some errors

* Improve bert input debug
* Check for SFF_CNG and ignore those frames

* Use digital milliwatt as the test sequence pattern
* Add debug IO files (enabled using bert_debug_io_file variable)

* Calculate sampling error rate over a time window

* Create the following variables to control bert testing behavior:
  bert_timeout_ms - Milliseconds to wait for bert sync before timing out
  bert_window_ms - Window of time to calculate sampling error rate percentage
  bert_max_err - Max percentage of error tolerated before going out of sync
  bert_hangup_on_error - Hangup when error occurs (Timeout or going out of sync)