[asterisk-bugs] [JIRA] Commented: (ASTERISK-20221) seg fault when register via websocket

[James Mortensen (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-20221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195774#comment-195774 ] 

James Mortensen commented on ASTERISK-20221:
--------------------------------------------

Hi Michael,

I apologize. It looks like the patch did fix the crash. I had two instances of Asterisk running, discovered after running "ps -C asterisk u".  One must have been the previous instance, before applying the patch and recompiling.  

While the server isn't crashing anymore, I'm still getting the 400 Bad Request and the 401 Unauthorized when trying to login.  From what I hear, this could be something that needs to be modified in the sipML5 library itself. Thus, I'll see what I can find. If anyone knows why I'm getting the unauthorized and bad requests, please let me know.  I'll update the mailing list as well. 

Thanks again!
James


> seg fault when register via websocket
> -------------------------------------
>
>                 Key: ASTERISK-20221
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20221
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/WebSocket
>    Affects Versions: 11.0.0-beta1
>         Environment: debian wheezy: Linux debian 3.2.0-3-686-pae running in a virtual machine
>            Reporter: Sven Beisiegel
>         Attachments: asterisk-20221-ws-family-filter.diff, crash_when_register_via_websocket.txt, james_output.txt
>
>
> Asterisk has been compiled with option "--disable-asteriskssl", "DON'T OPTIMIZE"-Flag and "BETTER_BACKTRACES"-Flag
> A default configuration has been created with "make samples"
> The default configuration has been adjusted like in the three files below (link to pastbin)
> httpd.conf: http://pastebin.com/UMmkJqxt
> extensions.conf: http://pastebin.com/kKa4Mqvi
> sip.conf: http://pastebin.com/JysvnpS8
> The following scenario crashes Asterisk every time: 
> - Register with user 100 or 101 with correct credentials for digest authentication. For registration via websockets, two clients have been used. 1) SIPML5, 2.) SIP-JS (http://code.google.com/p/sip-js)
> The following does not crash Asterisk at all:
> - Use a wrong user-id or password for digest authentication, Asterisk tells me that digest credentials are wrong (403 Forbidden - Auth)
> - Try to register with user credentials where the user is not configured for registration via websockets, Asterisk sends a forbidden as well.
> The backtrace can be found at pastebin: http://pastebin.com/bhy3RjgC
> best regards,
> Sven

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira