Re: [Okeo-developers] [SSBC] Ack problem on the plateform

[frank s. <fra...@gm...>]

Hi Philippe, good to see you here,

I finally got internet at home, don't ask me how ;)

About the problem you're right.
In fact I found two problems.

the first one is that the proxy don't set the record-route header in the 180
Ringing but only in the 200 OK.
This should be ok because the RFC doesn't specify it's mandatory to add it
in the 180 but only in the 200. ( I love optionnal things in RFC....)

the second one, is that it seems that sailfin construct the Ack request from
the first response received and not really from the 180.
(or the sailfin stack use the first response receive to know if it has to
use a receive record-route.

What I saw when I made some tests with the following :
UA1 -> Proxy -> B2B -> proxy -> UA2
(the unit test is avalaible on the SVN in the proxy project) is that :

When I send a 180 from the UA2, the Ack request sent by the b2b agent
(sailfin based) is directly sent to the UA2.
When I didn't send a 180 from the UA2, the Ack is sent by the b2b through
the proxy.

I assume its the same problem on the okeo project.
But I'm worry because you told me that you don't send any 180 from the SBC.

Do you have a tcpdump trace from the SBC, from the proxy and from the
service b2b ?

It should help to understand what happen exactly.


2008/8/26 Philippe Bernard <phb...@gm...>

> 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
> >
> >
>
> -------------------------------------------------------------------------
> 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
>