A Stream is an access object: it binds a protocol server, connection role and identity rule. Create it before handing URLs or stream keys to encoders and receivers.
Avant de commencer
A running SRT or RTMP server.
The intended role: publisher sends media; receiver consumes it.
A planned stream ID, stream key or allowed host that does not collide with another connection.
Réglages expliqués
Seuls les contrôles utiles à l’opérateur sont expliqués. Les noms de champs internes et événements d’implémentation sont volontairement masqués.
Identity
Name the connection and choose its server.
- Name
Operator-facing name for the encoder, feed or receiver.
- Active
Allow the connection object to be used after it is saved.
- Protocol
Choose SRT or RTMP to match the owning server and client.
- Streaming server
Select the existing server that accepts this connection.
Access
Grant only the role and identity the client needs.
- Role
Publisher sends a feed; receiver reads a feed.
- Stream ID or stream key
Stable media identifier used by the client connection.
- Allowed host
Optional IP-based restriction for the connecting client.
Premier workflow sûr
- 01
Open Streams and choose the same protocol as the target server.
- 02
Select the running server and choose Publisher or Receiver.
- 03
Set the stream identity or permitted host required by the server access policy.
- 04
Save and start the Stream.
- 05
Use the generated connection details in one real encoder or receiver and verify media.
Exemples de workflows
Give a remote encoder publisher-only access
An external operator should send one feed but must not receive other feeds.
Comment le construire
- 1
Create a Publisher Stream on the selected server.
- 2
Assign a unique stream ID/key or restrict the known encoder host.
- 3
Send only that connection detail to the encoder operator.
- 4
Start the encoder and verify that a different identity is rejected.
Create a receiver for a monitored output
A decoder or confidence monitor should read one named stream.
Comment le construire
- 1
Create a Receiver Stream on the server that owns the live feed.
- 2
Use the expected stream identity and optional receiver host restriction.
- 3
Connect the decoder with the generated receiver details.
- 4
Confirm playback and server-side connection state.
Vérifier le résultat
- The intended publisher or receiver connects with its assigned role.
- An incorrect stream identity is rejected when explicit access is enabled.
- The owning server and live statistics show the expected connection.
Dépannage
A valid client is rejected
Vérifier- Compare protocol and selected server.
- Check role, stream identity and host restriction exactly.
Correct the single mismatched access value; do not enable allow-all as a diagnostic shortcut.