AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Jitsi call pause number1/1/2024 ![]() ![]() Now, I want to invite in this call a new external user (not from chat). A call is initialized, and chat members jump in. Assume the following: We have a channel with chat participants. JWT is not solving the issue in this scenario. To protect Jitsi from guest you need to implement Secure Domain with JWT authentication, also you can select plain call name and rename chat - call name will be different and guest will not know it. So, if your call logic would be implemented, will be much worth. But with my experience, there is a tons of Jitsi integration issue like "Call already ended", where users need to start call by them self, issues where button don't appears in chat on call start. Now if you think about it, you could make this agent configurable on more aspects, in order to administer the call. When the call has ended, the "call" button back in RC generates a new link, like step 1.Ī flow like that maybe addresses some privacy issues, some functionality issues and the recurring bug "this call has ended". If in the meanwhile a user joins, timer resets again until agent is left alone. If after this configurable window (30 seconds) RC is still the only user in the call, exits and then marks the call as "ended". RC bot stays in the call, and when it is the only user in the call, waits for a configurable time period (e.g. How to know if a call has ended? RC itself joins with an agent account all new calls (a bot, by simply following the relevant link generated in 1, and applied in 2). So when users click, they join the last running call if it is still on, or create a new call link is generated (see 1), if the call has ended. a room.Ĭall button always follows last call link in chat, generated in step 1. This way, if you add a guest ONCE in a call (share the link manually with someone), he doesn't have a permanent link for all the future calls initiated from the specific chat, e.g. Unique link could be in the form of "RC deployment ID + room id + random new token for each call", hashed. So I do not understand the difficulty of sharing a link among people that are in a common chat tbh. Like it is already done: When there is a call, the link is right there, in the chat and people click and open it. When a new call is generated, the link is posted as a message in the chat so that everyone in the chat has it. How user will get same Jitsi call if every single user will get different Jitsi room name? In that case there will be set of different rooms (calls, conferences) with only one participant. ![]()
0 Comments
Read More
Leave a Reply. |