You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unlike HTTP, RTSP allows the media server to send requests to the
media client. However, this is only supported for persistent
connections, as the media server otherwise has no reliable way of
reaching the client. Also, this is the only way that requests from
media server to client are likely to traverse firewalls.
The RTSP server I've tried do in fact support that, but I see no way to dispatch such updates in the client. Worse yet, with persistent connections and periodic invocations of Describe() I'm currently getting ERR: expected 'RTSP/1.0', got 'ANNOUNCE' when the server actually did notify the client on a change.
The only option I currently see is to periodically poll Describe() and close the connection after each run, which is a bit nasty. Is there a better way I'm not aware of?
The text was updated successfully, but these errors were encountered:
Hello, you're right, this is a missing feature that can be added in the future. The only server->client request that i was aware of was REDIRECT, but you rightly pointed out that also ANNOUNCE can be sent in this direction.
Is there a way to react to server stream changes?
Quoting RFC2326, section 9
The RTSP server I've tried do in fact support that, but I see no way to dispatch such updates in the client. Worse yet, with persistent connections and periodic invocations of
Describe()
I'm currently gettingERR: expected 'RTSP/1.0', got 'ANNOUNCE'
when the server actually did notify the client on a change.The only option I currently see is to periodically poll
Describe()
and close the connection after each run, which is a bit nasty. Is there a better way I'm not aware of?The text was updated successfully, but these errors were encountered: