485
SIP
485 Ambiguous
The Request-URI was ambiguous. The response body may contain a list of possible unambiguous addresses.
Wenn Sie diesen Code sehen
When the destination address matches multiple users and the server cannot determine which one is intended.
Wie man es behebt
Use a more specific SIP URI. Check the response body for a list of possible matches and select the correct one.
Spezifikation
Vergleichen mit
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
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