Skip to main content

​
Introduction

In every Bolna Voice AI conversation, the system records metadata about how and why a call was terminated. This information is critical for debugging, analytics, compliance, and improving user experience across various industries, geographies, and use cases. Each call termination is associated with:
  • hangup_by: Identifies the party or system that initiated the hangup (e.g., caller, callee, system).
  • hangup_code: A numeric code indicating the specific reason for the hangup, typically provided by the telecom provider or API response.

​
Why Hangup Codes Matter

Understanding hangup statuses and codes helps:
  • Improve call handling workflows and automation
  • Identify systemic or geographic call issues
  • Monitor telecom partner reliability (e.g., Plivo, Twilio)
  • Pinpoint user-initiated hangups vs system or error-based disconnects
  • Enhance regional support (United States, India, Southeast Asia, MENA, etc.)

​
List of Hangup Statuses and Codes

Below is a detailed list of common call hangup reasons and their associated codes used in Bolna’s Voice
Hangup byHangup DescriptionHangup provider code
API RequestCall was ended by the Bolna agent via an API request4000, 4020
CalleeThe recipient of the call hung up (applies to outbound calls)3020, 4000
CallerThe caller ended the call (applies to inbound calls)4000
CarrierCall was terminated by the telecom carrier2000, 3000, 3010, 3020, 3040, 3050, 3070
ErrorCall ended due to an unexpected error3080, 3090, 3110, 5010, 5020, 7011, 8011
PlivoThe telephony provider (Plivo) disconnected the call1010, 4010, 5020, 6000, 6010, 6020
UnknownReason for call termination is unknown0
(empty)No hangup reason was recorded(empty)

​
Notes on Code Interpretation

  • Multiple codes may map to a single hangup_by status depending on the network or device behavior.
  • Codes like 4000 appear in multiple categories (API, caller, callee) - interpretation depends on context and direction of the call (inbound vs outbound).
  • Carrier-related hangups are often location-sensitive. If you’re noticing frequent 3010 or 3050 codes in a specific region, consider checking local routing or carrier coverage.