[asterisk-bugs] [Asterisk 0009503]: [patch] separate sections in zapata.conf
noreply at bugs.digium.com
noreply at bugs.digium.com
Fri Mar 7 12:49:11 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=9503
======================================================================
Reported By: tzafrir
Assigned To: kpfleming
======================================================================
Project: Asterisk
Issue ID: 9503
Category: Channels/chan_zap
Reproducibility: always
Severity: feature
Priority: normal
Status: assigned
Asterisk Version: 1.6.0-beta4
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 106240
Disclaimer on File?: Yes
Request Review:
======================================================================
Date Submitted: 04-08-2007 14:29 CDT
Last Modified: 03-07-2008 12:49 CST
======================================================================
Summary: [patch] separate sections in zapata.conf
Description:
As chan_zap already supports parsing separate sections from users.conf,
there's no reason why it should parse sections in zapata.conf as well.
Possible issues:
* The name of the section is meaningless. This is quite unexpected.
* Which should be parsed first: users.conf's sections or zapata.conf's
sections?
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0007290 [patch] asterisk should not fail on cha...
======================================================================
----------------------------------------------------------------------
kpfleming - 03-07-08 12:49
----------------------------------------------------------------------
CRVs are used for GR-303 signaling, and are unlikely to ever be useful for
someone using users.conf for configuration chan_zap.
You should be able to pass a flag into process_zap indicating whether the
config structure came from users.conf or zapata.conf, so that it can warn
about unknown config options when zapata.conf is being parsed.
Issue History
Date Modified Username Field Change
======================================================================
03-07-08 12:49 kpfleming Note Added: 0083610
======================================================================
More information about the asterisk-bugs
mailing list