| Previous | Next |
| RTC_E_SIP_AUTH_FAILED | RTC_E_DESTINATION_ADDRESS_LOCAL |
RTC_E_INVALID_SIP_URL
What the RTC value marks: RTC_E_INVALID_SIP_URL
Read this result as an RTC state-machine result: at this point in resolving a SIP destination and establishing UDP, TCP, TLS, or proxy transport before a transaction can proceed, the supplied destination cannot be parsed or normalized as a SIP URI accepted by RTC.
Log this result as 0x80EE0012 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.
The first useful check is to record a redacted URI, scheme, escaping, user/host split, port, and parameters. The result must be separated from nearby conditions because URI syntax failure occurs before DNS or server lookup.
A safe diagnostic sequence
- Record this result and
0x80EE0012at the first RTC method or event that returns it. - Prove the condition by ensuring the trace can record a redacted URI, scheme, escaping, user/host split, port, and parameters.
- Apply one controlled change: construct the URI through one canonical parser and validate user input before session creation; then verify the result return value and resulting RTC state.
Evidence that separates the cause
Do not wait for a generic failure notification to log it; preserve the API call or event producing it together with the RTC object and transaction state visible at that moment.
- Code-specific proof: record a redacted URI, scheme, escaping, user/host split, port, and parameters.
- Identity and target: local/remote socket tuple.
- State at production: proxy tunnel response.
- Timing and ordering:
SIPtransaction timer and retransmit count.
Protocol and object state
| RTC area | SIP transport and reachability |
|---|---|
| Objects to correlate | SIP URI, proxy/registrar address, DNS results, socket, HTTP CONNECT tunnel, transaction timer |
| Condition to prove | the supplied destination cannot be parsed or normalized as a SIP URI accepted by RTC |
| Safe corrective direction | construct the URI through one canonical parser and validate user input before session creation |
Related RTC results
RTC_E_SIP_STACK_SHUTDOWN | an operation targeted an RTC SIP stack that has already entered shutdown |
|---|---|
RTC_E_DESTINATION_ADDRESS_MULTICAST | the signaling destination resolves to a multicast address unsupported for this RTC operation |
RTC_E_SIP_TLS_FAIL | the TLS transport failed outside the more specific tunnel, timeout, certificate, or compatibility cases |
How to handle the result
The owning RTC component should construct the URI through one canonical parser and validate user input before session creation; it should also settle or cancel its previous operation before callers begin a replacement.
Example: An application passes a display name and spaces where AddParticipant expects a SIP URI.
Actions that do not address this condition
- Do not switch transports without checking profile policy and authentication constraints.
- Do not retry rapidly across every resolved address without preserving the failure phase.
Technical references
Looking for a different code? Search another status or error code.