Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Microsoft Edge support #432
referenced this issue
Sep 12, 2017
According to the release announcement, Microsoft Edge is supported in 0.8:
Microsoft edge works with the WebRTC adapter and SIP.js. Simply load the adapter before SIP.js on the DOM and SIP.js has everything it needs.
In my testing it appears that Edge is unhappy with SDP generated from anything that is not Edge. I am working on a base set of modifiers to get better compatibility with Edge.
Yes, it works in Chrome and Firefox.
I've solved the problem with Edge periodically sending requests to web sockets to keep them active:
Now, I've new errors and warnings:
Sending those requests manually seems like something the keepAlive system should take care of- websockets can have their own system to keep the connection alive, but in the event of that not working/existing SIP.js has its keepAlive system that's configurable with the
I've configured KeepAliveInterval to 20 (seconds) and it doesn't work. Every 30 seconds I've the same error reported 3 days ago.
SIP.js with Edge only works sending requests to web sockets to keep them active:
Is there any open issue about this?