Reference:Supported SIP Features and List of RFC's

Summary

SIP Features and list of RFC’s supported since version 6 of innovaphone firmware

Applies To

This information applies to

• All innovaphone V6 devices

Build 06-6040001 and later.

More Information

PBX Features and their corresponding RFCs

MWI (RFC 3842/RFC 3265 "Subscription für message-summary")

DTMF (RFC 2833 "RTP payload for DTMF")

Name Identification (Display String, RFC 3325 "Asserted Identity")

Hold/Retrieve (RFC 3264 "Offer/Answer Model for SDP") Howto:SIP Reverse Negotiation - Call Transfer

Transfer (RFC 3515 "REFER Method", RFC 3891 "Replaces Header)

Coder Change [T.38] (RFC 3264 "Re-Negotiation")

Call Forwarding (PBX internal, "183 Call Is Being Forwarded", "Diversion Header")

Overlap Dialing (RFC 3578)

Dialoge State monitoring (partner Key) (RFC 4235)

Instant Messaging (RFC 3428)

CTI Features and their corresponding RFCs

Initiate outgoing call (a call with Answer-Mode: Auto header (RFC 5373) is sent to the originating phone)

Accept incoming call (an unsolicited NOTIFY-Request with Event: talk header (RFC 3265) is sent to the accepting phone)

In a scenario where a call is accepted on a different device (e.g. pickup group), the PBX will use the Reason Header Reason: SIP ;cause=200 ;text="Call completed elsewhere" in its Cancel Message to signal that a call is accepted elsewhere and must not be entered in the phones call list. (RFC 3326)

List of supported RFCs

• RFC 1889

RTP: Real-Time Transport Protocol

• RFC 1890

RTP Profile for Audio and Video Conferences with Minimal Control

• RFC 2327, RFC 3266, RFC 4566

SDP: Session Description Protocol

• RFC 2396

Uniform Resource Identifiers (URI): Generic Syntax

• RFC 2543

SIP: Session Initiation Protocol (obsolete)

• RFC 2616

Hypertext Transfer protocol (HTTP/1.1)

• RFC 2617

HTTP Authentication: Basic and Digest Access Authentication

• RFC 2782

A DNS RR for specifying the location of services (DNS SRV)

• RFC 2976

The SIP INFO Method (including the non-standard application/dtmf-relay and application/dtmf content types with a fixed duration of 250)

• RFC 3203

DHCP reconfigure extension

• RFC 3261

SIP: Session Initiation Protocol

• RFC 3263

Session Initiation Protocol (SIP): Locating SIP Servers

• RFC 3264

An Offer/Answer Model with the Session Description Protocol (SDP) Howto:SIP Reverse Negotiation - Call Transfer

• RFC 3265

SIP-Specific Event Notification

• RFC 3323

A Privacy Mechanism for the Session Initiation Protocol (SIP)

• RFC 3326

The Reason Header Field for the Session Initiation Protocol

• RFC 3389

RTP Payload for Comfort Noise

• RFC 3515

The Session Initiation Protocol (SIP) Refer Method

• RFC 3550

RTP: Transport Protocol for Real-Time Applications

• RFC 3551

RTP Profile for A/V Conferences with Minimal Control

• RFC 3555

MIME Type Registration of RTP Payload Formats

• RFC 3578

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

• RFC 3680

SIP Event Package for Registrations

• RFC 3764

enumservice registration for SIP Adresses-of-Record

• RFC 3824

Using E.164 numbers with SIP

• RFC 3891

The Session Initiation Protocol ‘Replaces Header’

• RFC 3892

The SIP Referred-By Mechanism -SIP-aware filtering (to prevent SIP attacks)

• RFC 3842

SIP Message Waiting

• RFC 3311

re-INVITE

• RFC 2833

DTMF via RTP Channel , RTP payload for DTMF

• RFC 3325

Name identification

• RFC 3578

Overlap Dialing

• RFC 3420

Internet Media Type message/sipfrag

• RFC 3428

Extension for Instant Messaging

• RFC 3262

Reliability of Provisional Responses in Session Initiation Protocol (SIP)

• RFC 4028

Session Timers in the Session Initiation Protocol (SIP)

• RFC 4235

Dialoge State monitoring (partner Key)

• RFC 4612

Real-Time Facsimile (T.38) - audio/t38 MIME Sub-type Registration

• RFC 4733

RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals

• RFC 4916

Connected Identity in the Session Initiation Protocol (SIP)

• RFC 5373

Requesting Answering Modes for the Session Initiation - only Header Answer-Mode: Auto for calls started via SOAP/TAPI is supported. Header Priv-Answer-Mode for urgent calls is not supported.

• RFC 4568

Session Description Protocol (SDP) Security Descriptions for Media Streams

List of supported RFCs in V8

• RFC 3863

Presence Information Data Format (PIDF)

• RFC 4480

Rich Presence Extensions to the Presence Information Data Format (PIDF)

• RFC 3856

A Presence Event Package for the Session Initiation Protocol (SIP)

List of supported RFCs in V9

• RFC 4235

An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)

• RFC 4040

RTP Payload Format for a 64 kbit/s Transparent Call

List of supported RFCs in v11r1

• RFC 5245

Interactive Connectivity Establishment (ICE)

• RFC 6336

Interactive Connectivity Establishment (ICE) Options

• RFC 5763

DTLS-SRTP Framework

List of supported RFCs in v13r2

• RFC 5626

Client-Initiated Connections in SIP

Related Articles

• Howto:SIP Reverse Negotiation - Call Transfer
• Howto:SIP Media Negotiation - Details
• Howto:Guidelines for Testing 3rd Party SIP Terminal Devices
• Additional RFC's listed here: Howto:Security_works_with_innovaphone