What SIP Cause 18 (request timeout) means on your VICIdial calls

You pulled a disconnect breakdown and a chunk of your calls came back as HUC18. That code is a Cause 18 hangup, which maps to SIP 408 Request Timeout. In plain terms: the dialer sent the call, waited, and never heard a final answer signal back in time, so it gave up.

A Cause 18 is a kind of Hangup cause — the reason a call ended. VICIdial only writes the granular HUC code when Enhanced Disconnect Logging is turned up, so seeing HUC18 at all means you are logging the detail correctly. The number after HUC is just the cause: 18 here.

What is actually happening

The dialer hands the call to your Carrier, which routes it toward the destination. If no final response (answer, busy, reject) comes back before the ring timer expires, you get a timeout. That is the 408. It is a no-answer-in-time event, not an active rejection.

sequenceDiagram
  participant D as VICIdial dialer
  participant C as Carrier
  participant F as Far end
  D->>C: INVITE
  C->>F: INVITE
  F-->>C: no final response
  C-->>D: 408 Request Timeout
  D->>D: log HUC18 Cause 18

Three common stories sit behind a Cause 18: a dead or unreachable number where nothing ever picks up; a slow carrier or route that takes longer than your ring window allows; or a plain ring-no-answer where the phone rang out. They look identical in the code, so you separate them by pattern, not by one call.

What to check, in order

1. Compare your HUC18 rate against your overall no-answer rate. A few percent is normal phone behaviour. A sudden jump usually points at a list or a route, not at the box.
2. Check whether HUC18 clusters on one list or one lead source. If a single fresh list is full of timeouts, the data is stale or the numbers are dead.
3. Look at your Dial timeout setting. If it is set very short, slow-answering destinations time out before they ever get a chance to pick up, inflating Cause 18.
4. If HUC18 spikes across every list at once, the route is the suspect. Pull the per-call detail and confirm the 408 is coming back from the carrier and not from a local ring window.
5. Map the 408 back to a SIP response code trace on a few sample calls. That tells you whether the timeout fired on your side or upstream.

Cause 18 is rarely a system fault on its own. It is the dialer telling you a destination went quiet. Treat a steady low rate as background noise and a spike as a signal to look at one list or one route.

For the wider map of disconnect codes and where each report lives, start with the troubleshooting playbook. To see exactly where these codes land in your reporting, read how to read the hangup cause report. If you would rather not chase timeouts on a self-managed install, VICIfast runs the box and the carrier wiring for you → see plans and pricing.