| Previous | Next |
| RTC_E_NO_WATCHER | RTC_E_NO_TRANSPORT |
RTC_E_NO_REALM
What the RTC value marks: RTC_E_NO_REALM
The useful interpretation of this result is narrower than “SIP error”; within creating or enabling an XML profile that defines user identity, servers, transports, authentication, and supported session types, it means the profile or authentication context lacks a realm required to select credentials.
The stored value is 0x80EE0056 in the RTC interface facility 0xEE; keep both forms in telemetry so COM error wrapping does not erase whether RTC produced an interface result, mapped a SIP response, or surfaced a PINT outcome.
Collect enough state to inspect enabled server entries, challenge realm, profile realm mapping, and credential store keys; the result evidence should demonstrate why missing realm is configuration/selection failure before verifying a password.
A safe diagnostic sequence
- Use protocol and object evidence to inspect enabled server entries, challenge realm, profile realm mapping, and credential store keys.
- Confirm the distinction that missing realm is configuration/selection failure before verifying a password.
- Start a fresh operation after you provision the correct realm and bind credentials to it without using a catch-all secret, and compare its final state with the failing run.
Evidence that separates the cause
- Code-specific proof: inspect enabled server entries, challenge realm, profile realm mapping, and credential store keys.
- Identity and target: session type and party attributes.
- State at production: redacted profile
XMLpath/version. - Timing and ordering: user URI and profile key hash.
Protocol and object state
| RTC area | RTC provisioning profile validation |
|---|---|
| Objects to correlate | profile XML, provision/user/server/session elements, registrar and proxy roles, transport and authentication method |
| Condition to prove | the profile or authentication context lacks a realm required to select credentials |
| Safe corrective direction | provision the correct realm and bind credentials to it without using a catch-all secret |
CreateProfile validates the provisioning schema and cross-field constraints; a field can be present yet still be unusable with the chosen transport or role. The enabled profile selected for a call must support both the destination and the requested session type.
Related RTC results
RTC_E_LOCAL_PHONE_NEEDED | the selected phone-service operation requires a local telephone number that the profile does not provide |
|---|---|
RTC_E_INVALID_PORTRANGE | the configured RTC media/listening port range is malformed or outside accepted limits |
RTC_E_PROFILE_NO_USER | the provisioning profile omits the required user field |
How to handle the result
The appropriate response to this result is not a blanket reconnect. Instead, provision the correct realm and bind credentials to it without using a catch-all secret, while preserving ownership of cleanup and any bounded retry.
Example: An imported profile omits realm data and the client cannot select credentials for REGISTER.
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.
Technical references
Looking for a different code? Search another status or error code.