A Mechanism for Transporting User to User Call Control Information in SIP

Document Type Replaced Internet-Draft (individual)
Authors Alan Johnston  , Joanne McMillen  , James Rafferty 
Last updated 2011-11-22 (latest revision 2010-12-14)
Replaced by RFC 7433
Stream (None)
Intended RFC status (None)
Expired & archived
plain text html xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-cuss-sip-uui
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


There is a need for applications using SIP to exchange User to User Information (UUI) data during session establishment. This information, known as call control UUI, is a small piece of data inserted by an application initiating the session, and utilized by an application accepting the session. This data is opaque to SIP and its function is unrelated to any basic SIP function. Several approaches to transporting call control UUI in SIP have been proposed. As networks move to SIP it is important that applications requiring this data can continue to function in SIP networks as well as the ability to interwork with this ISDN service for end-to-end transparency. This document discusses three mechanisms to meet the requirements defined in the Requirements for SIP Call Control UUI document. A new SIP header field which bests meets these requirements is proposed.


Alan Johnston (alan.b.johnston@gmail.com)
Joanne McMillen (c.joanne.mcmillen@gmail.com)
James Rafferty (james.rafferty@dialogic.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)