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

SourceForge.net noreply at sourceforge.net
Tue Nov 13 08:56:54 UTC 2007


Bugs item #1803916, was opened at 2007-09-28 03:09
Message generated for change (Comment added) made by bogdan_iancu
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: modules
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: serwide (daveswide)
Assigned to: Bogdan (bogdan_iancu)
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)...."); 
}


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

>Comment By: Bogdan (bogdan_iancu)
Date: 2007-11-13 10:56

Message:
Logged In: YES 
user_id=1275325
Originator: NO

Normally an automatica err reply is sent back to the client. If you want
to disable this reply and deal with the error from the script, there is a
parameter for t_relay() :
   http://www.openser.org/docs/modules/1.2.x/tm.html#AEN335
See flag 0x02.

Is this what you are looking for?

Regards,
Bogdan

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

Comment By: serwide (daveswide)
Date: 2007-11-13 03:54

Message:
Logged In: YES 
user_id=1900568
Originator: YES

I didn't check in packet capture for error reply to originating caller. 
My guess is that it did send an error reply.
However the problem is that I can not handle the dns lookup failure
gracefully in openser by sending it down other gateways, or ultimately
sending them to a media server to play the appropriate message about the
error.

Thanks,
Dave

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

Comment By: Bogdan (bogdan_iancu)
Date: 2007-11-12 16:20

Message:
Logged In: YES 
user_id=1275325
Originator: NO

Hi,

Don't you see on an error reply automatically generated by openser in this
case? (even if it is not controlable from script).

Regards,
Bogdan

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

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



More information about the Devel mailing list