Class Notes (884,988)
US (343,718)
SJSU (645)
EE (86)
EE 284 (10)
balaji (10)
Lecture 7

EE 284 Lecture 7: sip notes3
Premium

6 Pages
45 Views

Department
Electrical Engineering
Course Code
EE 284
Professor
balaji

This preview shows pages 1 and half of page 2. Sign up to view the full 6 pages of the document.

Loved by over 2.2 million students

Over 90% improved by at least one letter grade.

Leah — University of Toronto

OneClass has been such a huge help in my studies at UofT especially since I am a transfer student. OneClass is the study buddy I never had before and definitely gives me the extra push to get from a B to an A!

Leah — University of Toronto
Saarim — University of Michigan

Balancing social life With academics can be difficult, that is why I'm so glad that OneClass is out there where I can find the top notes for all of my classes. Now I can be the all-star student I want to be.

Saarim — University of Michigan
Jenna — University of Wisconsin

As a college student living on a college budget, I love how easy it is to earn gift cards just by submitting my notes.

Jenna — University of Wisconsin
Anne — University of California

OneClass has allowed me to catch up with my most difficult course! #lifesaver

Anne — University of California
Description
Registration The very first request issued by a client is likely to be REGISTER, because this is the request that provides the server with an address at which the user can be reached for SIP sessions. The REGISTER request is somewhat similar to the Registration Request between a terminal and a gatekeeper in H.323. • In this scenario, Collins has logged in to host station1.work.com. This causes a REGISTER request to be sent to the local registrar. • Note the format of the Via: header and in particular the fact that it specifies the transport being used. The default is the User Datagram Protocol (UDP). • Note also that the Via: header contains a branch parameter which will discusses in proxy servers. • The From: header field indicates the address of the individual who has initiated the registration. • The To: header field indicates the “address of record” of the user being registered and is the address that the registrar will store for that user. In other words, this is the address at which the user wants to be contactable. • The From: and To: fields will be identical if a user is registering himself. The two fields need not be identical, however, which means that one individual can perform a registration on behalf of another. • Note that the From: field in our example contains a tag parameter, which is a pseudoran- dom value generated at the sender of the request and is used for identifica- tion purposes. • The Call-ID: header field is set by the originating client. In order to avoid the possibility that different clients might choose the same Call-ID, the recommended syntax for the Call-ID is [email protected], thereby making the Call-ID host specific. • In Figure 5-8, Collins has inserted a Contact: header field that indicates that future SIP messages should be routed to sip:[email protected] .work.com. In other words, messages that are addressed to sip:Collins @work.com should be forwarded to sip:[email protected] • The REGISTER request does not contain a message body, since the mes- sage is not used to describe a session of any kind. Therefore, the Content- Length: field is set to 0 Response • The response to the REGISTER request is positive, as indicted by the 200 (OK) in the response line. • Note that the content of the Via: header field is copied from request to response. The content of the CSeq: (or command sequence) header field is also copied from request to response. The CSeq: header field indicates the method used in the request and an integer num- ber. • the use of the CSeq is very important in other requests where dif- ferent requests can be issued for the same Call-ID, in which case the CSeq is used to avoid ambiguity. A response to any request must use the same value of CSeq as used in the request itself. • Through the use of the Expires: header, Collins has requested that the registration be effective for 2 hours. The registrar can change this time. • If it is specified as a number of seconds, the maximum value is such that a registration may be active for up to approximately 136 years, • If a REGISTER request contains an Expires: header with a value that is too short (the registration is to be active for too short a time), then the REGISTER request will be rejected with the status code 423 (Interval too brief). The response will include the Min-Expires: header field, which specifies the minimum registration interval that the registrar will accept. To cancel a registration request it can be done by sending another REGISTER request for the same address of record and Contact and specifying a registration interval of 0. In this case, the REG- ISTER request would be identical to the first REGISTER request, with the exceptions that the CSeq integer is incremented and the Expires header field contains the value 0. If Collins wanted to cancel all existing registra- tions, then he would send a REGISTER message with the Expires header field set to 0 and the Contact header field populated with the wildcard char- acter *. The Expires header value of 0 indicates the cancellation of a Regis- tration and the Contact: header value of * indicates that the request is applicable to all contact information for Collins. • TheTo:headerfieldisnotusedtocontaintheaddress of the registrar. 
 • TheRegistrar’saddressisindicatedinthefirstlineof the request. 
 • TheREGISTERrequestdoesnotcontainamessage body, since the message is not used to describe a session of any kind. Therefore,theContent-Length:fieldissetto 0. Invitation The INVITE request is the most fundamental and important SIP request, as it is the request used to initiate a session (i.e., establish a call). SIP Call Sequence: Invitation • TheINVITErequestisthemostfundamentaland important SIP request, as it is the request used to initiate a session (i.e., establish a call). • Figureshowsatwo-partycall • – The INVITE request is issued to 
[email protected] 
 • – this signaling flow does not traverse any proxies. Otherwise the message would be addressed to sip:manag
More Less
Unlock Document
Subscribers Only

Only pages 1 and half of page 2 are available for preview. Some parts have been intentionally blurred.

Unlock Document
Subscribers Only
You're Reading a Preview

Unlock to view full version

Unlock Document
Subscribers Only

Log In


OR

Don't have an account?

Join OneClass

Access over 10 million pages of study
documents for 1.3 million courses.

Sign up

Join to view


OR

By registering, I agree to the Terms and Privacy Policies
Already have an account?
Just a few more details

So we can recommend you notes for your school.

Reset Password

Please enter below the email address you registered with and we will send you a link to reset your password.

Add your courses

Get notes from the top students in your class.


Submit