| Previous | Next |
| RTC_E_DUPLICATE_REALM | RTC_E_PORT_MAPPING_UNAVAILABLE |
RTC_E_POLICY_NOT_ALLOW
What RTC_E_POLICY_NOT_ALLOW means in RTC
The legacy RTC Client API reports this result while working with applying client policy, authorized domains, transport requirements, and negotiated media security levels; the precise meaning of it is effective RTC policy explicitly prohibits the requested action, not merely that a call or registration failed.
The numeric form of this result is 0x80EE0044 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.
Evidence should show that you record the action, selected profile, effective policy source/value, and user or machine scope; the diagnostic distinction is that policy denial is intentional and should not trigger network or credential retries.
Minimum incident record
- Code-specific proof: record the action, selected profile, effective policy source/value, and user or machine scope.
- Owning object: peer capability result.
- Wire evidence: transport selected for signaling.
- Lifecycle state: policy name/source and effective value.
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 | effective RTC policy explicitly prohibits the requested action |
| Safe corrective direction | change the request or policy through its authoritative management channel |
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.
Correct application response
To correct this, change the request or policy through its authoritative management channel.
Example: A managed client attempts a media feature disabled by enterprise RTC policy.
How to prove the condition
- Test the competing explanation explicitly, because policy denial is intentional and should not trigger network or credential retries.
- Apply the targeted fix — change the request or policy through its authoritative management channel — and validate both protocol completion and object cleanup.
Nearby failure modes
RTC_E_SECURITY_LEVEL_NOT_DEFINED | the application has not defined the media security level required for the operation |
|---|---|
RTC_E_DUPLICATE_REALM | more than one enabled profile defines the same authentication realm in a conflicting way |
RTC_E_UDP_NOT_SUPPORTED | the requested feature or profile combination is incompatible with at least one server using UDP transport |
Actions that do not address this condition
- Do not downgrade security without an explicit product policy and user-visible result.
- Do not bypass policy by editing generated profile XML in memory.
Technical references
Looking for a different code? Search another status or error code.