| Previous | Next |
| RTC_E_SDP_CONNECTION_ADDR | RTC_E_SIP_TIMEOUT |
RTC_E_SDP_NO_MEDIA
Operational meaning: RTC_E_SDP_NO_MEDIA
This result should be investigated at the point where RTC handles parsing, constructing, or reconciling SIP signaling and the SDP offer/answer carried by it, and the condition to prove for this HRESULT is the SDP contains no enabled media description usable for the requested RTC session.
This result is represented as 0x80EE000B in the RTC interface facility 0xEE; record the symbolic name alongside the unsigned hexadecimal value; a decimal exception alone is poor evidence for RTC protocol diagnosis.
A defensible diagnosis of this result requires you to enumerate m= lines, zero ports, directions, and the session type expected by the caller; in the case, an SDP document can parse successfully while offering no active media.
Signals worth preserving
- Code-specific proof: enumerate m= lines, zero ports, directions, and the session type expected by the caller.
- Correlation key: each m= line and codec mapping.
- Protocol or object snapshot: message direction and transport.
- Last completed transition: start-line plus header names.
- Expected output: Content-Type and Content-Length.
Protocol and object state
| RTC area | SIP message and SDP negotiation |
|---|---|
| Condition to prove | the SDP contains no enabled media description usable for the requested RTC session |
| Objects to correlate | SIP start-line and headers, message body framing, SDP session and media sections, offer/answer generation |
| Safe corrective direction | offer at least one supported media line or use a nonmedia session type |
SIP transaction state and media negotiation are separate: a syntactically valid SIP request can still contain absent or unacceptable SDP. An SDP update must be checked against the previous offer/answer state, not merely parsed as a standalone text document.
Verification workflow
- Start from
0x80EE000B, then find the method/event pair that first exposed it. - To verify this, enumerate m= lines, zero ports, directions, and the session type expected by the caller.
- Keep the analysis at the right boundary: an
SDPdocument can parse successfully while offering no active media. - After you offer at least one supported media line or use a nonmedia session type, repeat the smallest reproducer rather than restarting the entire application environment.
Do not confuse it with
RTC_E_SDP_CONNECTION_ADDR | an SDP media description has no usable connection address at session or media level |
|---|---|
RTC_E_SDP_FAILED_TO_BUILD | the RTC stack could not serialize the current media/session state into an SDP offer or answer |
RTC_E_SIP_STREAM_NOT_PRESENT | code attempted to stop or remove a stream that is not active in the current session generation |
Recovery and control flow
The appropriate response to it is not a blanket reconnect. Instead, offer at least one supported media line or use a nonmedia session type, while preserving ownership of cleanup and any bounded retry.
Example: A re-INVITE sets all media ports to zero and code then tries to start an audio call.
Actions that do not address this condition
- Do not log credentials or an unredacted SDP body from production calls.
- Do not repair malformed signaling by silently deleting unknown headers or media sections.
Technical references
Looking for a different code? Search another status or error code.