On Wed, Jul 2, 2008 at 12:57 AM, <[EMAIL PROTECTED]> wrote: > IMMO, since the timestamp of the original request was set by the same > originating UAC, the UAC can simply substract the timestamp value when this > particular response was received and the original value set in the Timestamp > header (the one received in the response). This will help the UAC > automatically estimate RTT, without the need of storing the value when > sending the initial request -"storage" is actually achieved by mandating the > UAS copy the value into the response. As Víctor indicates, this should be > useful to adapt timers. > > Furthermore, with the delay parameter added by the UAS, the UAC can even > estimate what percentage of the total RTT was consumed as processing delay > at the UAS.
Exactly. I just want to add that AFAIK this RTT estimation can only be computed if a 100 (Trying) response is received before the client transaction generates a retransmission. -- Victor Pascual Ávila _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
