| Previous | Next |
| RTC_E_STATUS_INFO_QUEUED | RTC_E_STATUS_SUCCESS |
RTC_E_STATUS_SESSION_PROGRESS
RTC signaling reports session progress
RTC_E_STATUS_SESSION_PROGRESS is HRESULT 15663287 (0x00EF00B7) from RTC Core. The documented description is “Session Progress.” 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.
Wrappers should not translate this result to an undifferentiated Boolean before state handling finishes.
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 response may establish early media or other progress before final call acceptance and media handling follows negotiated parameters. Validation of it keeps a success-severity result from becoming a broader promise than the API made.
Correct handling and recovery
Process any session description, open early media only when policy allows, and keep the call provisional until a final response.
Difference from nearby results
Ringing communicates alerting; Session Progress can carry media or progress without asserting ringing.
The distinction around it should be visible in control flow, telemetry classification, and user messaging.
Practical scenario
A gateway sends Session Progress with an SDP answer and an announcement. The client plays early media while still allowing cancel.
References
Looking for a different code? Search another status or error code.