| Previous | Next |
| OLE_E_CANT_BINDTOSOURCE | OLE_E_STATIC |
TAPI_E_DIALMODIFIERNOTSUPPORTED
Dial-string modifier is not supported
TAPI_E_DIALMODIFIERNOTSUPPORTED is HRESULT 2147745802 (0x8004000A) from TAPI 3.0. AllStat describes it as “The dial modifier is not supported.” The result belongs to dialing or creating a call with provider-specific or standard dial modifiers. Interpret this result at the native boundary before a wrapper hides the condition that the destination string contains a modifier the selected address or service provider cannot interpret.
The decisive meaning of this result is that the destination string contains a modifier the selected address or service provider cannot interpret. The severity bit does not decide handling; the controlling fact is that the destination string contains a modifier the selected address or service provider cannot interpret. The symbol it is useful only when tied to the method and lifecycle phase where the destination string contains a modifier the selected address or service provider cannot interpret.
Where the result appears
- This result can surface in a TAPI 3 address, call-control, terminal, stream, conference, dialing, or completion-management code.
- map the failure to one concrete operation among ITTAPI, ITAddress, ITBasicCallControl, ITCallInfo, terminal and stream interfaces, provider events, and asynchronous request state.
- Preserve provider name and version, address and call IDs, device class, media type, privilege, current address and call states, and asynchronous request ID before releasing or replacing the object that returned this result.
An incident record for this HRESULT must distinguish caller, runtime, provider, and backing resource while testing whether the destination string contains a modifier the selected address or service provider cannot interpret.
Typical causes and interpretation boundary
The immediate contract boundary is specific: the destination string contains a modifier the selected address or service provider cannot interpret. Common cause branches include the following:
- A modem-only pause or wait character is used on VoIP.
- The provider does not support partial dialing.
- Country or location translation introduced an unsupported modifier.
Confirm the cause branch that explains why the destination string contains a modifier the selected address or service provider cannot interpret by using call arguments, object state, metadata, device information, or provider traces.
Correct handling and recovery
The primary recovery is to normalize the destination for the selected provider and remove only modifiers that are not semantically required. The result failure report should expose enough dialing or creating a call with provider-specific or standard dial modifiers state to understand why the destination string contains a modifier the selected address or service provider cannot interpret without a production debugger.
A UI loop must not repeat it without refreshing the state behind “the destination string contains a modifier the selected address or service provider cannot interpret” and checking for prior side effects. Reconcile persistent, remote, device, or ownership state before repeating it.
Practical scenario
A SIP address receives a modem comma-pause sequence; provider-aware normalization sends the digits without the unsupported pause token. Record the decisive state for this HRESULT and verify recovery on a fresh object or request generation.
Difference from related HRESULTs
TAPI_E_INVALADDRESS says the address itself is invalid; it isolates an unsupported modifier within it Tests and telemetry should preserve that boundary for this HRESULT.
Developer and administrator guidance
Developers handling it should make object lifetime and state transitions explicit, preserve the native HRESULT, and keep cleanup paths safe when initialization or output is partial. Use a controllable service provider or simulator to cover state races, capability differences, device removal, cancellation, and provider restart.
Dashboards should keep it distinct and attach dimensions that can prove or disprove: the destination string contains a modifier the selected address or service provider cannot interpret. Repair for this HRESULT should target only the evidence-backed component, provider, document, device, or configuration.
References
- Microsoft: TAPI_E constants
- Microsoft: ITAddress::CreateCall
- Microsoft: ITBasicCallControl
- Microsoft: TAPI 3 reference
Looking for a different code? Search another status or error code.