Lyamc
commented
4 years ago I'd just like to confirm that I have this exact same issue:
Android --> iOS call
Failed to set remote offer sdp: Failed to set remote video description send parameters.
iOS --> Android call the iPhone shows that it's trying to ring the other person, but as soon as the other person answers, it ends the call saying the other person didn't pick up
ckatterl
There are plenty of issues related to how bad riot-ios is when it comes to audio/video calls. Nothing has changed with regards to this - riot-ios is the worst app one could possible use for such a thing.
This issue is about something else -- riot-ios being so crippled, that its mere existence on the network causes disturbance for other, better-written clients.
As documented in another issue (https://github.com/vector-im/riot-android/issues/3246), I'm trying to initiate a call from a riot-android user's device to myself. I can theoretically answer the call from riot-ios (haha, you wish!) and riot-web.
As soon as riot-ios gets a push notification about the call, it would do something silly and trip up the whole call, disconnecting it with a "the user failed to pick up" error.
That call is perfectly answerable from riot-web each and every time.. But only as long as the riot-ios device is taken off the network (put into Airplane mode). Killing the app does not work, because it seems like the push notification triggers it anyway.
Turning off the Integrated calls checkbox in riot-ios does not seem to help, but it does at least show some error when you open the riot-ios app:
Perhaps that's helpful for figuring out what's wrong and why these 2 devices cannot talk to one another. Fixing this would be nice but.. the real and more disturbing issue is that riot-ios does something which aborts the whole call.. with no way to tell it not to do it. That's not playing nice at all..