[asterisk-bugs] [Asterisk 0013432]: outboundproxy=proxy.mmmydomain.net where domain can not be resolved silently removes the sip section

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13432 
====================================================================== 
Reported By:                p_lindheimer
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13432
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.21.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-09-05 15:07 CDT
Last Modified:              2008-09-05 23:18 CDT
====================================================================== 
Summary:                    outboundproxy=proxy.mmmydomain.net where domain can
not be resolved silently removes the sip section
Description: 
Setting outboundproxy to a fully qualified domain name that can not be
resolved results in the sip section configuration being silently removed.

The only error that is provided in the log file is a warning:

[Sep  5 13:07:04] WARNING[20522] acl.c: Unable to lookup
'proxy.mmmydomain.net'

I don't know what the proper behavior should be. Ignore the setting,
remove the section as is the case but with a very prevalent error, keep it
but show it as unreachablem, or something else. But something better then
this silent nature would be preferred
====================================================================== 

---------------------------------------------------------------------- 
 (0092131) p_lindheimer (reporter) - 2008-09-05 23:18
 http://bugs.digium.com/view.php?id=13432#c92131 
---------------------------------------------------------------------- 
At a minimum, at least a warning message such as below should be added.
Although question, if there is a host= line, should the failure mode be a
warning with a fallback to the host in place of the outbound proxy?

--- chan_sip.c.ORIG     2008-09-05 21:02:59.000000000 -0700
+++ chan_sip.c  2008-09-05 21:19:07.000000000 -0700
@@ -16763,6 +16763,7 @@
                                ast_clear_flag(&peer->flags[1],
SIP_PAGE2_DYNAMIC);
                                if (!obproxyfound || !strcasecmp(v->name,
"outboundproxy")) {
                                        if (ast_get_ip_or_srv(&peer->addr,
v->value, srvlookup ? "_sip._udp" : NULL)) {
+                                               ast_log(LOG_ERROR,
"srvlookup failed for outboundproxy: %s, on peer %s, removing peer\n",
v->value, peer->name);
                                                ASTOBJ_UNREF(peer,
sip_destroy_peer);
                                                return NULL;
                                        } 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-05 23:18 p_lindheimer   Note Added: 0092131                          
======================================================================