Thanks for your answers, with the chain of response arises another question
+ If UAC receives a response that is not relevant to the particular request sent, what must be the UAC behaviour? - Must UAC simply parse and ignore the response? As an example: UAC Generates OPTIONS -> UAS responds with 180/486/423/487 (assuming it is not been taken care!) -> UAC did not receive any other Final Response for OPTIONS (except above mentioned responses) what must be the UAC behaviour? + Must it process the responses and ignore? + Must it resend the Request? + What else UAC behaviour can be expected? + What is the valid UAC behaviour that is suggested under such cases? regards, naresh On 5/22/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > From: "Naresh R" <[EMAIL PROTECTED]> > > + Is there any website or document that has given any simpler > combination > about what all error responses that can be expected for every SIP > request? > + Is it Valid if I assume that every SIP method can expect any SIP > response > (2XX to 6XX) unless and until it is specified explicitely in rfc? > > I am a tester and answers for above questions for me will be essential > in > case of fault injection testing. > > Any request can potentially receive any response. If the UAC does not > understand the semantics of the response, it must process it as one of > the following generic response types: > > 100 > non-100 1xx > 200 > 300 > 400 > 500 > 600 > > I suppose that there are situations where a UAC *knows* that a > particular response code is impossible for a particular request (due > to some specification), but that seems to be an unsafe rule to try to > enforce (since the UAC has no way to signal this to the UAS, and > because future specifications might make the combination legal). I > expect that the safest way to process the response would be to treat > it as the corresponding generic response. > > Dale > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
