[asterisk-bugs] [Asterisk 0013432]: [patch] outboundproxy=proxy.mmmydomain.net where domain can not be resolved silently removes the sip section
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Jun 4 12:29:41 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=13432
======================================================================
Reported By: p_lindheimer
Assigned To: oej
======================================================================
Project: Asterisk
Issue ID: 13432
Category: Channels/chan_sip/General
Reproducibility: always
Severity: minor
Priority: normal
Status: confirmed
Asterisk Version: 1.4.21.1
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2008-09-05 15:07 CDT
Last Modified: 2009-06-04 12:29 CDT
======================================================================
Summary: [patch] 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
======================================================================
----------------------------------------------------------------------
(0106001) oej (manager) - 2009-06-04 12:29
https://issues.asterisk.org/view.php?id=13432#c106001
----------------------------------------------------------------------
Forgot all about this. My apologies. We have a lot of issues where DNS
does not resolve and cause issues with peers and such. I agree though, we
should at least have an error message. Putting this issue back in queue.
Issue History
Date Modified Username Field Change
======================================================================
2009-06-04 12:29 oej Note Added: 0106001
======================================================================
More information about the asterisk-bugs
mailing list