| Previous | Next |
| TAPI_E_DESTNOANSWER | TAPI_E_REQUESTFAILED |
TAPI_E_DESTUNAVAIL
The called number could not be reached
TAPI_E_DESTUNAVAIL is HRESULT 2147745846 (0X80040036) from Tapi3err.h. AllStat describes it as “The called number could not be reached.” The result normally appears while placing a call when routing, numbering, or network state cannot reach the destination. Its useful interpretation is precise: the unavailable 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 unavailable 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 routing, numbering, or network state cannot reach the destination.
When the application constructed the unavailable 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 can indicate an unassigned number, invalid route, unavailable gateway, or destination outside the provider routing plan.
- Loss of network registration, trunk service, DNS or SIP resolution, or address availability can prevent the call from reaching an alerting endpoint.
- Number translation can create it when prefixes, country rules, outside-line access, or canonical formatting select a nonexistent route.
- A provider may expose a remote network cause through it; preserve that cause to distinguish permanent numbering errors from temporary infrastructure outages.
Choose among those branches only after comparing the failed unavailable 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, 0X80040036, the native method, operation ID, elapsed time, process and thread IDs, application build, architecture, and COM apartment.
- capture canonical and dialable destination, provider cause, route, address availability, location, and network registration.
- 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 unavailable 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 with both canonical and dialable forms of the destination, the selected address, and the provider route or cause code.
- Verify current provider registration, address availability, gateway or trunk state, and any name-resolution step used before call setup.
- Compare the translated number with a known-working route and test prefixes, location rules, and international formatting independently.
- Determine whether the provider classifies the destination as unassigned, unreachable, out of service, or temporarily unavailable.
- Reproduce it through one alternate route or provider to separate destination numbering from local infrastructure failure.
Handling the result
The evidence-based correction for this HRESULT is to verify number translation and network registration, then retry only after the route or destination can change. 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, a SIP provider has no route for a malformed international number; correcting canonical form restores routing The application should log the failed unavailable 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_ADDRESSBLOCKED is policy denial; it is reachability or routing failure 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 unavailable 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.