Using Content-Base from Describe

Wowza Streaming Engine
1

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 ?

2

If the stream name is an url as it is in this case then the query parameters are considered part of the url and not part of the stream name. The best I can do for now is fix it so the SETUP RTSP calls look like this:

rtsp://:554/sdpfile.sdp/trackId=n?secret=&client_id=

rather than this:

rtsp://:554/sdpfile.sdp?secret=&client_id=/trackId=n

Does this help?

Charlie

3

The code with the fix I proposed is here:

https://www.wowza.com/downloads/WowzaMediaServer-1-7-0/WowzaMediaServerPro1.7.0-patch9.zip

Charlie

4

I believe it was good practice to use the content-base when provided.

A post in another forum says:

"The new versions of the RTSP spec have clearer

language about this and mentions that the best way to figure out the URI is

to look at:

  1. Content-base

  2. Content-Location

  3. Original URL"

Anyway, the suggested fix is cleaner then the current append of the trackID.

We have created an exception in our code to deal with the current situation.

Thanks for the quick reply !