What is RFC 3261?

Rosenberg, et. al. Standards Track [Page 137] RFC 3261 SIP: Session Initiation Protocol June 2002 17.2.3 Matching Requests to Server Transactions When a request is received from the network by the server, it has to be matched to an existing transaction. This is accomplished in the following manner.

What does 3261 stand for?

RFC 3261 SIP: Session Initiation Protocol June 2002 encrypted request properly, which could lead to some avoidable error signaling. This is especially likely when an encrypted request is forked.

When is the header field required in RFC 3261 SIP?

RFC 3261 SIP: Session Initiation Protocol June 2002 *: The header field is required if the message body is not empty. See Sections 20.14, 20.15 and 7.4 for details. -: The header field is not applicable.

What is Max-Forwards in RFC 3261?

RFC 3261 SIP: Session Initiation Protocol June 2002 8.1.1.6 Max-Forwards The Max-Forwards header field serves to limit the number of hops a request can transit on the way to its destination. It consists of an integer that is decremented by one at each hop.

Which authentication is not enclosed in quotation marks in RFC 3261?

RFC 3261 SIP: Session Initiation Protocol June 2002 authentication is not enclosed in quotation marks. (The example in Section 3.5 of RFC 2617 is correct.) For SIP, the ‘uri’ MUST be enclosed in quotation marks. 3. The BNF for digest-uri-value is: digest-uri-value = Request-URI ; as defined in Section 25 4.