| Previous | Next |
| RTC_E_SIP_AUTH_TIME_SKEW | RTC_E_MEDIA_DISABLED |
RTC_E_INVALID_REGISTRATION_STATE
What the RTC value marks: RTC_E_INVALID_REGISTRATION_STATE
Read this result as an RTC state-machine result: at this point in enabling a profile, registering the user URI, refreshing bindings, and interpreting server-driven account changes, the requested registration operation is illegal for the profile’s current registration state.
Log this result as 0x80EE006D in the RTC interface facility 0xEE, not only as a signed decimal; the facility distinguishes local RTC validation from a response status mapped by the stack.
Before changing configuration, record enabled profile, registration state, pending REGISTER, last response, and requested transition; the RTC codes surrounding this result are not equivalent because this is local state sequencing, not necessarily server rejection.
A safe diagnostic sequence
- Use protocol and object evidence to record enabled profile, registration state, pending
REGISTER, last response, and requested transition. - Confirm the distinction that this is local state sequencing, not necessarily server rejection.
- Start a fresh operation after you wait for the current
REGISTERoperation or perform the documented enable/disable sequence, and compare its final state with the failing run.
Evidence that separates the cause
- Code-specific proof: record enabled profile, registration state, pending
REGISTER, last response, and requested transition. - Identity and target:
REGISTERCall-ID and CSeq. - State at production: Contact and requested expiration.
- Timing and ordering: final response and reason data.
Protocol and object state
| RTC area | SIP registration state |
|---|---|
| Objects to correlate | REGISTER client transaction, Contact binding, registrar, expiration, account and profile state |
| Condition to prove | the requested registration operation is illegal for the profile’s current registration state |
| Safe corrective direction | wait for the current REGISTER operation or perform the documented enable/disable sequence |
A registration result applies to a user binding and registrar, not automatically to existing dialogs or local media devices. Deactivation, rejection, and unregistration describe different server decisions and should produce different user messaging and retry policy.
Related RTC results
RTC_E_REGISTRATION_UNREGISTERED | the server removed this registration because the same user registered elsewhere or another binding policy took precedence |
|---|---|
RTC_E_REGISTRATION_DEACTIVATED | the registrar deactivated the binding because the user is being moved or reprovisioned |
RTC_E_REGISTRATION_REJECTED | the registrar rejected registration because the account or SIP identity is no longer accepted |
How to handle the result
To correct this, wait for the current REGISTER operation or perform the documented enable/disable sequence.
Example: Code tries to unregister while initial registration is still pending.
Actions that do not address this condition
- Do not loop on REGISTER when the server indicates an account or identity change.
- Do not discard the old binding state before recording why it ended.
Technical references
Looking for a different code? Search another status or error code.