What does HRESULT 0x80EE0067 (RTC_E_SIP_TCP_FAIL) mean?

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: Fails to make a TCP connection

Previous	Next
RTC_E_SIP_DNS_FAIL	RTC_E_TOO_SMALL_EXPIRES_VALUE

RTC_E_SIP_TCP_FAIL

What `RTC_E_SIP_TCP_FAIL` means in RTC

This code belongs to resolving a SIP destination and establishing UDP, TCP, TLS, or proxy transport before a transaction can proceed: RTC failed to establish or maintain the TCP transport needed for the SIP request. Treating it as a generic RTC failure loses the state needed to choose a safe next action.

For correlation, retain 0x80EE0067 in the RTC interface facility 0xEE together with this result; generic HRESULT text can otherwise hide the protocol family and the exact RTC branch.

Evidence should show that you record resolved address, connect error, local bind, proxy path, bytes sent, and connection reuse state; the diagnostic distinction is that TCP failure is below SIP status processing and distinct from TLS negotiation.

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	RTC failed to establish or maintain the `TCP` transport needed for the `SIP` request
Safe corrective direction	repair routing/listener/firewall state and reconcile whether a prior request was transmitted

How to prove the condition

Use protocol and object evidence to record resolved address, connect error, local bind, proxy path, bytes sent, and connection reuse state.
Confirm the distinction that TCP failure is below SIP status processing and distinct from TLS negotiation.
Start a fresh operation after you repair routing/listener/firewall state and reconcile whether a prior request was transmitted, and compare its final state with the failing run.

Minimum incident record

Code-specific proof: record resolved address, connect error, local bind, proxy path, bytes sent, and connection reuse state.
Owning object: SIP transaction timer and retransmit count.
Wire evidence: original SIP URI and selected next hop.
Lifecycle state: DNS query type and answers.

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.

Correct application response

To correct this, repair routing/listener/firewall state and reconcile whether a prior request was transmitted.

Example: The registrar name resolves, but no server accepts the configured TCP port.

Nearby failure modes

`RTC_E_SIP_TIMEOUT`	the local RTC SIP transaction reached its timer limit without a qualifying final response
`RTC_E_SIP_REQUEST_DESTINATION_ADDR_NOT_PRESENT`	the RTC stack cannot determine a network destination for the outgoing SIP request
`RTC_E_SIP_STACK_SHUTDOWN`	an operation targeted an RTC SIP stack that has already entered shutdown

Technical references

Looking for a different code? Search another status or error code.