ADCT — Auto Disconnected Timeout

What ADCT Means

Similar to ADC but specifically indicates the call timed out at the Asterisk or carrier level with a disconnect signal — the call was not answered AND the carrier indicated the number may be problematic.

When This Status Is Set

ADCT is assigned when VICIdial’s dial_timeout expires and the carrier response accompanying the timeout carries disconnect-related signaling rather than a standard no-answer indication. This typically occurs when the carrier returns a SIP 408 (Request Timeout) alongside supplementary headers suggesting the destination number may be decommissioned, ported, or unreachable at the network level. Unlike a clean NA where the phone simply rang without pickup, ADCT implies the carrier could not complete the call path to the destination at all. The status is written to vicidial_list automatically and logged in vicidial_log with the corresponding term_reason, giving you the data needed to distinguish between genuine no-answers and network-level failures.

Impact on List Management

Exclude ADCT from your dial_status_filter by default — these leads consume trunk time during the full dial_timeout window without producing a contact, making them expensive in terms of dialer throughput. However, ADCT is more ambiguous than a hard ADC or DC because the disconnect indication came alongside a timeout rather than an explicit out-of-service signal. In some cases, carrier routing issues, number portability delays, or temporary network congestion can produce ADCT outcomes on numbers that are actually still active. For this reason, consider running ADCT leads through a batch phone validation service before permanently suppressing them. Track ADCT volumes per carrier trunk in vicidial_carrier_log — a sudden ADCT spike on a single trunk usually indicates a provider routing problem rather than a list quality issue.

Best Practices

• Do not include ADCT in dial_status_filter for standard campaign recycling

• Distinguish ADCT from standard DC — ADCT may recover if the carrier routing issue resolves, so do not permanently suppress without validation

• Batch-verify ADCT numbers against a phone lookup API before final suppression to avoid discarding still-active numbers

• Monitor ADCT rate by SIP trunk to detect carrier-side routing degradation early

• If ADCT rate spikes across all trunks simultaneously, investigate whether your dial_timeout setting is too aggressive for the destination geography

Admin Configuration

ADCT is a system-level status defined in Admin → System Statuses with callable set to N and human_answered set to N. It does not appear in agent disposition screens since it is auto-assigned by the dialer. To analyze ADCT trends, query vicidial_log filtered by status = 'ADCT' and join against vicidial_carrier_log for carrier-level detail including the specific SIP response code and carrier route used. The dial_timeout value that influences when ADCT fires is configured per-campaign under Campaign Detail → Dialing Options, typically set between 26 and 60 seconds depending on carrier and geography. For operations that want to reclassify ADCT leads after validation, use Admin → List Modification to batch-update verified-active numbers from ADCT to NEW status so they re-enter the dial flow.

ViciStack’s List Management module monitors disposition distribution in real time — automatically adjusting recycling logic, dial_status_filter priorities, and hopper fill strategies based on how your dispositions are trending. No manual SQL, no spreadsheet audits.