This is permitted to give a chance to crashed end-points to re-create state from a mid-dialog request such as re-INVITE to refresh the call. This is clearer from Section 16.6: Step 4.
"The proxy will remain on the path if it chooses to not insert a Record-Route header field value into requests that are already part of a dialog. However, it would be removed from the path when an endpoint that has failed reconstitutes the dialog." Regards, Siddharth -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Will Quan Sent: Wednesday, March 14, 2007 5:47 AM To: [email protected] Subject: [Sip-implementors] Record-Route in dialog Quick query from 3261 section 12.2 "Requests within a Dialog"..<<SNIP>>Requests within a dialog MAY contain Record-Route and Contact header fields. However, these requests do not cause the dialog's route set to be modified, although they may modify the remote target URI. Specifically, requests that are not target refresh requests do not modify the dialog's remote target URI, and requests that are target refresh requests do.<<END>>Since the routeset is already established, why would the Record-Route headers be allowed in new requests?-will _______________________________________________ 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
