The table below shows whether a particular standard is supported in the OC SIP RA itself (Full), or if the standard may be easily supported by an application using the RA (Partial).

The SIP protocol was designed to be very extensible, so most SIP standards assume a basic SIP stack is available, and add extensions that can be implemented at the application layer.

The rapid pace of development in the SIP world means it is not feasible to support every new standard directly in the RA, and this is not necessary when they can be easily implemented by an application.

Spec Description Compliance Notes

RFC4028

Session Timers

Full

RFC5626

Managing Client-Initiated Connections

Full

RFC2848

The PINT Service Protocol: Extensions to SIP and SDP for IP Access to Telephone Call Services

Partial

RFC2976

INFO Method

Full

Compliance required by JAIN SIP 1.2.

RFC3261

SIP: Session Initiation Protocol

Full

Compliance required by JAIN SIP 1.2.

RFC3262

Reliability of Provisional Responses

Full

Compliance required by JAIN SIP 1.2.

RFC3263

SIP: Locating SIP Servers

Full

RFC3265

SIP-Specific Event Notification

Full

Compliance required by JAIN SIP 1.2.

RFC3311

UPDATE Method

Full

Compliance required by JAIN SIP 1.2.

RFC3312

Integration of Resource Management and SIP

Full

RFC3313

Private SIP Extensions for Media Authorization

Full

RFC3320

Signalling Compression (SigComp)

None

RFC3323

A Privacy Mechanism for SIP

Full

RFC3325

Private Extensions to SIP for Asserted Identity within Trusted Networks

Full

RFC3326

The Reason Header Field for the Session Initiation Protocol

Full

RFC3327

SIP Extension Header Field for Registering Non-Adjacent Contacts

Full

RFC3329

Security Mechanism Agreement for SIP

Partial

Supported using Extension headers.

RFC3372

SIP for Telephones (SIP-T)

Partial

Best current practice RFC.

RFC3398

ISUP to SIP Mapping

Partial

RFC3428

Extension for Instant Messaging

Full

Compliance required by JAIN SIP 1.2.

RFC3455

P-Header Extensions to SIP for 3GPP

Full

RFC3515

The SIP Refer Method

Full

Compliance required by JAIN SIP 1.2.

RFC3578

Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to SIP

Partial

RFC3581

An Extension to SIP for Symmetric Response Routing

Full

Compliance required by JAIN SIP 1.2.

RFC3603

Private SIP Proxy-to-Proxy Extensions for Supporting the PacketCable Distributed Call Signaling Architecture

Partial

Supported using Extension headers.

RFC3608

SIP Extension Header Field for Service Route Discovery During Registration: Service-Route header

Full

RFC3680

A SIP Event Package for Registrations

Partial

RFC3702

Authentication, Authorization, and Accounting Requirements for the Session Initiation Protocol

N/A

Informational RFC.

RFC3725

Best Current Practices for Third-Party Call Control

N/A

Best current practice RFC.

RFC3764

Enumservice Registration for SIP Addresses-of-Record

Partial

Application must implement ENUM DNS lookups.

RFC3840

Indicating User Agent Capabilities in SIP

Full

RFC3841

Caller Preferences for SIP

Partial

Supported using Extension headers.

RFC3842

A Message Summary and Message Waiting Indication Event Package for SIP

Partial

RFC3853

S/MIME Advanced Encryption Standard (AES) Requirement for SIP

Partial

RFC3856

A Presence Event Package for SIP

Partial

RFC3857

A Watcher Information Event Template-Package for SIP

Partial

RFC3891

The SIP "Replaces" Header

Partial

Supported using Extension headers.

RFC3892

The SIP Referred-By Mechanism

Partial

Supported using Extension headers.

RFC3893

SIP Authenticated Identity Body (AIB) Format

Partial

RFC3903

SIP Extension for Event State Publication

Full

Supports PUBLISH method

RFC3911

Join header

Partial

Supported using Extension headers.

RFC3959

The Early Session Disposition Type for SIP

Partial

RFC3966

The tel URI for Telephone Numbers

Full

RFC4028

Session Timers in the Session Initiation Protocol

Partial

RA supports headers, but timers must be implemented by the application.
The RA may support session timers automatically in the future.

RFC4032

Update to the SIP Preconditions Framework

Full

RFC4092

Usage of the Session Description Protocol (SDP) Alternative Network Address Types (ANAT) Semantics in SIP

Partial

RFC4168

The Stream Control Transmission Protocol (SCTP) as a Transport for the SIP

None

SIP RA supports TCP, UDP and TLS.

RFC4235

An INVITE-Initiated Dialog Event Package for SIP

Partial

RFC4244

An Extension to SIP for Request History Information

Partial

Supported using Extension headers.

RFC4320

Actions Addressing Identified Issues with the SIP Non-INVITE Transaction

Partial

RFC4411

Extending the SIP Reason Header for Preemption Events

Partial

RFC4412

Communications Resource Priority for SIP

Partial

Supported using Extension headers.

RFC4457

The SIP P-User-Database Private-Header

Partial

Supported using Extension headers.

RFC4474

Enhancements for Authenticated Identity Management in SIP

Partial

Supported using Extension headers.

RFC4483

A Mechanism for Content Indirection in SIP Messages

Partial

Supported using Extension headers.

RFC4488

Suppression of SIP REFER Method Implicit Subscription

Partial

Supported using Extension headers.

RFC4508

Conveying Feature Tags with the SIP REFER Method

Full

RFC4538

Request Authorization through Dialog Identification in SIP

Partial

Supported using Extension headers.

RFC4575

A SIP Event Package for Conference State

Partial

RFC4730

A SIP Event Package for Key Press Stimulus (KPML)

Partial

RFC4780

Management Information Base for the SIP

None

RFC4916

Connected Identity for the SIP

Partial

RFC4964

The P-Answer-State Header Extension to SIP for the Open Mobile Alliance Push to Talk over Cellular

Partial

Supported using Extension headers.

RFC5002

The SIP P-Profile-Key Private Header (P-Header)

Partial

Supported using Extension headers.

RFC5079

Rejecting Anonymous Requests in the SIP

Full

RFC5009

Private Header (P-Header) Extension to the SIP for Authorization of Early Media: P-Early-Media

Partial

Supported using Extension headers.

RFC5360

A Framework for Consent-Based Communications in the SIP

Partial

RFC5362

The SIP Pending Additions Event Package

Partial

RFC5365

Multiple-Recipient MESSAGE Requests in the SIP

Full

RFC5366

Conference Establishment Using Request-Contained Lists in the SIP

Partial

RFC5367

Subscriptions to Request-Contained Resource Lists in the SIP

Partial

RFC5368

Referring to Multiple Resources in the SIP

Full

RFC5373

Requesting Answering Modes for SIP

Partial

Supported using Extension headers.

RFC5393

Addressing an Amplification Vulnerability in SIP Forking Proxies

Partial

RFC5502

The SIP P-Served-User P-Header for the 3GPP IM CN Subsystem

Partial

RFC5621

Message Body Handling in SIP

Partial

RFC5626

Managing Client-Initiated Connections in SIP

Partial

RA supports an earlier draft, draft-ietf-sip-outbound-03.

RFC5627

Obtaining and Using Globally Routable User Agent URIs (GRUUs) in SIP

Partial

RFC5628

Registration Event Package Extension for SIP GRUUs

Partial

RFC5630

Use of the SIPS URI Scheme in SIP

Partial

RFC5658

Addressing Record-Route Issues in SIP

Partial

RFC5688

A SIP Media Feature Tag for MIME Application Subtypes

Partial

RFC5806

Diversion Indication in SIP

Full

Supported using Extension headers.

RFC6026

Correct Transaction Handling for 2xx Responses to SIP INVITE Requests

Full

3GPP TS 23.218

IP Multimedia (IM) session handling; IM call model; Stage 2

Full

3GPP TS 24.229

IP Multimedia Call Control Protocol based on SIP and Session Description Protocol (SDP)

Partial

Application must implement AS behaviour.

3GPP TS 24.841

Presence service based on SIP; Functional models, information flows and protocol details

Partial

ITU-T Q.1912.5

Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control protocol or ISDN User Part (SIP-I)

Partial

JSR 32

JAIN SIP API

Full

Version 1.2

JSR 240

JAIN SLEE (JSLEE) v1.1

Full

JSR 289

SIP Servlet API v1.1

Full

Rhino SIP Servlet is compliant with JSR 289 as it passes the TCK