Dialogues
Every time the system makes or receives a call within the Voice bot application, the system logs the progress and result of the script execution and saves it as a Dialogue.
To enable the Dialogue storage function, contact the manager.
To view the Dialogue, go to the “Dialogues” section and click on any of them in the list.
Set the period for which you want to display the report (if necessary, specify the request using additional filters on the page), and click “Show”. Then, the dialogs can be exported in csv/xls formats.
Each Dialogue is presented as a sequence of results of the call scenario blocks.
At the top of the Dialogue there is a block with a record of the Date and time of the call, Duration, A- and B-numbers, as well as the status with which this call ended:
Status | Description |
---|---|
Normal scenario completion | Scenario is fully completed |
Scenario error with the error code | An error appeared during the scenario execution |
Caller hung up | Caller hung up, scenario was not completed |
Audio recordings with the possibility of listening and download are stored in the blocks in which there is speech synthesis, media file playback or a subscriber’s voice response. The full audio recording of the call is located at the beginning of the Dialogue under the completion status:
Script execution error codes
Error value | Error | Description |
---|---|---|
1001 | SCENARIO_NOT_FOUND | An internal script execution error indicates that the script that should have been executed does not exist or cannot be found |
1002 | SCENARIO_JSON_PARSER_ERROR | An internal Json script parsing error can occur if the script has incorrect syntax or structure |
1003 | SCENARIO_VAR_ID_ERROR | An internal error in parsing script variables may indicate problems with variable identification (not used) |
1004 | SCENARIO_VAR_NAME_ERROR | Indicates problems with variable names in the script may be caused by an incorrect or missing variable name (not used) |
1005 | TRUNK_NOT_FOUND | The trunk cannot be found according to the specified routing rules may be caused by incorrect routing settings or the absence of the required trunk |
1006 | REDIRECT_TRUNK_NOT_FOUND | The trunk cannot be found according to the specified routing rules when forwarding a call may occur due to errors in the forwarding settings |
1007 | MODIFIERS_ERROR | The error of the call modifiers indicates that the values of sourceAddr, destAddr, trunk Data were incorrectly changed for this call |
1008 | REDIRECT_MODIFIERS_ERROR | Call modifiers error during forwarding the values of source Addr, dest Addr, trunk Data were incorrectly changed for call forwarding |
1009 | CHANNEL_CREATION_ERROR | An error that occurs when creating a communication channel transmitted from Asterisk may be caused by problems with the configuration or resources of the system |
1010 | REDIRECT_CHANNEL_CREATION_ERROR | An error when creating a forwarding channel indicates problems with creating a channel for a forwarded call |
1011 | REDIRECT_BRIDGE_CREATION_ERROR | An error creating a conference bridge during forwarding transmitted from Asterisk a bridge cannot be created to connect multiple call participants |
1012 | REDIRECT_ADDING_SOURCE_CHANNEL_TO_BRIDGE_ERROR | Error when adding a forwarded call channel to the bridge, transmitted from Asterisk the original channel cannot be correctly added to the bridge |
1013 | REDIRECT_ADDING_DEST_CHANNEL_TO_BRIDGE_ERROR | Error when adding the channel to which calls are forwarded to the bridge transmitted from Asterisk |
1014 | INCOMING_CALL_ANSWER_ERROR | Occurs if the call was dropped before the script execution started, because the channel no longer existed when the incoming call was answered with an error from Asterisk |
1015 | PLAYBACK_START_ERROR | The error when playing to the channel comes from Asterisk |
1016 | RECORD_START_ERROR | The error when writing from the channel comes from Asterisk |
1017 | TTS_FAULT | A speech synthesis error transmitted from the app-TTS application may be caused by problems with speech synthesis or incorrect data for synthesis |
1018 | WRONG_DATA_IN_REQUEST | Request data parsing error indicates incorrect or missing data in the request |
1019 | NUMBER_NOT_FOUND_IN_POOL_BY_ENDING | Selecting a number from the pool at the end of the number for FlashCall it may be caused by the absence of the corresponding number in the pool |
1020 | INTERFACE_NAME_EMPTY_ERROR | Error when selecting a trunk indicates incorrect or missing trunk configuration data |
1021 | REDIRECT_INTERFACE_NAME_EMPTY_ERROR | An error when selecting a trunk for forwarding due to the absence of an interface name indicates incorrect or missing trunk configuration data |
0 | Call sent to void | The completion of a normal scenario indicates that the call has completed normally, without any problems or errors |
1 | Unallocated | It can happen when the requested resource does not exist or is currently unavailable |
4-5 | Vendor specific 4-5 | Vendor-specific error the specific error value depends on the hardware or service provider |
6 | Channel unaccessible | The channel is unavailable indicates that the communication channel required for the call is unavailable |
9-13 | Vendor specific 9-13 | Vendor-specific error the specific error value depends on the hardware or service provider |
16 | Normal Clearing | Normal termination the call is completed on the initiative of one of the parties (subscriber or operator) without errors |
17 | Line busy | The user is busy the number of the called party is busy and the call cannot be completed |
18 | No user response | No response from the user the called party does not answer the call during the set waiting time |
19 | No answer | The user was notified, but did not answer the subscriber was notified of an incoming call (for example, the phone rang), but did not accept it |
20 | Subscriber absent | Missing subscriber indicates that the called subscriber is temporarily unavailable |
21 | Call Rejected | The call is rejected the called party intentionally rejected the incoming call |
22 | Number changed | The number has been changed |
27 | Destination out of order | The purpose of the call is out of service the end equipment or network of the called party is not working or unavailable |
28 | Invalid number format | Incorrect number format the entered phone number has an incorrect format and cannot be recognized by the network |
29 | Facility rejected | Feature rejected the requested service or feature is not supported or rejected by the network |
31 | Normal unspecified | The usual unspecified the call ended for the usual reason, which was not explicitly stated |
32 | (Reserved) | Reserved for future use |
34 | No circuit available | Circuit/channel overload there is an overload in the network and the call cannot be processed |
36 | Out of order | Faulty indicates that the equipment or line is not working properly |
38 | Network out of order | The network is not working there has been a network outage, which makes it impossible to end the call |
43 | Access disconnect | Disabling access indicates that network access has been disabled |
58 | Bearer capability not available | Load-bearing capacity is not available |
98 | Blacklist | Indicates that the call was blocked because the number is on the blacklist |
99 | Vad avtoinformator error | Indicates that the call was processed by the auto-informer |
100 | InvalidIe contents | Invalid IE content (Information Element) indicates an error in the information passed in the element |
102 | Recover on timer expiry | Recovery after the timer expires |
127 | Failure | Interaction/not specified |
199 | Transaction abort | Abort a transaction the transaction was aborted for some reason |
200 | No translation for address of such nature | It may be due to the fact that the address is invalid, non-existent or not recognized by the system |
201 | No translation for this specific address | There is no conversion for this particular address indicates that there is no routing or conversion for the specified address |
212 | Hop counter violation | Violation of the traffic counter indicates that the allowed number of clicks in the network has been exceeded |