Administrator’s Guide for SIP-T5 Series Smart Media Phones798Appendix H: SIP (Session Initiation Protocol)This section describes how Yealink IP phones comply with the IETF definition of SIP as describedin RFC 3261.This section contains compliance information in the following: RFC and Internet Draft Support SIP Request SIP Header SIP Responses SIP Session Description Protocol (SDP) UsageRFC and Internet Draft SupportThe following RFC’s and Internet drafts are supported: RFC 1321—The MD5 Message-Digest Algorithm RFC 1889—RTP Media control RFC 2112—Multipart MIME RFC 2327—SDP: Session Description Protocol RFC 2387—The MIME Multipart/Related Content-type RFC 2543—SIP: Session Initiation Protocol RFC 2617—Http Authentication: Basic and Digest access authentication RFC 2782—A DNS RR for specifying the location of services (DNS SRV) RFC 2806—URLs for Telephone Calls RFC 2833—RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals RFC 2915—The Naming Authority Pointer (NAPTR) DNS Resource Record RFC 2976—The SIP INFO Method RFC 3087—Control of Service Context using SIP Request-URI RFC 3261—SIP: Session Initiation Protocol (replacement for RFC 2543) RFC 3262—Reliability of Provisional Responses in the Session Initiation Protocol (SIP) RFC 3263—Session Initiation Protocol (SIP): Locating SIP Servers RFC 3264—An Offer/Answer Model with the Session Description Protocol (SDP) RFC 3265—Session Initiation Protocol (SIP) - Specific Event Notification RFC 3266—Support for IPv6 in Session Description Protocol (SDP) RFC 3310—HTTP Digest Authentication Using Authentication and Key Agreement (AKA) RFC 3311—The Session Initiation Protocol (SIP) UPDATE Method RFC 3312—Integration of Resource Management and SIP
