# RTMS June release

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

## Rest API

Apps can start RTMS for a participant when both of the following are true:

-   The participant is an invitee to the meeting. An invitee is a participant who was added to the meeting's invite list, not a participant who joined with a shared meeting link.
-   The participant has already joined the meeting.

To do this, send API requests to [Update participant Realtime Media Streams (RTMS) app status](/docs/api/meetings/#tag/meetings/patch/live_meetings/{meetingId}/rtms_app/status) using a valid Zoom access token.

## Chat Message Media Data

-   RTMS now supports chat message media data for meetings and webinars. Subscribe to 5 new `RTMS_EVENT_TYPE` events (10–14) to receive chat group updates:
    -   `CHAT_GROUP_CREATE` (10) – a new private chat group has been created in the meeting
    -   `CHAT_GROUP_DELETE` (11) – one or more private chat groups have been deleted
    -   `CHAT_GROUP_MEMBERS_ADD` (12) – one or more members are added to a private chat group
    -   `CHAT_GROUP_MEMBERS_DELETE` (13) – one or more members are removed from a private chat group
    -   `CHAT_GROUP_MEMBER_STATUS_UPDATE` (14) – the in-meeting status of a private chat group member changed

## Protocol Definition updates

The following enums have been updated or added. For more information, see [Data type definitions](/docs/rtms/data-types/).

-   **Updated enums:**
    -   `RTMS_EVENT_TYPE`:
        -   `CHAT_GROUP_CREATE` (10) – A new private chat group has been created in the meeting
        -   `CHAT_GROUP_DELETE` (11) – One or more private chat groups have been deleted
        -   `CHAT_GROUP_MEMBERS_ADD` (12) – One or more members are added to a private chat group
        -   `CHAT_GROUP_MEMBERS_DELETE` (13) – One or more members are removed from a private chat group
        -   `CHAT_GROUP_MEMBER_STATUS_UPDATE` (14) – The in-meeting status of a private chat group member changed
    -   `RTMS_STATUS_CODE`:
        -   `STATUS_INVALID_MEDIA_TRANSCRIPT_TARGET_LANGUAGE` (46) – Invalid media transcript target language
        -   `STATUS_CHAT_SESSION_KEY_NOT_AVAILABLE` (47) – Chat session key not available
-   **New enums:**
    -   `RTMS_CHAT_GROUP_TYPE`
    -   `RTMS_CHAT_GROUP_MEMBER_STATUS`
    -   `RTMS_CHAT_OPERATION_TYPE`
    -   `RTMS_CHAT_SESSION_TYPE`

## PSTN User Identification

-   Each PSTN user ID is now transmitted independently, enabling accurate identification of all speaking participants when multiple PSTN clients join a meeting simultaneously.