Browse Prior Art Database

The Session Initiation Protocol (SIP) "Join" Header (RFC3911)

IP.com Disclosure Number: IPCOM000032055D
Original Publication Date: 2004-Oct-01
Included in the Prior Art Database: 2004-Oct-21
Document File: 18 page(s) / 35K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Mahy: AUTHOR [+2]

Abstract

This document defines a new header for use with SIP multi-party applications and call control. The Join header is used to logically join an existing SIP dialog with a new SIP dialog. This primitive can be used to enable a variety of features, for example: "Barge-In", answering-machine-style "Message Screening" and "Call Center Monitoring". Note that definition of these example features is non- normative.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

Network Working Group                                            R. Mahy

Request for Comments: 3911                                     Airespace

Category: Standards Track                                      D. Petrie

                                                                 Pingtel

                                                            October 2004

          The Session Initiation Protocol (SIP) "Join" Header

Status of this Memo

   This document specifies an Internet standards track protocol for the

   Internet community, and requests discussion and suggestions for

   improvements.  Please refer to the current edition of the "Internet

   Official Protocol Standards" (STD 1) for the standardization state

   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   This document defines a new header for use with SIP multi-party

   applications and call control.  The Join header is used to logically

   join an existing SIP dialog with a new SIP dialog.  This primitive

   can be used to enable a variety of features, for example: "Barge-In",

   answering-machine-style "Message Screening" and "Call Center

   Monitoring".  Note that definition of these example features is non-

   normative.

Table of Contents

   1.   Introduction . . . . . . . . . . . . . . . . . . . . . . . .   2

   2.   Conventions  . . . . . . . . . . . . . . . . . . . . . . . .   3

   3.   Applicability of RFC 2804 ("Raven"). . . . . . . . . . . . .   3

   4.   User Agent Server Behavior: Receiving a Join Header  . . . .   4

   5.   User Agent Client Behavior: Sending a Join header  . . . . .   6

   6.   Proxy behavior . . . . . . . . . . . . . . . . . . . . . . .   7

   7.   Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . .   7

        7.1.  The Join Header  . . . . . . . . . . . . . . . . . . .   7

        7.2.  New option tag for Require and Supported headers . . .   8

   8.   Usage Examples . . . . . . . . . . . . . . . . . . . . . . .   8

        8.1.  Join accepted and transitioned to central conference .   9

        8.2.  Join rejected  . . . . . . . . . . . . . . . . . . . .  12

   9.   Security Considerations  . . . . . . . . . . . . . . . . . .  13

   10.  IANA Considerations  . . . . . . . . . . . . . . . . . . . .  14

        10.1. Registration of "Join" SIP header. . . . . . . . . . .  14

Mahy & Petrie               Standards Track                     [Page 1]

RFC 3911                        SIP Join          ...