New
v0.15.0
- [BREAKING] Adds
PeerConnection.close/1function that irreversibly closes peer connection. Most of the functions (except getters) will return{:error, :invalid_state}when called after closing the peer connection. CallingPeerConnection.close/1will also send a close_notify DTLS alert to the other side. - [BREAKING] - So far,
close_notifyDTLS alert caused immediate DTLS state change tofailed. Right now, this alert moves DTLS transport to theclosedstate, but does not move peer connection, signaling, or ice transport to theclosedstate. A peer connection that received aclose_notifyDTLS alert can still do an ICE restart with a different peer.
What's Changed
- Add close/1. Handle DTLS close_notify alert by @mickel8 in https://github.com/elixir-webrtc/ex_webrtc/pull/218
- Look for SPS instead of keyframe with H264 packetization_mode=0 by @sgfn in https://github.com/elixir-webrtc/ex_webrtc/pull/220
- Always include track id in MSID/SSRC attributes by @Karolk99 in https://github.com/elixir-webrtc/ex_webrtc/pull/221
- AV1 payloader by @sgfn in https://github.com/elixir-webrtc/ex_webrtc/pull/222
- Update ex_ice by @Karolk99 in https://github.com/elixir-webrtc/ex_webrtc/pull/225
- Add "For Developers" guides - Debugging, Encryption and SDP by @mickel8 in https://github.com/elixir-webrtc/ex_webrtc/pull/223
- Release 0.15.0 by @Karolk99 in https://github.com/elixir-webrtc/ex_webrtc/pull/226
New Contributors
- @Karolk99 made their first contribution in https://github.com/elixir-webrtc/ex_webrtc/pull/221
Full Changelog: https://github.com/elixir-webrtc/ex_webrtc/compare/v0.14.0...v0.15.0