Reference:Supported SIP Features and List of RFC's: Difference between revisions
Jump to navigation
Jump to search
(New page: ==Summary== SIP Pbx Features and list of RFC’s supported in version 6 of innovaphone firmware ==Applies To== This information applies to This information applies to − all i...) |
No edit summary |
||
Line 40: | Line 40: | ||
- Call Forwarding (PBX internal, "183 Call Is Being Forwarded", "Diversion Header") | - Call Forwarding (PBX internal, "183 Call Is Being Forwarded", "Diversion Header") | ||
- Overlap Dialing (rfc3578) | - Overlap Dialing (rfc3578) | ||
Revision as of 12:29, 20 April 2007
Summary
SIP Pbx Features and list of RFC’s supported in version 6 of innovaphone firmware
Applies To
This information applies to
This information applies to
− all innovaphone products with V6
Build 06-604000102 and later.
More Information
Supported Sip features in the innovaphone Pbx
- 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)
RFC table
RFC Description
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
Hypertext Transfer protocol (HTTP/1.1) Yes
RFC 2617
HTTP Authentication: Basic and Digest Access Authentication Yes
RFC 2782
A DNS RR for specifying the location of services (DNS SRV) Yes
RFC 2976
The SIP INFO Method Yes (for outband DTMF)
RFC 3261
SIP: Session Initiation Protocol Yes
RFC 3263
Session Initiation Protocol (SIP): Locating SIP Servers Yes
RFC 3264
An Offer/Answer Model with the Session Description Protocol (SDP) Yes
RFC 3265
SIP-Specific Event Notification Yes
RFC 3326
The Reason Header Field for the Session Initiation Protocol Yes
RFC 3389
RTP Payload for Comfort Noise Yes
RFC 3515
The Session Initiation Protocol (SIP) Refer Method Yes
RFC 3550
RTP: Transport Protocol for Real-Time Applications Yes
RFC 3551
RTP Profile for A/V Conferences with Minimal Control Yes
RFC 3555
MIME Type Registration of RTP Payload Formats Yes
RFC 3578
Mapping of Integrated Services Digital Network (ISDN) User Part (ISUP) Overlap Signalling to the Session Initiation Protocol (SIP) Yes
RFC 3680
SIP Event Package for Registrations Yes
RFC 3764
enumservice registration for SIP Adresses-of-Record Yes
RFC 3824
Using E.164 numbers with SIP Yes
RFC 3891
The Session Initiation Protocol ‘Replaces Header’ Yes
RFC 3892
The SIP Referred-By Mechanism 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
…