| Previous | Next |
| RTC_E_STATUS_INFO_CALL_FORWARDING | RTC_E_STATUS_SESSION_PROGRESS |
RTC_E_STATUS_INFO_QUEUED
RTC signaling reports the request is queued
RTC_E_STATUS_INFO_QUEUED is HRESULT 15663286 (0x00EF00B6) from RTC Core. The documented description is “Queued.” In the legacy RTC Client API and SIP-style provisional call signaling, the value reports a nonfailure state that must not be collapsed into plain S_OK.
The application should branch on this result before a generic success path consumes the details.
Where the status is encountered
- RTC call setup and provisional signaling; capture the exact API, object, and phase because the same numeric success severity does not define the state by itself.
- Roaming capability negotiation;
- Softphone, conferencing, gateway, or proxy call-state UI;
What must be true before accepting it
Verify that the server or endpoint has accepted the request for delayed handling and queue limits and cancellation remain defined. The boundary determines whether the caller continues, waits, falls back, or ends the operation.
Correct handling and recovery
Show queued state, maintain transaction timers, and allow cancellation. Escalate when queue duration exceeds policy or no progress arrives.
Difference from nearby results
Trying is active processing; Queued explicitly means delayed service order.
Using one generic success branch for this HRESULT and its neighbor can lose output, repeat work, or misreport completion.
Practical scenario
A conferencing service queues a join request during admission control. The client displays queue position and waits for progress.
References
Looking for a different code? Search another status or error code.