RFC 3665: Session Initiation Protocol (SIP) Basic Call Flow Examples

In plain English — editorial summary, not part of the RFC

This document gives examples of Session Initiation Protocol (SIP) call flows. Elements in these call flows include SIP User Agents and Clients, SIP Proxy and Redirect Servers. Scenarios include SIP Registration and SIP session establishment. Call flow diagrams and message details are shown.

Document record

Document ID

RFC3665

Published

January 2004

Authors

A. Johnston; S. Donovan; R. Sparks; C. Cunningham; K. Summers

Status

BEST CURRENT PRACTICE

Stream

IETF

Area

rai

Pages

94

Also known as

BCP75

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC3665
• Reported errata exist →

Topics

• user agent
• client proxy
• redirect

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 3608Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During RegistrationUpdated

  October 2003

• RFC 3840Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)Current

  August 2004

• RFC 3329Security Mechanism Agreement for the Session Initiation Protocol (SIP)Updated

  January 2003

• RFC 3327Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent ContactsUpdated

  December 2002

• RFC 3324Short Term Requirements for Network Asserted IdentityCurrent

  December 2002

• RFC 4189Requirements for End-to-Middle Security for the Session Initiation Protocol (SIP)Current

  October 2005

• RFC 4730A Session Initiation Protocol (SIP) Event Package for Key Press Stimulus (KPML)Current

  November 2006

• RFC 4916Connected Identity in the Session Initiation Protocol (SIP)Current

  June 2007

Also filed under

• BEST CURRENT PRACTICE
• 2004
• IETF stream
• rai area
• BCP 75