>Technically, it is a dialog, but it is commonly referred to as a >session. Thats too bad that specification wont say it 100%. Otherwise every implementor will choose own naming.
>Yes. Some common examples are INVITE/PRACK, INVITE/UPDATE transactions INVITE and UPDATE ??? isn't it do race condition, both may change media settings. Raj Jain wrote: > On Thu, May 29, 2008 at 7:33 AM, Ivar Lumi <[EMAIL PROTECTED]> wrote: > >> What is right term for INVITE dialog + media ? >> Call,Invite session, ... >> > > Technically, it is a dialog, but it is commonly referred to as a > session. The term 'session' is somewhat abstract, however. Search this > mailing list's archives and you'll see various attempts at defining > the term session. > > >> Can dialog have multiple active transactions ? >> In rfc i found only place what restricts to have single INVITE, but what >> about other transactions. >> > > Yes. Some common examples are INVITE/PRACK, INVITE/UPDATE transactions > that can run simultaneously w/in a dialog. > > >> What UA must show If proxy forks request and >> 1 target returns 180 Ringing >> 2 target returns 182 Queued >> > > That is implementation-defined. > > -- > Raj Jain > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
