# RTMS April release

<!-- WARNING: THIS FILE WAS AUTOGENERATED! DO NOT EDIT! -->

The RTMS April release introduces a variety of improvements and new functionality.

## Webhook events

-   New `account_id`, `is_original_host`, `meeting_id`, and `webinar_id` fields in the following **Notifications** webhook events:
    -   `meeting.rtms_started`
    -   `webinar.rtms_started`
-   New `account_id` field in the following **Notifications** webhook event:
    -   `session.rtms_started`

## Signaling handshake request

-   New `buffer_data` boolean parameter added to the signaling handshake request.
    -   When a `meeting.rtms_started`, `webinar.rtms_started`, `contact_center.voice_rtms_started`, or `session.rtms_started` webhook event is received, the RTMS server starts buffering audio packets, and the timestamps start to increment, while the signaling connection is made.
    -   The RTMS server buffers audio up to 60 seconds while the signaling and media connections are established. Once the connections are established, the buffered audio packets are delivered if `buffered_data` is set to `true`.
    -   The `buffer_data` is set to `true` by default. When `buffer_data` is set to `false` the buffered audio data is dropped.

## Media data events

-   New `length` parameter in the following **RTMS** messages that denotes the length of the data:
    -   `Audio data`
    -   `Video data`
    -   `Screen share data`

## Data types

-   New `CONFERENCE_PARTICIPANT_LEFT` event type in the following **RTMS** data type:
    -   `RTMS_ZCC_VOICE_EVENT_TYPE`