ProDeveloperTutorial.com

Tutorials and Programming Solutions
Menu
  • Shell Scripting
  • System Design
  • Linux System Programming
  • 4g LTE
  • Coding questions
  • C
  • C++
  • DSA
  • GIT
  • 450 DSA Cracker
  • 5G NR
  • O-RAN

SIP Registration and Invite Call flow

prodevelopertutorial August 31, 2020

In this chapter we shall see SIP Registration and SIP Invite call flow.

 

SIP REGISTRATION Call flow:

   User1                        SIP Server
     |                               |
     |          REGISTER M1          |
     |------------------------------>|
     |      401 Unauthorized M2      |
     |<------------------------------|
     |          REGISTER M3          |
     |------------------------------>|
     |            200 OK M4          |
     |<------------------------------|
     |                               |

In the above diagram, User 1 is trying to register to SIP server.

User1 will first send registration request to SIP server (M1).

Then SIP server will challenge the Registration request by sending 401 Unauthorized response (M2).

Then User1 will fill the user information and sends one more Registration Request (M3).

SIP server will check HSS database and validates user’s credentials.

Then SIP server will send “200 OK” (M4).

SIP INVITE Call flow through two proxies.

     A            Proxy 1          Proxy 2              B
     |                |                |                |
     |   INVITE M1    |                |                |
     |--------------->|                |                |
     |     407 M2     |                |                |
     |<---------------|                |                |
     |     ACK M3     |                |                |
     |--------------->|                |                |
     |   INVITE M4    |                |                |
     |--------------->|   INVITE M5    |                |
     |     100  M6    |--------------->|   INVITE M7    |
     |<---------------|     100  M8    |--------------->|
     |                |<---------------|                |
     |                |                |     180 M9     |
     |                |    180 M10     |<---------------|
     |     180 M11    |<---------------|                |
     |<---------------|                |     200 M12    |
     |                |    200 M13     |<---------------|
     |     200 M14    |<---------------|                |
     |<---------------|                |                |
     |     ACK M15    |                |                |
     |--------------->|    ACK M16     |                |
     |                |--------------->|     ACK M17    |
     |                |                |--------------->|
     |                Both Way RTP Media                |
     |<================================================>|
     |                |                |     BYE M18    |
     |                |    BYE M19     |<---------------|
     |     BYE M20    |<---------------|                |
     |<---------------|                |                |
     |     200 M21    |                |                |
     |--------------->|     200 M22    |                |
     |                |--------------->|     200 M23    |
     |                |                |--------------->|
     |                |                |                |

 

From the above image we can see that, User Agent “A” is calling User Agent “B”.

“A” will initiate a SIP session by sending “INVITE” request (M1) to the proxy server.

The proxy server will challenge “A” by sending “407” response (M2). “A” will acknowledge it by sending “ACK” (M3) message.

Then “A” will send “INVITE” request with authentication details. Proxy 1 will verify the changes and forwards INVITE to Proxy 2. (M5).

As soon as “Proxy 1” forwards message to “Proxy 2”, “Proxy 1” will send “100 trying” to “A”.

When the “INVITE” is reached to “B” (M7), “B” UA will send “180 Ringing” to “A”.

If “B” picks the call, it will send “200Ok” to “A” (M12).

“A” will acknowledge the final response to INVITE message by sending “ACK” (M15).

Then the session has been established, and 2 way audio communication will start.

If “B” wants to terminate the current session, then “BYE” will be sent (M19).

“A” responds to it by sending “200OK” (M21) to “B.”

Reference: RFC 3261

 

 

Share
Email
Tweet
Linkedin
Reddit
Stumble
Pinterest
Prev Article
Next Article

About The Author

prodevelopertutorial

Follow this blog to learn more about C, C++, Linux, Competitive Programming concepts, Data Structures.

Leave a Reply Cancel Reply

You must be logged in to post a comment.

ProDeveloperTutorial.com

Tutorials and Programming Solutions
Copyright © 2023 ProDeveloperTutorial.com
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept”, you consent to the use of ALL the cookies.
Do not sell my personal information.
Cookie SettingsAccept
Manage consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
SAVE & ACCEPT