Audio and video calling issue

I try to call, user at the other end accept it n then the call ends automatically n im recieving this error in log
: [features/base/lib-jitsi-meet] Failed to load config from Error(Error){“message”:“timeout”}

Hi @rizwann,

Can you share the SDK version you are using…?


Also message for audrio call is not returning metaData
This is the error: Attempt to invoke virtual method ‘boolean org.json.JSONObject.has(java.lang.String)’ on a null object reference
if (baseMessages.size() != 0) {
BaseMessage baseMessage = baseMessages.get(baseMessages.size() - 1);
try {
if (baseMessages.get(baseMessages.size() - 1).getMetadata().has(“bookingId”)) {
// bookingID = baseMessages.get(baseMessages.size() - 1).getMetadata().getInt(“bookingId”);
bookingID = baseMessages.get(baseMessages.size() - 1).getMetadata().getInt(“bookingId”);
} catch (JSONException e) {

@darshan.bhanushali any update regarding these issues?

Hello @rizwann,

This issue has been fixed in our latest API release deployed on 17th May. If you create a new Call and the pass the metadata to the same, you should be able to retrieve the metadata for the same Call.
Unfortunately, the call sessions created prior to the release will still continue to return stale data as the entries have already been added to the database.

Hope this helps. Please let us know if you are still facing the same issue with the newly created Call session and we will be happy to help you out with the same
Appreciate your patience

[features/base/lib-jitsi-meet] Failed to load config from Error(Error){“message”:“timeout”}

Anything about this issue?
When i call n other user picks the call and then it ends automatically

Hello @rizwann

Can you please let me know if this issue is being faced every time or is it random as we are not able to replicate this at our end.


Im facing this everytime im trying to call
PS. Everything was running smooth without metaData but im facing all these issue with metaData

Any update?? Please we’re running out of time

Hello @rizwann
We were able to generate the issue at our end. However, the issue seems to be very random and was not generated every single time we tested. We have gone ahead and added a couple of failsafes for the Calling mechanism at our end. Also, we have added a retry logic if the timeout issue is encountered.
Now the SDK will try to connect to the call 3 times, if it encounters the timeout error.
We should be able to release a version of the Android SDK latest by tomorrow end of the day. We have created a Github issue on your behalf for the same. Please watch the below issue on Github so that you can come to know about the status and events regarding when the issue will be fixed and a new version of the SDK with the fix is released.

Github issue:

We will go ahead and mark this post as solved as all the further communication can happen on the Github issue


1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.