----- Original Message ----- From: "Christer Holmberg" <[EMAIL PROTECTED]>
> > Hi, > > The 18x MUST contain a Contact header, and MAY (if inserted by proxies in the > signalling path) contain Record-Route header(s). > Christer is correct. The reliable provisional response MUST establish a new dialog or match an existing dialog between the UAC and the responsing UAS. The PRACK is a request within that dialog and must not be forked. It needs to be routed just like a BYE request for the dialog. If there are no Record-Route headers in the 1xx, the UAC would send the request directly to the UAS. If there were Record-Routes, it would insert Route headers which would prevent the proxies from forking. > Regards, > > Christer Holmberg > Ericsson Finland > > ����� wrote: > > > Hi.. > > > > I would like to know How PRACK will be routed.. when original Request forked.. > > > > Let's think What will be done by Forking Proxy when it meets following situation.. > > > > 1. INVITE (Supported : 100Rel - forking) > > UAC->Forking Proxy -> UAS1 > > -> UAS2 > > -> UAS3 > > > > 2. 180 (Require : 100Rel, No Record-Route, No Contact) > > UAC<-Forking Proxy <- UAS1 > > UAC<-Forking Proxy <- UAS2 > > UAC<-Forking Proxy <- UAS3 > > > > 3. PRACK (forking) > > UAC->Forking Proxy -> UAS1 > > -> UAS2 > > -> UAS3 > > UAC->Forking Proxy -> UAS1 > > -> UAS2 > > -> UAS3 > > UAC->Forking Proxy -> UAS1 > > -> UAS2 > > -> UAS3 > > > > Is above Flow Correct?? > > _______________________________________________ > > 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 > _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
