Browse Prior Art Database

URNs for the Alert-Info Header Field of the Session Initiation Protocol (SIP) (RFC7462) Disclosure Number: IPCOM000241083D
Original Publication Date: 2015-Mar-01
Included in the Prior Art Database: 2015-Mar-26
Document File: 92 page(s) / 98K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L. Liess: AUTHOR [+6]


The Session Initiation Protocol (SIP) [RFC3261] includes a means to suggest to a User Agent (UA) a particular ringback tone or ring tone to be used during session establishment. In [RFC3261], this is done by including a URI, in the Alert-Info header field, that specifies a reference to the tone. The URI is most commonly the HTTP URL to an audio file. On the receipt of the Alert-Info header field, the UA may fetch the referenced ringback tone or ring tone and play it to the user.

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

Internet Engineering Task Force (IETF)                     L. Liess, Ed. Request for Comments: 7462                                     R. Jesske Updates: 3261                                        Deutsche Telekom AG Category: Standards Track                                    A. Johnston ISSN: 2070-1721                                                    Avaya                                                                D. Worley                                                                  Ariadne                                                               P. Kyzivat                                                                   Huawei                                                               March 2015

               URNs for the Alert-Info Header Field of the                    Session Initiation Protocol (SIP)


   The Session Initiation Protocol (SIP) supports the capability to    provide a reference to a specific rendering to be used by the User    Agent (UA) as an alerting signal (e.g., a ring tone or ringback tone)    when the user is alerted.  This is done using the Alert-Info header    field.  However, the reference (typically a URL) addresses only a    specific network resource with specific rendering properties.  There    is currently no support for standard identifiers for describing the    semantics of the alerting situation or the characteristics of the    alerting signal, without being tied to a particular rendering.  To    overcome these limitations and support new applications, a new family    of URNs for use in Alert-Info header fields (and situations with    similar requirements) is defined in this specification.

   This document normatively updates RFC 3261, which defines the Session    Initiation Protocol (SIP).  It changes the usage of the Alert-Info    header field defined in RFC 3261 by additionally allowing its use in    any non-100 provisional response to INVITE.  This document also    permits proxies to add or remove an Alert-Info header field and to    add or remove Alert-Info header field values.

Liess, et al.                Standards Track                    [Page 1]
 RFC 7462                       Alert URNs                     March 2015

 Status of This Memo

   This is an Internet Standards Track document.

   This document is a...