Call Status refers to the different states or conditions that a call may go through during its lifetime. These states could include call ended, declined, busy, not answered, cancelled, abandoned, unreachable, or call failed, among others.
Bye Reason, on the other hand, explains why a call has been disconnected. When a call is disconnected, the party initiating the disconnection will send a bye message, which could include a reason code to explain the cause. Some of these reasons could include the user hanging up, network or service congestion, bearer capability not authorised or available, and outgoing or incoming call barred, among others.
The Call Status page provides a helpful and informative resource for users who encounter different call statuses during call communication.
The Call Status provides a comprehensive list of statuses that could be encountered when making a call, along with their respective definitions. This will serve as a reference that helps to understand the reason behind a specific call status and how it ended. Each status is accompanied by a definition explaining what it means and what actions the user can take in response.
|- Call connected and completed (e.g., normal clearing - ended by caller/receiver).
- Call connected and dropped (e.g., network issue, service congestion, unspecified error).
|The receiver rejected the call.
|The receiver is unable to accept another call.
|The receiver did not respond and timed out.
|The ongoing call hung up before the receiver picked up.
|The call was established to the receiver, however,
- Caller hung up while in the IVR menu;
- Caller hung up while on Voicemail;
- The caller hung up while on hold with a staff member (i.e., during call transfer).
|The caller cannot reach the receiver due to the following reasons:
- Receiver's device is turned off
- Receiver has no data connection
- Receiver was out of coverage area
- Service temporarily congested
|In general, the call failed because of call service and network-related issues.
The Last Response Code and Bye Reason table shows the reasons behind specific call disconnections. The table lists different codes and their respective definitions, including an explanation of the corresponding bye reason.
|Last Response Code
|Unspecified. No other cause codes are applicable.
|This China Unicon Global (CUG) member was not allowed outgoing calls.
|Incoming calls were not allowed to this member of the CUG.
|The user has requested a bearer capability implemented by the equipment, but the user was not authorised to use it.
|The user has requested a bearer capability implemented by the equipment, but the bearer capability was not available at this time.
|Unallocated (unassigned) number.
|No route to the specified transit network. (National use)
|No route to a destination.
|No user is responding.
|The call was redirected to a new destination.
|No answer from the callee (aka called party/receiver).
|The destination indicated by the user cannot be reached
|Invalid number format. (Address incomplete)
|If a visitor made PSTN call and cancelled it.
|The equipment sending this cause has received a request to establish a call with low-layer compatibility, high-layer compatibility or other compatibility attributes (e.g. data rate) that cannot be accommodated.
|invalid message, unspecified
|The equipment sending this cause has received a message missing information that must be present in the message before that message can be processed.
|The equipment sending this cause has received a message with a message type it does not recognize because it is not defined or implemented by the equipment sending this cause.
|The equipment sending this cause has received a message such that the procedures do not indicate that this was a permissible message to receive. In contrast, a STATUS message was received in the call state indicating that it was in an incompatible call state.
|The equipment sending this cause has received a message which includes information element(s)/parameter(s) not recognized because the information element(s)/parameter name(s) were not defined or were defined but not implemented by the equipment sending the cause.
|The equipment sending this cause has received the information element it has implemented; however, one or more fields in the information element were coded in a way that has not been implemented by the equipment sending this cause.
|The message was received when the message was incompatible with the call state.
|The equipment sending this cause does not support the bearer capability requested.
|The equipment sending this cause does not support the channel type requested
|The equipment sending this cause does not support the requested supplementary services.
|Service or option not implemented, unspecified
|Destination out of order
|network out of order
|No circuit or channel is available.
|The network did not function correctly.
|Switching equipment congestion.
|The other side of the interface cannot provide the circuit or channel indicated by the requesting entity.
|The expiration of a timer in association with error handling procedures has initiated a procedure.
|The call was rejected.
|The call was cancelled on the server side.
|The caller hung up the call in the IVR menu.
|The caller hung up the call while the call was on hold with an agent (e.g., Call Transfer).
|The caller hung up the call while the call was in the Voicemail.
|The caller left the call with a voicemail.
|The caller hung up the call while the call was in the IVR menu.
|The caller selected the call transfer option inside the IVR menu and transferred the call to the configured destination (Agent)
|The call was hung up while the call was in the ACD greeting prompt mode before the agent could pick up the call.
|Automatic Call Distribution (ACD) system started distributing the call to an agent to pick up the call.
|The user requested a supplementary service, which was available, but the user was not authorised to use it.
|Response to status inquiry.
|Service or option not available.
|The equipment sending this cause has received a message with a call reference which was not currently in use on the user-network interface.
|The equipment sending this cause has received a message which includes parameters not recognized because the parameters were not defined or were defined but not implemented by the equipment sending this cause.
|This cause was used to report a protocol error event only when no other cause in the protocol error class applies.
|This cause indicates an interworking call (usually a call to SW56 service) has ended.
|This cause was used when you sent an API command to make it hang up. For example uuid_kill
|The blind transfer was taken to the call.
|The warm transfer was taken to the call.
|The call was picked up by intercepting it from another extension (i.e. dialling the ext_number from another extension).
|You tried to originate a call to a SIP user who forgot to register.
|The call progress exceeds the time limit.
|Gateway was down (not answering on OPTIONS or SUBSCRIBE)
|The caller hung up the call while the call was in voicemail mode.
|The call was forwarded to a PSTN Number.
|Call awarded being delivered in an established channel.
|Normal call clearing.
|The network could not deliver access information to the remote user.