Section 21 of RFC-3261 provides detail about response codes and In my opinion the UAC should be able to process any final response or provisional response and appropriately handle it assuming that the UAS is generating meaningful response codes.
Now UAS also has responsibility to use the appropriate response codes while replying to a request, for UAC to process it meaningfully. So to answer your question let us consider this example: If an UAC sends a BYE and it it gets 415 unsupported media type response code from the UAS should the UAC process it. From protocol perspective there was a request and there was a final error response for it, so the transaction is complete. But now the UAC core can detect that 415 response code for the BYE is not appropriate and take appropriate action ( like re-issue the BYE or generate error log or from it's side consider the call terminated ). In this case the fault is primarily with UAS which is not using the correct response code for the request as per the protocol recommendation. This is what my thoughts on this query is :) Regards, Indresh K Singh ------------------------------------------------------------- Sr. Software Engineer SIP Media Control and Signaling Nokia Siemens Networks Boca Raton, FL-33487 Ph: 561-923-5085 (o), 561-923-2048 (o) ------------------------------------------------------------- >>-----Original Message----- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] On Behalf >>Of ext Naresh R >>Sent: Tuesday, May 22, 2007 2:57 AM >>To: Sip-implementors@cs.columbia.edu >>Subject: [Sip-implementors] Request and Response Match >> >>hi, >> >>+ 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. >> >>Thanks for your response >> >>regards., >>_______________________________________________ >>Sip-implementors mailing list >>Sip-implementors@cs.columbia.edu >>https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> _______________________________________________ Sip-implementors mailing list Sip-implementors@cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
