Visual RFC.
ALL RFCs / RFC 3261
Read the RFC ↗
RFC 3261 / MECHANISMS

Cancel a request, end a session

04

CANCEL and BYE operate at different points in the call lifecycle.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 9 ↗
RFC 3261 · § 9EXAMPLE
3 / 3
Cancel a request, end a sessionCANCEL and BYE operate at different points in the call lifecycle. Current state: BYE for established session.Cancel a request, end a sessionpending INVITECANCEL ↔ final response raceACK successful INVITE; then BYECANCEL cannot undo a final success
03
BYE for established session

Terminate the resulting session with BYE instead of assuming CANCEL ended it.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

CANCEL targets a pending request.

  • CANCEL targets a pending request.
  • It cannot undo a final response that has already won the race.
  • BYE terminates an established session according to dialog rules.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Register a reachable contact
  2. Invite through a proxy
  3. A dialog outlives a transaction
  4. Cancel a request, end a session
  5. Signaling is not the media stream
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗