Supported RFCs(Request for Comments)

Scout's SIP implementation is compliant with the following IETF Request for Comments (RFCs).

Core RFCs Title
RFC 2617 HTTP Authentication: Basic and Digest Access Authentication
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 3581 An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing
RFC 4320 Actions Addressing Identified Issues with the Session Initiation Protocol's (SIP) Non-INVITE Transaction
RFC 4566 SDP: Session Description Protocol
 
DNS-Related RFCs 
RFC 3263 Session Initiation Protocol (SIP): Locating SIP Servers [also listed above]
RFC 2181 Clarifications to the DNS Specification
RFC 2915 The Naming Authority Pointer (NAPTR) DNS Resource Record
RFC 2782 A DNS RR for specifying the location of services (DNS SRV)
 
Extension RFCs
RFC 2976 The SIP INFO Method
RFC 3265 Session Initiation Protocol (SIP)-Specific Event Notification
RFC 3311The Session Initiation Protocol (SIP) UPDATE Method
RFC 3326The Reason Header Field for the Session Initiation Protocol (SIP)
RFC 3420 Internet Media Type message/sipfrag
RFC 3515The Session Initiation Protocol (SIP) Refer Method
RFC 3891The Session Initiation Protocol (SIP) "Replaces" Header
RFC 3892The Session Initiation Protocol (SIP) Referred-By Mechanism
RFC 4028Session Timers in the Session Initiation Protocol (SIP)
RFC 4488 Suppression of Session Initiation Protocol (SIP) REFER Method Implicit Subscription
RFC 4538Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)
RFC 5359Session Initiation Protocol Service Examples
RFC 5589 Session Initiation Protocol (SIP) Call Control - Transfer
 
RTP-Related RFCs
RFC 1889 Realtime Transport Protocol (RTP)
RFC 2833 / 4733 RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals
RFC 3551RTP Profile for Audio and Video Conferences with Minimal Control
RFC 4856Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences