Call logs can be used to identify call outcomes reasons including the hangup cause and call status. The hangup by and status can be found when navigating to Reporting Logs
Hangup By: |
Description: |
TERMINATOR END |
The termination point ended the call |
TERMINATOR REFUSE |
Termination point refused the call |
ORIGINATOR END |
Origination point ended the call |
ORIGINATOR_CANCEL |
The request has been terminated by bye or cancel |
ABORT |
The originator ended the call |
Status: |
Description: |
CALL_REJECTED |
The destination does not wish to participate in the call, or cannot do so, and additionally, the destination knows there are no alternative destinations (such as a voicemail server) willing to accept the call. |
COMPLETED |
The call was completed |
DIALING |
The call is currently dialing |
IN-PROGRESS |
The call is currently in progress |
IN-QUEUE |
The calls in the queue pending to be answered |
INSUFFICENT_FUNDS |
The account has no funds |
LOSE_RACE |
The originator ended the call to a group called |
NO_ANSWER |
Callee is currently unavailable |
NO_ROUTE_DESTINATION |
Number Unreachable |
NO_ROUTE_TRANSIT_NET |
Number Unreachable |
NORMAL_TEMPORARY_FAILURE |
Failure to receive a response from the carrier |
NORMAL_UNSPECIFIED |
Callee is currently unavailable. |
NUMBER_CHANGED |
The called party number indicated by the calling party is no longer assigned. |
REQUESTED_CHAN_UNAVAIL |
Service Unavailable |
SERVICE_UNAVAILABLE |
This cause is used to report a service or option not available event only when no other cause in the service or option, not available class applies. |
UNALLOCATED_NUMBER |
The number is currently unassigned and unreachable |
USER_BUSY |
This indicates that the called party is unable to accept another call because the user's busy condition has been encountered. |
ACCESS_INFO_DISCARDED |
This cause indicates that the network could not deliver access information to the remote user as requested, i.e. user-to-user information, low layer compatibility, high layer compatibility, or sub-address as indicated in the diagnostic. It is noted that the particular type of access information discarded is optionally included in the diagnostic. |
ALLOTTED_TIMEOUT |
This cause means that the server canceled the call because the destination channel took too long to answer |
BEARERCAPABILITY_NOTAUTH |
The server understood the request but is refusing to fulfill it. |
BEARERCAPABILITY_NOTAVAIL |
Service Unavailable |
BEARERCAPABILITY_NOTIMPL |
This cause indicates that the equipment sending this cause does not support the bearer capability requested. |
CALL_AWARDED_DELIVERED |
This cause indicates that the user has been awarded the incoming call and that the incoming call is being connected to a channel already established for that user for similar calls |
CHAN_NOT_IMPLEMENTED |
This cause indicates that the equipment sending this cause does not support the channel type requested |
CHANNEL_UNACCEPTABLE |
This cause indicates that the channel most recently identified is not acceptable to the sending entity for use in this call. |
DESTINATION_OUT_OF_ORDER |
Received an invalid response from a downstream server while attempting to fulfill the request. |
EXCHANGE_ROUTING_ERROR |
Number was unreachable |
FACILITY_NOT_IMPLEMENTED |
The server does not have the ability to fulfill the request, such as because it does not recognize the request method. |
FACILITY_NOT_SUBSCRIBED |
This cause indicates that the user has requested a supplementary service, which is available, but the user is not authorized to use it. |
FACILITY_REJECTED |
The server does not have the ability to fulfill the request |
GATEWAY_DOWN |
Gateway is down (not answering on OPTIONS or SUBSCRIBE) |
IE_NONEXIST |
This cause indicates that 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) are not defined or are defined but not implemented by the equipment sending the cause. This cause indicates that the information element(s)/parameter(s) were discarded. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message. |
INCOMING_CALL_BARRED |
The server understood the request but is refusing to fulfill it. |
INCOMPATIBLE_DESTINATION |
Request to establish a call that has low layer compatibility, high layer compatibility, or other compatibility attributes (e.g. data rate) which cannot be accommodated. |
INTERWORKING |
This cause indicates that an interworking call (usually a call to SW56 service) has ended. |
INVALID_CALL_REFERENCE |
This cause indicates that the equipment sending this cause has received a message with a call reference that is not currently in use on the user-network interface. |
INVALID_IE_CONTENTS |
This cause indicates that the equipment sending this cause has received an information element that it has implemented; however, one or more fields in the I.E. are coded in such a way that has not been implemented by the equipment sending this cause |
INVALID_MSG_UNSPECIFIED |
This cause is used to report an invalid message event only when no other cause in the invalid message class applies. |
INVALID_NUMBER_FORMAT |
This cause indicates that the called party cannot be reached because the called party number is not in a valid format or is not complete. |
MANAGER_REQUEST |
This cause is used when you send an API command to make it hang up. For example uuid_kill |
MANDATORY_IE_LENGTH_ERROR |
This cause indicates that the equipment sending this cause has received a message which includes parameters not recognized because the parameters are not defined or are defined but not implemented by the equipment sending this cause. The cause indicates that the parameter(s) were ignored. In addition, if the equipment sending this cause is an intermediate point, then this cause indicates that the parameter(s) were passed unchanged. |
MANDATORY_IE_MISSING |
This cause indicates that the equipment sending this cause has received a message which is missing an information element that must be present in the message before that message can be processed. |
MESSAGE_TYPE_NONEXIST |
This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined of defined but not implemented by the equipment sending this cause. |
NETWORK_OUT_OF_ORDER |
Temporarily overloaded and so cannot process the request |
NO_USER_RESPONSE |
Couldn't find the user in time. The server could not produce a response within a suitable amount of time |
NORMAL_CIRCUIT_CONGESTION |
Temporarily overloaded and so cannot process the request |
NORMAL_CLEARING |
This cause indicates that the call is being cleared because one of the users involved in the call has requested that the call be cleared. Under normal situations, the source of this cause is not the network. |
OUTGOING_CALL_BARRED |
The server understood the request but is refusing to fulfill it. |
PICKED_OFF |
This cause means the call was picked up by intercepting it from another extension (i.e. dialing **ext_number from another extension) |
PROTOCOL_ERROR |
This cause is used to report a protocol error event only when no other cause in the protocol error class applies |
RECOVERY_ON_TIMER_EXPIRE |
Time-out reached during request |
REDIRECTION_TO_NEW_DESTINATION |
This is used by an exchange to decide that the call should be set up to a different call number. |
RESPONSE_TO_STATUS_ENQUIRY |
This cause is included in the STATUS message when the reason for generating the STATUS message was the prior receipt of a STATUS INQUIRY. |
SERVICE_NOT_IMPLEMENTED |
The server does not have the ability to fulfill the request, such as because it does not recognize the request method. |
SUBSCRIBER_ABSENT |
Callee is currently unavailable. |
SWITCH_CONGESTION |
This indicates that the switch is experiencing a period of high traffic. |
UNSPECIFIED |
This is usually given by the router when none of the other codes apply. This cause usually occurs in the same type of situations as cause 1, cause 88, and cause 100. |
USER_NOT_REGISTERED |
This means you tried to originate a call to a SIP user who forgot to register. |
WRONG_CALL_STATE |
This cause indicates that a message has been received which is incompatible with the call state. |
WRONG_MESSAGE |
This cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is a permissible message to receive while in the call state, or a STATUS message was received indicating an incompatible call state. |