Call registration
Good afternoon.
Please tell me what needs to be done to start the action "Convert call to process"?
I register a call via API /api/registercall/ with the INCOMING status. The call card pops up. I receive the call ID in the response.
How can I close the call further (I transferred the same call with the ANSWER status), I get the answer Ok and that's it. Maybe I need to use the call ID that I get in response when registering the call?
Original question is available on version: ru
Please tell me what needs to be done to start the action "Convert call to process"?
I register a call via API /api/registercall/ with the INCOMING status. The call card pops up. I receive the call ID in the response.
How can I close the call further (I transferred the same call with the ANSWER status), I get the answer Ok and that's it. Maybe I need to use the call ID that I get in response when registering the call?
Answers:
Good day. There are two concepts: an active call (right here and now) and an event (the history of the fact that the call was once). The call that you create is needed to show the call window in real time to the user who is being called in the box. To close the call, you can send the same request, only with a different status, for example ANSWER or CANCEL. So here you did everything correctly.
Further, all actions work with events, so in order for the action "Convert call to process" to work, you need to create an event. https://swagger.1b.app/#/event/event
Further, all actions work with events, so in order for the action "Convert call to process" to work, you need to create an event. https://swagger.1b.app/#/event/event
18.10.2024, 11:35
Original comment available on version: ru
Here I have an event created https://swagger.1b.app/#/event/event.
But for some reason the process was not created.
Is call registration (/api/registercall/) only needed to display the card?
id that I get in response after registration, can I use it somewhere? View the entire list of registered calls (not events).
But for some reason the process was not created.
Is call registration (/api/registercall/) only needed to display the card?
id that I get in response after registration, can I use it somewhere? View the entire list of registered calls (not events).
Снимок экрана 2024-10-18 в 11.37.51.png
Снимок экрана 2024-10-18 в 11.38.02.png
Снимок экрана 2024-10-18 в 11.38.35.png
18.10.2024, 11:40
Original comment available on version: ru
Samokhin Vladislav wrote:
Is call registration (/api/registercall/) only needed to display the card?
Yes, there are a couple more places where it is used, but you hardly need it.
Samokhin Vladislav wrote:
id that I get in response after registration, can I use it somewhere? View the entire list of registered calls (not events).
If some kind of telephony is connected, it usually contains a list of calls from this telephony.
If you need calls only to create tasks, you can skip /api/registercall/ and immediately create an event at the end of the call.
If there is an event, provide a link to it and, accordingly, a link to your system so that you can check the action settings.
18.10.2024, 11:44
Original comment available on version: ru
https://box.fialan.com/
https://box.fialan.com/app/event/979616/
+ it is not clear how to make there be a player in the event.
https://box.fialan.com/app/event/979616/
+ it is not clear how to make there be a player in the event.
18.10.2024, 11:53
Original comment available on version: ru
1. To play a recording, you need to write it in a separate field. In apiv2 there is no such possibility as far as I can see (all telephony has its own integrations, no one pushes calls there). It can be improved in 2 hours.
2. A missed call is when the client's phone was not picked up or something like that.
$statusArray[] = 'NOANSWER';
$statusArray[] = 'NO ANSWER';
$statusArray[] = 'CANCEL';
$statusArray[] = 'BUSY';
$statusArray[] = 'CONGESTION';
$statusArray[] = 'CHANUNAVAIL';
$statusArray[] = 'CALLFAILED';
list of statuses for which a call is considered missed.
2. A missed call is when the client's phone was not picked up or something like that.
$statusArray[] = 'NOANSWER';
$statusArray[] = 'NO ANSWER';
$statusArray[] = 'CANCEL';
$statusArray[] = 'BUSY';
$statusArray[] = 'CONGESTION';
$statusArray[] = 'CHANUNAVAIL';
$statusArray[] = 'CALLFAILED';
list of statuses for which a call is considered missed.
18.10.2024, 12:01
Original comment available on version: ru
The question is not about the action “Create a process based on the missed call”, but about the action “Reverse the call in the process”.
In this action, any call should turn into a process.
In this action, any call should turn into a process.
18.10.2024, 12:04
Original comment available on version: ru
The status field is missing from the call. Either remove the setting "Take only call statuses (show some through whom)" or pass the status. Calls are checked by default for the last hour, i.e. if you need to test, you will need to create a new one or change the action settings one-time, so that it takes, for example, for the last day.
18.10.2024, 12:51
Original comment available on version: ru
Can I pass the status to an event via api v2 (https://swagger.1b.app/#/event/event)?
18.10.2024, 13:00
Original comment available on version: ru
Unfortunately, no, as far as I can see. Remove the status action in the settings so that it is not filtered, or we can improve the status transfer, it will take about an hour. If the status and audio playback at once, 2 hours. Issue an invoice?
18.10.2024, 13:33
Original comment available on version: ru
How then to create a call so that this action would work?
18.10.2024, 13:41
Original comment available on version: ru
2 options
1.
let him cook
OneBox production wrote:
Remove the status in the action settings so that it is not filtered
2.
let him cook
OneBox production wrote:
we can improve the status transfer, it will take about an hour
1.
let him cook
OneBox production wrote:
Remove the status in the action settings so that it is not filtered
2.
let him cook
OneBox production wrote:
we can improve the status transfer, it will take about an hour
18.10.2024, 13:56
Original comment available on version: ru
And according to api v1, there are statuses in call registration. Will processes not be created according to this webhook?
18.10.2024, 14:03
Original comment available on version: ru
As I described above, this API is needed to show the user a window with a call.
18.10.2024, 14:07
Original comment available on version: ru
You can look at the log for today 12:49.
https://box.fialan.com/admin/logs/showall/ajax/?file=fatal-2024-10-18.log
Error in file box_auto_action_event_call2issue.php
https://box.fialan.com/admin/logs/showall/ajax/?file=fatal-2024-10-18.log
Error in file box_auto_action_event_call2issue.php
18.10.2024, 14:38
Original comment available on version: ru
Tell me, with standard integration https://1b.app/ua/app/ringostat/ should processes be created by the action "Convert call to process"?
18.10.2024, 15:15
Original comment available on version: ru
Got it, thank you very much for your help
18.10.2024, 16:58
Original comment available on version: ru
Please tell me, should the call card be displayed in the standard Ringostat integration?
21.10.2024, 13:49
Original comment available on version: ru
https://www.youtube.com/watch?v=mSPMRWj-ucg setup instructions.
21.10.2024, 14:18
Original comment available on version: ru
For some reason the calls are duplicated(
I send one webhook, but get 2 calls.
https://box.fialan.com/ringostat/push/?custom=117&caller=380931112233&ca...
I send one webhook, but get 2 calls.
https://box.fialan.com/ringostat/push/?custom=117&caller=380931112233&ca...
21.10.2024, 15:54
Original comment available on version: ru
Perform the main task - show the window to the user, you should not care about the rest. In this case, the window will appear for user number 117
21.10.2024, 16:17
Original comment available on version: ru
I disabled INPROGRESS statuses, but the integration still pulls calls with this status and creates an event(
21.10.2024, 16:30
Original comment available on version: ru
Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter.
Log in and comment
Copyright © OneBox 2024
