What does HRESULT 0x80EE0019 (RTC_E_SIP_CALL_DISCONNECTED) mean?

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: The Call has been disconnected

Previous	Next
RTC_E_SIP_NEED_MORE_DATA	RTC_E_SIP_REQUEST_DESTINATION_ADDR_NOT_PRESENT

RTC_E_SIP_CALL_DISCONNECTED

Operational meaning: `RTC_E_SIP_CALL_DISCONNECTED`

The operational meaning of this result is tied to resolving a SIP destination and establishing UDP, TCP, TLS, or proxy transport before a transaction can proceed: the call dialog or session was disconnected before the requested call operation could complete.

The machine-readable identity of this result is 0x80EE0019 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.

Before changing configuration, correlate BYE/CANCEL, local hang-up, transport loss, and the pending operation callback; the RTC codes surrounding this result are not equivalent because the disconnected state is terminal for that session generation even if the network is now reachable.

Verification workflow

Collect enough evidence to correlate BYE/CANCEL, local hang-up, transport loss, and the pending operation callback.
Test the competing explanation explicitly, because the disconnected state is terminal for that session generation even if the network is now reachable.
Apply the targeted fix — finish cleanup and create a new session only for a deliberate new call attempt — and validate both protocol completion and object cleanup.

Protocol and object state

RTC area	`SIP` transport and reachability
Condition to prove	the call dialog or session was disconnected before the requested call operation could complete
Objects to correlate	`SIP` URI, proxy/registrar address, DNS results, socket, `HTTP` CONNECT tunnel, transaction timer
Safe corrective direction	finish cleanup and create a new session only for a deliberate new call attempt

Signals worth preserving

Code-specific proof: correlate BYE/CANCEL, local hang-up, transport loss, and the pending operation callback.
Correlation key: proxy tunnel response.
Protocol or object snapshot: SIP transaction timer and retransmit count.
Last completed transition: original SIP URI and selected next hop.
Expected output: DNS query type and answers.

Recovery and control flow

To correct this, finish cleanup and create a new session only for a deliberate new call attempt.

Example: A user hangs up while a hold operation is still pending.

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.

Do not confuse it with

`RTC_E_SIP_SSL_NEGOTIATION_TIMEOUT`	the secure transport handshake did not complete before the RTC negotiation timer expired
`RTC_E_SIP_TRANSPORT_NOT_SUPPORTED`	the requested SIP transport is not implemented or allowed by the RTC profile/platform path
`RTC_E_SIP_REQUEST_DESTINATION_ADDR_NOT_PRESENT`	the RTC stack cannot determine a network destination for the outgoing SIP request

Technical references

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