text stringlengths 17k 45.8k |
|---|
Network Working Group J. Rosenberg Request for Comments: 3261 dynamicsoft Obsoletes: 2543 H. Schulzrinne Category: Standards Track Columbia U. G. Camarillo Ericsson A. Johnston World Com J. Peterson Neustar R. Sparks dynamicsoft M. Handley ICIR E. Schooler AT&T June 2002 SIP: Session Initiation Protocol Status of this ... |
locate Bob. Similarly, more than one user can be registered on a single device at the same time. The location service is just an abstract concept. It generally contains information that allows a proxy to input a URI and receive a set of zero or more URIs that tell the proxy where to send the request. Registrations are... |
requests. These six header fields are the fundamental building blocks of a SIP message, as they jointly provide for most of the critical message routing services including the addressing of messages, the routing of responses, limiting message propagation, ordering of messages, and the unique identification of transact... |
targeted by the initial request but specify additional transport parameters such as a different server or multicast address to try, or a change of SIP transport from UDP to TCP or vice versa. However, redirect servers MUST NOT redirect a request to a URI equal to the one in the Request-URI; instead, provided that the ... |
represents a peer-to-peer SIP relationship between two user agents that persists for some time. The dialog facilitates sequencing of messages between the user agents and proper routing of requests between both of them. The dialog represents a context in which to interpret SIP messages. Section 8 discussed method indep... |
Note that the paragraph above refers to automatically generated BYEs and re-INVITEs. If the user hangs up upon media failure, the UA would send a BYE request as usual. 14. 1 UAC Behavior The same offer-answer model that applies to session descriptions in INVITEs (Section 13. 2. 1) applies to re-INVITEs. As a result, a... |
Furthermore, if the Request-URI contains a SIPS URI, TLS MUST be used to communicate with that proxy. If the copy contains a Route header field, the proxy MUST inspect the URI in its first value. If that URI does not contain an lr parameter, the proxy MUST modify the copy as follows:Rosenberg, et. al. Standards Track ... |
Rosenberg, et. al. Standards Track [Page 120] RFC 3261 SIP: Session Initiation Protocol June 2002 P4 is not responsible for the resource indicated in the Request-URI so it will leave it alone. It notices that it is the element in the first Route header field value so it removes it. It then prepares to send the request ... |
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. The branch parameter in the topmost Via header field of the request is examined. If it is present and begins with the magic cookie "z9h G4b K", the request was gener... |
sip:carol@chicago. com sip:carol@chicago. com;newparam=5 sip:carol@chicago. com;security=on sip:biloxi. com;transport=tcp;method=REGISTER?to=sip:bob%40biloxi. com sip:biloxi. com;method=REGISTER;transport=tcp?to=sip:bob%40biloxi. com sip:alice@atlanta. com?subject=project%20x&priority=urgent sip:alice@atlanta. com?pri... |
Two From header fields are equivalent if their URIs match, and their parameters match. Extension parameters in one header field, not present in the other are ignored for the purposes of comparison. This means that the display name and presence or absence of angle brackets do not affect matching. See Section 20. 10 for... |
Example response to a request with the Request-URI sip:lee@example. com: SIP/2. 0 485 Ambiguous Contact: Carol Lee <sip:carol. lee@example. com> Contact: Ping Lee <sip:p. lee@example. com> Contact: Lee M. Foote <sips:lee. foote@example. com> Some email and voice mail systems provide this functionality. A status code s... |
* Content-Type: application/sdp * * * * v=0 * * o=alice 53655765 2353687637 IN IP4 pc33. atlanta. com * * s=- * * t=0 0 * * c=IN IP4 pc33. atlanta. com * * m=audio 3456 RTP/AVP 0 1 3 99 * * a=rtpmap:0 PCMU/8000 * ******************************************************* Rosenberg, et. al. Standards Track [Page 206] RFC ... |
[ message-body ]Request-Line = Method SP Request-URI SP SIP-Version CRLFRequest-URI = SIP-URI / SIPS-URI / absolute URIabsolute URI = scheme ":" ( hier-part / opaque-part )hier-part = ( net-path / abs-path ) [ "?" query ]net-path = "//" authority [ abs-path ]abs-path = "/" path-segments Rosenberg, et. al. Standards Tr... |
Rosenberg, et. al. Standards Track [Page 240] RFC 3261 SIP: Session Initiation Protocol June 2002 The usage of S/MIME in SIP is detailed in Section 23. 26. 3 Implementing Security Mechanisms26. 3. 1 Requirements for Implementers of SIP Proxy servers, redirect servers, and registrars MUST implement TLS, and MUST support... |
It is now well specified; if a request had a Route header field, its CANCEL or ACK for a non-2xx response to the request need to carry the same Route header field values. ACKs for 2xx responses use the Route values learned from the Record-Route of the 2xx responses. o RFC 2543 allowed multiple requests in a single UDP... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.