Yealink SIP-T2XP Administrator's Guide

Administrator’s Guide for SIP-T2xP and SIP-T19P IP Phones
434
This section describes how Yealink IP phones comply with the IETF definition of SIP as
described in 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) Usage
The 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 2246—The TLS Protocol Version 1.0
 RFC 2327—SDP: Session Description Protocol
 RFC 2543—SIP: Session Initiation Protocol
 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 2806—URLs for Telephone Calls
 RFC 2833—RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals
 RFC2915—The Naming Authority Pointer (NAPTR) DNS Resource Record
 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)

Yealink SIP-T2XP Specifications

General

Brand	Yealink
Model	SIP-T2XP
Category	IP Phone
Language	English