| Previous | Next |
| RTC_E_SDP_MULTICAST | RTC_E_SDP_NO_MEDIA |
RTC_E_SDP_CONNECTION_ADDR
What the RTC value marks: RTC_E_SDP_CONNECTION_ADDR
The useful interpretation of this result is narrower than “SIP error”; within parsing, constructing, or reconciling SIP signaling and the SDP offer/answer carried by it, it means an SDP media description has no usable connection address at session or media level.
The stored value is 0x80EE000A in the RTC interface facility 0xEE; keep both forms in telemetry so COM error wrapping does not erase whether RTC produced an interface result, mapped a SIP response, or surfaced a PINT outcome.
Collect enough state to check inheritance of the session-level c= line and each media-level override; the result evidence should demonstrate why a media line can list codecs and ports yet remain unroutable without a connection address.
A safe diagnostic sequence
- Collect enough evidence to check inheritance of the session-level c= line and each media-level override.
- Test the competing explanation explicitly, because a media line can list codecs and ports yet remain unroutable without a connection address.
- Apply the targeted fix — generate a valid unicast connection address from the correct interface or NAT mapping — and validate both protocol completion and object cleanup.
Evidence that separates the cause
- Code-specific proof: check inheritance of the session-level c= line and each media-level override.
- Identity and target: each m= line and codec mapping.
- State at production: message direction and transport.
- Timing and ordering: start-line plus header names.
Protocol and object state
| RTC area | SIP message and SDP negotiation |
|---|---|
| Objects to correlate | SIP start-line and headers, message body framing, SDP session and media sections, offer/answer generation |
| Condition to prove | an SDP media description has no usable connection address at session or media level |
| Safe corrective direction | generate a valid unicast connection address from the correct interface or NAT mapping |
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.
Related RTC results
RTC_E_SIP_NO_STREAM | the operation requires at least one active media stream but the session currently has none |
|---|---|
RTC_E_SIP_CODECS_DO_NOT_MATCH | the local offer and remote answer have no common codec for an active media line |
RTC_E_SIP_PARSE_FAILED | the RTC SIP parser could not construct a valid message from the received or generated bytes |
How to handle the result
Recovery should be narrow: generate a valid unicast connection address from the correct interface or NAT mapping; while handling this result, do not let a higher layer simultaneously recreate the same session, registration, listener, or profile.
Example: A custom SDP builder writes m= and a= lines but omits every c= line.
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.