Administrator’s Guide for SIP-T2 Series/T19(P) E2/T4 Series/CP860 IP Phones1018 RFC 5806—Diversion Indication in SIP RFC 5954—Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261 RFC 6026—Correct Transaction Handling for 2xx Responses to SIP INVITE Requests RFC 6141—Re-INVITE and Target-Refresh Request Handling in SIP draft-ietf-sip-cc-transfer-05.txt—SIP Call Control - Transfer draft-anil-sipping-bla-02.txt—Implementing Bridged Line Appearances (BLA) Using SessionInitiation Protocol (SIP) draft-anil-sipping-bla-03.txt—Implementing Bridged Line Appearances (BLA) Using SessionInitiation Protocol (SIP) draft-ietf-sip-privacy-00.txt—SIP Extensions for Caller Identity and Privacy, November draft-ietf-sip-privacy-04.txt—SIP Extensions for Network-Asserted Caller Identity andPrivacy within Trusted Networks draft-levy -sip-diversion-08.txt—Diversion Indication in SIP draft-ietf-sipping-cc-conferencing-03.txt—SIP Call Control - Conferencing for User Agents draft-ietf-sipping-cc-conferencing-05.txt—Connection Reuse in the Session InitiationProtocol (SIP) draft-ietf-sipping-rtcp-summary-02.txt—Session Initiation Protocol Package for VoiceQuality Reporting Event draft-ietf-sip-connect-reuse-06.txt—Connection Reuse in the Session Initiation Protocol(SIP) draft-ietf-bliss-shared-appearances-15.txt—Shared Appearances of a Session InitiationProtocol (SIP) Address of Record (AOR)To find the applicable Request for Comments (RFC) document, go tohttp://www.ietf.org/rfc.html and enter the RFC number.SIP RequestThe following SIP request messages are supported:Method Supported NotesREGISTER YesINVITE YesYealink IP phones supportmid-call changes such asplacing a call on hold assignaled by a new INVITEthat contains an existingCall-ID.ACK YesCANCEL Yes
