Live Events on the Wowza Server You Already Run

What you can do together

• Run a town hall as a scheduled event on Nexus, streamed through your Wowza server: registered viewers get an email reminder, watch in the portal or in a player embedded on your site, and rewind within the DVR window if they join late.
• Take moderated chat and questions during the session, with questions on their own channel and exported afterwards.
• Record on Wowza and have the capture land in the library as on-demand content, with a transcript aligned to the timeline, captions generated from it, and chapters at topic boundaries.
• Keep the library on Wowza as the portal's storage provider, so recordings and uploads sit on infrastructure you already operate.
• Ask AI Intelligence Hub what was said about a subject across a year of town halls and get an answer citing the moment.

How it connects

An administrator sets Wowza as the portal's streaming server provider, choosing Wowza on premises or Wowza cloud, and the portal talks to it over Wowza's REST API. Each live event gets a publishing point created on Wowza. The encoder sends RTMP to that point, Wowza ingests and delivers the stream, and viewers play it over HLS in the portal's own player. A persistent publishing point keeps the same destination across a recurring series, so the encoder configuration stands.

Recording starts and stops from the publishing point. Where Wowza records server-side, the capture is uploaded into the library as on-demand content under the portal's access control and retention. Separately, Wowza can be the portal's storage provider, set in the control panel, so the library itself is kept on Wowza rather than Azure, AWS or local storage.

Nothing about Wowza's own setup changes. Its applications, transcoder settings and administration stay with your Wowza administrator. The portal creates points and drives recording, and that is all it writes.