<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi all,<div class=""><br class=""></div><div class="">I have a custom routing logic implemented in my module. This routing logic may return a list of 2 or more endpoints where INVITE should be attempted to be routed. Since endpoint URI can contain domain names, I’m also trying to take care of DNS resolution. Based on the documentation found in <a href="https://github.com/kamailio/kamailio/blob/master/doc/tutorials/dns.txt" class="">https://github.com/kamailio/kamailio/blob/master/doc/tutorials/dns.txt</a> current DNS resolver/failover logic takes good care of RFC3263.</div><div class=""><br class=""></div><div class="">To support switching between various endpoints returned by custom routing logic I have been using “tm:branch-failure” routing blocks. Problem I’m facing right now is that I am unable to distinguish between a DNS failover branch failure that has more SRV records to try and the “final” DNS failover branch failure (at which point I should be switching to another endpoint).</div><div class=""><br class=""></div><div class="">I’ve tried monitoring $T_reply_code values, but it is “408” in both cases.</div><div class=""><br class=""></div><div class="">Any ideas on how “final” and “non-final” DNS failover branch failures can be distinguished?</div><div class=""><br class=""></div><div class="">Regards,</div><div class="">Ivan</div></body></html>