Hi, The Request-URI in the CANCEL shall be identical to the URI in the INVITE, no matter what Contact header value you may have received in a 18x response.
Also, the CANCEL shall be routed like the INVITE, no matter what Record-Route headers you may have received. Regards, Christer Holmberg Ericsson Finland Attila Sipos wrote: > Hello everyone, > > I have a a question regarding request-URI's > for a CANCEL request. > > Say you have this call flow: > > INVITE---------------> > <-----------------100 Trying > <-----------------180 Ringing > CANCEL---------------> > > (I haven't included anything after the CANCEL > because this doesn't interest me right now) > > Anyway, the question is this: > MUST the Request URI in the CANCEL > be identical to that used in the INVITE? > > If the terminator sends a "Contact" > header in the "180 Ringing", can the > originator use this as the request-URI > in the CANCEL? > > In other words, is this OK... > > --- TX --> > INVITE sip:[EMAIL PROTECTED]:5060 SIP/2.0 > > <-- RX --- > SIP/2.0 100 Trying > Contact: <sip:192.168.1.150:5060> > > <-- RX --- > SIP/2.0 180 Ringing > Contact: <sip:192.168.1.150:5060> > > --- TX --> > CANCEL sip:192.168.1.150:5060 SIP/2.0 > > ?? > > In the RFC3261 it says: > When a UAC receives a 2xx response to a target refresh request, it > MUST replace the dialog's remote target URI with the URI from the > Contact header field in that response, if present. > > But what about a 18x response? > > Thanks, > > Attila > > <http://www.vegastream.com> > VegaStream : A World of difference for your Integrated Communications > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
