| Previous | Next |
| RTC_S_ROAMING_NOT_SUPPORTED | RTC_E_STATUS_INFO_RINGING |
RTC_E_STATUS_INFO_TRYING
RTC signaling reports Trying
RTC_E_STATUS_INFO_TRYING is HRESULT 15663204 (0x00EF0064) from RTC Core. The documented description is “Trying.” 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 transaction remains active and provisional responses are correlated to the correct request. That proof prevents usable partial state from being confused with full completion.
Correct handling and recovery
Keep call setup pending, refresh timers according to the RTC stack, and avoid presenting ringing before a later response confirms it.
Do not use an unchanged tight retry loop for this HRESULT; it can duplicate effects or conceal a terminal state.
Difference from nearby results
Ringing indicates alerting at the destination; Trying only confirms that processing has begun.
Practical scenario
An outbound call receives Trying from a proxy. The UI remains in Connecting until a subsequent Ringing or final response.
References
Looking for a different code? Search another status or error code.