media-server-node
media-server-node copied to clipboard
Older h264 (RTSP) streams break on v0.136.0
We get some RTSP-streams that gets buggy after this update. We don't get any image in our JS-client, but we see the stream being transported in chrome://webrtc-internals.
0.135.1 to v0.136.0 https://github.com/medooze/media-server-node/commit/b314638af4b184afe4c9ef03f83a54097563205b
We're quite sure it's related to all the commits done 12th May 2023:
From https://github.com/medooze/media-server/commit/275cb8be0c842aaf0e49c51cf683d5efd4e343ee to https://github.com/medooze/media-server/commit/c560e1c0679387873cbb6e64bb6b6763244d373a
This affect a bit older RTSP-cameras.
Are there any any modifications we can add to the Capabilitites of the Media-server that can work-around this issue?
module.exports = {
audio: {
codecs : ["opus"],
extensions: [
"urn:ietf:params:rtp-hdrext:ssrc-audio-level",
"http://www.ietf.org/id/draft-holmer-rmcat-transport-wide-cc-extensions-01",
],
},
video: {
codecs : ["h264;packetization-mode=1"],
rtx : true,
rtcpfbs : [{ id: "ccm", params: ["fir"] }, { id: "nack" }, { id: "nack", params: ["pli"] }],
extensions: [
"http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time",
"urn:ietf:params:rtp-hdrext:sdes:repaired-rtp-stream-id",
"urn:ietf:params:rtp-hdrext:sdes:rtp-stream-id",
"urn:ietf:params:rtp-hdrext:sdes:mid",
],
simulcast: true,
},
};