Hi guys,
I am building a Zoom calling app that feeds real time transcripts back to the app during a call, I am using Attendee in my stack but the streams coming out of attendee are all being labeled as ‘unknown’. But I think that since RTMS can define the account that triggers the app - and know 100% that it’s the host, then surely this makes it simple to therefore identify the other party as the guest? I’m not sure if Attendee is feeding the right RTMS signals to my app or if it’s just putting out a mixed signal? Their documentation is a little incomplete. Any help is appreciated, thanks!
Hi @BrianCassingena this is Noah from Attendee. You may want to talk about this in our Slack first to see if it’s an Attendee issue or a Zoom issue.
And apologies for the incomplete documentation, our RTMS implementation is still in an early state. We try to make up for it by being super-responsive on our Slack.
Can you clarify where you are seeing ‘Unknown’? I took a look in our logs and I’m seeing various speaker names come through for your RTMS session. May be best to reply on the Attendee Slack since this is an Attendee-specific discussion.
The official RTMS docs say the service sends individual participant audio streams and diarized transcripts, so a direct RTMS integration should not need to guess “host vs guest” from session ownership alone.
If you’re looking to use Zoom RTMS out-of-the-box, we’re a Zoom RTMS Preferred Partner. We’ve helped thousands of developers integrate with Zoom and can help you with your RTMS integration too!
Thanks, we actually solved this problem already but Recall is already on our radar as a possibility.
1 Like