Recording bot (unnamed participant) in call when using CallComposite
We are using the CallComposite component to join to an already existing teams meeting created through the Graph API. Auto recording is enabled when creating the meeting.
When the user joins the call an "Unnamed Participant" is already in the meeting, and remains there. This turned out to be the bot responsible for starting the recording, so if the user joins the meeting quickly before the recording starts, the bot does not show up. Sometimes the bot disappears randomly as well, but sometimes it remains for the whole duration of the call. (Also, it is not visible when you join the same meeting from the Teams Browser or desktop client)
The expected behaviour is ofcourse for this bot not to show up as a participant in the call.
-
@azure/communication-reactnpm package version: 1.17.0 -
OS: Windows 10 on PC
-
Browser: Google Chrome
-
Browser Version: 126.0.6478.62
Hi I'm looking into the issue, thanks for bring it up!
Do you mind sharing the call id related to this issue?
@carocao-msft
Sure, I can provide you with a call id where I have confirmed that such a participant was present: afdb7782-6894-4f98-bb11-515cfe8a7cc4
This is a call from today.
@Likvid2 thank you for the callId, we are digging into the issue now as this bot should be being filtered, but we see an issue service-side where the bot is not being flagged as hidden. You mentioned that a Teams client joining the call didn't see the bot in the set of participants. To help us narrow down where the issue lies, could you reproduce the scenario where in the same call, the ACS client is seeing the bot but a Teams client is not seeing the bot - and send us the callId
@carocao-msft @JamesBurnside Sure. I have done as you asked, and recreated the screnario.
Here is the relevant call ID: 1d081d7e-630c-4491-8e5e-5f9bf6c1494e
@JamesBurnside, many thx for investigating on this issue. I have some diagnostics which (may or may not) inconsistent your result of "but we see an issue service-side where the bot is not being flagged as hidden."
Having the call, and the CallComposite showing the recording bot. (which is the issue itself) When I connect to very same ongoing call with the very same user which is using the CallComposite in this call, using the Teams Desktop, then Teams Desktop warns me that I am in this call already, what do I want a) take over or b) view silently, I choose b), then Teams Desktop do not show the recording bot, which is shown by CallComposite the same time.
Maybe the bot has some metainfo/attribute what Teams Desktop honors, but CallComposite disregards.
The OP also wrote about the timing, if the user who using the CallComposite joins within 1-2 second (before the bot?) then the bot will not be shown during the call, however if the user who using the CallComposite joins with 10 seconds later (when the bot already in the call) then the bot is shown.
There is a slight chance that the CallComposite (or the adapter?) implementation logic of filtering out of flagged participants is not exactly the same a) in the initial already existing participant list when joining and b) the event handling when new participant (the bot) is added to the participants.
Quick update here: We are actively looking into this issue. We have implemented a possible fix that will be available in the next beta/stable version. Once it is available, we will let you know asap.
@Likvid2 unfortunately we weren't able to reproduce the issue. However, an extra check was added to @azure/communication-calling to try detect isHidden bots.
Could you try @azure/[email protected] and accompanying @azure/communication-calling@^1.26.1 and see if the issue still reproduces?
@JamesBurnside Thanks for the update, however we have in the meanwhile changed our application in a way that the user is added to the call immediately, and as I mentioned in the beginning in such cases the bot wont show up anyways, so I can't confirm wether or not the new version has fixed the issue.
Thank you for looking into it either way.
Thanks Likvid2, I will close this issue but please open a new issue if you see the same/similar issues