| Previous | Next |
| RTC_E_SIP_AUTH_TYPE_NOT_SUPPORTED | RTC_E_INVALID_SIP_URL |
RTC_E_SIP_AUTH_FAILED
Operational meaning: RTC_E_SIP_AUTH_FAILED
This result is useful only when preserved with its producing phase; in selecting an allowed authentication method, validating the challenge realm, and establishing a protected SIP transport, it denotes the selected SIP authentication attempt was rejected or could not validate for the challenge.
The machine-readable identity of this result is 0x80EE0011 in the RTC interface facility 0xEE; the result identity matters because RTC uses separate facilities for API conditions, SIP final responses, and PINT service statuses.
The first useful check is to preserve scheme, realm, user identity, response status, nonce lifecycle, and credential source without secrets. The result must be separated from nearby conditions because authentication failure is separate from authorization refusal after successful identity verification.
Signals worth preserving
- Code-specific proof: preserve scheme, realm, user identity, response status, nonce lifecycle, and credential source without secrets.
- Correlation key: client/server UTC time and
TLSphase. - Protocol or object snapshot: 401 or 407 challenge source.
- Last completed transition: authentication scheme and realm.
- Expected output: credential identity without secret material.
Protocol and object state
| RTC area | SIP authentication and TLS identity |
|---|---|
| Condition to prove | the selected SIP authentication attempt was rejected or could not validate for the challenge |
| Objects to correlate | profile authentication method, challenge headers, realm, credential source, TLS certificate and tunnel |
| Safe corrective direction | correct credentials, realm mapping, or credential selection and cap prompts/retries |
RTC profile rules tie some authentication methods to TCP or TLS; Basic authentication requires TLS in the legacy API contract. A certificate failure, a challenge mismatch, and invalid credentials occur at different layers and need different remediation.
Verification workflow
- Start from
0x80EE0011, then find the method/event pair that first exposed it. - Keep the analysis at the right boundary: authentication failure is separate from authorization refusal after successful identity verification.
- After you correct credentials, realm mapping, or credential selection and cap prompts/retries, repeat the smallest reproducer rather than restarting the entire application environment.
Do not confuse it with
RTC_E_BASIC_AUTH_SET_TLS | the profile allows Basic authentication without selecting the TLS transport required by RTC |
|---|---|
RTC_E_SIP_AUTH_TYPE_NOT_SUPPORTED | the challenge requests an authentication scheme the RTC profile or stack cannot use |
RTC_E_SIP_INVALID_CERTIFICATE | the certificate presented or selected for SIP TLS does not satisfy RTC validation requirements |
Recovery and control flow
The owning RTC component should correct credentials, realm mapping, or credential selection and cap prompts/retries; it should also settle or cancel its previous operation before callers begin a replacement.
Example: A profile uses credentials for a different SIP realm and repeated REGISTER attempts fail.
Actions that do not address this condition
- Never record Authorization header contents or plaintext passwords.
- Do not disable certificate checking or lower transport security to make authentication appear successful.
Technical references
Looking for a different code? Search another status or error code.