Invalid value for stunServers

[jwoertink]

I'm getting an Invalid value error when trying to add an array of stunServers to my config. Using version 0.6.3.

http://sipjs.com/api/0.6.0/ua_configuration_parameters/#stunservers

[wakamoleguy]

It looks like we are translating the array of stun servers improperly when creating the media handler. The error shows up only when you attempt to place a call. For the lazy, here are statements that can reproduce the error:

a = new SIP.UA({stunServers: ['stun:stun.l.google.com','stun:stun2.l.google.com']})
a.invite('foo@example.com');

[josephfrazier]

@jwoertink, I wasn't able to reproduce your error in JSFiddle. Could you provide a code snippet that will (in either a browser or Node)?

However, that fiddle did reproduce @wakamoleguy's error in Firefox. It looks like Firefox only allows String RTCIceServer urls, so I'll push a fix for that.

[jwoertink]

hm... Yeah, I made a separate app to test it, and I can't reproduce it either. It must be something else in my app that conflicts and causing the issue. At least we got one issue solved! I'll close this out for now.

[jwoertink]

I'm getting this issue again, but a little easier to debug.

Using stun:global.stun.twilio.com:3478?transport=udp for my stunServers setting throws this error. If I remove the query param, then it will work.

[josephfrazier]

Hmm, I would have expected that to work, too. Since it didn't, I dug into the code and the relevant specs to find out why. Here's what I found:

When you create the UA, it validates the stunServers against a formal grammar derived from draft-nandakumar-rtcweb-stun-uri (now RFC 7064), which does not allow for parameters in the URI. The Design Notes Appendix of the aforementioned draft links to a blog post that goes into detail about why the "transport" parameter is not allowed in a STUN URI, if you're really curious.

[jwoertink]

oh wow. Yeah, that's the URI given by twilio for their new STUN/TURN service. Both the stun and trun uri's have a transport query param 😒 I'll see what they say about the specs to see if they are planning on changing that.

[josephfrazier]

Are you able to make calls using the STUN URI with the parameter removed? If so, I'd just go with that.

EDIT: Note that TURN URIs can have the "transport" parameter and should work with the turnServers UA option

[wakamoleguy]

I do not believe we currently plan on supporting invalid STUN URLS. I'll close the issue, and it can be reopened if it looks like there is a compelling reason to tackle this.