webrtcbin connection-state always new because dtls-transport states don't change

Submitted by Jan Schmidt @thaytan

Link to original bug (#796896)

Description

GstWebRTCDTLSTransport doesn't ever change the "state" property from NEW, so the overall connection-state of webrtcbin never changes.

Part of the problem is that dtlssrtpbin doesn't expose enough API to report the state properly yet, but for now just switching to CONNECTED when on-key-set is fired.

This issue has been open for over a year now. I'd like to request this be made a higher priority, not having info on the connection state presents some issues for production usage. I need to know when the remote end is hanging up. I'll look for workarounds, as my timeline can't wait for this to be fixed, but I'm sure I won't like my workaround and I'd like to get rid of it someday.

Note, one can workaround by monitoring the expiration of the related RTP session.

@ndufresne Thanks for that info, noob question, what signals or properties would one listen to in gstreamer to do said monitoring? Or would that just be external to gstreamer?

Right, RTP statistics are usually monitored using polling (e.g. every half a second). You can look at the generic property signal (notify::property-name), but from my experience, that was too high pace, and was introducing overhead. RTP streaming is state-less / connection less, so you can't always rely on disconnection signalling.

mentioned in issue #1143 (closed)

assigned to @slomo

mentioned in commit slomo/gst-plugins-bad@508c523a

mentioned in commit slomo/gst-plugins-bad@1f844105

mentioned in merge request !966 (merged)

mentioned in commit slomo/gst-plugins-bad@73aa5c81

mentioned in commit slomo/gst-plugins-bad@bbfc2575

mentioned in commit slomo/gst-plugins-bad@4c6b80d2

mentioned in commit slomo/gst-plugins-bad@01f1a207

mentioned in commit slomo/gst-plugins-bad@2118b52e

mentioned in commit slomo/gst-plugins-bad@694c91f2

mentioned in commit slomo/gst-plugins-bad@c66d636e

mentioned in commit slomo/gst-plugins-bad@d6e373e2

!966 (merged) fixes this.

mentioned in commit slomo/gst-plugins-bad@74dbd58a

mentioned in commit slomo/gst-plugins-bad@ecddfbfd

mentioned in commit slomo/gst-plugins-bad@d6183a46

mentioned in commit slomo/gst-plugins-bad@832ec30d

mentioned in commit slomo/gst-plugins-bad@b3431b72

mentioned in commit slomo/gst-plugins-bad@d6c4d50c

mentioned in commit slomo/gst-plugins-bad@584f8739

mentioned in commit slomo/gst-plugins-bad@2c9cc26f

mentioned in commit slomo/gst-plugins-bad@5e16159e

mentioned in commit slomo/gst-plugins-bad@6d340c7e

mentioned in commit slomo/gst-plugins-bad@2b24da73

mentioned in commit slomo/gst-plugins-bad@41175f4e

mentioned in commit slomo/gst-plugins-bad@b2e77393

mentioned in commit slomo/gst-plugins-bad@2798a80e

mentioned in commit slomo/gst-plugins-bad@22869356

closed via commit b2e77393

closed via commit 2798a80e

mentioned in commit ystreet/gst-plugins-bad@87beaabe

mentioned in issue #1539 (closed)

mentioned in commit ystreet/gst-plugins-bad@c5c50260