-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reservation is not revoked when conference ends #39
Comments
Hi ! Thanks for the report ! Not sure when we'll have the time to fix the issue, but PR fixing it would be welcome ! |
Actually it should be called from here as well: |
Are you sure? Because the |
I've been digging through the code, but I see that the reservation system does a |
Nice catch ! Thanks for looking into this. I was planning to get rid of FocusAllocationListener in favour of "focus created" and "focus destroyed" events: |
i am also running into this issue. |
Hi, I had an ambiguity about expected behavior of reservation system: Any further works on this problem is appreciated :) |
Hi, I'm having the same behaviour, it is unexpected to be able to join a deleted conference. I'm expecting the DELETE request to "delete" the conference. Any attempt to access it again should IMO result in another post request. |
I'm not looking on any of those issues and have no plans to do so in the near future. If you have a problem the fastest way would be to submit a patch. |
@NeoN0x I'm planning to look into this in the near future: jitsi/jitsi-meet#8386 |
Reservations are moved to a prosody module |
The reservation system REST API documentation mentions the following about conference (reservation) deletion: "Jicofo deletes conferences in the reservation system in two cases. First when all users leave XMPP Multi User Chat room. Second when conference duration limit is exceeded."
I am only experiencing the latter. With the duration set to 10 minutes, the conference is never deleted before the 10 minutes expire, even if everyone leaves within the minute.
(I see no call to
deleteConference
except from within theConferenceExpireTask
.)The text was updated successfully, but these errors were encountered: