You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The trouble is that the gatherer will start gathering on construction and reporting candidates. The trouble is the priority cannot be calculated as per recommendation because the component ID is not known upon construction. Associated RTCP based gatherers are passed into the start method for a transport created by "createAssociatedTransport()" but the gatherer is not specifically an RTCP based gatherer.
The text was updated successfully, but these errors were encountered:
One way to fix this would be to add a .createAssociatedGatherer() method to the IceGatherer, which would return an IceGatherer object with a component attribute of RTCP.
#148
- Clarified handling of incoming connectivity checks prior to calling iceTransport.start(), as noted in:
#170
- Clarified handling of incoming DTLS packets, as noted in:
#173
- Added RTCIceGatherer as an optional argument to the RTCIceTransport constructor, as noted in:
#174
- Clarified handling of contradictory RTP/RTCP multiplexing settings, as noted in:
#185
- Clarified error handling relating to RTCIceTransport, RTCDtlsTransport and RTCIceGatherer objects in the "closed" state, as noted in:
#186
- Added component method and createAssociatedGatherer() method to the RTCIceGatherer object, as noted in:
#188
- Added close() method to the RTCIceGatherer object as noted in:
#189
- Clarified behavior of TCP candidate types, as noted in:
#190
- Clarified behavior of iceGatherer.onlocalcandidate, as noted in:
#191
- Updated terminology in Section 1.1 as noted in:
#193
- Updated RTCDtlsTransportState definitions, as noted in:
#194
- Updated RTCIceTransportState definitions, as noted in:
#197
https://tools.ietf.org/html/rfc5245#section-4.1.2.1
The trouble is that the gatherer will start gathering on construction and reporting candidates. The trouble is the priority cannot be calculated as per recommendation because the component ID is not known upon construction. Associated RTCP based gatherers are passed into the start method for a transport created by "createAssociatedTransport()" but the gatherer is not specifically an RTCP based gatherer.
The text was updated successfully, but these errors were encountered: