SIP

406 Not Acceptable

The resource identified by the request is only capable of generating responses with content characteristics not acceptable according to the Accept header.

Wenn Sie diesen Code sehen

When content negotiation fails — the server cannot produce a response matching the Accept header fields in the request.

Wie man es behebt

Review the Accept headers in your request and broaden the acceptable content types.

Spezifikation

RFC / Spezifikation anzeigen →

Vergleichen mit

100 Trying 180 Ringing 181 Call Is Being Forwarded 182 Queued 183 Session Progress 199 Early Dialog Terminated 200 OK 202 Accepted 204 No Notification 300 Multiple Choices 301 Moved Permanently 302 Moved Temporarily

Anleitungen

401 Unauthorized vs 403 Forbidden: When to Use Each Security & Authentication

SIP Response Codes: Understanding VoIP Call Flow Real-Time Protocols

SIP Call Flow: Understanding Session Setup Real-Time Protocols

WebRTC Signaling with SIP and WebSocket Real-Time Protocols

RFC 3261: SIP Protocol Deep Dive Protocol Deep Dives

TLS 1.3: Faster, Simpler, More Secure Protocol Deep Dives

Debugging-Szenarien

488 Not Acceptable Here — Codec Mismatch Advanced

Glossar

Status Code Request Method (HTTP Verb) TLS Handshake Authentication TCP/IP Port Number NAT (Network Address Translation) Socket Request-Response Model RFC (Request for Comments) Connection-Oriented Full-Duplex SRV Record SIP Dialog Signaling SIP Registrar STUN (Session Traversal Utilities for NAT) TURN (Traversal Using Relays around NAT) SDP (Session Description Protocol) SIP INVITE SIP Proxy Server SIP Redirect Server SIP Transaction SIP User Agent SIP Trunk RTP (Real-time Transport Protocol) SRTP (Secure Real-time Transport Protocol) SIP ACK SIP BYE SIP CANCEL SIP OPTIONS SIP SUBSCRIBE/NOTIFY B2BUA (Back-to-Back User Agent) SBC (Session Border Controller) Codec Negotiation SIP Response Classes VoIP (Voice over IP) Presence (SIP) PBX (Private Branch Exchange) MFA (Multi-Factor Authentication) TLS Versions