Unexpected Onvif bridge RTSP session behaviour

MIP
, , ,
1

I am developing a solution to stream RTP via the Onvif bridge, and am experiencing some unexpected behaviour with how the RTSP session is bound to it’s TCP connection:

Specifically, the Onvif bridge seems to expect the RTSP TCP connection to be maintained to allow the RTP stream to flow. I.e. as soon as the RTSP TCP connection disconnects, the RTP stream stops ( Trace logging on the Onvif bridge confirms it is reacting to the TCP connection disappearing).

This appears to be against RTSP 1.0 standard, which states that:

There is no notion of an RTSP connection; instead, a server maintains a session labeled by an identifier. An RTSP session is in no way tied to a transport-level connection such as a TCP connection. During an RTSP session, an RTSP client may open and close many reliable transport connections to the server to issue RTSP requests
https://www.ietf.org/rfc/rfc2326.txt

Can anyone confirm if my observations are correct? Or whether this is configurable?

Thanks

Hayden.

2

Hi Hayden,

You observations are correct.

This is the behavior of the RTSP server.

And you are right, it is against the RFC.

And unfortunately there is no setting that could change this behavior.