Skip to main content
All CollectionsAnalytics and call history
Track how the call was ended
Track how the call was ended

See exactly how the call was ended: if the user hung up, the agent, if the call was transferred, etc.

Maurizio avatar
Written by Maurizio
Updated over a week ago

You can check the reason why a call is disconnected through the Call history page:

What it all means

How the call ended

Description

user_hangup

Expected behavior, user hangup the call.

agent_hangup

Expected behavior, AI agent hangup the call.

call_transfer

Expected behavior, AI agent transferred the call.

voicemail_reached

Expected behavior, if AI agent configured voicemail settings, and reached voicemail.

inactivity

Expected behavior, call was terminated due to the “End the call after x time” setting reached after long inactivity.

machine_detected

Expected behavior, call was ended due to the “Hang up the phone” setting triggering when an voicemail or similar is detected.

max_duration_reached

Expected behavior, call was terminated due to maximum duration reached.

concurrency_limit_reached

Error, concurrency limit reached, add a retry with exponential backoff. Or consider enterprise plan.

no_valid_payment

Error, no valid payment registered on file, or service shut down due to bill overdue.

scam_detected

Error, scam detected for that particular agent.

error_inbound_webhook

Error, failed to retrieve dynamic variables for inbound phone call.

dial_busy

The number dialed in busy.

dial_failed

Dailing failed, might be due to callee number is non existent, or the agent number is marked as spam and got blocked.

dial_no_answer

The number dialed did not answer.

error_llm_websocket_lost_connection

Error, LLM websocket connection broke during the call.

error_llm_websocket_runtime

Error, LLM websocket received a closing signal other than 1000 from your server.

error_llm_websocket_corrupt_payload

Error, LLM websocket received unspecified payload.

error_frontend_corrupted_payload

Error, frontend audio websocket received unspecified payload.

error_twilio

Error, Twilio websocket connection between Ringly.io server encountered an error.

error_no_audio_received

Error, has not received audio from Twilio or web frontend for a while after connection has established.

error_asr

Error, Ringly's ASR encountered a problem.

error_ringly

Error, unspecified Ringly.io side problem.

error_unknown

Error, unknown error.

registered_call_timeout

Error, phone call is 30s or more apart from registering.

​Understand why an outbound call fails

When an outbound call is made and a dial_failed, dial_no_answer reason is returned, it means that the call is not successful. Possible reasons are:

  1. The number dialed does not exist

  2. The number you use to dial is marked as spam and got blocked

  3. Error met in telephony provider (for example, max call per second limit reached)

  4. The number dialed did not answer

It’s however beyond our scope and control to have more information about why it did not connect. If further information is needed, shoot us a message.

Did this answer your question?