This video explains very basic sip(session initiation protocol) call flow as per the RFC 3261. We have used well known sip proxy opensips for our experiment. This flow explains the sip transaction, sip dialog, different request etc.
The 100 (Trying) response indicates that the INVITE has been received and that the proxy is working on her behalf to route the INVITE to the destination
Great Presentation . I was very impatient to read the entire stuff online & learn . But this presentation has made it in a very short time . Now I am clear with the basic working of the SIP protocol . Please continue the same method of teaching . 1. 100 is sent to avoid re-transmission of Invite (much like a TCP-ACK ) , informing the sender that "I have received the invite packet " 2. I am not sure about the second question . I am not aware of the fields in the SIP protocol .Since I am from the ip domain , I could give you an answer wrt the IP DOMAIN . If the route for the destination (1002 ) is through the proxy , then it would obviously pass through it . (It would answer this , after looking into the information at the SIP layer ) Venky .
Than you very much!!!!!!!!Very nice video for basic understanding of SIP. 100 trying is sending bcz to stop the retransmission of SIP. Proxy has to add Record Route header it'self if he want to bypass all message and response.
Many thanks for giving this video and it gave me more idea about SIP .. Its really helpful for the beginners ..looking forward to ur next video Message Header Exp ....
Good guide, very clear! Thank You, Vishal! Some extracts from rfc could be also useful here for someone who're looking for understanding of SIP dialogs: 1) A dialog is identified at each UA with a dialog ID, which consists of a Call-ID value, a local tag and a remote tag. 2) Dialogs are created through the generation of non-failure responses to requests with specific methods. Within this specification, only 2xx and 101-199 responses with a To tag, where the request was INVITE, will establish a dialog.
It is very impressive and helpful with SIP experiment demo. Thank you very much for sharing your your knowledge with the experiment. However you lost the audio after you make the SIP call. I could not hear your explanation very well after the call set up.
100 trying is for indication for client as INVITE has been received , so client won't send the INVITE request again...if 100trying was not received then the client send continuously INVITE requests.
Thanks for your series of videos, i liked your explanation and practical series the most!! Probably you can improve on your accent a bit and make it more neutral, that's my only suggestion.
Hi Vishal, Thanks for the great explanation. One Question is always irritating me !> Why ACK is termed as seperate transaction when Invite goes with C-SEQ = 1 Invite from Invite to 20Ok , ACK has C-SEQ = 1 ACK and BYE C-SEQ = 2 BY E so it clearly show only 2 transactions right. Why ACK is termed as SEPERATE TRANSACTIONS.