Here, users will find all inbound call reporting status description which will help them to understand and analysis the call flow of configured DeskPhone/IVR/Toll-free Number.

S.NoTrigger bySTATUSCALL STATUSDESCRIPTION
1.LEG BANSWERANSWER (16)Call is answered. A successful dial.
2. 3.Either party A or BNO ANSWERCANCEL (0)Call is cancelled. The dial command reached its number but the call hung up by customer or agent/member before picked up.
4.LEG BNO ANSWERNO ANSWER (0-Agent)The dial command reached its number, the number rang for too long, then the dial timed out.
5.LEG BNO ANSWERBUSY (17)Busy signal. The dial command reached its number but the number is busy.
6.LEG BNO ANSWERCONGESTIONThis status usually indicates that the dialled number was not recognised by the operator due to a network problem.
7.LEG BNO ANSWERUnavailable (19)Number not reachable due to network/congestion
8.LEG BNO ANSWERCHANUNAVAILChannel unavailable. On SIP, peer may not be registered.
9.LEG BNO ANSWERNot connectedThe call was received in the IVR system, but no call forwarding occurred.
10.LEG BNO ANSWERAgentEngaged(0-Agent)The status indicates that the agent is on another picked running call on another SIP trunk channel.
11.LEG BNO ANSWERAgentonRing(0-Agent)The status indicates that the agent number is Ringing for another incoming call on another SIP trunk channel at that time.
12.LEG BNO ANSWERAbandonedCallWhen no agent answers the phone,  than caller is disconnected during the  “retry music” notification.
13.LEG BN/ATransfer to agentCaller call is transferring on agent number
14.LEG BN/APickedIt Represent caller call is pick

Asterisk Hangup Cause Code Mapping

User may confuse about the reason of showing brackets ( ) under mentioned above call status head. So let we explain you that these bracket mentioned numbers are actually cause code which we are receiving from operator and all are benchmarked globally accepted cause codes.

Reason of showing it on panel reports – Sometime, user may curious to know that this status are same which operator is sending to us. In this case, we may share backend logs of that particular call which will be send by operator including cause code. It helps users to match the report from what operator is sending to us, and what we are showing to users.

S.NoCause Codes
1.0= Cause not defined
2.16= Normal Clearing
3.17= User busy
4.19= No answer from user (user alerted)
5.21= Call Rejected

For more detailed Hangup Cause code Mapping status, Kindly visit below link:

https://wiki.asterisk.org/wiki/display/AST/Hangup+Cause+Mappings

Leave a Reply

Your email address will not be published. Required fields are marked *