14.1.2. Supported RFCs (Request for Comments) for SIP Interfaces 
Table 78. Supported RFCs (Request for Comments) for SIP interfaces
|
RFC-Number
|
Title
|
Interfaces:
|
||
|
Subscriber
|
Native Trunk
|
SIP-Q
|
||
|
RFC 2198
|
RTP Payload for Redundant Audio Data
|
Yes
|
Yes
|
Yes
|
|
RFC 2246
|
The TLS Protocol Version 1.0
|
Yes
|
Yes
|
Yes
|
|
RFC 2327
|
SDP: Session Description Protocol (obsoleted by RFC4566)
|
Yes
|
Yes
|
Yes
|
|
RFC 2396
|
Uniform Resource Identifiers (URI): Generic Syntax
|
Yes
|
Yes
|
Yes
|
|
RFC 2617
|
HTTP Authentication: Basic and Digest Access Authentication
|
Yes
|
Yes
|
Yes
|
|
RFC 2782
|
DNS RR for specifying the location of services (DNS SRV)
|
No
|
Yes
|
Yes
|
|
RFC 2833
|
RTP Payload for DTMF Digits, Telephony Tones and Telephony
Signals
|
Yes
|
Yes
|
Yes
|
|
RFC 2976
|
The SIP INFO Method
|
No
|
No
|
Yes
|
|
RFC 3204
|
MIME media types for ISUP and QSIG Objects
|
Yes
|
Yes
|
Yes
|
|
RFC 3261
|
SIP: Session Initiation Protocol
|
Yes
|
Yes
|
Yes
|
|
RFC 3262
|
Provisional Response Acknowledgment (PRACK) Early Media
|
Yes
|
Yes
|
Yes
|
|
RFC 3263
|
SIP Locating Servers
|
No
|
Yes
|
Yes
|
|
RFC 3264
|
An Offer/Answer Model with SDP
|
Yes
|
Yes
|
Yes
|
|
RFC 3265
|
Session Initiation Protocol (SIP)-Specific Event Notification
|
Yes
|
No
|
No
|
|
RFC 3310
|
HTTP Digest Authentication
|
Yes
|
Yes
|
Yes
|
|
RFC 3311
|
Session Initiation Protocol (SIP) UPDATE Method
|
Yes
|
Yes
|
Yes
|
|
RFC 3323
|
A Privacy Mechanism for the Session Initiation Protocol (SIP)
|
Yes
|
Yes
|
No
|
|
RFC 3324
|
Short Term Requirements for Network Asserted Identity
|
Yes
|
Yes
|
Yes (but no use case)
|
|
RFC 3325
|
Private Extensions to the Session Initiation Protocol (SIP) for
Asserted Identity within Trusted Networks
|
Yes
|
Yes
|
No
|
|
RFC 3326
|
The Reason Header Field for the Session Initiation Protocol
(SIP)
|
No
|
No
|
Yes
|
|
RFC 3484
|
Default Address Selection for Internet Protocol version 6
(IPv6)
|
Yes
|
Yes
|
Yes
|
|
RFC 3515
|
The Session Initiation Protocol (SIP) Refer Method(1)
|
Yes
|
Yes
|
No
|
|
RFC 3550
|
RTP: Transport Protocol for Real-Time Applications
|
Yes
|
Yes
|
Yes
|
|
RFC 3551
|
RTP Profile for Audio and Video Conferences with Minimal
Control
|
Yes
|
Yes
|
Yes
|
|
RFC 3581
|
An Extension to the Session Initiation Protocol (SIP) for
Symmetric Response Routing
|
No
|
Yes
|
No
|
|
RFC 3711
|
The Secure Real-time Transport Protocol (SRTP)
|
Yes
|
Yes
|
Yes
|
|
RFC 3725
|
Best Current Practices for Third Party Call Control (3pcc) in the
Session Initiation Protocol (SIP)
|
Yes
|
No
|
Yes
|
|
RFC 3830
|
MIKEY: Multimedia Internet KEYing
|
No
|
Yes
|
Yes
|
|
RFC 3842 (partly)(2)
|
Message Waiting Indication Event Package
|
Yes
|
Yes
|
No
|
|
RFC 3891
|
The Session Initiation Protocol (SIP) Replaces Header
|
Yes
|
Yes
|
No
|
|
RFC 3892
|
The Session Initiation Protocol (SIP) Referred-By Mechanism (3)
|
Yes
|
Yes
|
No
|
|
RFC 4028
|
Session Timers in the Session Initiation Protocol (SIP)
|
Yes
|
Yes
|
Yes
|
|
RFC 4119
|
A Presence-based GEOPRIV Location Object Format
|
No
|
Yes
|
Yes
|
|
RFC 4291
|
IP Version 6 Addressing Architecture
|
Yes
|
Yes
|
Yes
|
|
RFC 4568
|
Session Description Protocol (SDP) Security Descriptions for
Media Streams
|
Yes
|
Yes
|
Yes
|
|
RFC 4733
|
RTP Payload for DTMF Digits, Telephony Tones and Telephony
Signals
|
Yes
|
Yes
|
Yes
|
|
RFC 5009
|
Private Header (P-Header) Extension to the SIP for Authorization
of Early Media
|
No
|
Yes
|
No
|
|
RFC 5139
|
Revised Civic Location Format for Presence Information Data
Format Location Object (PIDF-LO)
|
No |
Yes
|
Yes |
|
RFC 5246
|
Transport Layer Security (TLS) Protocol Version 1.2
|
Yes
|
Yes
|
Yes
|
|
RFC 5491
|
GEOPRIV Presence Information Data Format Location Object (PIDF-LO) Usage Clarification, Considerations and Recommendations |
No
|
Yes
|
Yes
|
|
RFC 5746
|
Transport Layer Security (TLS) Renegotiation Indication
Extension
|
Yes
|
Yes
|
Yes
|
|
RFC 5806
|
Diversion Indication in SIP
|
Yes
|
Yes
|
No
|
|
RFC 5923
|
Connection Reuse in the Session Initiation Protocol (SIP)
|
Yes
|
Yes
|
Yes
|
|
RFC 6140
|
Registration for Multiple Phone Numbers in the Session Initiation
Protocol (SIP)(4)
|
No
|
Yes
|
Yes
|
|
RFC 6716
|
Definition of the Opus Audio Codec
|
Yes
|
Yes
|
Yes
|
|
RFC 7433
|
A Mechanism for Transporting User-to-User Call Control Information in SIP | No |
Yes
|
Yes
|
|
RFC 7852
|
Additional Data Related to an Emergency Call |
No
|
Yes
|
Yes
|
|
RFC 7044
|
An Extension to the Session Initiation Protocol (SIP) for Request
History Information
|
No
|
Yes
|
Yes
|
|
RFC 8446
|
Transport Layer Security (TLS) Protocol Version 1.3
|
No
|
Yes
|
Yes
|
| (1) | Refer is only supported I/C for SIP subscribers and native SIP Trunks (configurable in WBM > SIP Trunk Profiles) - (NOT RECOMMENDED FOR SIP Service Providers due to accounting, billing, permissions etc.) |
| (2) | "partly" means that only the static subscription at Voice Mail Server is supported (in outgoing direction). OpenScape 4000 doesn't support dynamic subscription in outgoing direction, i.e. no SUBSCRIBE message is sent. Static subscription is typical for PBXes (like OpenScape 4000) and dynamic subscription is typical for SIP clients. In incoming direction (e.g. from a SIP client to OpenScape 4000), both static and dynamic subscription is supported. |
| (3) | Refer is only supported I/C for SIP subscribers and native SIP Trunks (configurable in WBM > SIP Trunk Profiles) - (NOT RECOMMENDED FOR SIP Service Providers due to accounting, billing, permissions etc.) |
| (4) | Only possible if SIP trunk profile is used. |