-
Notifications
You must be signed in to change notification settings - Fork 16
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
Questions regarding translation #27
Comments
cc @fippo |
(1): port 1 should be translated to port 9 these days |
Thanks for the info @fippo, I'll work on updating this lib and open a pr. I've also come across this:
where the original looked like this:
Should this be changed also to match the original? |
no, those lines can have a direction. Which defaults to sendrecv so sendrecv may be omitted but it should be parsed properly in the current state |
@legastero Can you provide some insight on the following?
Here: https://github.com/otalk/sdp-jingle-json/blob/master/lib/tojson.js#L20 it looks like the port is getting changed? I'm seeing something like
m=audio 9 ...
(from the offer) be changed tom=audio 1 ...
. Is there a reason for that? I would think the goal would be to convert sdp to json, and be able to get the original sdp back when converting the json back to sdp.Here: https://github.com/otalk/sdp-jingle-json/blob/master/lib/tosdp.js#L55 It looks like it's basically hard coding the sdp for data channels but this is blowing up for me in chrome with the following error:
The sdp being generated for the offer looks like
but what's being received looks like this:
I assume this is a chrome change of some sort because this used to not be a problem. I'm also seeing issues in firefox:
Can you weigh in on these issues?
The text was updated successfully, but these errors were encountered: