@Pro100Andrey , regarding "Accept Call". As I mentioned Android to Android calls work perfectly, also Android to iOS. So I use accept call and it works, video call is completely established.
So the issue take place only if the call is initiated from iOS either to iOS or Android.
From Android I see the "Accept Call" action is sent.
Extracted logs for full call attempt session from iOS to Android could be found here: https://gist.github.com/devsherif/a460dcd6dd21939b409a7cfb14f5c95c
This session also call is initiated by the iOS device, Android started ringing, Accept call action is sent from Android to iOS, iOS received call acceptance as method "acceptedByUser" is called, then it keeps in "Connecting" state and method "connectedToUser" is never called.
I did the same test again, and found in my logs that Session ID is the same on Android and iOS.
One note: Do you think if session ID is different, the iphone will start the call and android receive it then iOS call status changes to be "Connecting" !!! I believe the session ID is the same on both android and iOS.
Anyways, I attached the new logs. In which the same behaviour took place, iOS initiated the call, Android received then accepted it, iOS "Session acceptedByUser" delegate method is called, then nothing more happened, call dropped.
Hi @Pro100Andrey , @VitaliyGuru ,
Sorry for my late reply.
Using the samples, the issue is not reproducible.
But even after following the samples, I still couldn't find the issue in my code. I didn't have much time to investigate my code yet, but will do soon and let you know what I will find.
Finally I was able to find the root cause of the issue and fix it. Let me explain it as It may need an update in QuickBlox code.
Briefly, the issue happened because I create a new Session in ViewController then pass it to another ViewController.
So, noting that both ViewControllers are QBRTCClientDelegate, it seems very miss-leading to get most of overridden method being called normally except for "StartedConnectingToUser".
Once I moved "createNewSessionWithOpponents" call to the second ViewController, everything worked perfectly.
Thanks for your support. And I hope that I have explained the issue properly and clearly.