[OpenSER-Devel] [ openser-Bugs-1803916 ] DNS resolve error handeling doesn't triger failure_route

[SourceForge.net]

Bugs item #1803916, was opened at 2007-09-27 17:09
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1803916&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: serwide (daveswide)
Assigned to: Nobody/Anonymous (nobody)
Summary: DNS resolve error handeling doesn't triger failure_route

Initial Comment:
Using OpenSER 1.2.1
When I have a FQDN in my R-URI and DNS is not available or the FQDN doesn't resolve, the error logs show:
ERROR: mk_proxy: could not resolve hostname: "srv.dest.sipserver.com"
ERROR: uri2proxy: bad host name in URI <sip:mynum at srv.dest.sipserver.com>
ERROR:tm:t_forward_nonack: failure to add branches

for sending the call I have
t_on_failure("1");
if (!t_relay()) {
  # This section doesn't seem to be reached even on failures.
  xlog("L_INFO", "Failed sending to: $ru\n");
}
exit;

but even through I have t_on_failure(1); prior to t_route(), failure_route[1] is never hit. failuer_route[1] is hit/used if FQDN does resolve and sip call fails/rejected.

I also have a error function that has never been hit:
error_route { 
  xlog("L_INFO", "--- error route class=$(err.class)...."); 
}


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1803916&group_id=139143