Bump github.com/pion/webrtc/v3 from 3.1.61 to 3.2.1

[dependabot]

Bumps github.com/pion/webrtc/v3 from 3.1.61 to 3.2.1.

Release notes

Sourced from github.com/pion/webrtc/v3's releases.

v3.2.1

Changelog

• 5bdbaca Update module github.com/pion/sctp to v1.8.7

v3.2.0

Pion WebRTC v3.2.0 is now available. Pion WebRTC is a Go implementation of WebRTC. If you haven't used it before check out awesome-pion or example-webrtc-applications for what people are doing. We maintain a feature list and other helpful resources in our README.md

This release includes 260 commits from 55 authors. This release was primarily focused on providing more tools around understanding and handling network conditions. Pion wouldn't be possible without everyone involved.

New Features

Media Bandwidth Estimator

Pion now provides a Bandwidth Estimator in-tree for serving media. You now get signals about how much bandwidth is available so you can either send more or less data, giving your users the best experience possible. We currently have a implementation of Google Congestion Control. This was implemented using a generic interface so we can provide more implementations in the future.

To use this you create a cc.BandwidthEstimator provided by pion/interceptor. This estimator then can be queried via estimator.GetTargetBitrate(). This returned value tells you if you should raise, lower or sustain the bitrate you are currently sending.

See bandwidth-estimation-from-disk for a full example of how it can be used.

This was implemented by @​mengelbart. Work on Pion's congestion control and bandwidth estimation was funded through the User-Operated Internet fund, a fund established by NLnet made possible by financial support from the PKT Community/The Network Steward and stichting Technology Commons Trust.

webrtc-stats implementation

You can now query and process metadata about your media connections. This data is presented in the standardized webrtc-stats format. These statistics give insight into the why of a WebRTC session.

You can use this to monitor how your Pion WebRTC PeerConnections are operating. Users are also finding this useful to monitor, debug and analyze other WebRTC media servers. You can quickly start up a Pion WebRTC PeerConnection and write canaries and tests against other WebRTC software.

To use this you create a stats.Interceptor provided by pion/interceptor. This allows you to query on a per SSRC basis the status of a stream. The following is an example of query it in a loop in the OnTrack for each stream.

peerConnection.OnTrack(func(track *webrtc.TrackRemote, receiver *webrtc.RTPReceiver) {
    fmt.Printf("New incoming track with codec: %s\n", track.Codec().MimeType)
    for {
        // Pull the stats for the stream that caused OnTrack to be fired
        stats := statsGetter.Get(uint32(track.SSRC()))
     // Print InboundRTPStreamStats. Other stats are available as well
     fmt.Println(stats.InboundRTPStreamStats)
 time.Sleep(time.Second * 5)     

}

})

See stats for a full example of how it can be used.

This was implemented by @​mengelbart

Simulcast Sender

You are now able to send Simulcast traffic with Pion WebRTC. Before this commit we were only able to receive Simulcast traffic.

Developer are using this to move Simulcast traffic between their servers as they scale out. It has also been useful for testing WebRTC servers. Using a small Pion process you can assert that your servers are properly handling Simulcast traffic.

... (truncated)

Commits

• 5bdbaca Update module github.com/pion/sctp to v1.8.7
• 2bf9486 Add examples/stats
• 03c83a1 Use new intervalpli interceptor in examples
• 98860dd Update module github.com/pion/interceptor to v0.1.14
• bea0059 Improve MediaEngine docs
• dfaf820 Update module github.com/pion/interceptor to v0.1.13
• 16fea9e Set DataChannel SCTPTransport before OnDataChannel
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)