Session Initiation Protocol
0 sources
Session Initiation Protocol
Summary
Session Initiation Protocol is a signaling protocol[1]. It draws 457 Wikipedia views per month (signaling_protocol category, ranking #1 of 3).[2]
Key Facts
- Session Initiation Protocol is credited with the discovery of Jonathan Rosenberg[3].
- Session Initiation Protocol's instance of is recorded as signaling protocol[4].
- Session Initiation Protocol's Library of Congress authority ID is recorded as sh2008009773[5].
- Session Initiation Protocol's has use is recorded as Voice over IP[6].
- Session Initiation Protocol's has use is recorded as Call control[7].
- Session Initiation Protocol's Commons category is recorded as Session Initiation Protocol[8].
- Session Initiation Protocol's Freebase ID is recorded as /m/07362[9].
- Session Initiation Protocol's described by source is recorded as RFC 3261: SIP: Session Initiation Protocol[10].
- Session Initiation Protocol's described by source is recorded as RFC 2543: SIP: Session Initiation Protocol[11].
- Session Initiation Protocol's described by source is recorded as RFC 3265: Session Initiation Protocol (SIP)-Specific Event Notification[12].
- Session Initiation Protocol's described by source is recorded as RFC 6665: SIP-Specific Event Notification[13].
- Session Initiation Protocol's described by source is recorded as RFC 7621: A Clarification on the Use of Globally Routable User Agent URIs (GRUUs) in the SIP Event Notification Framework[14].
- Session Initiation Protocol's described by source is recorded as RFC 5367: Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)[15].
- Session Initiation Protocol's described by source is recorded as RFC 5727: Change Process for the Session Initiation Protocol (SIP) and the Real-time Applications and Infrastructure Area[16].
- Session Initiation Protocol's described by source is recorded as RFC 3969: The Internet Assigned Number Authority (IANA) Uniform Resource Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)[17].
- Session Initiation Protocol's described by source is recorded as RFC 3427: Change Process for the Session Initiation Protocol (SIP)[18].
- Session Initiation Protocol's described by source is recorded as RFC 3968: The Internet Assigned Number Authority (IANA) Header Field Parameter Registry for the Session Initiation Protocol (SIP)[19].
- Session Initiation Protocol's described by source is recorded as RFC 7957: DISPATCH-Style Working Groups and the SIP Change Process[20].
- Session Initiation Protocol's described by source is recorded as RFC 6446: Session Initiation Protocol (SIP) Event Notification Extension for Notification Rate Control[21].
- Session Initiation Protocol's described by source is recorded as RFC 3853: S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)[22].
- Session Initiation Protocol's described by source is recorded as RFC 4320: Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction[23].
- Session Initiation Protocol's described by source is recorded as RFC 4916: Connected Identity in the Session Initiation Protocol (SIP)[24].
- Session Initiation Protocol's described by source is recorded as RFC 5393: Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking Proxies[25].
- Session Initiation Protocol's described by source is recorded as RFC 5621: Message Body Handling in the Session Initiation Protocol (SIP)[26].
- Session Initiation Protocol's described by source is recorded as RFC 8262: Content-ID Header Field in the Session Initiation Protocol (SIP)[27].
Body
Works and Contributions
Session Initiation Protocol is credited with the discovery of Jonathan Rosenberg[3].
Why It Matters
Session Initiation Protocol draws 457 Wikipedia views per month (signaling_protocol category, ranking #1 of 3).[2] It has Wikipedia articles in 27 language editions, a strong signal of global cultural recognition.[28] It is known by 25 alternative names across languages and contexts.[29]