Does not work with chrome 52 (Media stream permission denied)

[vishal4487]

Hi, i m using asterisk 13.10 with sipml5 on chrome52. User registration works ok. but when try to call gives error "Media stream permission denied" Pls help.

[roginvs]

Usually this problem is caused by plain http connection, not https. Try to use https for webpage and wss for asterisk websockets. You can get a free ssl certificate from startssl or wosign, but if you will prefer to use self-signed, then do not forget to open https://IP:8089/ws link in browser in order to add :8089 port certificate to trusted in Chrome.

[bendney]

i'm using chrome 56, and met same issue, I tried to use https for webpage, but page show "2:SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS." sipml5 is the current master branch code

[roginvs]

@bendney , use wss instead of ws (i.e. wss://example.org/ws)

[bendney]

I'm using freepbx, when I change ws to wss, asterisk CLI print "HTTP closing session. status_code:400" and page said "Failed to connet to the server"

[access2praveen]

Try accepting the risk by navigating to https://example.com:8089/ and this would add certificate to security exception from web browser

On Fri, Mar 24, 2017 at 3:05 PM, Bendney Yu notifications@github.com wrote:

i'm using chrome 56, and met same issue, I tried to use https for webpage, but page show "2:SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS." sipml5 is the current master branch code

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/DoubangoTelecom/sipml5/issues/269#issuecomment-288928197, or mute the thread https://github.com/notifications/unsubscribe-auth/AWW4kkq6gbaxa8iZCFAPnCgSqjfMcxOlks5ro0ENgaJpZM4JrTlZ .

[bendney]

@access2praveen I'm trying to accept risk by navigating to https://IP:8089/, I can't access this url

[access2praveen]

then your http server is not running .. did you try http://IP:8080/

Check the listening port of https in your server

On Mon, Mar 27, 2017 at 6:41 PM, Bendney Yu notifications@github.com wrote:

@access2praveen https://github.com/access2praveen I'm trying to accept risk by navigating to https://IP:8089/, I can't access this url

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/DoubangoTelecom/sipml5/issues/269#issuecomment-289377196, or mute the thread https://github.com/notifications/unsubscribe-auth/AWW4kibJRBqz9n7GfqPT1uFnHOWPBaE0ks5rp2gPgaJpZM4JrTlZ .

[mrbarua]

http://IP:8080

but I got the new issue that after call progress it says not acceptable here.