Yealink SIP-T38G

Administrator’s Guide for SIP-T3xG IP Phones
334
 RFC 3891—The Session Initiation Protocol (SIP) ―Replaces‖ Header
 RFC 3892—The Session Initiation Protocol (SIP) Referred-By Mechanism
 RFC 3968—The Internet Assigned Number Authority (IANA) Header Field
Parameter Registry for the Session Initiation Protocol (SIP)
 RFC 3969—The Internet Assigned Number Authority (IANA) Uniform Resource
Identifier (URI) Parameter Registry for the Session Initiation Protocol (SIP)
 RFC 4028—Session Timers in the Session Initiation Protocol (SIP)
 RFC 4235—An INVITE-Initiated Dialog Event Package for the Session Initiation
Protocol (SIP)
 RFC 4662—Session Initiation Protocol (SIP) Event Notification Extension for Resource
Lists
 draft-levy-sip-diversion-04.txt—Diversion Indication in SIP
 draft-anil-sipping-bla-02.txt—Implementing Bridged Line Appearances (BLA) Using
Session Initiation Protocol (SIP)
 draft-ietf-sip-privacy-04.txt—SIP Extensions for Network-Asserted Caller Identity
and Privacy within Trusted Networks
 draft-levy-sip-diversion-06.txt—Diversion Indication in SIP
 draft-ietf-sipping-cc-conferencing-03.txt—SIP Call Control - Conferencing for User
Agents
 draft-ietf-sipping-rtcp-summary-02.txt —Session Initiation Protocol Package for
Voice Quality Reporting Event
 draft-ietf-sip-connect-reuse-04.txt—Connection Reuse in the Session Initiation
Protocol (SIP)
To find the applicable Request for Comments (RFC) document, go to
http://www.ietf.org/rfc.html and enter the RFC number.
The following SIP request messages are supported:
Method
Supported
Notes
REGISTER
Yes
INVITE
Yes
The Yealink SIP-T3xG IP
phones support mid-call
changes such as putting a
call on hold as signaled by
a new INVITE that contains
an existing Call-ID.