> The proxy server only creates a whole new RTSP session under certain
> conditions, for example while waiting for an "OPTIONS" liveness reply.
> If the RTSP TCP session is interrupted when there is no pending
> request, the proxy server instead silently reconnects before sending
> the next request
>>
>> To reproduce the issue:
>> - Restart 'back end' server
>> - RTSP proxy will reconnect, and reuse the previous SESSION identifier
>> for PLAY / PAUSE, assuming the session is still valid
>> - 'Back end' server incorrectly accepts this, although the SESSION has
>> not been setup
>
> I don’t und
> It turns out that the sequence of SESSION identifiers is the same each
> time the 'back end' server's RTSP deamon is restarted, presumably
> because dome device unique constant such as serial number or MAC is
> used as random seed for the session identifiers.
>
> To reproduce the issue:
> - Rest
>> 1) The proxyserver reconnects to the source, but no data frames are
>> forwarded to the clients.
>
> If no data are forwarded to the (‘front-end’) clients, then that must mean
> that the ‘back-end’ server was not sending any data to the proxy server. If
> the ‘back-end’ server appears respons
