|
From: Philippe B. <phb...@gm...> - 2008-08-26 19:24:32
|
Hello, On Tue, Aug 26, 2008 at 2:23 PM, Sergio AFANOU <afa...@ya...> wrote: > We lose a little about the origin of the problem of ack in preparing the > appeal on the platform. Can you tell us once more? What should be done to > resolve it? I'm not sure myself about what exactly the problem was, but IIRC, Sailfin (as an UAC) seemed to build the route set from Record-Route headers in 1xx responses. The Record-Route headers in the 200 response were not taken into account (not changed to Route headers in the ACK request). Cf. RFC 3261, page 71, 12.1.2. As I understand it, the route set should be built by the UAC from Record-Route in the response *establishing the dialog* (i.e. 2xx). You should probably try to reproduce this using SipUnit or sipp and put different Record-Route in 180 and 200 responses from an UAS. And then see what Route headers are put by Sailfin in the ACK request. Frank, please correct me if I'm wrong. > > Rgrds > Sergio > Philippe. > ________________________________ > Envoyé avec Yahoo! Mail. > Une boite mail plus intelligente. > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Okeo-developers mailing list > Oke...@li... > https://lists.sourceforge.net/lists/listinfo/okeo-developers > > |