| Previous | Next |
| ERROR_SPACES_POOL_WAS_DELETED | RTC_E_STATUS_INFO_TRYING |
RTC_S_ROAMING_NOT_SUPPORTED
RTC server does not support the requested roaming type
RTC_S_ROAMING_NOT_SUPPORTED is HRESULT 15597633 (0x00EE0041) from RTC Core. AllStat describes it as “Server does not support this type of roaming.” 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.
A cleared severity bit does not make the return equivalent to ordinary completion; the postcondition remains specific.
What must be true before accepting it
Verify that the client can continue with a documented local or nonroaming mode and does not assume server-side persistence. The boundary determines whether the caller continues, waits, falls back, or ends the operation.
Also confirm that returned outputs belong to the current operation generation and were not inherited from an earlier attempt.
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;
Keep this result attached to the operation that returned it. Interpreting it outside that API contract can turn a normal continuation or partial result into an incorrect retry or false completion.
Correct handling and recovery
Disable only the unsupported roaming feature, preserve local configuration, and inform the user when settings will not follow them.
A new attempt following it should be triggered by a meaningful transition, not merely by elapsed time.
Practical scenario
An RTC client signs in to a server without contact-list roaming. It uses a local list and labels it as device-specific.
Difference from nearby results
This is capability negotiation, not a general sign-in or network failure.
The distinction around it should be visible in control flow, telemetry classification, and user messaging.
References
Looking for a different code? Search another status or error code.