Based upon RFC 3891 section 4, the URI portion of the Refer-To should reflect the Contact’s URI. The Replaces header is embedded within the Refer-To URI. Examples are within RFC 5359 and RFC 3515.
RFC 3891 section 4. “Although this specification takes reasonable precautions to prevent unexpected behavior in the face of forking, implementations SHOULD only address replacement requests (i.e., set the Request-URI of the replacement request) to the SIP Contact URI of the target.” *From:* K sipuser [mailto:subscriberaddr...@yahoo.com] *Sent:* Tuesday, September 29, 2015 11:20 AM *To:* Brett Tate; sip-implementors@lists.cs.columbia.edu *Subject:* Re: [Sip-implementors] 3pcc Thank you Brett, in the same example what should be the value of refer-to Header? should that be contact (or) From (or) Asserted identity On Tuesday, September 29, 2015 6:59 AM, Brett Tate <br...@broadsoft.com> wrote: > This discusses the R-URI, I was looking for the URI > in the replaces header. in the example in that. > Replaces: 425...@bobster.example.org;to-tag=7743;from-tag=6472 > > what is the guidance for "425...@bobster.example.org" > should this be the contact-header of the Dialog planning > to be replaced? The Replaces header does not contain a URI. It contains the Call-ID header value of the dialog being replaced. Replaces = "Replaces" HCOLON callid *(SEMI replaces-param) _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
