[asterisk-bugs] [JIRA] (ASTERISK-20745) In MESSAGE received over WebSocket, the body last char is cut

[Iñaki Baz Castillo (JIRA)]

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

Iñaki Baz Castillo commented on ASTERISK-20745:
-----------------------------------------------

Probably the bug also exists when processing a SDP received in an INVITE over WebSocket, but SDP's usually end in CRLF so removing the last char is not so "important". Not sure about it however.

For sure this is a bug in the WebSocket layer. This issue does not occur when using other WebSocket capable SIP servers/proxies. And it's clear in the above wireshark capture that the web browser is sending a correct MESSAGE with body "qwer".
                
> In MESSAGE received over WebSocket, the body last char is cut
> -------------------------------------------------------------
>
>                 Key: ASTERISK-20745
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20745
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/WebSocket
>    Affects Versions: SVN, 11.0.1
>            Reporter: Iñaki Baz Castillo
>
> When Asterisk receives a SIP MESSAGE over WebSocket it cuts the last char of the body. So if for example the MESSAGE contains "Content-Length: 4" and a body with content "1234" (without quotes), the Asterisk debug console prints the body as "123", and then it forwards the MESSAGE with "123" as body.
> This bug seems not to occur when the SIP MESSAGE arrives via SIP over TCP or UDP, so it must be a bug in the SIP WebSocket layer/parser.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira