- Avoid USE-CANDIDATE attribute in controlled agent binding requests.
- Don't respond to success responses in handleInboundControlled.
- Controlling agent now re-sends binding with USE-CANDIDATE when
receiving a binding request from a controlled agent.
Resolves#164
IceAgent improperly returns XorAddress when finding ports.
This would cause the portManager to fail finding the relevant port
since we are bound on the local (and not our public XorAddress)
Resolves#140
pion-WebRTC passes through every step, but messages get discared because
MI check is failing. We are able to Offer (or answer) to Chrome after
this is done
All the examples need to be updated, SDP should only be
emitted after gathering is done (until we support trickle)
Currently we can't be controlling-ICE, but that is probably a days
worth of work. After that is done pion-WebRTC should be able to talk
to itself.
Candidates are now generated with real priority, and actually pay
attention to the inbound messages.
Next we just need to pluck use-candidate + ice-controlling from the
messages and we will have a full-ice implementation (but we are not
controlling)
We then need to add timers to alert when the peer goes away OR when we
need to send again.
