Related specifications
RFC 2617, HTTP Authentication: Basic and Digest Access Authentication, available at http://www.ietf.org/
RFC 3261, SIP: Session Initiation Protocol, available at http://www.ietf.org/
RFC 3262, Reliability of Provisional Responses in the Session Initiation Protocol (SIP), available at http://www.ietf.org/
RFC 3310, Hypertext Transfer Protocol (HTTP) Digest Authentication Using Authentication and Key Agreement (AKA), available at http://www.ietf.org/
[32] RFC 3550, RTP: A Transport Protocol for Real-Time Applications, available at http://www.ietf.org/
RFC 3551, RTP Profile for Audio and Video Conferences with Minimal Control, available at http://www.ietf.org/
RFC 4855, Media Type Registration of RTP Payload Formats, available at http://www.ietf.org/
RFC 4856, Media Type Registration of Payload Formats in the RTP Profile for Audio and Video Conferences, available at http://www.ietf.org/
RFC 3665, Session Initiation Protocol (SIP) Basic Call Flow Examples, available at http://www.ietf.org/
RFC 3824, Using E.164 numbers with the Session Initiation Protocol (S IP), available at http://www.ietf.org/
Implementation notes
Support is provided for:
the creation of a new request after responses 401 and 407. (Section 8.1.3.5, RFC 3261.) Re-INVITE once after receipt of response 491 is supported. (Section 14.2, RFC 3261.)
INVITE in and outside a dialog. CANCEL is supported outside a dialog. ACK, BYE, NOTIFY, REFER, PRACK, and UPDATE are supported inside an existing dialog. The phone responses to incoming unsupported messages with responses 501, ‘Not Implemented’, or 405, ‘Method Not Allowed’.
IPv4 and IPv6 in signalling.
E.164 numbers in SIP URI format: sip:<telephone number>@<domain>. For example, sip:[email protected], that is the parameter user:phone is not included. (RFC 3824)
HTTP Digest and Digest AKA as SIP authentication method.
Support is not available for:
Session establishment through two proxies. (Sections 3.2, RFC 3665.)
Successful session with proxy failure. (Sections 3.4, RFC 3665.)
Session through a SIP ALG. (Sections 3.5, RFC 3665.)