What does HRESULT 0x80EE0073 (RTC_E_SIP_HOLD_OPERATION_PENDING) mean?

RTC_E_SIP_HOLD_OPERATION_PENDING

What the RTC value marks: RTC_E_SIP_HOLD_OPERATION_PENDING

This result should be investigated at the point where RTC handles creating a session, adding or removing participants, and serializing operations that alter call topology, and the condition to prove for this HRESULT is a hold transaction is already pending for the RTC session.

This result is represented as 0x80EE0073 in the RTC interface facility 0xEE; record the symbolic name alongside the unsigned hexadecimal value; a decimal exception alone is poor evidence for RTC protocol diagnosis.

A defensible diagnosis of this result requires you to record pending re-INVITE CSeq, desired/current media direction, and completion callback; in the case, pending hold is serialized offer/answer state, not proof that the call is already on hold.

Protocol and object state

Adding the first participant starts an idle RTC session; later participant operations are constrained by the chosen session type. An outstanding INVITE, join, hold, or REFER operation owns part of the session state until its completion event arrives.

Evidence that separates the cause

• Code-specific proof: record pending re-INVITE CSeq, desired/current media direction, and completion callback.
• Identity and target: participant URI and count.
• State at production: Call-ID/dialog identifiers.
• Timing and ordering: pending operation instance.

A safe diagnostic sequence

1. Use protocol and object evidence to record pending re-INVITE CSeq, desired/current media direction, and completion callback.
2. Confirm the distinction that pending hold is serialized offer/answer state, not proof that the call is already on hold.
3. Start a fresh operation after you wait for the result and coalesce duplicate hold commands, and compare its final state with the failing run.

How to handle the result

Resolve it at its producing layer: wait for the result and coalesce duplicate hold commands; after it, a separate UI or watchdog retry must wait until that layer reports a final state.

Example: The user presses Hold twice before the first re-INVITE completes.

Actions that do not address this condition

• Do not create a second session until the first operation outcome is reconciled.
• Do not issue overlapping topology changes from independent callbacks.

Related RTC results

Technical references

• Create a Session and Make a Call.
• Microsoft RTC return constants.
• SIP dialog and transaction rules.