This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 38%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
Hi Azure,
I've implemented a calling to teams users based upon the samples, using CallComposite and the TeamsCallAdapter.
When I turn on captions from CallComposite, captions appear but the user name says "Unnamed Participant".
Based upon samples for teamsadapteroptions, using
onFetchProfile
to set the display name for participants, is there a similar hook/API/callback to set the caption name? "Unnamed Participant" doesn't match the people in the call.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 59%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
@Martin Rojo Thanks for asking question! This is expected behavior as in this scenario, we don't get the display name from the calling sdk.
And currently we do not have a similar hook to set the captions name.
However there is a way to solve this and it's in public preview https://azure.github.io/communication-ui-library/?path=/docs/communicationasteamsuser--page
Hope this helps.
Please let us know if you are already following this and still facing issue, happy to assist you further.
I'm already using onFetchProfile, that sets the user name in the people list , not in the captions.
@Martin Rojo Thanks for reply! Having internal discussion with PG, will update you soon.
@Florencio Martin Rojo Update- Created Product Bug here https://github.com/MicrosoftDocs/azure-docs/issues/123090 and team responded-
They have created a fix and it will be included in our next beta release. Please stay tuned!