- we still need to remove the connection from the global audio list but not send the global audio left event
   to akka-apps

   user from the voice conference

 - do not use another thread to do the transcoding. The thread doesn't get cleaned up when the call ends
   and the thread is waiting for packet in the queue. I am noticing a lot of threads hanging around
   in Yourkit from the mem dump. Not sure if this is contributing to OOM.

This function is responsible for building the 200 OK to answer the REINVITE coming from Freeswitch. In our cause, we just need to use bbb-voice local sdp to answer it. To a later and permanent change, however, it's recommended to investigate the SdpTools.java. My guess is that sdpMediaProduct function is comparing the media codecs in a wrong way.

bbb-voice was responding the Freeswitch REINVITE with 200 OK containing remote SDP and with no media description.

The 'From' field must contain bbb-voice IP. We were getting Freeswitch IP instead (that is ok ONLY when bbb-voice and Freeswitch share the same machine with same IP Address).

 Removing unused source files so we can remove jmx dependency jar.

 Update builds to use gradle 2.12

 Updating Red5 triggered updating of ffmpeg jars for screensharing.

 Change dependencies to build against latest red5 to upgrade to java 8

 - attempt to reconnect redis pubsub subscriber if disconnected

   see https://ria101.wordpress.com/2011/12/12/concurrenthashmap-avoid-a-common-misuse/
 - Noticed that Red5 became slow to response after a while and usin Yourkit saw that
   a lot of threads are blocked in GlobalAudio.getGlobalAudioStream

 - update red5 to bring in fix for connections not cleanedup properly which may be cause OOM Exception