You do not have permission to delete messages in this group
Report message as abuse
Sign in to report message as abuse
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
Please find below WebRTC Release Notes for Chrome M30. Below is the list of major changes:
Issue 1425 :- Add TURN/TLS support to connect to TURN server via TLS using turns: TURN URI's.
Issue 1493 :- Add support for SCTP based data channels. Currently, it is behind a flag for M30.
Issue 1408 :- Add support for sending binary data through data channel. You would need to enable SCTP flag for M30.
Issue 1430 :- Add support for Reliable data channels in chrome.You need to enable SCTP flag for M30.
Issue 1864 :- Implement cert caching for DTLS. DTLS cert generation has been moved into the browser with persistent caching. This improves call startup time when using DTLS. You need to specify 'DtlsSrtpKeyAgreement: true' when creating peerconnection to test this feature.
Issue 1837 :- Wire up to have padding packet generation be driven by pacer.
Issue 1897 :- Add support for Error concealment when NACK is disabled.
Issue 1881 :- Add support for maxaveragebitrate. You should now be able to control the opus bit-rate with maxaveragebitrate fmtp parameter in sdp.
Issue 79949 :- Implement CreateMediaElementSource() on audio/video elements. As an example you can use this API to apply effects on an audio tag and play it back using WebAudio.
Issue 262117 :- Multiple media streams with audio tracks can now be added to a peerconnection. However, only one microphone source at a time is permitted as currently WebRTC supports only one audio processing module (APM).
iOS :- An ObjC PeerConnection API is now available for signaling & one-way audio (README). Known issues include two-way audio (2191) and video support (2168).