| Previous | Next |
| RTC_E_REDIRECT_PROCESSING_FAILED | RTC_E_INVALID_LISTEN_SOCKET |
RTC_E_LISTENING_SOCKET_NOT_EXIST
Operational meaning: RTC_E_LISTENING_SOCKET_NOT_EXIST
Read this result as an RTC state-machine result: at this point in registering listening sockets and supplying internal/external media mappings before session establishment, code attempted to stop or use a listening address/port registration that is not active.
Log this result as 0x80EE007A in the RTC interface facility 0xEE, not only as a signed decimal; the facility distinguishes local RTC validation from a response status mapped by the stack.
Before changing configuration, record local tuple, transport, registration handle/generation, and prior stop or interface-change event; the RTC codes surrounding this result are not equivalent because no registered RTC listen socket differs from a socket existing but using invalid address parameters.
Signals worth preserving
- Code-specific proof: record local tuple, transport, registration handle/generation, and prior stop or interface-change event.
- Correlation key: local and external address/port.
- Protocol or object snapshot: port type and allowed range.
- Last completed transition: mapping owner and lifetime.
- Expected output: listen registration state.
Recovery and control flow
To correct this, make stop idempotent or register the tuple before depending on incoming requests.
Example: Network-change cleanup removes a listener, then a second cleanup path removes it again.
Protocol and object state
| RTC area | RTC listening and NAT port-mapping |
|---|---|
| Condition to prove | code attempted to stop or use a listening address/port registration that is not active |
| Objects to correlate | IRTCClientPortManagement, IRTCSessionPortManagement, IRTCPortManager, address/port range and mapping lifetime |
| Safe corrective direction | make stop idempotent or register the tuple before depending on incoming requests |
For outgoing sessions the port manager must be set before adding the participant; for incoming sessions it must be set before acceptance. The address advertised in SDP and the local socket receiving media are different values when NAT mapping is involved.
Verification workflow
- Confirm the distinction that no registered RTC listen socket differs from a socket existing but using invalid address parameters.
- Start a fresh operation after you make stop idempotent or register the tuple before depending on incoming requests, and compare its final state with the failing run.
Actions that do not address this condition
- Do not set or replace the port manager after session initiation has consumed the mapping.
- Do not advertise an external mapping before confirming that it belongs to the current local socket.
Do not confuse it with
RTC_E_PORT_MAPPING_UNAVAILABLE | the port manager cannot provide a usable internal/external mapping for the requested media flow |
|---|---|
RTC_E_INVALID_LISTEN_SOCKET | the address and port supplied for RTC listening cannot be bound or accepted as a valid listen tuple |
RTC_E_PORT_MAPPING_FAILED | the port manager returned a concrete failure while creating or retrieving a mapping |
Technical references
Looking for a different code? Search another status or error code.