RFC 8599

Push Notification with the Session Initiation Protocol (SIP), May 2019

File formats:
icon for text file icon for PDF icon for HTML
C. Holmberg
M. Arnold
sipcore (art)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC8599

Discuss this RFC: Send questions or comments to the mailing list sipcore@ietf.org

Other actions: View Errata  |  Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 8599


This document describes how a Push Notification Service (PNS) can be used to wake a suspended Session Initiation Protocol (SIP) User Agent (UA) with push notifications, and it also describes how the UA can send binding-refresh REGISTER requests and receive incoming SIP requests in an environment in which the UA may be suspended. The document defines new SIP URI parameters to exchange PNS information between the UA and the SIP entity that will then request that push notifications be sent to the UA. It also defines the parameters to trigger such push notification requests. The document also defines new feature-capability indicators that can be used to indicate support of this mechanism.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

Advanced Search