| Previous | Next |
| OLE_E_NOCONNECTION | OLE_E_NOTRUNNING |
TAPI_E_INVALIDMEDIATYPE
TAPI media type is invalid for the operation
TAPI_E_INVALIDMEDIATYPE is HRESULT 2147745796 (0x80040004) from TAPI 3.0. The documented description is “The MEDIATYPE passed in to this method was invalid.” The result belongs to call creation, terminal selection, or stream configuration using a media-type value. This HRESULT is most useful when tied to the method and lifecycle phase where the supplied media type is malformed, unsupported by the address, or inappropriate for the selected method.
This result means that the supplied media type is malformed, unsupported by the address, or inappropriate for the selected method.
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 must distinguish caller, runtime, provider, and backing resource while testing whether the supplied media type is malformed, unsupported by the address, or inappropriate for the selected method.
Typical causes and interpretation
The immediate contract boundary is specific: the supplied media type is malformed, unsupported by the address, or inappropriate for the selected method. Common cause branches include the following:
- An invalid bit combination is used.
- The address supports audio but the caller requests video only.
- Legacy and TAPI 3 media identifiers are mixed.
Confirm the cause branch that explains why the supplied media type is malformed, unsupported by the address, or inappropriate for the selected method by using call arguments, object state, metadata, device information, or provider traces.
Correct handling and recovery
The primary recovery is to derive the media type from address capabilities and pass only the documented combination for that operation. The failure report should capture the relevant state during call creation, terminal selection, or stream configuration using a media-type value so it is clear why the supplied media type is malformed, unsupported by the address, or inappropriate for the selected method.
The owner of it must define idempotency, cancellation, attempt limits, and reconciliation for the failed call creation, terminal selection, or stream configuration using a media-type value.
Practical scenario
A call is created on a modem address with a video media flag; the client retries with the provider-reported audio or datamodem type.
Difference from related HRESULTs
TAPI_E_NOTSUPPORTED may reject the method generally; it identifies the media-type argument
Developer and administrator guidance
Use a controllable service provider or simulator to cover state races, capability differences, device removal, cancellation, and provider restart.
Broad permission or compatibility changes are inappropriate unless evidence for the supplied media type is malformed, unsupported by the address, or inappropriate for the selected method points to that layer.
References
Looking for a different code? Search another status or error code.