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

Invite through a proxy

02

SIP proxies route signaling toward a user; the media path can be separate.

Related RFCs and changes

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

DIAGRAM§ 4 ↗
RFC 3261 · § 4EXAMPLE
3 / 3
Invite through a proxySIP proxies route signaling toward a user; the media path can be separate. Current state: ACK.Invite through a proxyCallerProxyCalleeINVITEINVITE180 Ringing → 200 OKACK
03
ACK

Acknowledge the successful INVITE response.

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

INVITE begins an invitation transaction.

  • INVITE begins an invitation transaction.
  • Provisional responses report progress.
  • A successful final response is acknowledged with ACK.
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 ↗