-
Notifications
You must be signed in to change notification settings - Fork 702
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
New media stream does not contain ICE candidates in SDP #631
Comments
Your logs indicate that you are using a 0.7.X version of SIP.js with a custom media handler. Can you provide logs with a more recent version and no custom hacks? 0.11.3 has code that resets ICE gathering state
|
Ok. I see the issue.
The |
I removed case #1. Looks like issue was in old library, but I cannot reproduce any more. So, issue only with outgoing re-Invite. |
Hi, #815 is a new implementation which I believe/hope addresses this issue. Dealing with ICE gathering starting again after it has once completed is now handled. And ...
... is now supported. |
As there was no response and we believe this is fixed, we are going to close the issue. Please test with 0.17.0 and re-open if there is still an issue there. |
Hi, Thanks for fixes, I just verified and now Google Chrome works fine. |
But I still have problems with FireFox. When reinvite is called to add video stream FireFox adds one more audio stream and video stream with "c=IN IP4 0.0.0.0". Does anyone know why ? any ideas ? (maybe it's know issue)
|
Unfortunately the latest Chrome do the same. |
Describe the bug
There is no ICE candidates when I try to escalate audio only call to video call.
Looks like this happens because waitForIceGatheringComplete() does not wait because isIceGatheringComplete() is true because it's re-INVITE and ICE was completed for the first/initial INVITE.
Logs
1.txt
To Reproduce (if possible)
Steps to reproduce the behavior:
Expected behavior
SDP should contains ICE candidates.
Observed behavior
New stream does not have ICE candidates.
Environment Information
"sip.js": "0.11.3"
Chrome 70 and FireFox 63 on windows.
The text was updated successfully, but these errors were encountered: