Add REST API support for starting RTMS for meeting participants, add chat message media data support with 5 new event types for meetings and webinars, updates to protocol definitions including new and updated enums, improve PSTN user identification for simultaneous participants.

RTMS June release


## 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.

## 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_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

## 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.
