-
Notifications
You must be signed in to change notification settings - Fork 6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RtspMediaTrack absolute path (URI) for track #9183
Labels
Comments
It seems your camera is not accepting a URL. Or your control attribute contains an |
We will have a fix for this, thanks for pointing out! |
Yes, our control attribute has an absolute path (starts with rtsp://123.123.....) |
The use of absolute paths is in the RFC, so we should support it. The fix
is on the way.
…On Tue, Jul 13, 2021 at 8:07 PM Aleksey Blekot ***@***.***> wrote:
Yes, our control attribute has an absolute path (starts with
rtsp://123.123.....)
Again I'm not sure, maybe our camera responses implementation does not
follow RTSP standards...
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#9183 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUCMUUS4R5WG5HJZZOTPBWTTXSFHRANCNFSM5AG6KJ2A>
.
|
ojw28
pushed a commit
that referenced
this issue
Jul 14, 2021
Issue: #9183 RFC2326 Section C.1.1 specifies that the URI to identify a track can be either absolute (like rtsp://example.com/path) or relative (like "path"). Currently we don't handle absolute URI, and this CL is to add the support. Note though, we don't currently use the Content-Base or Content-Location headers for the session URI. PiperOrigin-RevId: 384649818
icbaker
pushed a commit
that referenced
this issue
Jul 21, 2021
Issue: #9183 RFC2326 Section C.1.1 specifies that the URI to identify a track can be either absolute (like rtsp://example.com/path) or relative (like "path"). Currently we don't handle absolute URI, and this CL is to add the support. Note though, we don't currently use the Content-Base or Content-Location headers for the session URI. PiperOrigin-RevId: 384649818
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If mediaDescription.attributes.get(ATTR_CONTROL) - returns absolute path (started with rtsp://) we have invalid path.
So, I have made little checking to handle this case:
The text was updated successfully, but these errors were encountered: