SIP requires a Content-Length header for TCP transport. But most HTTP clients do not set the content length for normal GET requests. Therefore, the core must be configured to allow incoming requests without content length header:

tcp_accept_no_cl=yes

Hi,

That is before the event_route is executed.

It might be worth trying to increase the size of tcp_rd_buf_size.

Regards,

Peter

On Mon, 2012-07-09 at 12:27 +0300, Juha Heinanen wrote:

Peter Dunkley writes:

> The nathelper stuff works for me, and is useful if your client doesn't
> support the various extensions.

ok, i'll check if sipml5 supports gruu once i manage to make it send
register request.  currently initial GET fails like this:

Jul  9 11:29:43 siika /usr/sbin/sip-proxy[9153]: ERROR: <core> [tcp_read.c:1292]: ERROR: tcp_read_req: bad request, state=7, error=4 buf:#012GET / HTTP/1.1#015#012Upgrade: websocket#015#012Connection: Upgrade#015#012Host: 192.98.103.10#015#012Origin: https://localhost#015#012Sec-WebSocket-Protocol: sip#015#012Sec-WebSocket-Key: 3uCSAAgsydjW9+RD857uXg==#015#012Sec-WebSocket-Version: 13#015#012Sec-WebSocket-Extensions: x-webkit-deflate-frame#015#012#015#012#012parsed:#012GET / HTTP/1.1#015#012Upgrade: websocket#015#012Connection: Upgrade#015#012Host: 192.98.103.10#015#012Origin: https://localhost#015#012Sec-WebSocket-Protocol: sip#015#012Sec-WebSocket-Key: 3uCSAAgsydjW9+RD857uXg==#015#012Sec-WebSocket-Version: 13#015#012Sec-WebSocket-Extensions: x-webkit-deflate-frame#015#012#015#012

i'm not sure if this error is generated before
event_route[xhttp:request] is executed.

-- juha

_______________________________________________
sr-dev mailing list
sr-dev@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

_______________________________________________ sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev

-- 
Peter Dunkley
Technical Director
Crocodile RCS Ltd