Infinity Campus

Campus | Why are my calls failing?

Written by Infinity | Nov 19, 2026, 11:26:46 PM

Why are calls failing? This article explains the common reasons for call fails, and how to pull a call state report from our API to find the cause.

As with any business that receives incoming calls, you may receive call fails. A key benefit of call tracking is that it shows any call fails that have been happening for a while. As these calls never reached your phone system, you would otherwise be unaware of them. Infinity is equipped to identify any issues and respond where appropriate.

Why are calls failing: common causes

Common reasons for call fails within the Infinity Platform are:

  • Internal phone system issues with the number we are connecting the call through to. This can be due to the phone system rejecting our calls.
  • Unanswered calls due to busy periods in the working day, when there are not enough call handlers to answer all incoming calls. This can be a good indication of staff shortages.
  • The caller hanging up before the call is connected.

To rule out your phone system entirely, we recommend pulling a call state report from our API. Here is an article which explains call state reports in more detail.

Why are calls failing in the call state report?

If you are experiencing call fails within the Infinity Platform, or unusual call behaviour, the call state report is a good report to start with to find the cause.

Here are two useful reports for you to pull:

Text
https://api.infinitycloud.com/reports/v2/triggers/calls?igrp=XXXX&sort[]=triggerDatetime-desc&limit=50000&format=csv&display[]=triggerDatetime&display[]=srcPhoneNumber&display[]=callState
Text
https://api.infinitycloud.com/reports/v2/triggers/calls?igrp=XXXX&sort[]=triggerDatetime-desc&limit=50000&format=csv&display[]=triggerDatetime&display[]=srcPhoneNumber&display[]=callState&display[]=txr&display[]=destPhoneNumber&display[]=ringTime

Update XXXX with your installation ID (IGRP ID).

You can also add other parameters to suit your needs. See our API documentation if you would like the report customised to your own style.

Once the report has run, you will see the call states. These are the most common call states:

Call state Description
NO_ANSWER This cause is used when the called party has been alerted but does not respond with a connect indication within a prescribed period of time.
NO_USER_RESPONSE This cause is used when a called party does not respond to a call establishment message with either an alerting or connect indication within the prescribed period of time allocated.
UNALLOCATED_NUMBER This cause indicates that the called party cannot be reached because, although the called party number is in a valid format, it is not currently allocated (assigned). We get this from our carrier, who in turn get it from BT and upstream telcos.
USER_BUSY This cause is used to indicate that the called party is unable to accept another call because the user busy condition has been encountered. This cause value may be generated by the called user or by the network. In the case of user determined user busy, the user equipment is compatible with the call.
ORIGINATOR_CANCEL When the caller hangs up before being connected, this is probably because they have been waiting too long. Occasionally this may be due to Post Dial Delay (PDD).
PROTOCOL_ERROR This cause is used to report a protocol error event only when no other cause in the protocol error class applies. This too may be indicative of an upstream carrier issue or a problem routing calls to the customer, although they do not happen often.
NORMAL_CLEARING_A This is caused when the caller hangs up and is a normal call state.
NORMAL_CLEARING_B This is caused when the operator hangs up and it is a normal call state, for example the operator rejecting the call before it is answered on the handset.
NORMAL_TEMPORARY_FAILURE_B This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long period of time, for example the user may wish to try another call attempt almost immediately. The B means it is the B leg of the call that is causing the problem, the leg going to the customer's call centre, and not the caller.

If there is a call state within your report that is not listed above, contact our Support Team.