On a related note, you might be interested to read RFC 4321 and RFC 4320, if you haven't read them already.
On Thu, Feb 4, 2010 at 12:33 AM, Iñaki Baz Castillo <[email protected]> wrote: > El Miércoles, 3 de Febrero de 2010, Olle E. Johansson escribió: >> > However I've found a case in which this mechanism is needed: >> > >> > - alice sends MESSAGE to bob through the proxy. >> > - the proxy replies 100 to alice and routes the MESSAGE to bob. >> > - bob replies 200. >> > - the proxy replies 200 to alice but the message is lost due to >> > network problems. >> > - alice (according to RFC 3261) retransmits the MESSAGE. >> > >> > Is it? >> >> I think that is it. It makes sense to me. > > Understood now. In INVITE transaction the above is not required as the UAS > would retransmit the final response until getting an ACK (from the proxy if > it's a [3456]XX or from the UAC if it's a 2XX). > > SIP is easy! > > :) > > > -- > 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
