|
The 100-rel draft’s 03 version has this additional line (compared to 02) in section 6.1, that puzzles me – If the provisional response contained a Timestamp
header, this is copied into the PRACK. As per
rfc2543bis-02 Section 6.43. The Timestamp general-header field describes when the
client sent the
request to the server. The value of the timestamp is of significance
only to the client and it MAY use any timescale. The server MUST echo
the exact same value and MAY, if it has accurate information about
this, add a floating point number indicating the number of seconds
that have elapsed since it has received the request. The timestamp
is used by the client to compute the round-trip time to the server so
that it can adjust the timeout value for retransmissions. Question: if the
Timestamp is of interest only to the UAC (which sent the INVITE) and it has
received the value in a provisional response from the server, why is this to be
copied into the PRACK? |
- [Sip-implementors] UAC state machine fork? Vijay Ramachandran Iyer
- RE: [Sip-implementors] UAC state machine fork... Jonathan Rosenberg
- Re: [Sip-implementors] UAC state machine fork... Shan Lu
- RE: [Sip-implementors] UAC state machine ... Arunachalam Venkatraman
- RE: [Sip-implementors] UAC state machine fork... Jonathan Rosenberg
