Reference:Supported SIP Features and List of RFC's: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
==Summary==
==Summary==
 
SIP Features and list of RFC’s supported in version 6 of innovaphone firmware
SIP Pbx Features and list of RFC’s supported in version 6 of innovaphone firmware


==Applies To==
==Applies To==
This information applies to
This information applies to
 
* All innovaphone V6 devices
 
Build  06-6040001 and later.
−        all innovaphone products with V6
 
Build  06-604000102 and later.


==More Information==
==More Information==


Supported Sip features in the innovaphone Pbx
*RFC 1889
RTP: Real-Time Transport Protocol
   
   
            - MWI (rfc3842/rfc3265 "Subscription für message-summary")
*RFC 2327
 
SDP: Session Description Protocol
   
   
 
*RFC 2396
            - DTMF (rfc2833 "RTP payload for DTMF")
Uniform Resource Identifiers (URI): Generic Syntax
 
   
   
 
* RFC 2543
            - Name Identification (Display String, rfc3325 "Asserted Identity")
SIP: Session Initiation Protocol (obsolete)
 
   
   
 
* RFC 2616
            - Hold/Retrieve (rfc3264 "Offer/Answer Model for SDP")
Hypertext Transfer protocol (HTTP/1.1)
 
   
   
 
*RFC 2617
            - Transfer (rfc3515 "REFER Method", rfc3891 "Replaces Header")
HTTP Authentication: Basic and Digest Access Authentication
 
   
   
 
*RFC 2782
            - Coder Change [T.38] (rfc3264 "Re-Negotiation")
A DNS RR for specifying the location of services (DNS SRV)  
 
   
   
 
*RFC 2976
            - Call Forwarding (PBX internal, "183 Call Is Being Forwarded", "Diversion Header")   
The SIP INFO Method
 
   
   
 
*RFC 3261
            -  Overlap Dialing (rfc3578)
SIP: Session Initiation Protocol
 
 
RFC table
   
   
 
*RFC 3263
RFC Description
Session Initiation Protocol (SIP): Locating SIP Servers
RFC 1889
RTP: Real-Time Transport Protocol
Yes
RFC 2327
SDP: Session Description Protocol
Yes
RFC 2396
Uniform Resource Identifiers (URI): Generic Syntax
Yes
RFC 2543
SIP: Session Initiation Protocol (obsolete)
Yes
   
   
RFC 2616
*RFC 3264
Hypertext Transfer protocol (HTTP/1.1)
An Offer/Answer Model with the Session Description Protocol (SDP)  
Yes
   
   
RFC 2617
*RFC 3265
HTTP Authentication: Basic and Digest Access Authentication
SIP-Specific Event Notification
Yes
   
   
RFC 2782
*RFC 3326
A DNS RR for specifying the location of services (DNS SRV)
The Reason Header Field for the Session Initiation Protocol
Yes
   
   
RFC 2976
*RFC 3389
The SIP INFO Method
RTP Payload for Comfort Noise
Yes (for outband DTMF)
   
   
RFC 3261
*RFC 3515
SIP: Session Initiation Protocol
The Session Initiation Protocol (SIP) Refer Method
Yes
   
   
RFC 3263
*RFC 3550
Session Initiation Protocol (SIP): Locating SIP Servers
RTP: Transport Protocol for Real-Time Applications
Yes
   
   
RFC 3264
*RFC 3551
An Offer/Answer Model with the Session Description Protocol (SDP)
RTP Profile for A/V Conferences with Minimal Control
Yes
   
   
RFC 3265
*RFC 3555
SIP-Specific Event Notification
MIME Type Registration of RTP Payload Formats
Yes
   
   
RFC 3326
*RFC 3578
The Reason Header Field for the Session Initiation Protocol
Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)
Yes
   
   
RFC 3389
*RFC 3680
RTP Payload for Comfort Noise
SIP Event Package for Registrations
Yes
   
   
RFC 3515
*RFC 3764
The Session Initiation Protocol (SIP) Refer Method
enumservice registration for SIP Adresses-of-Record
Yes
   
   
RFC 3550
*RFC 3824
RTP: Transport Protocol for Real-Time Applications
Using E.164 numbers with SIP
Yes
   
   
RFC 3551
*RFC 3891
RTP Profile for A/V Conferences with Minimal Control
The Session Initiation Protocol ‘Replaces Header’
Yes
   
   
RFC 3555
*RFC 3892
MIME Type Registration of RTP Payload Formats
The SIP Referred-By Mechanism
Yes
-SIP-aware filtering (to prevent SIP attacks)
*RFC 4235
Dialog Package
   
   
RFC 3578
*RFC 3842
Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP)
SIP Message Waiting
Yes
   
   
RFC 3680
*RFC 3311
SIP Event Package for Registrations
re-INVITE
Yes
   
   
RFC 3764
*RFC 2833
enumservice registration for SIP Adresses-of-Record
DTMF via RTP Channel , RTP payload for DTMF
Yes
   
   
RFC 3824
*RFC 3325
Using E.164 numbers with SIP
Name identification
Yes
   
   
RFC 3891
*RFC 3578
The Session Initiation Protocol ‘Replaces Header’
Overlap Dialing
Yes
   
   
RFC 3892
*RFC 3420
The SIP Referred-By Mechanism
Internet Media Type message/sipfrag
Yes
   
   
SIP-aware filtering (to prevent SIP attacks)
Yes
RFC 4235
Dialog Package
Yes
RFC 3842
SIP Message Waiting
Yes
RFC 3311
re-INVITE
Yes
RFC 2833
DTMF via RTP Channel , RTP payload for DTMF
Yes
RFC 3325
Name identification
Yes
RFC 3578
Overlap Dialing
Yes
RFC 3420
Internet Media Type message/sipfrag
Yes
[[Category:Faq]]
[[Category:Faq]]

Revision as of 13:09, 20 April 2007

Summary

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

Applies To

This information applies to

  • All innovaphone V6 devices

Build 06-6040001 and later.

More Information

  • RFC 1889

RTP: Real-Time Transport Protocol

  • RFC 2327

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

  • 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)

  • RFC 3265

SIP-Specific Event Notification

  • 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 4235

Dialog Package

  • 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