HRESULT 0x80EE007E (RTC_E_UDP_NOT_SUPPORTED): meaning and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: This feature is not supported when one of the server in profile has UDP transport

Previous	Next
RTC_E_SECURITY_LEVEL_ALREADY_SET	RTC_E_SIP_REFER_OPERATION_PENDING

RTC_E_UDP_NOT_SUPPORTED

What the RTC value marks: `RTC_E_UDP_NOT_SUPPORTED`

The operational meaning of this result is tied to applying client policy, authorized domains, transport requirements, and negotiated media security levels: the requested feature or profile combination is incompatible with at least one server using UDP transport.

The machine-readable identity of this result is 0x80EE007E in the RTC interface facility 0xEE; the result identity matters because RTC uses separate facilities for API conditions, SIP final responses, and PINT service statuses.

The first useful check is to identify the UDP server entry, requested roaming/authentication feature, and cross-field rule. The result must be separated from nearby conditions because UDP itself may be supported for basic signaling while this particular feature is not.

Protocol and object state

RTC area	RTC policy and media-security
Objects to correlate	enabled profile, policy source, authorized domain, media type, local and remote security level
Condition to prove	the requested feature or profile combination is incompatible with at least one server using `UDP` transport
Safe corrective direction	switch the affected server to `TCP`/`TLS` or disable only the incompatible feature

Policy refusal is distinct from transport failure: the requested operation may be technically possible but prohibited for the current profile or platform. Media security must be compatible for each participating endpoint and should not be silently downgraded after negotiation begins.

Evidence that separates the cause

Code-specific proof: identify the UDP server entry, requested roaming/authentication feature, and cross-field rule.
Identity and target: policy name/source and effective value.
State at production: profile/server domain.
Timing and ordering: requested media security level.

Related RTC results

`RTC_E_DUPLICATE_REALM`	more than one enabled profile defines the same authentication realm in a conflicting way
`RTC_E_SECURITY_LEVEL_NOT_COMPATIBLE`	local and remote media security requirements have no compatible negotiated level
`RTC_E_SECURITY_LEVEL_ALREADY_SET`	the media security level has already been fixed for this media type and cannot be changed in the current session state

A safe diagnostic sequence

Collect enough evidence to identify the UDP server entry, requested roaming/authentication feature, and cross-field rule.
Test the competing explanation explicitly, because UDP itself may be supported for basic signaling while this particular feature is not.
Apply the targeted fix — switch the affected server to TCP/TLS or disable only the incompatible feature — and validate both protocol completion and object cleanup.

How to handle the result

To correct this, switch the affected server to TCP/TLS or disable only the incompatible feature.

Example: A roaming profile includes a UDP registrar even though presence roaming requires a connection-oriented transport.

Actions that do not address this condition

Do not bypass policy by editing generated profile XML in memory.
Do not downgrade security without an explicit product policy and user-visible result.

Technical references

Looking for a different code? Search another status or error code.