Realtime Media Streams (RTMS) uses events and messages to establish connections, manage state, and deliver media data. Events are organized into three categories based on their scope and applicability.
Event categories
RTMS events fall into three categories. Understanding which categories apply to your implementation helps you integrate the correct event handlers.
| Category | Applies to | Description |
|---|---|---|
| Universal events | Meetings, Webinars, Video SDK, Contact Center | Protocol handshakes, keep-alive operations, session and stream state management, and media data delivery. Required for all RTMS implementations. |
| Session events | Meetings, Webinars, Video SDK | Real-time updates about session activity including participants, active speaker, screen sharing, video state, and in-meeting chat groups. |
| Contact Center events | Contact Center | Voice call lifecycle, transfers, conferences, supervisor monitoring, IVR streaming, and queue operations. |
Which events do I need?
Your RTMS implementation requires different event categories depending on your product.
For Meetings, Webinars, or Video SDK:
- Universal events (required for connection and media)
- Session events (for participant and session activity)
For Contact Center:
- Universal events (required for connection and media)
- Contact Center events (for call lifecycle and operations)
Getting started
To begin working with RTMS events:
- Review Universal events to understand the connection handshake and media delivery protocol.
- Check the product-specific event reference for your implementation (Session events or Contact Center events).
- Refer to Data type definitions for detailed field value specifications.