What does HRESULT 0x80EE002C (RTC_E_LOCAL_PHONE_NEEDED) mean?

RTC_E_LOCAL_PHONE_NEEDED

What RTC_E_LOCAL_PHONE_NEEDED means in RTC

This code belongs to creating or enabling an XML profile that defines user identity, servers, transports, authentication, and supported session types: the selected phone-service operation requires a local telephone number that the profile does not provide.

For correlation, retain 0x80EE002C in the RTC interface facility 0xEE together with this result; generic HRESULT text can otherwise hide the protocol family and the exact RTC branch.

The quickest way to localize this result is to inspect session type, profile user data, local-number normalization, and gateway requirements; the important boundary is that a SIP user URI cannot always substitute for the PSTN callback number.

Protocol and object state

Interpreting this result requires both of these facts: CreateProfile validates the provisioning schema and cross-field constraints; a field can be present yet still be unusable with the chosen transport or role; also, the result branch assumes that The enabled profile selected for a call must support both the destination and the requested session type.

How to prove the condition

1. Use protocol and object evidence to inspect session type, profile user data, local-number normalization, and gateway requirements.
2. Confirm the distinction that a SIP user URI cannot always substitute for the PSTN callback number.
3. Start a fresh operation after you provision and validate the local number according to the service’s numbering plan, and compare its final state with the failing run.

Minimum incident record

• Code-specific proof: inspect session type, profile user data, local-number normalization, and gateway requirements.
• Owning object: user URI and profile key hash.
• Wire evidence: server role/address/transport.
• Lifecycle state: authentication method.

Actions that do not address this condition

• Do not log passwords or provisioning secrets from profile XML.
• Do not insert placeholder values solely to pass schema validation.

Correct application response

To correct this, provision and validate the local number according to the service’s numbering plan.

Example: A phone-to-phone service request has a destination number but no number for the originating leg.

Nearby failure modes

Technical references

• IRTCClientProvisioning::CreateProfile.
• IRTCProfile server fields.
• Microsoft RTC return constants.
• SIP and TEL URLs.