Konformität mit den SIP-Industriestandards in Liberty

Session Initiation Protocol (SIP) in Liberty ist mit Industriestandards für den SIP-Container und SIP-Anwendungen konform.

SIP-Container

Liberty ist mit den folgenden SIP-Standards konform: Liberty ist außerdem mit den IETF- (Internet Engineering Task Force) und JCP-Industriestandards (Java™ Community Process) für SIP konform. In der folgenden Tabelle sind die IETF- und JCP-Standards aufgelistet.
Tabelle 1. Liberty ist mit den folgenden SIP-Standards konform
Standard Beschreibung
JR116 SIP: SIP Servlet API
JR289 SIP: SIP Servlet API v1.1
RFC 2543 SIP: Session Initiation Protocol
RFC 3261 SIP: Session Initiation Protocol
RFC 3262 Reliability of Provisional Responses in the Session Initiation Protocol (SIP)
RFC 3263 Session Initiation Protocol (SIP): Locating SIP Servers
RFC 3265 Session Initiation Protocol (SIP)-Specific Event Notification
RFC 3311 The SIP UPDATE Method
RFC 3325 Private Extensions to the SIP for asserted identity within trusted networks
RFC 3326 The Reason Header Field for the Session Initiation Protocol (SIP)
RFC 3515 The Session Initiation Protocol (SIP) Refer Method
RFC 3581 The SIP Extension for Symmetric Response Routing
RFC 3824 Using E.164 numbers with the Session Initiation Protocol (SIP)
RFC 3891 The SIP Replace header
RFC 3903 Session Initiation Protocol (SIP) Extension for Event State Publication
RFC 3911 The SIP Join header
RFC 4475 SIP torture test messages
RFC 5057 Multiple dialog usages in SIP
RFC 5626 Managing Client-Initiated Connections in SIP
Anmerkung: Der SIP-Server kann als Proxy oder Registrator eingesetzt werden, wie in den Abschnitten 5, 6 und 7 von RFC 5626 beschrieben. RFC 5626 ist eine Erweiterung von RFC 3261. Der SIP-Server bietet vollständige Unterstützung für RFC 3261. Die Unterstützung für RFC 5626 weist jedoch folgende Einschränkungen auf:
  • Der SIP-Server kann als Benutzeragent gemäß Definition in RFC 3261 eingesetzt werden, aber nicht als Benutzeragent gemäß Definition in Abschnitt 4 von RFC 5626.
  • Der SIP-Server unterstützt keine STUN-Keepalives gemäß Festlegung in RFC 5626.
RFC 5658 Addressing Record-Route issues in SIP

SIP-Anwendungen

Liberty ist mit Standards für SIP-Anwendungen konform.

Tabelle 2. Konformität mit Standards für SIP-Anwendungen
Standard Beschreibung
RFC 2848 The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services
RFC 2976 The SIP INFO Method
RFC 3050 Common Gateway Interface for SIP
RFC 3087 Control of Service Context using SIP Request-URI
RFC 3264 An Offer/Answer Model with the Session Description Protocol (SDP)
RFC 3266 Support for IPv6 in Session Description Protocol (SDP)
RFC 3312 Integration of Resource Management and Session Initiation Protocol (SIP)
RFC 3313 Private Session Initiation Protocol (SIP) Extensions for Media Authorization
RFC 3319 Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers
RFC 3327 Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts
RFC 3372 Session Initiation Protocol for Telephones (SIP-T): Context and Architectures
RFC 3398 Integrated Services Digital Network (ISDN) User Part (ISUP) to Session Initiation Protocol (SIP) Mapping
RFC 3428 Session Initiation Protocol (SIP) Extension for Instant Messaging
RFC 3455 Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)
RFC 3578 Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)
RFC 3603 Private Session Initiation Protocol (SIP) Proxy-to-Proxy Extensions for Supporting the PacketCable Distributed Call Signaling Architecture
RFC 3608 Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration
RFC 3665 Session Initiation Protocol (SIP) Basic Call Flow Examples
RFC 3666 Session Initiation Protocol (SIP) Public Switched Telephone Network (PSTN) Call Flows
RFC 3680 A Session Initiation Protocol (SIP) Event Package for Registrations
RFC 3725 Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)
RFC 3840 Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
RFC 3842 A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)
RFC 3856 A Presence Event Package for the Session Initiation Protocol (SIP)
RFC 3857 A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP)
RFC 3959 The Early Session Disposition Type for the Session Initiation Protocol (SIP)
RFC 3960 Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)
RFC 3976 Interworking SIP and Intelligent Network (IN) Applications
RFC 4032 Update to the Session Initiation Protocol (SIP) Preconditions Framework
RFC 4092 Usage of the Session Description Protocol (SDP) Alternative Network Address Types (ANAT) Semantics in the Session Initiation Protocol (SIP)
RFC 4117 Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)
RFC 4235 An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)
RFC 4240 Basic Network Media Services with SIP
RFC 4353 A Framework for Conferencing with the Session Initiation Protocol (SIP)
RFC 4354 A Session Initiation Protocol (SIP) Event Package and Data Format for Various Settings in Support for the Push-to-Talk over Cellular (PoC) Service
RFC 4411 Extending the Session Initiation Protocol (SIP) Reason Header for Preemption Events
RFC 4457 The Session Initiation Protocol (SIP) P-User-Database Private-Header (P-Header)
RFC 4458 Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)
RFC 4483 A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages
RFC 4497 Interworking between the Session Initiation Protocol (SIP) and QSIG
RFC 4508 Conveying Feature Tags with the Session Initiation Protocol (SIP) REFER Method

Symbol das den Typ des Artikels anzeigt. Referenzartikel

Dateiname: rwlp_sip_refstandard.html