This module allows you to view an RTSP stream in your web browser using an existing express.js server.
Internally, this module uses websockets to create an endpoint in your web server (e.g. /api/stream
) which relays the RTSP stream using ffmpeg. On the client side, JS-MPEG is used to decode the websocket stream.
The module handles all the complications that unreliable connections introduce:
server
<=> RTSP stream
is disconnected, it will automatically be reconnected when availableclient
<=> server
is disconnected, the client will keep trying to reconnectnpm install -S rtsp-relay express
You don't need to install ffmpeg!
const express = require('express');
const app = express();
const { proxy, scriptUrl } = require('rtsp-relay')(app);
const handler = proxy({
url: `rtsp://admin:admin@10.0.1.2:554/feed`,
// if your RTSP stream need credentials, include them in the URL as above
verbose: false,
});
// the endpoint our RTSP uses
app.ws('/api/stream', handler);
// this is an example html page to view the stream
app.get('/', (req, res) =>
res.send(`
<canvas id='canvas'></canvas>
<script src='${scriptUrl}'></script>
<script>
loadPlayer({
url: 'ws://' + location.host + '/api/stream',
canvas: document.getElementById('canvas')
});
</script>
`),
);
app.listen(2000);
Open http://localhost:2000 in your web browser.
If you have babel/webpack set up, you can import the loadPlayer
instead of using a <script>
tag.
Example code is available for react and for angular.
// client side code
import { loadPlayer } from 'rtsp-relay/browser';
loadPlayer({
url: `ws://${location.host}/stream`,
canvas: document.getElementById('canvas'),
// optional
onDisconnect: () => console.log('Connection lost!'),
});
If you have hundreds of cameras and don't want to define a seperate route for each one, you can use a dynamic URL:
app.ws('/api/stream/:cameraIP', (ws, req) =>
proxy({
url: `rtsp://${req.params.cameraIP}:554/feed`,
})(ws),
);
You may see a MaxListenersExceededWarning
if the relay is re-transmitting 10+ streams at once, or if 10+ clients are watching.
This is expected, and you can silence the warning by adding process.setMaxListeners(0);
to your code.
Depending on your network configuration, you can try the following options to improve the stream quality:
// try this:
app.ws('/api/stream', proxy({ additionalFlags: ['-q', '1'] }));
// or this:
app.ws('/api/stream', proxy({ transport: 'tcp' }));
Note that both these methods will use more bandwidth.
If you want to use HTTPS, you will need to change the stream URL to wss://
, like the following example:
const rtspRelay = require('rtsp-relay');
const express = require('express');
const https = require('https');
const fs = require('fs');
const key = fs.readFileSync('./privatekey.pem', 'utf8');
const cert = fs.readFileSync('./fullchain.pem', 'utf8');
const ca = fs.readFileSync('./chain.pem', 'utf8'); // required for iOS 15+
const app = express();
const server = https.createServer({ key, cert, ca }, app);
const { proxy, scriptUrl } = rtspRelay(app, server);
app.ws('/api/stream', proxy({ url: 'rtsp://1.2.3.4:554' }));
app.get('/', (req, res) =>
res.send(`
<canvas id='canvas'></canvas>
<script src='${scriptUrl}'></script>
<script>
loadPlayer({
url: 'wss://' + location.host + '/api/stream',
canvas: document.getElementById('canvas')
});
</script>
`),
);
server.listen(443);
We have end-to-end tests to ensure that the module actually works. These tests spin up a RTSP server using aler9/rtsp-simple-server and create several different streams for testing. These tests are far from complete.
To make developing easier, run node test/setupTests
. This creates two RTSP streams that can be used instead of real IP cameras (rtsp://localhost:8554/sync-test-1
and rtsp://localhost:8554/sync-test-2
).