Hi, I'm not sure that I understand your question (although RFC 3891 section 4 likely answers your question). For instance, are you asking how to populate the REFER's Request-URI (if sent outside of dialog) or Refer-To (when using Replaces)?
Either way, you'd likely want to use the Contact. You will be interested in RFC 7647 which clarifies the GRUU mandate and updates RFC 3515. Without the use of GRUU, you might not reach the desired device. Similarly with the use of GRUU, things might not work. Intermediaries can complicate things as discussed within draft-allen-dispatch-routing-out-of-dialog-request. > -----Original Message----- > From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip- > implementors-boun...@lists.cs.columbia.edu] On Behalf Of K sipuser > Sent: Monday, September 28, 2015 9:36 PM > To: sip-implementors@lists.cs.columbia.edu > Subject: [Sip-implementors] 3pcc > > Hi,When sending REFER, we use refer-to.which has Userurl and the DialogID > to > be replaced. > If I am doing 3PCC for a incoming call,and if it has P-Asserted > identity, From Header and contact which one should we use? > From Header looks correct.can we use P-Asserted identity? is there any > reference for this Header to be taken? else which one is better to > take?The > Dialogid part is clear as it contains the from tag , to tag and callid. > Can you help me in clarifying this?/ > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
