[sr-dev] Outbound: Flow Timer, tcp_connection_timeout, and WebSocket pings

[Peter Dunkley]

Actually, on re-reading RFC 5626 it is perfectly OK to use WebSocket
keep-alive instead of SIP keep-alives.

Section 3.5 states, "UAs and Proxies are also free to use native transport
keep-alives;"

Regards,

Peter



> Peter Dunkley writes:
>
>> When using outbound it is mandatory to have some form of SIP keep-alive
>> between the UA and the edge proxy.  However, in the case where SIP over
>> WebSocket is used the WebSocket transport has its own ping/pong
>> keepalive
>> mechanism.
>
> the whole section 6 of the websocket draft is a mess.  since websocket
> runs over tcp, it should use normal tcp keepalive like any other
> outbound tcp ua.
>
>> So to my mind, SIP keep-alives are optional when WebSocket is in use?
>
> section 6 is non-normative. if websocket guys want to change what
> outbound rfc tells, they have to write an rfc about it.
>
> -- juha
>
> _______________________________________________
> sr-dev mailing list
> sr-dev at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
>


-- 
Peter Dunkley
Technical Director
Crocodile RCS Ltd