[Bug 797266] webrtcbin: allow specifying ICE network addresses

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=797266

Matthew Waters (ystreet00) <ystreet00 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #12 from Matthew Waters (ystreet00) <ystreet00 at gmail.com> ---
(In reply to Aleix Conchillo Flaqué from comment #11)
> (In reply to Aleix Conchillo Flaqué from comment #10)
> > (In reply to Aleix Conchillo Flaqué from comment #9)
> > 
> > > I see. Does the candidate numbering affect at all? That is, if you get
> > > 
> > > candidate:1 1 UDP 2013266431 10.10.131.127 58037 typ host
> > > candidate:2 1 TCP 1015022335 10.9.0.3 9 typ host tcptype active
> > > candidate:3 1 TCP 1010828031 10.4.8.7 37152 typ host tcptype passive
> > > 
> > > And you only want the two last ones, is it ok to send?
> > > 
> > > candidate:2 1 TCP 1015022335 10.9.0.3 9 typ host tcptype active
> > > candidate:3 1 TCP 1010828031 10.4.8.7 37152 typ host tcptype passive
> > > 
> > > without candidate:1?
> > 
> > This seems to work, but is it allowed? Or would I need to recreate those
> > numbers in the right order?
> 
> According to the RFC, this is a just an identifier (not an ordering), the
> foundation:
> 
> https://tools.ietf.org/id/draft-ietf-mmusic-ice-sip-sdp-14.html#rfc.section.
> 5.1
> https://tools.ietf.org/html/draft-ietf-ice-rfc5245bis-00#page-23
> 
> So, if I understand correctly, I can just filter the address and keep
> sending the same thing.
> 
> Can you confirm? If so, we can just close this bug.

Correct.  If there's something that's not exposed from the candidate string, we
can look into adding something for that.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.