My understanding is that the deficiency in the standard here is that B is not required to copy RR headers into provisional responses, only final ones.
-- Alex Balashov - Principal Evariste Systems LLC 260 Peachtree Street NW Suite 2200 Atlanta, GA 30303 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/ On Jun 18, 2011, at 5:59 PM, Alex Balashov <abalas...@evaristesys.com> wrote: > On Jun 18, 2011, at 5:35 PM, Daniel-Constantin Mierla <mico...@gmail.com> > wrote: > >> iirc, the PRACK should follow the record-routing as part of its early dialog >> state. At least, from my experience the PRACKs I saw so far were sent to the >> proxy address due to record routing, not directly to contact address in 183. >> Without following the record routing, I see no way to go even for cases with >> NAT. For me looks like A is buggy, but I haven't checked actually the specs >> at this time. >> > > Daniel, > > Sorry, perhaps I was not clear. A is a softphone initiating a call through > Kamailio. Kamailio forwards the call to UAS B with Record-Route header > added, and UAS B sends 183s back to A through Kamailio, with 100rel > Require'd. There are no RR headers seen by A, and so it does not know to > send PRACK to something but the Contact in the 183. > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
