WebSocket field in Demo registration doesn't override the default about jssip HOT 11 CLOSED

Yes, that's a bug in the demo code. We will address it soon.

from jssip.

James,

WebSocket field does now honor it's content. Beware that 'wss' schema is allowed in this demo. Thanks.

from jssip.

Sorry, there is a typo in the previous comment. 'wss' schema is NOT allowed in this demo.

from jssip.

@jmillan Why not?

from jssip.

AFAIR currently the secure transport option is a separate config option. Remember the discussion: Should we accept that the user configures N WebSocket URI's somw of them with WS schema and others with WSS? IMHO security should be a global option.

from jssip.

@ibc This is not about security, some parameters affect the whole outbound proxy set and others just each record. We need to revisit this.

from jssip.

@saghul The 'secure_transport' config parameter is not a seteable parameter in this demo. You could set it in the web sources. That was what I meant.

from jssip.

hi, i am new at this SIP-JS roads !!!! i have an asterisk server configured but i didn't get how to connect jsSIP to my asterisk server! i get all the time "connected" but when i go to asterisk i see that is not true there are no clients connected.... so i think maybe i am doing something wrong!!! can someone help me?!?!

from jssip.

@goncaloazevedo - www.jssip.net is being prepared with the proper documentation in order to test JsSIP. It's going to be out in the coming days. There is also a googlegroup (email list) where you could address your question: https://groups.google.com/forum/?fromgroups#!forum/jssip.

regards

from jssip.

@goncaloazevedo, please update your git repository. The JsSIP demo page has been fixed today so now setting your own WS URI in the login box will make JsSIP to connect to that address (insted of the default one in tryit.jssip.net).

from jssip.

Fixed in ea0b054

from jssip.