I'm implementing a callback and have a problem. I'm calling the user1, they answer the call, listen to the message, then I call the user2, and they reject the call. I have checks for call fails but this continue happens, what could be the reason?
The only reason for this can be if your user2 has voicemail which successfully answers the call, so your checs do not work. You can use voicemail detection to avoid this: https://voximplant.com/docs/guides/ai/voicemail
Related
If I initialize the same user connected from multiple devices with the same apiCCId, when I try to call him, only one of the devices manages to start the call.
How can I deal with situation like that? Maybe I need to use JOIN / LEAVE room instead of calling.
If you have same user connected on multiple device, this user will receive call notification on all devices.
The first device where the call is accepted will make the call cancel on others devices (This is call forking).
You can check following tutorial to activate accept / refuse calls on apiRTC Client :
https://apirtc.com/tutos/Video_client_Material/apiRTC-Material-Client-Video-AcceptRefuse.html
My bot can send a response in multiple messages. I use the delivery callback to know that a message is delivered and the next can be sent. (https://developers.facebook.com/docs/messenger-platform/webhook-reference#message_delivery)
It works great except that sometimes I didn't receive Facebook's callback. I see no exact schema, for the exact same conversation it can works perfectly or miss a callback.
Have you ever noticed this problem ?
Opened a bug on Facebook plateform, answer is 'well do not rely on this delivery callback as it works mysteriously'
Facebook ticket
Update
The day after I closed this bug, new callbacks have been available on Messenger Platform, and the echo callback works exactly as intended.
Documentation of Echo callback here
I have a question about using remote push notifications in background. I know that I have just 30 seconds to run my code and must invoke completionHandler after that.
But what if while my application is active in background I received one more push notification? What completion handler should I invoke in that case?
Currently I try to use the last one but the system crash my app and I get BKProcessAssertion.
I can try to update the logic and call each of them (or the first? or the first immediately when get the second?..) but I am not sure that it would be the best solution.
Thank you
Looks like I must to call all of them. I have tried to call the completion handler immediately after receiving the next one and crashes are disappeared. I asked Apple engineers about that and they agreed that solution
In my project.i have below requirement.
we have to send some request to ATM.
so before sending response Atm will send some notifications.
As per requirement we have to listen the notifications and some how we need to send these content of this Notification tag to presenter.
for example
we are sending request to ATM---Rq1
then it sends some notifications like N1--it is a xml so for example value tag value is "some text".so this we need to send to presenter.if again we receive
N1 then needs to send the value tag value to presenter.so all these should send to presenter immediately.
once we receive response from ATM we can send the response data by using RPC.
The main motive is if we receive notification at 10:00 AM then we should send value tag value to the presenter.then next notification if we receive at 10:01 that value tag also we need to update to presenter.
So kindly advise us..if my question is not clear kindly let me know.
To my knowledge, an RPC call will only return once. And a server cannot directly communicate to a browser like the browser can to a server.
You might want to implement an asynchronous polling system. Essentially, your call your main RPC service, call it bigMethod(). After you call it, you immediately and asynchronously begin calling a polling method. just call it poll().
Every second or two, (or however long you think), it runs out to the ATM to check if there's a message. Once bigMethod() finishes you stop polling.
The downside is that this solution will require some tweaking of the back end code to handle it.
If a call is incoming when using a Client Browser (twilio.js) and I am already connected to an active call in the Client Browser. Client Browser doesn't ring or given any indication of an incoming call while I'm already on a call with someone else.
Is this a bug? What can be done about it so I can tell if there is an incoming call? I need to be able to answer that 2nd, 3rd, 4th, etc... incoming call should I have multiple people calling my Twilio number at the same time.
Kind of a late reply but you can use the Enqueue verb to place your callers in a queue, and then use the REST API with a javascript setInterval to list the callers in the queue. After that you can dequeue them with a Dial method or via the REST API.
We have crafted call-center functionality in node using a similar method where callers are placed in a queue which triggers a setInterval loop that monitors the queue for its members, and also looks for available agents to call.
For anyone interested I have solved this problem for myself, but in a different way to what #Ding suggests.
I'm not sure if the API has changed since this questions but you are able to access multiple Connections from a single Twilio.Device(). See this question for more details: Twilio call routing/management for small customer service team