Skip to main content

2 posts tagged with "forward"

View All Tags

Working with WHIP and Stream Forwarding

· 13 min read
Stefan Benicke
Senior Developer @ Eyeson

If you're building intelligent audio/video solutions - think real-time transcription, vision analytics, or smart moderation - you'll want an efficient way to get your audio/video streams for AI processing. Our platform makes this simple using WHIP (WebRTC-HTTP Ingestion Protocol), designed for low-latency media processing.

What Is WHIP?

WHIP is a straightforward signaling protocol that uses standard HTTP methods (like POST and DELETE) to establish and manage a WebRTC media session between a client and a media server.

By standardizing the signaling process, WHIP simplifies media ingestion—making it easier to integrate into workflows where audio or video streams are forwarded for processing, such as AI pipelines.

Benefits for AI Streaming

  • Low latency: WHIP leverages WebRTC for real-time media transport, ensuring minimal delay.
  • Scalability: Efficient HTTP-based signaling makes it easy to manage thousands of sessions.
  • Compatibility: WebRTC peer connections integrate seamlessly with AI pipelines like GStreamer, FFmpeg, or custom ML models.

Introducing API Stream Forward

· 4 min read
Stefan Benicke
Senior Developer @ Eyeson

The Eyeson API provides a powerful way to forward the stream of any meeting client in real-time and at its original quality to your desired destination for further processing.

This feature forms the backbone of the Eyeson AI Adatpter.

tl;dr
  • Your API key is required
  • You can forward a single stream from any client (source), the entire meeting stream (MCU), or a public video file (playback)
  • A WHIP-compatible destination endpoint is expected
  • You can forward audio only, video only, or both
  • The same stream can be forwarded multiple times to different destinations

For full API documentation, visit https://docs.eyeson.com/docs/rest/references/forward.