487
SIP
487 Request Terminated
The request was terminated by a BYE or CANCEL. The original request was cancelled before it could be completed.
On this page
When You See This Code
When the caller hangs up before the callee answers (CANCEL sent for pending INVITE). This is normal call abandonment.
How to Fix
No fix needed — the caller intentionally terminated the request. This is normal behavior.
Specification
Compare With
Guides
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
Specifications
Glossary
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
Frequently Asked Questions
What is SIP 487 Request Terminated?
The request was terminated by a BYE or CANCEL. The original request was cancelled before it could be completed.
When do you see SIP 487 Request Terminated?
When the caller hangs up before the callee answers (CANCEL sent for pending INVITE). This is normal call abandonment.
How to fix SIP 487 Request Terminated?
No fix needed — the caller intentionally terminated the request. This is normal behavior.