Proposed Extension of SIP

Add DO message type

Adding a new optional header: History-Info

provides information as to how and why a call arrives at a specific application or user [RFC 4244]

Build upon Event extensions (specifically SUBSCRIBE and NOTIFY)

For example, you can subscribe to know when a user is invited to a session or there is a change in a state of an INVITE initiated dialog [RFC 4235]

Add a new payload type via the new MIME type: Device Message Protocol (DMP) [Khurana 2000] -- this payload is translated into device specific payload at the SIP User Agent.

Note that you could also send SOAP payload either separately or as part of DMP.

Slide Notes

M. Barnes (Editor), An Extension to the Session Initiation Protocol (SIP) for Request History Information, IETF, RFC 4244, November 2005 ftp://ftp.rfc-editor.org/in-notes/rfc4244.txt Links to an external site.

J. Rosenberg, H. Schulzrinne, and R. Mahy (editors), An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP), IETF, RFC 4235, November 2005 ftp://ftp.rfc-editor.org/in-notes/rfc4235.txt

[Khurana 2000] Sumit Khurana, Provin Gurung, and Ashutosh Dutta, ‘Device Message Protocol (DMP): An XML based format for Wide Area Communication with Networked Appliances.’ IETF, Nov-2000 [Online]. Available: https://tools.ietf.org/html/draft-khurana-dmp-appliances-00 Links to an external site.

Transcript

[slide504] So a proposed extension was to add a so-called DO message. And now you could send a SIP message with this DO in it based upon, for instance, the SUBSCRIBE/NOTIFY extension. And now you could invoke specific functions of the device. Like turn a relay on or off. To turn the lights on or off. etc.