Ranga wrote: > On Thu, Nov 20, 2008 at 2:50 PM, Paul Mossman > <[EMAIL PROTECTED]> wrote: > > > > Ranga wrote: > >> On Thu, Nov 20, 2008 at 12:07 PM, Arjun Nair <[EMAIL PROTECTED]> > > wrote: > > .... > >> > When using in-dialog OPTIONs we are limited to parsing only > >> a 404, 408, or 481 response, for marking dialogs as terminated. > >> > >> > >> Why? Any kind of response means the other end is alive.... > > > > Won't you get a 408 (Request Timeout) if the other end is not alive? > > > > > > No because the other end has to be alive to send 408.
I believe our sipXtackLib manufactures a 408 when a transaction times out waiting for a response. See handleChildTimeoutEvent() in SipTransaction.cpp. This was my observation when I was working on XECS-1810: Timeout response to NOTIFY causes termination of subscription, affects sipXrls. (Although, I understand that this is not relevant to the current approach for fixing XECS-1594.) -Paul [EMAIL PROTECTED] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
