Yes I omited that Record-Route will require to change where to send Notify. I just wanted to say, that in general it may be quite possible for Notify to arrive before 200Ok (or 202) and that subscriber must accept Notify before 200Ok. If you are interested "how does it happen", then I think tracing internal sipx communications may shed a light. merge-logs --containing=<callid> Will prepare xml trace file for sipviewer. I'm not sure if something wrong is really happen in your case... May be dev. people will like to look at your trace or event a snapshot... Rgds, Nikolay.
> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Jean-Hugues Royer > Sent: Monday, September 13, 2010 2:59 PM > To: [email protected] > Subject: Re: [sipx-dev] Packet Order Conservation > > Hi, > > You are right, the RFC says that the Notify also creates the > dialog, thanks for pointing this out. > > But regarding your example the Notify is not sent directly to > the contact because sipXecs inserts a Record-route to stay on > the route. > > That's why there should be no reason to receive the Notify > before the 200 OK, unless the Via path is still slower, I > will investigate this... > > Regards. > > -------------------------------------------------------------- > --------------------------- > As far as I know, "Notify before 200OK" is quite legitimate. > If subscriber receives matching Notify before 200Ok, it > creates a subscription and dialog. > See http://tools.ietf.org/html/rfc3265#section-3.3.4. > I would explain it as following: > Suppose that "Subscribe" request traverses several proxies on > it's way to notifier. > Notifier replies with 200Ok and then Notify. > The thing is that Notify is to be sent directly to "Contact", > while 200OK is to traverse all "Via", that are present in the > subscribe request. > Thus it is quite possible that Notify will arrive before 200Ok. > That's why in this case subscriber just creates a > dialog/subscription when recieves Notify before 200Ok. > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
