SIP Event Package for Keys
draft-culpepper-sip-key-events-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Bert Culpepper , Robert Fairlie , Jean-Francois Mule | ||
| Last updated | 2002-03-06 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines a protocol independent message format for requesting and reporting state related to keys or buttons. The document also defines a SIP Event Package to make use of this extensible framework through the SIP SUBSCRIBE & NOTIFY messages. The draft currently defines key event sub-packages to represent the state of telephone dial pads, feature buttons found on many commercial telephones, standard keyboards as well as support for user or device specific buttons (for instance, a 'Double Latte' button). The event package and associated key packages can be used to enable new SIP services where an application or SIP entity requires notification of user interface activity either associated with a particular SIP session or simply in relation to the device itself.
Authors
Bert Culpepper
Robert Fairlie
Jean-Francois Mule
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)