Standard Plivo Hangup Causes

The reason for hangup could not be determined.

A known bug sets hangup cause to Unknown for calls hung up using the Delete All Calls API.

Initiated

Ringing

The destination number or SIP endpoint was found to be invalid.

Check that the destination number is valid and is specified in E.164 format (e.g. +12292442099 or 12292442099).

Plivo

Carrier

The destination SIP endpoint was found to be unregistered or could not be reached.

Confirm that the endpoint was logged in and connected to internet. If the call was to an endpoint connected through the Plivo iOS or Android SDK, ensure that your application is correctly configured to receive VoIP push notifications from Plivo. Read more about debugging calls to endpoints on iOS and Android SDKs.

The call was barred, as the destination country are disabled for the account or subaccount that initiated the call.

Check country permissions under Voice > Geo Permissions on the Plivo console.

The call was barred, as calls to premium rate numbers are disabled for the account or subaccount that initiated the call.

Check high risk permissions under Voice > Geo Permissions on the Plivo console.

The call could not be established because the call flow violates the country-specific media anchoring rules.

If you are using the domestic calling product in any country, the local regulations do not allow calls to be connected in some situations such as:

• If any of the call legs is geographically located outside the country.
• If two different calling routes are used for bridged PSTN calls via Dial XML or conferences.

For application-originated calls (WebRTC), please make sure the caller is present in the same country where the call is terminating. For PSTN calls, please use the Plivo DID from the same country as the caller Id and make outbound calls. For more information, please contact the Plivo support team.

Plivo, If the destination is a Plivo SIP endpoint.

Carrier, If the destination is a PSTN phone number or external SIP endpoint.

Plivo, if the destination is a Plivo SIP endpoint

Carrier, if the destination is a PSTN phone number or external SIP endpoint

Called party

Answer XML, if an inbound call is rejected using the Hangup XML element

Initiated

Ringing

Plivo

Answer XML, if an inbound call is rejected using the Hangup XML element

Pre-Initiation

Ringing

Plivo

Carrier

Plivo

Carrier

Plivo

Carrier

Initiated

Ringing

Caller

Called party

API request, if the call was hung up using the Hangup API

Answer XML, if the call was hung up using the Hangup XML element

Ringing

Answered

There were no more XML instructions to execute.

This is a normal hangup reason for calls that are being controlled by their own XML. This includes A legs (outbound and inbound) and B legs that have been transferred to their own XML using the Transfer API.

The call was canceled using the Stop an MPC API request, or the MPC ended due to reaching its max duration limit.

The participant was removed from the MPC using the Remove a Participant API.

The call was automatically terminated based on the max duration configured for the call.

For API-initiated calls, you can configure max call duration using the time_limit request parameter.

For calls initiated using the Dial XML element, you can configure max call duration using the timeLimit attribute. This property defaults to four hours when not specified.

The call was automatically terminated as it was not answered within the ring timeout value configured for the call.

For API-initiated calls, you can configure max ring time using the ring_timeout request parameter. This property defaults to 120 seconds when not specified.

For calls initiated using the Dial XML element, you can configure max ring time using the timeout attribute. This property defaults to 120 seconds when not specified.

Initiated

Ringing

Initiated

Ringing

A non-2xx HTTP response was encountered while fetching XML instructions from the specified action URL.

Note that a non-2xx response results in call termination only if the redirect attribute is set to true.

Ringing

Answered

Ringing

Answered

The action URL specified for the XML element is not a valid URL. Please ensure the URL begins with http or https.

Note that an invalid action URL results in call termination only if the redirect attribute is set to true.

Ringing

Answered

Ringing

Answered

Ringing

Answered

Ringing

Answered

Ringing

Answered

The XML returned by the action URL is not valid Plivo XML. View debug logs for the call on your Plivo console for more information.

Note that invalid XML results in call termination only if the redirect attribute is set to true.

Ringing

Answered

Ringing

Answered

Another B leg that was dialed in parallel accepted the call first.

This is a common hangup reason in simultaneous dial scenarios where multiple destinations are tried in parallel. The first destination to accept the call is connected with the A leg, and other calls are immediately terminated.

The call was answered by an answering machine.

This hangup reason is possible only for API-initiated calls having the machine_detection request parameter set to hangup.

The Add Participant API call was disconnected as the participant failed to enter the confirm_key DTMF input set in the MPC application.