rtmp
Starts a standalone RTMP ingest server that bridges published streams to MoQT. Like rtsp and rtsp-push, this is a self-contained origin and does not join the relay peer mesh (no peer connections, no announce relay).
Usage
qumo rtmpTakes no flags or arguments — configured entirely through environment variables.
Example
$ qumo rtmp
Ingest : :1935
Serve : :4433
Publishers then push to rtmp://<host>:1935/<path>, and subscribers consume
the same path over MoQT on :4433. Override either address to taste:
$ RTMP_INGEST_ADDR=:1936 RTMP_SERVE_ADDR=127.0.0.1:4456 qumo rtmp
Ingest : :1936
Serve : 127.0.0.1:4456
Configuration
| Variable | Default | Description |
|---|---|---|
RTMP_INGEST_ADDR | :1935 | RTMP listen address. |
RTMP_SERVE_ADDR | :4433 | MoQT listen address. |
CERT_FILE / KEY_FILE | certs/server.crt / certs/server.key | TLS certificate and key. |
CORS_ALLOWED_ORIGINS | (unset) | Comma-separated WebTransport origins (default: same-origin only; * allows any). |
See also
- rtsp — pull an RTSP source into MoQT.
- rtsp-push — the RTSP equivalent of this command.
- Deployment → Docker — running it as a container.
- Deployment → TLS & mTLS — generating the certificate it needs.