The issues XX-5816 and XX-5817 regard transient errors that are seen by re-SUBSCRIBEs and by NOTIFYs, particularly 408 responses. In both cases, we may be able to repair the situation by retrying the failed request. This involves yet another retry-and-backoff situation.
In addition, a 482 response should probably be taken as a transient error. (This usually happens when the request was sent via TCP and the response was lost, then the request was sent via UDP.) Receiving a 482 is assurance that the UAS received the request, though the first response was lost. But we cannot know whether the first response first request was successful or not, so we have to retry. (This situation supports restricting 482 responses to out-of-dialog requests only, and requiring a UAS to re-send its response when an in-dialog merged request is seen.) Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
