Hi Ramesh I believe this is an implementation choice. I suggest ignoring the duplicate DNS response. For e.g., if you did a AA / AAAA query and got IP1 followed by IP1 again, there is no point in trying to send the SIP message again on IP1 as it has already been tried in the 1st attempt and the result would most likely be similar in the 2nd attempt also. You should skip this response and move to next available response (if any).
An alternate approach would be to try to use all the responses available as is. On Timer B / Timer F expiry of the 1st attempt, there is a possibility that the SIP server was temporarily down and would be able to respond in the 2nd attempt. It is purely an implementation choice. Regards Tarun Gupta -----Original Message----- From: ramesh.madha...@wipro.com [mailto:ramesh.madha...@wipro.com] Sent: Friday, January 03, 2014 12:35 PM To: sip-implementors@lists.cs.columbia.edu Subject: [Sip-implementors] Handling duplicate dns response in SIP stack Hi , I have a clarification wrt handling of DNS responses in SIP stack. When there is a duplicate DNS response for a DNS query from the DNS server, how the duplicate dns response should be treated By the sip stack? Whether the duplicate dns response should be ignored (as it has already treated the original dns response) or should the sip stack Should throw some error ? I checked the relevant RFC's : RFC 3261, RFC 3263, RFC 1034 and RFC 1035 .I could not find any reference for this topic. Kindly let me know. Kind Regards, Ramesh.M The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors =============================================================================== Please refer to http://www.aricent.com/legal/email_disclaimer.html for important disclosures regarding this electronic communication. =============================================================================== _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
