Problem of websocket

Asterisk Asterisk Support
1

hello! I want to get the sipml5 connected to my asterisk, I have asterisk 11.11.0 installed in a CentOS. I have also the latest version of sipml5 running in the latest vesrsion of chrome.
in the server part when I make in the chrome 192.168.1.106:8088/ws I have a response in the page and the websocket work correctly (I suppose) but this is not the case when I try to connect from the client side. In fact I’m getting this message from the debug of the sipml5 :

YOUR ARE USING DEBUG CODE. PLEASE USE CODE UNDER 'release' FOLDER or check https://code.google.com/p/sipml5/wiki/FAQ#How_to_reduce_the_size_of_the_scripts_before_deploying for more information on how to amalgamate the code.
Uncaught ReferenceError: tmedia_session_jsep01 is not defined 192.168.1.105/myphone/SIPml-api.js?svn=224:29
location=http://192.168.1.105/myphone/call.htm?svn=224#
User-Agent=Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36
WebSocket supported = yes
Navigator friendly name = chrome
OS friendly name = linux
Have WebRTC = yes
Have GUM = yes
Engine initialized
s_websocket_server_url=ws://192.168.1.106:8088/ws
s_sip_outboundproxy_url=(null)
b_rtcweb_breaker_enabled=yes
b_click2call_enabled=no
b_early_ims=yes
b_enable_media_stream_cache=no
o_bandwidth={}
o_video_size={}
SIP stack start: proxy='ns313841.ovh.net:12062', realm='<sip:192.168.1.106>', impi='6001', impu='<sip:6001@192.168.1.106>'
Connecting to 'ws://192.168.1.106:8088/ws'
==stack event = starting
__tsip_transport_ws_onerror
__tsip_transport_ws_onclose
==stack event = failed_to_start

I don’t know where the problem is, I will be grateful if someone can help me, I’m really stack

2

Your browser has connectivity with the IP of the Asterisk?
Your browser are in the same LAN that Asterisk?
Your PBX firewall is allowing the websocket port?
Are you sure that Asterisk is listening and the websocket module loaded properly?

All of this questions can be resolved looking in the asterisk wiki or using google.

3

Thank you Mr navaismo! it was a problem of firewall :smile: