Reference:Supported SIP Features and List of RFC's: Difference between revisions
No edit summary |
No edit summary |
||
Line 13: | Line 13: | ||
MWI (rfc3842/rfc3265 "Subscription für message-summary") | MWI (rfc3842/rfc3265 "Subscription für message-summary") | ||
DTMF (rfc2833 "RTP payload for DTMF" | DTMF (rfc2833 "RTP payload for DTMF") | ||
Name Identification (Display String, rfc3325 "Asserted Identity" | Name Identification (Display String, rfc3325 "Asserted Identity") | ||
Hold/Retrieve (rfc3264 "Offer/Answer Model for SDP") | Hold/Retrieve (rfc3264 "Offer/Answer Model for SDP") | ||
Transfer (rfc3515 "REFER Method", rfc3891 "Replaces Header | Transfer (rfc3515 "REFER Method", rfc3891 "Replaces Header) | ||
Coder Change [T.38] (rfc3264 "Re-Negotiation") | Coder Change [T.38] (rfc3264 "Re-Negotiation") |
Revision as of 13:43, 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
PBX Features and their corresponding RFCs
MWI (rfc3842/rfc3265 "Subscription für message-summary")
DTMF (rfc2833 "RTP payload for DTMF")
Name Identification (Display String, rfc3325 "Asserted Identity")
Hold/Retrieve (rfc3264 "Offer/Answer Model for SDP")
Transfer (rfc3515 "REFER Method", rfc3891 "Replaces Header)
Coder Change [T.38] (rfc3264 "Re-Negotiation")
Call Forwarding (PBX internal, "183 Call Is Being Forwarded", "Diversion Header")
Overlap Dialing (rfc3578)
List of supported RFCs
- 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