5JVE5V7CS25H
A couple weeks ago I gave a brief synopsis of Session Initiation Protocol (SIP) and how a basic call is initiated. This article I would like to go in a little more detail about SIP, more specifically the message, also called a method, that starts it all – the INVITE.
First, let’s start with a quick refresher as to what SIP is and how it works. SIP is a signaling protocol that can be used by VoIP technologies to establish a session between an user agent client (UAC) and an User Agent Server (UAS). Similar to HTTP, SIP is also based on a request/response model. In other words, a SIP UAC sends some sort of request to the UAS, which requires the UAS to respond back to the UAC in turn. It is important to understand that an UAC and an UAS are just logical names. In fact an UAC can also be an UAS, it just depends if it is requesting or responding to a particular transaction. A transaction is the action of an UAC sending a request to the UAS or an UAS sending a response to a UAC.
The INIVITE of SIP signaling is one type of message that an UAC sends to an UAS, which requires the UAS to act upon it and respond back to the UAS. The INVITE method is probably the most important method in the SIP protocol, also know as IETF RFC 3261, as it is used by the UAC to initiate a dialog with a UAS. A dialog is a peer-to-peer relationship between an UAC and an UAS that lasts over a period of time is known as a session. A session can be made up of multiple dialogs between UAC, UAS, and stateful proxies.
Continue Reading »