--- title: System Dispositions in Exotel Contact Center slug: contact-center/system-dispositions-in-exotel-contact-center docTags: createdAt: 2025-12-28T17:40:55.791Z --- System Dispositions are those which are generated by the system automatically. The calls to which these dispositions are applicable, are disposed of by the system itself. # System Defined Dispositions When a call disconnects or the agent is not able to dispose of the call due to any of the following reasons (called Cause codes), then the system will provide the dispositions automatically. The dispositions are known as System Defined Dispositions. | ******Disposition Code****** | ******Meaning****** | ******Cause Codes****** | ******Call Direction Types****** | | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | | BUSY | If the customer is having the call from another source and will not be able to attend the agent's call, then the call disposed of with this disposition. It happens because of the following reasons.
1) User Busy 2) User not responding. 3) No answer from User. | - setup.timeout - busy - provider.temp.failure - number.failure - Provider.failure | Outbound | | No\_ANSWER | If the call ring timed out, or the customer disconnected the call without receiving it, then the call is disposed of with this disposition. | Not attended | Outbound | | CONNECTED | If a call gets connected with the customer and the communication between the customer and agent sets up, then the call is disposed of with this disposition. | * setup.timeout * busy * normal.clearing * provider.temp.failure * number.failure * Provider.failure | All type of Calls | | CALL\_DROP | If a call is waiting in the ACD Node. but none of the agent is found free thus the call gets disconnected without having the communication with any agent, then the call is disposed of with this disposition. | - setup.timeout - busy - normal.clearing - provider.temp.failure - number.failure - Provider.failure - Unknown | Inbound | | CALL\_HANGUP | If both the agent and the customer are connected on the call, but the call gets disconnect due to any issue, or the customer channel is up, then the call is disposed of with this disposition. | * hangup.job.timed.out * setup.timeout * busy * normal.clearing * provider.temp.failure * number.failure * provider.failure * Unknown | All type of Calls | | CALL\_NOT\_PICKED | If the agent does not answer the call or the call hangs up before answering to it, then the call is disposed of with this disposition. The possible reasons are listed hereinbelow.
1) The agent does not pick the call and ring times out. 2) The call hangs up before agent answers to it. | - setup.timeout - busy - normal.clearing - provider.temp.failure - number.failure - Provider.failure | Inbound, Outbound Auto Dial and Call Transfer. | | AMD | If the call gets disconnected due to customer channel is up, then the customer's channel will break and call will be disconnected and disposed of with this disposition. | | Outbound | | ATTEMPT\_FAILED | If the customer channel does not establish due to any of the following reasons, then the call is disposed of with this disposition.
1) The maximum call limit set by the administrator or the supervisor exceeded in the campaign. 2) Maximum call limit exceeded for allowed calls in the call context assigned to the campaign. 3) The call server is not established. 4) The call server is not reachable. 5) Preview call being canceled due to any of the reasons. 6) There is no free agent for the scheduled callbacks | | All type of Calls | | NUMBER\_FAILURE | If the call dialled to any number is hang-up due to any of the following reasons, then the call is disposed of with this disposition.
1) Number unassigned to any of the Queue. 2) There is no route to the specified transit network. 3) No route found to the destination. 4) Customer's Number has been changed. 5) The number dialed in the wrong format. 6) Multiple Choices arises. 7) The number has been moved permanently. 8) The number has been moved temporarily. 9) The customer is using Proxy network. 10) The possibility of alternative services. 11) The number is not Reachable 12) Bad Extension. 13) The customer has declined the call. 14) The number does not exist anywhere in the Ameyo System. | - number.failure - setup.timeout - provider.temp.failure - provider.failure | Outbound | | NUMBER\_TEMP\_FAILURE | If the call dialed to a number hang-up due to any of the following reasons, then the call is disposed of with this disposotion.
1) Call Rejected by the customer. 2) The facility by the provider rejects the calls. 3) Invalid call reference value. 4) Request Entity is too large. 5) Request-URI is too large. | | Outbound | | PROVIDER\_FAILURE | If the call hang-up due to the Provider failure because of any of the following reasons, then the call is disposed of with this disposition.
1) Channel unacceptable 2) Destination out of order 3) Access information discarded 4) Facility not subscribed 5) Outgoing call barred 6) Incoming call barred 7) Bearer capability not authorized 8) Bearer capability not available 9) Bearer capability not implemented 10) Call Facility not implemented 11) Incompatible destination 12) Message-Type does not exist or incorrect type of message 13) Bad Request from the client 14) Unauthorized number 15) Payment pending 16) Forbidden network 17) Method Not Allowed 18) Proxy Authentication Required 19) Unsupported Media Type 20) Unsupported URI Scheme 21) Channel is not acceptable by the client. 22) Undecipherable that is the recipient is not able to decrypt the message or MIME body. 23) The number is not implemented over the network. 24) Call version is not supported. | - busy - setup.timeout - provider.failure - provider.temp.failure | Outbound | | PROVIDER\_TEMP\_ FAILURE | If the call hang-up due to the Provider failure but will resolve after sometime due to any of the possible reasons, then the call is disposed of with this disposition.
1) Congestion in the circuit or channel 2) Network out of order 3) Temporary failure issue 4) Switching equipment Congestion 5) Requested channel not available 6) Pre-empted Network 7) Invalid / Unspecified message 8) The mandatory information element is missing 9) The wrong message entered 10) Request Timeout 11) Call or transaction does not exist 12) Loop detected in the network 13) Too Many Hops 14) Ambiguous Network 15) Request Terminated 16) Request Pending 17) Server Internal Error 18) Bad Gateway 19) Service Unavailable 20) The message is too large. | - number.failure - setup.timeout - provider.failure - provider.temp.failure - Licence Exhausted | Outbound | | SYSTEM\_ERROR | If the call gets connected successfully, but the customer channel disrupted unsuccessfully at the time of the call hangup or an error occurred at the customer channel end because of the following possible reasons, then the call is disposed of with this disposition.
1) Voice resource is not available. 2) Voice resource is not responding.Error received on requesting hangup on customer channel | | All type of Calls | | FAILED | If the call hangs up due to any unknown error. | - Busy - setup.timeout - provider.temp\_failure - provider.failure - number.failure | All type of Calls | | SIT\_REORDER | If the wrong number has been dialed or the number is not equal to the defined number format dialed (for example, less than 10 digits in the mobile number), then the call is disposed of with this disposition. | SIT Reorder | Outbound | | SIT\_NOCIRCUIT | If all circuits from which the call connects are busy, then the call is disposed of with this disposition. | | Outbound | | SIT\_INTERCEPT | If the customer's number changed or disconnected due to the unknown reason, then the call is disconnected with this disposition. | | Outbound | | Transfer to phone SIT\_VACANT | If the number is unassigned to any queue in Ameyo,. | | Outbound | | NOT\_TRIED | If the Supervisor churn some of those numbers from the Lead in Outbound Auto Dial that has to be dialed again, then the call made to these numbers will be disposed of with this disposition. | | Outbound | # System Generated User Dispositions The dispositions which will insert after those calls which are not completed due to any reason, then the system will insert the disposition automatically. When this scenario happens, the inserted call disposition is known as User disposition – set by System | **Disposition Code** | **Meaning** | **Suggested Call Types** | | ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ | | user.forced.logged.off | If the user logged off from his account while on the call, then the call is disposed of with this disposition. It may happen due to various reasons like server goes down or internet connectivity breaks down. | Inbound + Outbound | | entity.forced.clean.up | If the entity of the call gets cleaned-up forcedly, then the call is disposed of with this disposition. | Inbound + Outbound | | failed.association | In case of re-ACD, when the call call comes back to its previous ACD node, the disposition code for the previously associated user is marked as a failed association. | Inbound + Outbound | | wrap.timeout | The call will not get disposed of in the provided time; then the system set this disposition automatically. | Inbound + Outbound | | user.cancelled.preview | The agent canceled the call after watching the details of the customer, then this disposition is set. | Inbound + Outbound | | user.transferred.to.aq | If a call is transferred to the agent's queue by the previously assigned agent, then this call on behalf of the transferor (the agent who transferred it) is disposed of with this disposition. | Inbound + Outbound | | user.transferred.to.ivr | Upon call transfer from one campaign to another, if the customer disconnects the call from the IVR before the call gets connect to another Agent, then this call is disposed of with this disposition. | Inbound + Outbound | | user.transferred.to.campaign | If the call transferred to another campaign by the agent, and the previously assigned agent failed to dispose of the call successfully, then the call is disposed of with this disposition. | Inbound + Outbound | | entity.transferred.to.campaign | If the call transferred to another campaign from the nodeflow, then the call is disposed of with this disposition. | Inbound + Outbound |