Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed some errors that can occur when using Edge browser, when RTCPeerConnection is not implemented (ie. Edge), and when candidates have IPv6 addresses (Chrome and others too?) #16

Merged
merged 3 commits into from
Nov 30, 2015

Conversation

brianpursley
Copy link
Contributor

I didn't worry about trying to change the regex to match IPv6 addresses, I just left the matching code as-is and made it so that it does not cause an error message if it gets candidates with IPv6 addresses.

@brianpursley
Copy link
Contributor Author

Just a little more background on the IPV6 thing... I don't know why some of my candidates are coming in with IPV6 addresses, but I don't think I need or want them, so it is ok... I'm just trying to make it avoid having an error if that occurs.

May want to consider adding IPV6 support in the backlog though.

muaz-khan added a commit that referenced this pull request Nov 30, 2015
Fixed some errors that can occur when using Edge browser, when RTCPeerConnection is not implemented (ie. Edge), and when candidates have IPv6 addresses (Chrome and others too?)
@muaz-khan muaz-khan merged commit bee1a47 into muaz-khan:master Nov 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants