Merge pull request #55 in FS/freeswitch from ~DDRAGIC/freeswitch:bugfix/FS-6821-mod_gsmopen-wrong-interface-name-in-log to master

* commit 'f262dbce':
  FS-6821 mod_gsmopen: fix interface name in log

Fix interface name for logs emitted from mod_gsmopen.cpp during startup

Revert "depend on fs before install"
This reverts commit 6c522179.

Revert "removing commented work in progress on SDES and logging tunning on"
This reverts commit 6df5288f.

Revert "more formatting and logging tuning"
This reverts commit 0e89bbd0.

Revert "logging adjustment"
This reverts commit 764faad6.

Revert "missing host to network conversion highest_sequence_number_received"
This reverts commit 50c62cdf.

Revert "logging correction"
This reverts commit ea973b0b.

Revert "[FS-6623] implement RTCP report generation"
This reverts commit 0b7863a9.

rtcp_init

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