Hi Siga,

Take a look at the very well explained examples on Tech-invite
http://www.tech-invite.com/Ti-sip-service-1.html or
http://www.tech-invite.com/Ti-sip-archi.html (I've found this site to be
very useful). Also do not forget about early media such as in the case of a
183 response, which is where the media will begin before a 200 response is
received from an INVITE request. Like the others have stated, how you handle
your actual media code is specific to you, but for example in my
implementations I setup or initialize my media before I send an INVITE (that
way I know all resources are ready to go and also am able to provide the
connection info) and as soon as I receive an SDP payload (the answer to my
offer) in a 183 or 200 response I update my media to match the SDP answer
and begin sending media based on the transport (like RTP over UDP) and codec
(like g711u) described in the SDP answer. So in other words in my
implementations, because I react to responses or requests where SDP is
answered or offered, I rely on the ACK simply as a way to acknowledge that
the 200 OK response was received (that way I can stop resending the 200 OK
based on its timer) and not an indication that I should start sending audio
now.

I hope that helps,
Brandon

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Siga
Sent: Wednesday, December 08, 2010 6:57 AM
To: [email protected]
Subject: [Sip-implementors] after ACK, the sequence of events to take place!

Hi,
I wanted to have some general information regarding the sequence of events
after the Client sends ACK to the Server. Exactly after this what should
initiated. I have read in the books and seen the block diagram that the
media session should be established. But can one explain me what should be
done after this. Whether RTP should be initiated or the audio part where the
conversion of analog audio data to pcm data and the compression and so
on........,  I am really out of way here.
Or is there any good example which shows all these in one shot.

Regards,
Siga
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to