> From: "Kumar, Puneet (Puneet)" <pune...@avaya.com> > As per section 3.1.4.4 on RFC 3265 above behavior on UA1 is allowed.
The reason this is allowed is that the messages may go through the network at different speeds. Even if UA2 *sends* the NOTIFY after the 200, there is no guarantee it will *arrive* at UA1 after the 200. > Currently UA1 ignores this NOTIFY as it always expected NOTIFY after > 200(SUBSCRIBE) What should UA1 do so that it can handle this message > mismatch properly? The correct behavior for UA1 (the subscriber) is described in detail in RFC 6665 section 4.1.2. > If UA2 receive some 4xx response for NOTIFY with a retry-after > header will it retry NOTIFY? In general, if UA2 (the notifier) receives a 4xx response to a NOTIFY, it will delete the subscription. The correct behavior is described in RFC 6665 section 4.2.2, including: If the NOTIFY transaction fails due to the receipt of a 404, 405, 410, 416, 480-485, 489, 501, or 604 response to the NOTIFY request, the notifier MUST remove the corresponding subscription. See [RFC5057] for further details and notes about the effect of error codes on dialogs and usages within dialog (such as subscriptions). Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
