1. 13 Aug, 2019 1 commit
  2. 29 Jul, 2019 1 commit
    • Jakub Adam's avatar
      webrtcbin: Support data channel SDP offers from Chrome · 831b1249
      Jakub Adam authored
      When negotiating a data channel, Chrome as recent as 75 still uses SDP
      based on version 05 of the SCTP SDP draft, for example:
      
       m=application 9 DTLS/SCTP 5000
       a=sctpmap:5000 webrtc-datachannel 1024
      
      Implement support for parsing SCTP port out of SDP message with sctpmap
      attribute. Fixes data channel negotiation with Chrome browser.
      831b1249
  3. 08 Jul, 2019 1 commit
  4. 03 Jul, 2019 1 commit
  5. 04 Jun, 2019 1 commit
    • Matthew Waters's avatar
      webrtc: fix the location of signalling-state change notification · 95488812
      Matthew Waters authored
      1. The spec indicates that the notification should occur near the end of
         'setting the description' processing
      2. The current location with the drop of the lock could cause the 'check
         if negotiation is needed' logic to execute and become confused about
         the state of the webrtcbin's current local descriptions.
         In the bad case, the following assertions could be hit:
         g_assert (trans->mline < gst_sdp_message_medias_len (webrtc->current_local_description->sdp));
         g_assert (trans->mline < gst_sdp_message_medias_len (webrtc->current_remote_description->sdp));
      
      Moving the signalling state change later in the set description task
      means that checking for a renegotiation will early abort as the
      signalling state is not STABLE before the session description and
      transceivers have been updated.
      95488812
  6. 30 May, 2019 12 commits
  7. 17 May, 2019 1 commit
  8. 13 May, 2019 1 commit
  9. 09 May, 2019 1 commit
    • Niels De Graef's avatar
      webrtc: Fix signals documentation · ce92cb81
      Niels De Graef authored
      Some GIR annotations were incorrect or even missing. The former isn't
      good for bindings, while the latter is especially annoying for signal
      handlers, as that means your arguments will get the wrong names in the
      rendered documentation.
      ce92cb81
  10. 15 Mar, 2019 1 commit
  11. 12 Mar, 2019 1 commit
  12. 15 Feb, 2019 1 commit
    • Matthew Waters's avatar
      webrtc: fix rtx + bundle · 2a117697
      Matthew Waters authored
      If bundle was used in combination with rtx, only the bundled transport
      stream would have correctly configured rtx parameters.
      
      Iterate over the payloads upfront in the bundled case to ensure the
      correct payload mapping is set for the RTX elements.
      2a117697
  13. 23 Jan, 2019 1 commit
    • Mathieu Duponchelle's avatar
      webrtc: expose ice-transport-policy property · 85c75bb2
      Mathieu Duponchelle authored
      This is the equivalent of iceTransportPolicy in the RTCConfiguration
      dictionary.
      
      Only two values are implemented:
      
      * all: default behaviour
      * relay: only gather relay candidates
      
      The third member of the iceTransportPolicy enum, "public", is
      obsolete.
      85c75bb2
  14. 19 Dec, 2018 2 commits
  15. 26 Nov, 2018 6 commits
  16. 26 Oct, 2018 2 commits
  17. 15 Oct, 2018 1 commit
  18. 08 Oct, 2018 2 commits
    • Matthew Waters's avatar
      webrtc: start in the closed state · 7bf18ad2
      Matthew Waters authored
      This means that we will reject all operations before we've transitioned
      into READY.
      
      This also fixes the tests using the default GMainContext in the NULL
      state instead of the webrtcbin internal GMainContext and thread.  Also
      removes a potential ordering race where on the element transitioning to
      READY, an operations could have been queued on two different threads and
      removing a guarentee on operation ordering.
      7bf18ad2
    • Aleix Conchillo Flaqué's avatar
      webrtcbin: start and stop thread when changing state · c4fe5239
      Aleix Conchillo Flaqué authored
      It might be possible that if we set webrtcbin to the NULL state some
      tasks (idle sources) are still executed and they might even freeze. The freeze
      is caused because the webrtcbin tasks don't hold a reference to webrtcbin and
      if it's last unref inside the idle source itself this will not allow the main
      loop to finish because the main loop is waiting on the idle source to finish.
      
      We now start and stop webrtcbin thread when changing states. This will allow
      the idle sources to finish properly.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=797251
      c4fe5239
  19. 21 Sep, 2018 2 commits
  20. 19 Sep, 2018 1 commit