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
In the case of RTP streams, all media descriptions SHOULD contain
"a=rtpmap" mappings from RTP payload types to encodings. If there is
no "a=rtpmap", the default payload type mapping, as defined by the
current profile in use (for example, RFC 1890 [5]) is to be used.
The text was updated successfully, but these errors were encountered:
Since the server should send it, this isn't high prio. However, it would be nice to have a fallback for servers that don't do what they should do.
For the fallback, I don't think we can use the suggested fix, as we read the payload type later on. So we would need a way to completely bypass payload type selection and go for the default 26.
Can not depay MJPEG RTSP stream if SDP message does not contain a rtpmap attribute.
Reason
The
VideoMedia
can not be found, becausertpmap
is undefinedmedia-stream-library-js/streams/src/components/jpegdepay/index.ts
Lines 23 to 28 in 07f9471
...if camera sends DESCRIBE response like this:
Suggested fix
Do not require
rtpmap
and checkfmt
instead. For example:...because the RFC says:
The text was updated successfully, but these errors were encountered: