ACS Sample does not work. Joining teams chat 403 forbidden

ChoiMoonsun 1

I get this error...
I just tried the sample code from here:
https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/chat/meeting-interop?pivots=platform-web

I was able to receive the messages, but cant not send a message.
I already did submit the form (Teams interoperability) and checked it works.

Is there anything I should change on the ACS setting?

Please help.

Grmacjon-MSFT 16,011 Reputation points

2021-05-26T04:55:01.353+00:00

Hi @ChoiMoonsun

Thanks for bringing this to our attention. We apologize for the frustration this issue may have caused. We will bring this up with ACS team and update this thread when we hear back from them.

Thanks,

-Grace

3 answers

Michał Kluz 11 Reputation points

2022-05-02T10:56:02.27+00:00

Hello, I have the same exact problem. I'm using the quickstart code, I successfully join the thread and I'm able to receive messages written in Teams application, but whenever I try to send a message from custom code, I receive 403 Forbidden error. Is there any update on this issue? Is there anything I can do to fix it?
Please sign in to rate this answer.
Tom Kaupe - MSFT 6 Reputation points Microsoft Employee

2022-05-04T18:30:20.053+00:00

Hi @Michał Kluz -- can you give a little more detail about what you are attempting to do? Are you using ACS to join a Teams meeting and chat during the meeting? Or are you trying ad hoc chat outside the context of a Teams meeting? The later capability is currently only available in limited preview.

Michał Kluz 11 Reputation points

2022-05-24T08:24:20.97+00:00

Sure @Tom Kaupe - MSFT . I have a custom React web application using ACS to connect with a Teams Meeting. We successfully connect video, audio and screen share streams with the Teams meeting (we're able to talk and see camera streams). We'd also like to be able to chat with Teams users during meeting. I understand that this is possible by joining a main Teams meeting chat thread. Unfortunately it seems to be working only one way - my app is able to receive and display any message written in a Teams meeting chat, but I'm not able to send any message to a Teams meeting chat because whenever I try, I get 403 Forbidden error mentioned in the post. We're not interested in using the chat outside of the meeting - we're creating a live-only application.

Tom Kaupe - MSFT 6 Reputation points Microsoft Employee

2022-05-25T16:30:34.107+00:00

@Michał Kluz are you including the "chat" scope when requesting the ACS access token?

await identityClient.getToken(acsCaller, ["voip", "chat"]);

Michał Kluz 11 Reputation points

2022-05-26T07:45:59.327+00:00

Yes. I believe I'm able to connect with the chat thread, because messages sent from Teams are being received in my app without problems. Only outgoing messages (sent from my app to Teams) are met with an error.

this is my token creation code on the backend side:
Response<CommunicationUserIdentifierAndToken> response = await this.identityClient.CreateUserAndTokenAsync(scopes: new[] { CommunicationTokenScope.VoIP, CommunicationTokenScope.Chat });

Tom Kaupe - MSFT 6 Reputation points Microsoft Employee

2022-05-26T15:31:42.093+00:00

OK thanks for confirming. What value for the threadId do you use when initializing the chatThreadClient:

chatClient.getChatThreadClient(<threadid>);

It must be the thread ID associated with the meeting, which can be parsed from the meeting URL

Link:
https://teams.microsoft.com/l/meetup-join/**19%3ameeting_NDM5ZmQ5OWYtODQ2ZC00ODVmLWFjNmUtNGUwYTA5MGJmMTFi%40thread.v2**/0?context=%7b%22Tid%22%3a%22c30210de-b98b-4e6b-8eee-074c785e1ebb%22%2c%22Oid%22%3a%22aeb7c0e7-2f6d-43ef-bf33-bfbcb93fdc64%22%7d

ThreadId:
19:meeting_NDM5ZmQ5OWYtODQ2ZC00ODVmLWFjNmUtNGUwYTA5MGJmMTFi@thread.v2

Michał Kluz 11 Reputation points

2022-05-27T08:56:51.78+00:00

The value I'm using for the thread ID is exactly in the format you have specified and it was parsed from the Teams meeting link

ThreadId:
19:meeting_NGEwOTBlZDEtNmY0My00YzYyLThiYmUtMjg3ZWY3OGI0Zjdl@thread.v2

this is my code sending message
const chatThreadClient = chatClient.getChatThreadClient("19:meeting_NGEwOTBlZDEtNmY0My00YzYyLThiYmUtMjg3ZWY3OGI0Zjdl@thread.v2");
const sendMessageRequest = { content: "test" };
const sendMessageOptions = { senderDisplayName: userName };

await chatThreadClient.sendMessage(sendMessageRequest, sendMessageOptions);

Tom Kaupe - MSFT 6 Reputation points Microsoft Employee

2022-05-27T17:58:40.577+00:00

Can you provide the ms-cv and timestamp headers from a 403 response? We can check the logs...

Prathmesh Prabhu 86 Reputation points Microsoft Employee

2022-05-31T18:46:48.043+00:00

I'll note that trying to send a message "too soon" in a teams interop call can fail with 403. The reason is that the Azure Communication Services user is added to the chat thread after they join the Teams call. So, trying to send the message before joining the call / immediately after can fail. This problem should resolve within a few seconds.

This is not usually a problem, because the application only sends a message after the end-user types something.

Looking at the code snippet you posted, it looked as if you were trying to test things out by sending the message programmatically. In that case, it is possible to send the message to soon. So just double checking.

Michał Kluz 11 Reputation points

2022-06-01T08:35:43.717+00:00

You're exactly right @Prathmesh Prabhu , I was trying to send a message in my call initalization code, just to test the chat client, but I was getting an error. Now I moved the code to a point later in time when the call is already initialized and it works! I'm able to send and receive messages from the Teams thread. The issue is solved, thank you!
Sign in to comment
Prathmesh Prabhu 86 Reputation points Microsoft Employee

2022-06-01T21:28:35.257+00:00

[Promoting from a comment to an answer for posterity. This ended up resolving the OP's problem]

I'll note that trying to send a message "too soon" in a teams interop call can fail with 403. The reason is that the Azure Communication Services user is added to the chat thread after they join the Teams call. So, trying to send the message before joining the call / immediately after can fail. This problem should resolve within a few seconds.

This is not usually a problem, because the application only sends a message after the end-user types something.

Looking at the code snippet you posted, it looked as if you were trying to test things out by sending the message programmatically. In that case, it is possible to send the message to soon. So just double checking.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment
MAROUAN AOULAD BEN TAHER 0 Reputation points

2024-01-23T13:55:11.2366667+00:00

موقع منبع المعرفة هو من أفضل مواقع تحميل التطبيقات والالعاب الأندرويد والايفون و ايضا الكمبيوتر . لأنه من الواقع الخالية من الفيروسات والآمنة وهو من البرامج التي يتم من خلالا تحميل كل أنواع الألعاب والتطبيقات و ايضا طرق حصرية للربح من الانترنت
Please sign in to rate this answer.

0 comments No comments
Sign in to comment