Showing posts with label SIP. Show all posts
Showing posts with label SIP. Show all posts

Sunday, February 28, 2010

183 SIP MESSAGE- Session Progress Method

There are instances, most notably dealing with SIP to PSTN interwork-
   ing, that necessitate that the SIP called User Agent (UA) be able to
   suppress local alerting by the SIP calling UA and to set up a prelim-
   inary media session from the called UA to the calling UA.  This would
   allow the called UA to play back media prior to the full SIP session
   being set up.  This media would be used to report on the status of
   the session setup request.  It could also be used to play music while
   the session setup is attempted.  This would be useful for find-me
   like services that involve attempting multiple locations for a single
   setup request.

   The only method in the current SIP specification that allows the
   called UA to playback media would be to set up a full SIP session. In
   PSTN interworking situations (and likely in end-to-end SIP sessions)
   this will cause a billing relationship to be established between net-
   works for the session.  This causes a problem when the reason for
   setting up the media session is to indicate a failure in the session
   setup.

Wednesday, February 10, 2010

SIP Communication Example


SIP Communication Example

In this section a call will be analyzed in detail. In a SIP call there are several SIP transactions. A SIP transaction consists of several requests and answers and the way to group them in the same transaction is by means of CSeq parameter.
User AProxyUser B
- The first step is the user register. The users must register themselves to be found by other users. In this case, the terminals send a REGISTER request, where the fields "from" and "to" correspond to the registered user. The Proxy server, who acts as Register, consults if the user can be authenticated and sends an OK message if there is no problem.

-The following transaction corresponds to a session establishment. This session consists of an INVITE request of the user to the proxy. Immediately, the proxy sends a TRYING 100 to stop the broadcastings and reroute the request to the B user. The B user sends a Ringing 180 when the telephone begins to ring and it is also reroute by the proxy to the A user. Finally, the OK 200 message corresponds to the accept process (the user B response the call).

-At this moment the call is established, and the RTP transport protocol starts with the parameters (ports, addresses, codecs, etc.) of the SDP protocol.

-The last transaction corresponds to a session end . This is carried out with an only BYE request to the Proxy, and later reroute to the B user. This user replies with an OK 200 message to confirm that the final message has been received correctly.

Very useful link-
http://www.docs.hp.com/en/5992-4080/ch01s05.html

http://toncar.cz/Tutorials/VoIP/VoIP_Protocols_SIP_Messages.html