Hi vineet, i read the paragraph in that book. the statement is contradictory because the example which he talks about multiple m= lines i.e., media descriptions with single session description which won't match the the mentioned statement - ....There could more than one session description within a single SIP message.
As per my understanding, multiple session description will appear in a SIP message(using content-disposition header for boundary puposes) when there is a early media concept comes. Instead of adding multiple session description in a single sip message, send re-invite with different session/media description as many times as you want. I hope i gave sufficient information w.r.t your doubt. Regards, Praveen On Thu, Mar 1, 2012 at 12:45 PM, Vineet Menon <[email protected]>wrote: > The book is.. > > session initiation protocol (SIP) controlling convergent networks.. by > travis russel... > http://books.google.co.in/books/about/Session_Initiation_Protocol_SIP.html?id=WxXc0coHxyYC&redir_esc=y > > pp. 48, paragraph 1 > it says and I quote: > "One SIP invite could carry within itself SDP descriptors for more than > one session. This is so when supporting a conference call, as an example." > > Is this regarding the relationship between dialog and session? > I mean a conference can have multiple dialog within a single session! > > Regards, > > Vineet Menon > > > > > > On 29 February 2012 23:54, praveena ss <[email protected]> wrote: > >> Hi Paul... >> >> "RFC 3959-Early Session Disposition Type for SIP" is implemented in >> Packetcable2.0 RSTF solution. >> >> Vineeth............. can u give me the reference the one u read... >> >> Regards, >> Praveen. >> >> On Wed, Feb 29, 2012 at 9:33 PM, Paul Kyzivat <[email protected]> >> wrote: >> >> > On 2/29/12 4:33 AM, Vineet Menon wrote: >> > > Hi, >> > > >> > > I just read in a book about SIP that a single INVITE message can have >> > > multiple SDP payload...to be used for conferences. >> > > Why is multiple SDP needed in a conference scenario? >> > > Any ideas anyone?? >> > >> > This is news to me. What book? >> > >> > RFC3959 defines the early-session content-disposition, for purposes of >> > negotiating an early media session prior to answer that is distinct from >> > the eventual session. In principle this can result in two SDP body parts >> > in the same sip message. But I have never heard of this RFC having been >> > implemented. >> > >> > Thanks, >> > Paul >> > _______________________________________________ >> > 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 >> > > -- ------------------------------ Thanks and Regards, Praveen _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
