That is on our roadmap, but Conversations will support our way of initiating a call as well.

The next build of SiskinIM in TestFlight (and next beta build of BeagleIM) may support that

I think Conversations just did support Siskin way of initiating the call. so to have a call between Siskin and conversations you need that siskin initiates the call for now and not the other way around.

Do you have any news regarding this subject please ?

That is solved in beta builds and will be fixed in the next version

Has this been fixed? I am still having issues, calls from Siskin to Conversations work but not the other way around.

I am using Conversations from F-Droid which seems to be a few releases behind the Play store version. Perhaps this is the reason?

Nope, the reason is that Apple kills the app.

AFAIK, the hope is that the Tigase team ( ahem @hantu85 @woj-tek any day now, right?) standardize the XEPs used in their push server (or whatever) to actually send pushes for calls too, so that a push wakes up the app and the app can see the actual call.

ref: https://xeps.tigase.net/

@licaon-kter Do you happen to know of any iOS app that supports this right now?

@yannjor Siskin with accounts on sure.im or tigase.im or jabber.today or xmpp.cloud :)

Hello! It looks like this is closed, but perhaps still unresolved?

I'm experimenting with Siskin IM on iOS, Conversations on Android, and Dino on Linux, using a self-hosted ejabberd server, and I can originate calls from Siskin, and they work fine, but I cannot originate calls on Android/Linux to Siskin.

Based on this thread, am I right in thinking that this isn't something I can readily solve?

It depends on the server which you are using to host your account. AFAIR, push notifications for calls should work with Tigase XMPP Server and Prosody.

Thanks! It's a self-hosted ejabberd server (sadly, for this).

I appreciate your (instant!) response.