Thak you, Castillo, In summary, an (re)INVITE sometimes need an judgement by a human user, while an UPDATE need NOT it, that response automatecally.
By the way, which RFC that is written in and where is written? 2010/1/21 Iñaki Baz Castillo <[email protected]>: > El Jueves, 21 de Enero de 2010, Couret Tabt escribió: > >> > Also, an UPDATE is inmediately replied by the SIP core of the remote >> > endpoint. >> >> Does 'immediate' (above) means 'befor the session is established'? > > "Inmediate" means that the remote user (not the SIP UA but the user) will not > be asked by his phone to accept or reject the UPDATE. Please, recheck the > example I gave about adding video session to an existing audio session. > > > >> > In the other hand, re-INVITE could require, in some cases, authorization >> > of the user (human user). >> >> May this be done, as same, by an UPDATE , too? > > Not AFAIK. > > >> > For example, alice is in an audio call with bob, and >> > after some minutes of conversation bob decides to add video to the >> > session. This is acomplished by sending a re-INVITE with audio&video SDP. >> > Alice's phone receives such re-INVITE and ask the human user to accept or >> > reject the video session. >> >> I understood as follows: >> >> *A reINVITE MUST NOT be used until completion of the SESSION (NOT dialog). >> (For example, the session means a sequence from an INVITE to an ACK.) >> >> *An UPDATE MAY be used before completion of the SESSION. > > Yes. This can be used to change the SDP before establishing the dialog. > > >> * Both of them(a reINVITE and UPDATE) MUST NOT be used until completion >> of dialog(that means an offer/answer exchange). > > No, UPDATE can be sent before that as explained above. > > >> *An UPDATE MUST NOT be used before an initial INVITE ( that start a >> session). > > Of course, UPDATE is an in-dialog request. > > >> I think the important point is the following: >> "The SESSION and DIALOG are different." > > They are not the same. > > -- > Iñaki Baz Castillo <[email protected]> > > _______________________________________________ > 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
