| Previous | Next |
| RTC_E_SIP_REQUEST_DESTINATION_ADDR_NOT_PRESENT | RTC_E_SIP_SSL_TUNNEL_FAILED |
RTC_E_SIP_UDP_SIZE_EXCEEDED
What RTC_E_SIP_UDP_SIZE_EXCEEDED means in RTC
In the RTC Client API, this result separates one failure or completion path from its neighbors because it denotes the serialized SIP datagram exceeds the size accepted by the RTC UDP transport path.
At the HRESULT layer, this result appears as 0x80EE001B in the RTC interface facility 0xEE; preserving the facility and symbol prevents it from being grouped incorrectly with unrelated networking or media errors.
A defensible diagnosis of this result requires you to measure encoded request size and identify large headers, authorization data, routes, or SDP; in the case, the error is about one UDP message; it does not imply the peer rejected the SIP method.
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 | the serialized SIP datagram exceeds the size accepted by the RTC UDP transport path |
| Safe corrective direction | use a profile-supported connection-oriented transport or reduce optional message size without deleting required data |
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.
How to prove the condition
- Start from
0x80EE001B, then find the method/event pair that first exposed it. - To verify this, measure encoded request size and identify large headers, authorization data, routes, or
SDP. - Keep the analysis at the right boundary: the error is about one
UDPmessage; it does not imply the peer rejected theSIPmethod. - After you use a profile-supported connection-oriented transport or reduce optional message size without deleting required data, repeat the smallest reproducer rather than restarting the entire application environment.
Nearby failure modes
RTC_E_SIP_NEED_MORE_DATA | the receive buffer contains only part of a complete SIP message |
|---|---|
RTC_E_SDP_NO_MEDIA | the SDP contains no enabled media description usable for the requested RTC session |
RTC_E_SDP_UPDATE_FAILED | a new SDP description is incompatible with the prior negotiated offer/answer state |
Minimum incident record
- Code-specific proof: measure encoded request size and identify large headers, authorization data, routes, or
SDP. - Owning object: start-line plus header names.
- Wire evidence: Content-Type and Content-Length.
- Lifecycle state:
SDPo= version and c= address.
Correct application response
Resolve it at its producing layer: use a profile-supported connection-oriented transport or reduce optional message size without deleting required data; after it, a separate UI or watchdog retry must wait until that layer reports a final state.
Example: A large SDP plus authentication and routing headers no longer fits the RTC UDP limit.
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.