"user_name" occasionally missing from final RTMS transcript segment

Issue: The final Media connection Transcript JSON (“msg_type”:17) is occasionally missing the “user_name” element.

Example: See From JSON Transcript Log, below. We log every message and every webhook event. The last two messages demonstrate the issue, and the Server Log demonstrates the timing. I can make it happen a good percentage of the time by sending continuous voice input (talk radio) into my microphone, as I end the meeting or (assign and) Leave as the Host.

This isn’t a show stopper, but it seems odd, given that the “user_id” element persists
This only / alway occurs shortly before receiving the meeting.rtms_stopped event.

Background:
We are using webhooks to receive meeting and RTMS events.
We manually start RTMS after receiving meeting.started (via API and an StoS app).
We make signal and media websocket connections after receiving meeting.rtms_started.
We noticed occasional JSON parse errors, near the end of the RTMS feed and added pre-parse validation.
We subsequently verified the reason: the JSON (“msg_type”:17) is missing the “user_name” element.
I am testing on our sub-account

From JSON Transcript Log**:
9/4/2026 2:33:48 PM {“content”:{“attribute”:1,“data”:“It has caused us emotional damage, especially on my dad.”,“end_time”:1788557627436,“language”:9,“start_time”:1788557622696,“timestamp”:1788557628419608,“user_id”:16794624,“user_name”:“Bill Clark”},“msg_type”:17}
9/4/2026 2:33:51 PM {“content”:{“attribute”:1,“data”:“DHS did not.”,“end_time”:1788557628566,“language”:9,“start_time”:1788557627436,“timestamp”:1788557631222550,“user_id”:16794624},“msg_type”:17}

From Server Log**:
9/4/2026 2:31:06 PM Media handshake successful, sending CLIENT_READY_ACK
9/4/2026 2:33:51 PM Missing JSON Element
9/4/2026 2:33:56 PM body: {“event”:“meeting.rtms_stopped”,“payload”:{“meeting_uuid”:“ZBgvi9dKRhuuOTgBqiG9yQ==”,“rtms_stream_id”:“38aae162154442a387fc7129b53921b1”,“stop_reason”:6},“event_ts”:1788557636589}

** Times shown are PDT

I have previously posted as bclark@courtroomconnect.com.

Bill Clark