Extensions: Broadcast, Telephony, AI, Reference App

At this stage, you can extend your current app in the direction that matches your next implementation goal.

If you are deciding where to invest first, compare Broadcast overview with SIP interconnect.

Broadcast direction

Use broadcast when the goal is wider audience delivery, not symmetric room interaction.

For this starter path, choose the broadcast model that matches how your viewers will watch and how your team will operate it.

Telephony/SIP direction

Use SIP and telephony integration when your workflow must bridge browser sessions with phone or SIP endpoints.

This is optional for this tutorial, but useful when your workflow needs phone or SIP endpoints.

AI-enhanced experiences

  • Media Processor: Discover how to capture and modify video streams.
  • Audio Connector: Learn how to access and modify raw audio from live Vonage video sessions.
  • Blog Posts: See example tutorials on how live Vonage video sessions can be improved using AI.

Production-grade reference implementation

  • You need to validate that the Vonage Video API covers your meeting scenarios (lobbies, chat, reactions, screen sharing, recordings) before investing in a full build.
  • Your team wants to benchmark performance, CI coverage, or architecture decisions against Vonage’s recommended approach.
  • You are preparing a proof of concept or customer pilot and want a customizable baseline that already matches accessibility and quality gates.

For future reference

If you want to see how similar building blocks are applied in real product scenarios, these use-case paths are a strong next stop:

Wrap-up

Great work finishing the Multiparty Video with Archiving learning path!

You now have a working first version that covers multiparty sessions, frontend/backend integration, and recording flow.

If you want to continue with deeper topics (debugging, signaling, optimization, layouts), continue with Advanced Video Core API Features.