Guest user can't post message in room using Webex Browser SDK

[vojtech.koukal]

Hello,

I'm using the Browser SDK to create a doctor-patient scenario, where patient is not part of the Webex organization and I need to have chats in Room (I need to record the chat/attachments/video/audio/screenshare).
I have created a Service App to issue guest tokens for users without Webex.
The service works fine, the Access tokens are issued without any issues.

I created room within our organization and added the guest user to it.
Joining the meetings scheduled in the room works fine for the guest user.

But I have issues with sending and receiving messages using the guest user in this room.
I can see the guest user added to the space.

But when I try to listen to new messages using the Browser SDK I don't receive any messages I post (from my personal account) in the room - the websocket connection is fine and ping-acks messages are flowing.
When I try to post a message to the room using the guest user I get error:

WEBEX_TRACKING_ID: webex-js-sdk_1c4638f6-63a2-4ea2-8a0b-85acc4ed1f63_18

If I try to run the same code using my personal Access Token instead of the guest's Access Token, then everything works absolutely fine and message is posted and I can receive updates via websocket.
So I'm guessing it is some issue with permissions.

Is there anything that needs to be done for guest to post/read messages in Rooms within the organization?

Thank you

[vojtech.koukal · Accepted solution]

Just and update if anyone hits the same issue.

When adding a guest user to existing Webex Room, use personId instead of personEmail in the SDK call.
So the SDK code will look like this:

webex.memberships.create({  
   personId: <id from the /v1/guests/token call when creating guest>,  
   roomId: <room ID>  
})

With this, everything works fine.

[Janos Benyovszki]

@vojtech.koukal would you mind opening a support ticket for this devsupport@webex.com ? We will need to reproduce the same, so please include detailed steps about how you are reproducing the problem with the JS SDK in the ticket you open. thanks