Scribd
Upload
4 views

SIP-Protocol-2

The document outlines the core and extension requests in SIP (Session Initiation Protocol) messages. Core requests include INVITE, BYE, Register, Cancel, ACK, and Option, which are essential for session management. Extension requests, such as Subscribe, Notify, Publish, Refer, Info, Update, Prack, and Message, provide additional functionalities and information exchange between user agents.

Uploaded by

Adi B
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
4 views

SIP-Protocol-2

The document outlines the core and extension requests in SIP (Session Initiation Protocol) messages. Core requests include INVITE, BYE, Register, Cancel, ACK, and Option, which are essential for session management. Extension requests, such as Subscribe, Notify, Publish, Refer, Info, Update, Prack, and Message, provide additional functionalities and information exchange between user agents.

Uploaded by

Adi B
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

B Y - B H U S H A N B H O M B L E

SIP MESSAGES
a) Core Request: It is mandatory request, Must be present in SIP message.
1)INVITE: It is used to initiate session with user agent server (UAS).
2)BYE: It is used to terminate session.
3)Register: It is request which perform registration of user agent.
4)Cancel: It is used to terminate sesion which is not established. It can be only initiated by UAC.
5)ACK: It is used to acknowledge the final response to the INVITE method. ACK always go in the
direction of INVITE request.
6)Option: Option request allows UA to query another UA of its capabilities. This allows a client to
discover information about the supported method content types, extemsions, codec etc withou
ringing another party.

01
SIP MESSAGES
b) Extension Request: It is non-mandatory request.
1)Subscribe: This request is used to know current state or state update from UA. When subscribe
request is send to the server it indicates that the user wishes to receive the information about
status of the session. Subscribe request contains an expire header which tells the life of the
request made.
2)Notify: This request is used by UA to get the information about perticular event. The response to
notify is 200OK. It is always send at the start and termination of refer & subscribe request.
It comes at every state change. Subscription state may active or it may terminate.
3)Publish: It is used by UA to send event state information to the server. It is simillar to notify except
that it is not sent with in the dialog.
4)Refer: Is is used by UA to refer another UA to access the URI of a dialog. The responce for refer
request is 202 ACCEPTED. It contains “refer to” header which indicates that the recepient should
contact the third party using the information provided in the request.
5)Info: It is used for communicating mid session signalling information. It is not used to change the
state of SIP call not does it change the state of session initiated in SIP. It provides additional
optional information which can further enhance the application using SIP.

02
SIP MESSAGES
6)Update: Update is define under RFC3311. It is used for changing some of the media parameter
before and after call establishment.
7)Prack: Its stands for provisional acknowledgement. It is use to make any provisional response
reliable. There may be certain scenario where 1xx response must be deliver reliable.
eg, 1xx is carrying SDP.
PRACK contains RACK header. PRACK is applied on all 1xx response except 100 trying which is
never reliably transported.
8)Message: It is used to transport instant messages. It contain the message details in the different
format. Its successfull final response is 200 OK.

03

You might also like