[qodef_icon_with_text icon_pack=”simple_line_icons” simple_line_icons=”icon-location-pin” icon_position=”left” icon_type=”normal” icon_size=”qodef-icon-tiny” icon_animation=”” icon_margin=”3px 0 0 0″ title=”1801 Saint Clair Ave. NE” title_tag=”h6″ text=”Cleveland, OH 44114″ custom_icon_size=”28″ text_color=”#212121″ text_left_padding=”0″ icon_color=”#7c7c7c” title_color=”#212121″]

[qodef_icon_with_text icon_pack=”simple_line_icons” simple_line_icons=”icon-call-out” icon_position=”left” icon_type=”normal” icon_size=”qodef-icon-tiny” icon_animation=”” icon_margin=”3px 0 0 0″ title=”216.619.2000″ title_tag=”h6″ text=”888.626.3828″ custom_icon_size=”28″ text_color=”#212121″ text_left_padding=”0″ icon_color=”#7c7c7c” title_color=”#212121″]

SIP. A Primer. What the Heck is that?

SIP. A Primer. What the Heck is that?

In the world of telecommunications, SIP is a buzzword used by many but often misunderstood. SIP stands for Session Initiation Protocol and is defined in RFC 3261. SIP is a signaling protocol designed to set up, tear down and modify phone calls on modern VoIP networks. To be clear, SIP is not what transports the actual audio stream for a phone call; that transport is provided by the RTP (Real-time Transport Protocol) in a modern VoIP network and will be addressed in a later blog post.

 

The image below illustrates how a SIP dialog takes place:

What_is_SIP

 

In the SIP diagram above, User X picks up the phone and dials the extension of User Y. A SIP Invite message is then sent to User Y containing information about who the call is from, where the call is going, and how the audio of the call is to be routed.

Next, User Y’s phone sends a couple of messages back to User X’s phone. The first message indicates that it is trying to locate the phone User X is attempting to reach (in this case, User Y’s). The second message notifies User X that User Y’s phone has started ringing.

Once User Y has answered the phone, another SIP message is sent to User X’s phone indicating User Y has picked up the call. User X’s phone then relays a SIP message back to User Y’s phone recognizing that the call has been answered.

At that point, the path for the audio of the call has been negotiated in a series of messages containing SDP (Session Description Protocol). The audio can then flow between the two devices. In the example above, when User Y hangs up the phone, another SIP message is sent to User X’s phone indicating the call has been disconnected. A final message is then sent from User X’s phone to User Y’s phone acknowledging that the call has ended.  

This is a very fundamental example of how Session Initiation Protocol works. However, more often than not, multiple SIP proxies and NAT (Network Address Translation) devices are involved in the process but we will save that explanation for another day!

 

Did you find the SIP infographic helpful? Are you interested in finding out more? Schedule a discovery call or request a free sip trial!