Skip to main content
An Inbound Feed lets you bring a live video source from outside Coresee directly into a room, where it appears alongside participants as a media source on the stage. This is how you connect an external camera, encoder, or production switcher to a Coresee session.
Inbound vs. Outbound. An Inbound Feed brings an external source into the room. An Outbound Feed sends the room’s video out to an external destination (like YouTube Live or a custom RTMP endpoint). They’re configured in the same place but do the opposite job.

Where to find Inbound Feeds

Inbound Feeds live in the Streaming tab of the Side Panel, under the Feeds section alongside Outbound Feeds.
Host and co-host only. The Streaming tab — and Inbound Feeds within it — is not visible to participants, in either the pre-session homepage or an active room.
Streaming Tab

How an Inbound Feed works

Creating an Inbound Feed generates a unique ingest address for that feed — a Server URL and Channel ID. You enter these into your external device or encoder, which then pushes its video stream to Coresee. Once the stream is live, Coresee exposes it as a media source that can be brought into the room the same way you’d present a file.
  • The external source does the “pushing” — Coresee doesn’t reach out to the device, so the device needs network access to send its stream out.
  • A feed can be created and configured before a session starts, so it’s ready to go the moment you need it.
  • Multiple Inbound Feeds can exist on the same room at once, each with its own card in the Feeds list.

Creating an Inbound Feed

Set up a new Inbound Feed from the Streaming tab before connecting your external device.
1

Open the dropdown to select your streaming protocol

RTMP, SRT or RTSP
2

Click +

3

Expand the card for the connection details

Streamingtab Inbound Rtmp
Exactly where these values go on your device varies by manufacturer — typically a Server URL (or similar) field and a Stream Key/Channel ID (or similar) field.

Common Questions

Yes — Channel IDs are permanent per feed. You can create as many Inbound Feeds as you’d like within a room, and each one gets its own unique Channel ID, though all feeds in the room share the same Server URL. For example, if you create three Inbound Feeds in a room, you’ll have one Server URL and three distinct Channel IDs.
Inbound Feeds support RTMP, SRT, and RTSP. You choose the protocol from the dropdown when creating the feed, and the connection details shown (Server URL, Channel ID, or stream key) will match the format your protocol expects.
Yes. Inbound Feeds can be created and configured on your camera or encoder ahead of time, so the connection is ready the moment your session begins — you don’t need to wait until the room is live. The Streaming tab is available directly from your Homepage, so you can set everything up in advance and walk into your session stream-ready.
Yes. Multiple Inbound Feeds can exist in a room at the same time, each with its own card in the Feeds list and its own Channel ID. This is useful if you’re bringing in several external cameras or sources into one room.
The Inbound Feed card remains in the Streaming tab, but the corresponding media tile will lose signal until the external source reconnects and resumes pushing its stream.
Only hosts and co-hosts can see and manage the Streaming tab, including creating, configuring, and deleting Inbound Feeds. Participants don’t have access to this tab, whether on the homepage or in an active room.