[asterisk-bugs] [Asterisk 0007290]: [patch] asterisk should not fail on chan_zap config problems
noreply at bugs.digium.com
noreply at bugs.digium.com
Fri Oct 12 07:19:48 CDT 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=7290
======================================================================
Reported By: tzafrir
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 7290
Category: Channels/chan_zap
Reproducibility: sometimes
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 32350
Disclaimer on File?: No
Request Review:
======================================================================
Date Submitted: 06-05-2006 18:23 CDT
Last Modified: 10-12-2007 07:19 CDT
======================================================================
Summary: [patch] asterisk should not fail on chan_zap config
problems
Description:
Currently chan_zap considers many of its configuration problems fata and
fails its load. The result is a failiure of loading Asterisk.
The attached patch converts all of those to non-fatal errors (makes the
module return 0).
======================================================================
----------------------------------------------------------------------
tzafrir - 10-12-07 07:19
----------------------------------------------------------------------
Should we fail if there's no zapata.conf? What if the user wants to
configure everything in users.conf?
Strange things happen, though, if we have zapata.conf but it has no
[channels] section.
We also currently ignore errors from process_zap on users.conf sections
(which may create channels)
Issue History
Date Modified Username Field Change
======================================================================
10-12-07 07:19 tzafrir Note Added: 0071875
======================================================================
More information about the asterisk-bugs
mailing list