hum, looking at the code don’t show any special handling of 403 http eror code, so I think that you should first check if a Gtihub issue exists, and if not, create one. Well, if there is one already, post the obligatory ‘me too!’ in a comment
// Other error
logger.error("API error: " + result);
if you return a 403 I don’t see a clear way that the code could go elsewhere.
I’m not a Jitsi contributor, not even a Java dev, so I’ll not go further. I think that’s probably a question worth the time of this code’s author - still part of Jitsi if I"m not mistaken-, if only to clarify the doc in the case that really it’s user error
When you try to create a meeting, a call is made to your reservation API url/conference.
As mentioned in the above document - “When the first user joins MUC room(Jitsi-meet URL is opened) HTTP POST request is sent to '/conference' endpoint with the following parameters included…”
The above document gives you details on what your reservation API should return to successfully create a meeting. Your reservation API can determine if user is allowed to create a meeting and return appropriate Http status codes.
In terms of configuration, you just need to provide the URL.
Do you have an endpoint http://localhost:3001/conference?
When you first try to create the meeting, http://localhost:3001/conference is called. The document I mentioned earlier will give you the details about how the /conference endpoint is called and what return json it expects.
One thing missing from the reservation API document that is posted is the fact that “reservation system” is not something that is built already or otherwise provided by Jitsi Meet. You have to develop it yourself and using the referenced API specifications, ensure your system is (1) able to understand the data sent from Jicofo and (2) responds with data that Jicofo is expected.
If you already knew this then I am stating the obvious. If you are new to Jitsi Meet or where confused, now you know.