FMJ revision 91: Fixes a thread leak (and related memory leaks) when an RTP receive stream is never played back.
Uses OpenSSL (Crypto) for SHA-1 on GNU/Linux.
Fix NPE: Don't continue if chat room wrapper is null. (+ updated
documentation)
Optimized groupNode (sorted) add operations.

Original implementation used Collections.sort(...) to sort the elements
after having added a new element, which is typically a O(n log n)
operation, but O(n) in the best case which we are typically close to if
we insert a single element in an otherwise sorted vector. Afterwards
the index would be queried using getIndex(...) which is a O(n)
operation.

These operations are sufficiently slow that inserting a large number of
entries causes 100% CPU usage for a significant amount of time. In the
problematic case it would need to insert around 16000 IRC chat rooms
into this implementation, which caused very bad slow downs of Jitsi,
since it is the AWT thread that is doing the work.

The new implementation searching for the exact location at which to do a
sorted insertion, inserts the element at that location and returns that
index. It utilises a binarySearch, which is O(log n), to search for the
insertion point and since we then know the index, we do not have to look
that up.

In case of the (unsorted) add, since we know insertion behaviour we can
predict the insertion point and return that instead of doing an O(n)
getIndex(...) call for the just inserted element.

The largest deviation from the original implementation has to do with
the sorting operation. Now we insert in a way that a sorted list stays
sorted, however if other code would insert elements in an unsorted
manner into a sorted groupNode instance, then the new implementation
will not automatically correct itself, like the sort(...) operation
would.
Log number of channels on server in case of DEBUG-level logging.
Explicitly acknowledge and handle case of unknown mode symbol.
Fixed bad equality check between source chat room contact instance and chat
room instance.

This fails specifically when having, for example, 2 chat rooms with the
same name but for different accounts. Matching was done solely on chat
room name and as a consequence it changed/deleted the wrong contact list
entry.
Add account display name as display details for chat rooms.
Adds adaptive-simulcast as a bool attribute to the channel IQ.
Fixes possible NPE if OperationSetMultiUserChat is disabled for xmpp provider.
removed path from recording result
jitsi/libjitsi commit 09c18e90f4b35a63adca8009cf7ba24ebb61f154: Fixes a deadlock in SCTP.
Updates the bundled Java Runtime Environment (JRE) on Windows to 7u71.
Commit from translate.jitsi.org by user ibauersachs.: 1611 of 1611 strings translated (0 fuzzy).
Commit from translate.jitsi.org by user ibauersachs.: 1611 of 1611 strings translated (0 fuzzy).
Log the reason why a certificate is not trusted
Update AIA access to non-deprecated BC code
Always initialize the providers field to avoid NPE on exit
Implement a workaround for Java bug JDK-6672015
(Microsoft CryptoAPI KeyStore can have aliases duplicates)
added explicit import to avoid "CertificateServiceImpl.java:907: error: reference to Extension is ambiguous"