Just to request more clarification, did you originally mean a single call-id but different dialogs based on the To/From/Tags?
Kedar On 8/11/06, Bob Penfield <[EMAIL PROTECTED]> wrote: > > I stand corrected. A "session" is the set of media streams. I guess what I > was using the term session for can best be described as the collection of > dialogs created by a single dialog creating request. I don't know if we > have > a term for that. We call it a SIP session (as opposed to the media session > that the SDP describes) in our software. > > cheers, > (-:bob > > Robert F. Penfield > Chief Software Architect > Acme Packet, Inc. > 71 Third Avenue > Burlington, MA 01803 > [EMAIL PROTECTED] > > > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Friday, August 11, 2006 10:18 AM > Subject: Re: [Sip-implementors] Session, Dialog in RFC > > > > From: Benny Prijono <[EMAIL PROTECTED]> > > > > So unless these has been invalidated by recent discussions, I propose > we > > maintain the above definition of "session", and change your definition > > of "session" to something else (maybe "session-set", or > > "super-session"?). > > > > I'm not sure that I'm understanding everyone, but "session" has a set > > meaning, and it is *prior to* SIP -- it's a set of media streams, > > often as described by a particular SDP description. So when it says > > "the session is terminated", it means "stop sending media and don't be > > surprised if there is no incoming media". > > > > Dale > > _______________________________________________ > > 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 > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
