I’m running into a problem.
we created a tool that inserts some security based on parameters in rtsp urls.
it accepts urls like
rtsp://:554/sdpfile.sdp?secret=&client_id=
On a DESCRIBE request by wowza we return the following content-base:
rtsp://:554/sdpfile.sdp
Wowza however, continues to use the url with the parameters, but at some time it adds /trackID=n
rtsp://:554/sdpfile.sdp?secret=&client_id=/trackId=n
but we expect rtsp://:554/sdpfile.sdp/trackId=n
our security protocol fails, because basically the trackID=n is appended to the client identifier
Why doesn’t wowza use the content-base url returned from the DESCRIBE ?