4.3.0

Upgraded to using rtc-pluggable-signaller@2 which in turn uses rtc-signaller@6 under the hood. This brings some stability improvements for rtc-quickconnect with regards to reconnection logic thanks to closing rtc-io/rtc-signaller#35.

4.1.0

• Added a getLocalStreams() function for providing the information on local streams

4.0.0

• Upgrade to use rtc-signaller@5 which makes some substantial changes to how signalling communications are processed and buffered.
• Implement heartbeat via signalling channel to work around firefox issue 852665 which is a real showstopper for being able to detect disconnection between peers.

3.2.1

BUG FIXES:

• Do not announce if we have already announced in the checkReadyToAnnounce function.
• Do not response to peer:leave events with ending a call.

3.2.0

Added plugin initialisation logic into quickconnect so that lower level moving parts (such as rtc-tools, rtc-taskqueue, etc) would be able to interact with a plugin without having to worry that it has not been initialized. If a plugin is specified and applicable to the current platform, the plugin is initialised prior to quickconnect connecting to the signalling server and announcing.

3.1.0

Introduces the ability to specify ice servers through the ice option, which uses rtc-core/genice under the hood. This allows you to specify an array of values for the iceServers or a generator function that will asynchronously provide iceServers to quickconnect prior to initialization.

3.0.0

While this is a major version release, the external API of quickconnect remains the same and all code that is compatible with quickconnect 2.x should also be compatible with this new major release.

We are bumping the major version though, for the following reasons:

• Moving to using [email protected] which implements some major changes to the way connection negotiation occurs. Full details are available in the rtc-tools 4.0.0 and 4.1.0 release notes. If you were drilling down into interfaces provided by the rtc-tools package (the monitor for example) then you may need to make some changes to your code.
• Migrated to the 3.x release of rtc-signaller, which means that quickconnect instances are now also mbus instances. This means that you can a mbus feed to get a picture of all the event data being communicated within quickconnect.

2.7.0

• Added expectedLocalStreams option which if provided will defer the announce using the signaller until the required number of streams have been added to quickconnect.

2.6.0

• Expose and track plugins provided through creation options
• Upgrade to rtc-tools package version 3

2.5.0

• Added peer:connect event which is triggered when a new RTCPeerConnection is created for a newly discovered peer.
• Added peer:couple event which is triggered upon coupling the locally created RTCPeerConnection with its remote counterpart.