Quels sont les types de conclusion?
Lors du développement dans des rapports d'appel, un champ de conclusion affiche des codes de cause standardisés pour vous aider à comprendre pourquoi (ou comment) chaque appel se termine. Disponible uniquement en anglais pour le moment.
| Cause Code | Definition |
|---|---|
| 0: 'Valid Cause Code Not Yet Received' | Indicates that a standard cause code of 1-127 was not received due to a complicated call scenario. |
| 1: 'Unallocated Number' | Indicates that the called party cannot be reached because the called party number is not currently routed. |
| 16: 'Normal Call Clearing' | Indicates that the call is terminated by one of the parties involved. Under normal situations, the source of this cause is not the network. The call comes in normally, but the reasons for the cause could be:
|
| 17: 'User Busy' | Indicates that the called party is unable to accept another call because the user busy condition has been encountered. |
| 19: 'No Answer from User (user alerted)' | Indicates that the called party has been alerted but did not respond within a prescribed period of time. This cause may be generated by internal network timers. |
| 20: 'Subscriber Absent' | Indicates that a user/device is temporarily not addressable. This may be because the extension no longer exists or a device is unregistered. |
| 21: 'Call Rejected' | Indicates that the user or a user-set system setting, like DND, rejected the call from being answered. |
| 22: 'Number Changed' | Indicates that the number dialed by the calling party is no longer assigned. |
| 26: 'Non-selected User Clearing' | Indicates that the user has not been awarded the incoming call. This can happen in a ring group setup where multiple users are rung but only one of them answers the call. This code would show up for the users who did not answer the call. |
| 27: 'Destination Out of Order' | Indicates that the destination indicated by the user cannot be reached because the interface to the destination is not functioning correctly. The term "not functioning correctly" indicates that a signal message was unable to be delivered to the remote party; e.g., a physical layer or data link layer failure at the remote party, or user equipment off-line. |
| 28: 'Invalid Number Format (addr incomplete)' | Indicates that the called party cannot be reached because the called party number is not in a valid format or is not complete. |
| 29: 'Facility Rejected' | This cause is returned when a supplementary service, such as a third party auto attendant, requested by the user, cannot be provided by the network. |
| 34: 'No Circuit/Channel Available' | Indicates that there is no appropriate circuit/channel presently available to handle the call. This may be due to an at-capacity circuit on either side of the call. |
| 38: 'Network Out of Order' | Indicates that the network connecting the caller and callee is not functioning correctly. |
| 44: 'Requested Circuit/Channel N/A' | This cause is returned when the other side of the interface cannot provide the circuit or channel indicated by the requesting entity. |
| 58: 'Bearer Capability Not Available' | Indicates that the user has requested a bearer capability that is not available at this time. Bearer capability is when the calling system requests channel communication attributes at the start of the call, through which to communicate. |
| 102: 'Recovery on Timer Expiry' | Indicates that a procedure has been initiated by the expiration of a timer in association with error handling procedures. This is often associated with NAT problems. |
| 111: 'Protocol Error, Unspecified' | Reports a protocol error event only when no other cause in the protocol error class applies. |
| 127: 'Interworking, Unspecified' | Indicates that an interworking call (usually a call to SW56 service) has ended. |