ACS callEndReason CallSetupError code 403 subCode 5829

Alexandre Gurgel 60 Reputation points
2024-04-10T23:44:00.6233333+00:00

I'm developing a React application that connects users to a Room.

I'm using Azure Function to create the userCredential and the room, and then sending this to the frontend.

After that, I attempt to make a clientAgent.join({roomId}, options).

No errors appear, and it seems successful. However, I can't see other participants' streams or even the participant list, which remains empty.

Do I need to make a clientAgent.startCall([]) before everything else, or does clientAgent.join suffice?

And sometimes I've received this status: ACS callEndReason CallSetupError code 403 subCode 5829.

Azure Communication Services
Azure Communication Services
An Azure communication platform for deploying applications across devices and platforms.
684 questions
0 comments No comments
{count} votes

Accepted answer
  1. Grmacjon-MSFT 16,101 Reputation points
    2024-04-16T21:10:42.18+00:00

    Hi @Alexandre Gurgel we are sorry you are facing this error. which ACS SDK are you using?

    Here is how to troubleshoot the first part of the error:

    • Make sure you're calling clientAgent.startCall([]) after a successful clientAgent.join call. The join operation establishes the connection, while startCall activates the media aspects of the call.
    • Subscribe to the appropriate events from the callAgent object to update your React application's state with participant information and stream data. Check the Azure Communication Services documentation for events like: on('participantsUpdated'): Informs about changes in the participant list. on('videoStreamAdded'): Notifies about a new video stream being added.
    • This error ( ACS callEndReason CallSetupError code 403 subCode 5829) indicates a permission issue for the user attempting to join the room. Here's how to fix it: Double-check that the user credential (access token) generated by your Azure Function has the necessary permissions, specifically the "joinRoom" scope. If your room has access restrictions (e.g., requiring specific identities), confirm that the user's access token represents an authorized identity. Make sure your Azure Function has the required permissions to create rooms and generate access tokens with appropriate scopes.

    Hope that helps. Let us know if you have further questions.

    Best,

    Grace


0 additional answers

Sort by: Most helpful