What does HRESULT 0x80EE0014 (RTC_E_INVALID_ADDRESS_LOCAL) mean?

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: The Local Address is invalid, check the profile

Previous	Next
RTC_E_DESTINATION_ADDRESS_LOCAL	RTC_E_DESTINATION_ADDRESS_MULTICAST

RTC_E_INVALID_ADDRESS_LOCAL

Where the state changes: `RTC_E_INVALID_ADDRESS_LOCAL`

Diagnosis begins inside resolving a SIP destination and establishing UDP, TCP, TLS, or proxy transport before a transaction can proceed, where the relevant condition for this HRESULT is the local address configured in the RTC profile cannot be used for the requested transport or session.

The numeric form of this result is 0x80EE0014 in the RTC interface facility 0xEE; an exception translator handling it should preserve this value before converting it into application-facing call or presence states.

The quickest way to localize this result is to record interface state, address family, binding ownership, transport, and profile source; the important boundary is that this is a local bind/configuration problem rather than an invalid remote SIP URI.

Telemetry and packet evidence

Code-specific proof: record interface state, address family, binding ownership, transport, and profile source.
Addressing context: DNS query type and answers.
RTC callback state: local/remote socket tuple.
Transaction boundary: proxy tunnel response.
Media or profile detail: SIP transaction timer and retransmit count.

Protocol and object state

RTC area	`SIP` transport and reachability
Condition to prove	the local address configured in the RTC profile cannot be used for the requested transport or session
Objects to correlate	`SIP` URI, proxy/registrar address, DNS results, socket, `HTTP` CONNECT tunnel, transaction timer
Safe corrective direction	choose an active local interface/address and regenerate the profile or listen registration

Actions that do not address this condition

Do not switch transports without checking profile policy and authentication constraints.
Do not retry rapidly across every resolved address without preserving the failure phase.

Step-by-step isolation

Collect enough evidence to record interface state, address family, binding ownership, transport, and profile source.
Test the competing explanation explicitly, because this is a local bind/configuration problem rather than an invalid remote SIP URI.
Apply the targeted fix — choose an active local interface/address and regenerate the profile or listen registration — and validate both protocol completion and object cleanup.

Recovery

To correct this, choose an active local interface/address and regenerate the profile or listen registration.

Example: A laptop profile retains an address from a disconnected network adapter.

Comparison with adjacent codes

`RTC_E_DESTINATION_ADDRESS_LOCAL`	the resolved destination points back to the local machine in a path that forbids self-targeting
`RTC_E_SIP_TRANSPORT_NOT_SUPPORTED`	the requested SIP transport is not implemented or allowed by the RTC profile/platform path
`RTC_E_SIP_TLS_FAIL`	the TLS transport failed outside the more specific tunnel, timeout, certificate, or compatibility cases

Technical references

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