Commit b8938063 authored by Pekka Pessi's avatar Pekka Pessi

sip: updated documentation.

darcs-hash:20061207173533-65a35-bb2f502481401b0961e6e457a4ca4a45b9a10b35.gz
parent 5cd4231d
......@@ -172,7 +172,8 @@ static int sip_event_update(msg_common_t *h,
* follows:
*
* @code
* Allow-Events = ( "Allow-Events" | "u" ) ":" 1#event-type
* Allow-Events = ( "Allow-Events" / "u" ) HCOLON event-type
* *(COMMA event-type)
* @endcode
*
* The parsed Allow-Events header is stored in #sip_allow_events_t structure.
......
......@@ -218,8 +218,8 @@ issize_t sip_proxy_authenticate_e(char b[], isize_t bsiz, sip_header_t const *h,
*
* The Proxy-Authorization header consists of credentials containing the
* authentication information of the user agent for the proxy and/or realm
* of the resource being requested. Its syntax is defined in [H14.34,
* S10.32] (as follows:
* of the resource being requested. Its syntax is defined in @RFC3261
* as follows:
*
* @code
* Proxy-Authorization = "Proxy-Authorization" ":" credentials
......@@ -273,16 +273,17 @@ issize_t sip_proxy_authorization_e(char b[], isize_t bsiz, sip_header_t const *h
*
* The WWW-Authenticate header consists of at least one challenge that
* indicates the authentication scheme(s) and parameters applicable to the
* Request-URI. Its syntax is defined in [H14.47, S10.48] as
* Request-URI. Its syntax is defined in @RFC3261 as
* follows:
*
* @code
* WWW-Authenticate = "WWW-Authenticate" ":" 1#challenge
* challenge = auth-scheme 1*SP #auth-param
* WWW-Authenticate = "WWW-Authenticate" HCOLON challenge
* challenge = ("Digest" LWS digest-cln *(COMMA digest-cln))
* / other-challenge
* other-challenge = auth-scheme LWS auth-param *(COMMA auth-param)
* @endcode
*
* @todo Currently the parser fails if several challenges are included one
* header.
* See @ProxyAuthenticate for the definition of \<digest-cln\>.
*
* The parsed WWW-Authenticate header
* is stored in #sip_www_authenticate_t structure.
......
......@@ -1120,7 +1120,7 @@ int sip_response_terminates_dialog(int response_code,
This response indicates that the peer has lost its copy of the dialog
state. The dialog and any usages sharing it are destroyed.
The dialog
The dialog
itself should not be destroyed unless this was the last usage.
The effects of a 481 on a dialog and its usages are the most
ambiguous of any final response. There are implementations that
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment