I want to connect random users on a call (1 on 1 only) but that results sometimes in call collision. Steps that I took so far are:
On call button press I create a new session and try to connect with other users
The opponent users receives that call and has to accept or reject it, but in the meantime he is also waiting for accept/reject from the call that he made.
Basically everyone will end up calling someone and I am unable to think of a strategy where the system doesn't get overwhelmed with call requests.
Maybe someone who had a similar issue could help me with this problem
Related
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 ?
So I am trying to understand the workflow in kicking a user from a channel. I have a command I can issue to the channel #kick username. This is handle by a handle in which parse the message and will detect is a command. That will call the kick function in my channel. My issue is how I actually make the user leave. There is no such thing as Endpoint.Broadcast with a leave event like we have for disconnecting a socket from everything.
I've been told to use a Endpoint.Broadcast an event like kick and use a handle_out to intercept it. Well even if I use it, how is this disconnecting the user I want specifically to be kick as an admin.
I am looking for some source code for iOS 10 and below by which I can get the caller number when some phone call arrived and that call can be rejected by the application, if call is some fraud call (checking the local database).
I have followed following post but did not get any fruitful result.
Via call kit: how to get the incoming call number by using callkit
True caller app already added that feature:
https://blog.truecaller.com/2016/10/26/truecaller-now-available-on-ios-10/
I think it is possible, can anyone help me by giving some idea or source code by which that can be achieved?
It is not possible to get caller's number when user receives a call. Truecaller has a lot of conditions for it to be able to show caller's details. The truecaller app should be active. The caller should call using the truecaller app. Both the calling and call receiving devices should be connected to the internet.
So what it basically does is that when a user presses the call button on the app to call somebody, they simply send him a notification that this person is calling you. It has nothing to do with CallKit and the caller id is not displayed on the call receiving screen.
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 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.