| Previous | Next |
| RTC_E_SDP_NO_MEDIA | RTC_E_SDP_FAILED_TO_BUILD |
RTC_E_SIP_TIMEOUT
Operational meaning: RTC_E_SIP_TIMEOUT
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 local RTC SIP transaction reached its timer limit without a qualifying final response.
Log this result as 0x80EE000C 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, capture method, transport, retransmit schedule, last provisional response, and whether any peer bytes arrived; the RTC codes surrounding this result are not equivalent because a local timeout is not the same as receiving SIP 408 from a server.
Signals worth preserving
- Code-specific proof: capture method, transport, retransmit schedule, last provisional response, and whether any peer bytes arrived.
- Correlation key: DNS query type and answers.
- Protocol or object snapshot: local/remote socket tuple.
- Last completed transition: proxy tunnel response.
- Expected output:
SIPtransaction timer and retransmit count.
Recovery and control flow
To correct this, reconcile uncertain remote outcome, apply bounded backoff, and retry only when method semantics permit.
Example: A UDP INVITE is retransmitted until the client transaction times out with no response.
Protocol and object state
| RTC area | SIP transport and reachability |
|---|---|
| Condition to prove | the local RTC SIP transaction reached its timer limit without a qualifying final response |
| Objects to correlate | SIP URI, proxy/registrar address, DNS results, socket, HTTP CONNECT tunnel, transaction timer |
| Safe corrective direction | reconcile uncertain remote outcome, apply bounded backoff, and retry only when method semantics permit |
Verification workflow
- Start from
0x80EE000C, then find the method/event pair that first exposed it. - To verify this, capture method, transport, retransmit schedule, last provisional response, and whether any peer bytes arrived.
- Keep the analysis at the right boundary: a local timeout is not the same as receiving
SIP408 from a server. - After you reconcile uncertain remote outcome, apply bounded backoff, and retry only when method semantics permit, repeat the smallest reproducer rather than restarting the entire application environment.
Actions that do not address this condition
- Do not retry rapidly across every resolved address without preserving the failure phase.
- Do not switch transports without checking profile policy and authentication constraints.
Do not confuse it with
RTC_E_TOO_SMALL_EXPIRES_VALUE | the server rejected or replaced an expiration interval because the requested value is below its minimum |
|---|---|
RTC_E_DESTINATION_ADDRESS_MULTICAST | the signaling destination resolves to a multicast address unsupported for this RTC operation |
RTC_E_SIP_TRANSPORT_NOT_SUPPORTED | the requested SIP transport is not implemented or allowed by the RTC profile/platform path |
Technical references
Looking for a different code? Search another status or error code.