Vijay Amin
Vijay Amin
No, I am on the high speed internet. And testing through different system.
And this problem happen in the prod build, so, could not able to generate the log even.
Hello @jing-chen1 this is the correct meeting ID: f9673e6-34f2-463b-9b79-e95703080706 for above meeting Please check.
Hello @jing-chen1 { "ClientRequestToken": "845e2097-62e3-4080-bf71-1df23e8bfe57", "MediaRegion": "us-east-1", "NotificationsConfiguration": { "SqsQueueArn": "arn:aws:sqs:us-east-1:XXXXXXXXXXX:roomzzconnect-MeetingNotificationsQueue-1JM1A8SN2MQ18" }, "MeetingHostId": "6133fe57-0ac7-4ec7-89ed-12278390880a#Gene" } Please find the response of the create meeting API, Let me know if it's helpful...
Meeting ID1: dd7a9b1d-02e5-4825-808d-b80eb5d70706 Meeting ID2: 1d57c785-fbaa-498d-8a56-617a9ae80706 Thanks
Hello Support Team, Can you please check the log for this meeting id: ee6dcbf3-f935-4ee9-8bb9-604fff980706 The Problem with this meeting id is, even I stop the screen share, it keep changing...
Hello Support Team, Can you please debug the log for the following meeting ids: 1) 3e803317-7d26-4ce1-8b69-3ca770dc0706 2) d4f8a74c-2ae9-4c84-9129-84c4e7630706 It just not allowing the start screen share until I restart the...
Hello Support Team, Can you please revert on this?