Ignores the 'RTP pacing threshold' setting if it's set to over 1000 (as opposed to failing with an exception).

Attempts to improve the RTP packet queue/the audio jitter buffer with resepect to recovery when the queue/buffer is full. Works on bringing uniformity to the media processing threads created by FMJ and libjitsi as part of an effort to resolve quality degradation made very audible by jitsi-videobridge.

Improves handler for DTMF events: when sending several DTMF tones in a short frame, the notification sound is no more clipped but played entirely. The net.java.sip.communicator.service.protocol.maximalRtpDtmfToneDuration property is added to define a maximal duration for the RFC 2833/4733 DTMF tones.

Conflicts:
	trunk/lib/installer-exclude/libjitsi.jar

Fix for the issue when the encoder and the rtpConnectors are in separate VideoMediaDeviceSession instances and the encoder doesn't receive the key frame requests from other peers.

Improves setting of the stream direction when processing jingle content-accept messages. This fixes a problem with video conferences where video streams sometimes 'freeze' if a non-focus starts to send video (while the focus is not sending video)

Implements an alternative to PortAudio on Windows which uses Windows Audio Session API (WASAPI) and related Core Audio APIs such as Multimedia Device (MMDevice) API.

Changes the way FEC is handled in the Opus decoded. Makes it output a single Buffer containing both the data decoded from FEC and the packet's 'regular' data. Until now, it output two separate Buffers.

Adds an option to set the video bitrate. Patches provided by Benoît Laniel on the dev@ mailing list (under the subject of '[PATCH] Set default max video bandwidth to 128')

Corrects the RTP DTMF buffering management for the following case: when a key is hold down on Windows, it generates several start DTMF events and only one stop when released.

Update zrtp4j-light that implements new features to negotiate ZRP protocol
versions, support the B256 SAS authentication mode, some smaller updates and
bug fixes.

Fixes a problem with RTCP PLI packets not being sent. The problem was that the usePLI field of VideoMediaStreamImpl was accessed from the constructor of the superclass (through the overloaded deviceSessionChanged method), before being initialized. As a result it's value was 'false' rather than the intended 'true'. This patch makes the field static, since (once initialized) it's value was always 'true' anyway.

This is the stack trace observed:
     [java] 	at org.jitsi.impl.neomedia.VideoMediaStreamImpl.deviceSessionChanged(VideoMediaStreamImpl.java:520)
     [java] 	at org.jitsi.impl.neomedia.MediaStreamImpl.setDevice(MediaStreamImpl.java:1678)
     [java] 	at org.jitsi.impl.neomedia.MediaStreamImpl.<init>(MediaStreamImpl.java:284)
     [java] 	at org.jitsi.impl.neomedia.VideoMediaStreamImpl.<init>(VideoMediaStreamImpl.java:318)
     [java] 	at org.jitsi.impl.neomedia.MediaServiceImpl.createMediaStream(MediaServiceImpl.java:364)

Small fixes to various comments. Adds logs when a SIP outgoing call is created and when a Conference-Info IQ is received.

Adds a minimal duration for RTP DTMF tones. This minimal duration can be configured by provisioning with the net.java.sip.communicator.service.protocol.minimalRtpDtmfToneDuration property, or by setting it in the account preferences.

Seemingly fixes an issue which could cause a few pixels of the remote video in a call to be scaled out of proportion.

Updates to FMJ r20 (which reverts r18, since it causes problems -- symptoms are degraded video quality).

Works on preventing an issue with the display of remote video which could scale it down to a tiny number of pixels. Fixes multiple technical/programming errors, warnings, javadocs.

Adds log entries when a Cobri (Colibri) channel's SSRCs change. Minor corrections to comments and logging.

Removes attempts to register the speex JavaEncoder and JavaDecorer classes, since they are exluded in the default libjitsi build, and trying to register them raises exceptions.

Fixes the display of the remote video in a call which could appear as a single pixel (on Windows at least).