I'M Trying to implement a feature with an app include a call inside it. I already implemented the call kit with a lot of socket events and everything is works fine but there's an issue in that:
once the app is locked and get new incoming call, and answer the call, the socket is open and event reach to the other side, but joining the conference is not working till I unlock the device!, have any one any idea about this issue or can help ?
Related
Dear Connectycube Team,
I hope this email finds you well.
Our company has integrated Connectycube into our application, which primarily relies on video calling for communication between users and service providers. To ensure a seamless user experience, it's imperative that the video calling system is robust and reliable.
Unfortunately, our development team is facing challenges in making the system highly robust and 100% reliable. The issue lies in the connection dropping when the application is killed or the phone is locked.
issue: We are trying to integrate connecticube onto cordova app. We are using callkit to implement native incoming screen. The issue is that whenever the app is killed or the phone's screen is locked, accepting the call on callkit leads to failure since the accept call function gets called before the connecticube oncall event listener is called.
I would like to request a call with your technical team to discuss this matter and receive any insights or recommendations that could improve the video calling system.
Thank you for your assistance.
Best regards,
Kanhu
Once we receive incoming call using callkit and the user accepts the call, we try to send the accept call command to connectycube. But since the oncall event is not fired immediately, we create a callback loop to wait for the oncall event to get fired. This works sometimes but fails most of the time. Is there any other way ro achieve the accept call functionalities using callkit and connectycube on cordova.
I have implemented the opentok in my app, and did all necessary implementation which is required. I have been gone through sample code and did exactly same, by calling destination phone, the call reached perfectly, then issues comes.
Sometimes call connected to both device but most of the times not, receiver phone started the call with time counting but it has not been connected with voice chat in either way.
Some times loud speaker become active automatically in receiver phone and also by tapping it has not been disable.
Does anybody went through this situation and resolved it ? A
Any help will be appreciable.
Thanks.
If you're using callkit for voice calls then follow below solution to make your audio session active.
while making call or answering call :
Deactivate audio session.
initiate your audio session again.
answer/make call.
We have an app that calls two parties, and when they accept the call we dial them into the same conference call. One issue we have observed is that sometimes both parties will be connected, but one side isn't able to hear the other side. In these cases I usually verify that two calls were indeed created by Sinch (via the Sinch call logs/callbacks) and that they are using the same conference ID (via our own logs.)
I have seen two different types of problems related to this -
1. The "callDidEstablish" delegate method was hit, but a Sinch call was never actually created according to the Sinch logs.
2. Both calls were created, but there is just no audio.
I am not sure if (2) could potentially be an issue with the AudioSession? Any guidance in helping debug this type of issue would be much appreciated. Again, this doesn't happen every time, but we do see it quite often.
I'm fairly new to app development and am having trouble figuring this out. One part of my app involves a messaging platform. Right now I am using a php web server to connect to MySQL backend. I have all the functionality of a messaging app, but I am unsure how to push new messages when they are available.
One basic solution would be to call my function to check for new messages every x amount of seconds, but obviously that's not a good solution. I have looked into Apple Push Notification Service and am unsure if this would fit my needs. When I looked into it this seems to be for sending notifications to the user remotely. However, rather than the user getting these messages displayed I would like the app to call a function instead (the function would load the new messages). Is this possible with push notifications?
Also this app is on both iOS and Android, so if there is a (possibly third party) solution that would cover both it would be ideal.
Any insight into this problem is greatly appreciated!
When you send a push notification and the app is in the foreground, the AppDelegate has a method called which allows you to execute whatever method you want.
This is only for iOS though, I don't know know it's handled in Android.
I'm running into a problem with an app that I'm building that I'm a little stuck on.
I have an iOS app (handles initiating the call via Twilio SDK) that communicates with a Ruby on Rails back-end (handles the Twilio server side implementation) to enable communication between the iDevice and the phone number being called.
The issue I'm having is that when a call is initiated accidentally (user error or misunderstanding how the app works) and the user goes to terminate the call Twilio has already received the request to create the call and it still goes through.
I've tried disabling the TCConnection and the TCDevice using their respective disconnect methods ("disconnect" and "disconnectAll"), but I'm still seeing the call go through (phone number being called still receives the call from the Twilio side of things). I haven't tried anything on the server side of things because I'd like to avoid building a set of "oh &$^$%" protocols if I can avoid it.
Has anyone experienced this before? Does anyone have any suggestions? Is there anyway to terminate calls made accidentally?
Thanks in advance!
Checking back in to share what I've discovered after reaching out to Twilio support in the event anyone finds this in the future.
From Twilio support:
For canceling a call, you can use the REST API to modify the live call and set the Status to "completed", which will cancel a ringing call and end an established call:
https://www.twilio.com/docs/api/rest/change-call-state
So, in short, build some "oh #^%$*" protocols that you can ping as necessary to actively terminate any call that you need to. Not ideal, but the options are limited.