| Previous | Next |
| TAPI_E_REQUESTQUEUEFULL | TAPI_E_DESTNOANSWER |
TAPI_E_DESTBUSY
The called number is busy
TAPI_E_DESTBUSY is HRESULT 2147745844 (0X80040034) from Tapi3err.h. AllStat describes it as “The called number is busy.” The result normally appears while placing a call when the remote endpoint or network returns busy. Its useful interpretation is precise: the busy destination is not valid for the exact provider, object, method, or lifecycle state that consumed it.
Preserve this result at the native boundary instead of flattening it into a generic exception. The symbol identifies the busy destination as the decisive part of the failed contract, but the owning layer may still be the application, Windows, a TAPI or media service provider, a remote switch, a device, or a COM data source. Correct handling starts by recording who produced the value and who rejected it.
Owning component and lifecycle
- This result belongs to TAPI 3 address, call-control, phone, terminal, media-provider, request, or call-center processing.
- Associate this result with one concrete native method among ITTAPI, ITAddress, ITBasicCallControl, ITCallInfo, ITStream, ITTerminal, ITPhone, provider events, and Assisted Telephony.
- Before releasing objects after this result, retain provider identity, object generation, current state, requested transition, and the event sequence surrounding placing a call when the remote endpoint or network returns busy.
When the application constructed the busy destination, it usually calls for caller-side validation. When enumeration or an event supplied it, it more often points to stale lifetime, provider replacement, device removal, configuration drift, or cross-session reuse. The ownership distinction for this HRESULT prevents a broad repair from masking the real defect.
Plausible explanations
- It commonly reflects a network or switch busy indication before the call reaches an alerting state.
- A destination may return it because every line appearance, trunk, hunt-group member, or endpoint session is occupied.
- A fast-busy or congestion condition can be mapped to it by a provider, so retain the provider cause instead of assuming the subscriber pressed decline.
- Local retry logic can amplify it when it redials immediately and never gives the remote resource time to become free.
Choose among those branches only after comparing the failed busy destination with live capabilities or objects obtained from the same provider generation. A well-formed value can still be invalid because its scope, owner, state, or lifetime no longer matches the operation.
What to log before cleanup
- Record it, 0X80040034, the native method, operation ID, elapsed time, process and thread IDs, application build, architecture, and COM apartment.
- capture destination, address, call ID, provider disconnect code, attempt time, retry policy, and whether call waiting is available.
- Keep provider version, address/call/phone/terminal identities, current state, requested state, object generation, and the first lower-level error that preceded it.
- Redact telephone numbers, credentials, recordings, user-user data, and directory attributes from it telemetry while retaining lengths, types, hashes, ranges, capability flags, and opaque correlation identifiers.
A useful incident can answer whether the busy destination came from configuration, enumeration, user input, cached state, or a provider callback. The result record should also show whether the operation succeeds with a newly enumerated object or freshly validated value.
Reproduction and diagnosis
- Capture it together with the exact dial or call-creation method and the provider disconnect or call-state cause.
- Verify that number translation completed and that the call reached the network; a malformed destination should be classified separately from a busy response.
- Compare ordinary busy, fast-busy, trunk congestion, and provider-capacity indications rather than treating every tone as the same endpoint state.
- Measure the interval and count of previous attempts to determine whether application redial policy is maintaining the busy condition.
- Reproduce it with one destination and an operator-observed endpoint, then confirm that a later free line produces a different call-state sequence.
Handling the result
The evidence-based correction for this HRESULT is to end the attempt cleanly and retry only according to user intent or an explicit bounded policy. After it follows a provider, device, service, or configuration change, obtain a fresh object because an old interface or opaque identifier may remain invalid after recovery.
An automatic retry of it needs a bounded count, an idempotency rule, and a measurable changed-state predicate. User-visible handling of it should describe the actionable condition—invalid data, wrong state, missing resource, unavailable service, or policy refusal—rather than displaying only the HRESULT.
Practical example
For example, an outbound dialer reaches a busy analog line and schedules a later attempt instead of redialing immediately The application should log the failed busy destination, provider and object generation, native method, and state-changing event, then verify recovery with a newly obtained object instead of reusing the instance that returned it.
Related-result boundary
TAPI_E_DESTNOANSWER means ringing without answer; it means the network reported busy Keep that distinction when building dashboards and exception mappings for this HRESULT; otherwise input defects, lifecycle races, capacity limits, service outages, and final call outcomes collapse into one misleading category.
Long-term prevention
Code that handles it should scope provider-defined identifiers to their creating session, serialize state transitions, validate caller-owned structures at the native boundary, and keep cleanup safe after partial initialization. Tests for this HRESULT should cover cancellation, provider restart, device removal, stale cached objects, capability changes, wrong user context, and both successful and failed recovery.
Operational repair for this HRESULT should target only the component identified by evidence: the Telephony service, service provider, COM server, device, configuration record, application package, or remote system. Copying arbitrary DLLs or broadly deleting registration data can create additional failures without correcting the original busy destination.
References
- Microsoft: TAPI_E constants — official Microsoft documentation used to interpret it.
- Microsoft: lineMakeCall
- Microsoft: TAPI 3.1 Reference
- Microsoft: Telephony API interfaces
Looking for a different code? Search another status or error code.