[asterisk-bugs] [Asterisk 0009503]: [patch] separate sections in zapata.conf
noreply at bugs.digium.com
noreply at bugs.digium.com
Wed Mar 5 19:01:24 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: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 60795
Disclaimer on File?: Yes
Request Review:
======================================================================
Date Submitted: 04-08-2007 14:29 CDT
Last Modified: 03-05-2008 19:01 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...
======================================================================
----------------------------------------------------------------------
tzafrir - 03-05-08 19:01
----------------------------------------------------------------------
Notes as I work on refreshing the patch:
* users.conf syntax does not support 'crv =>'. Hence this wll not be
supported in sections. As I don't fully understand this functionality, I
don't know exactly what's the best strategy to fix that.
* iflock is released too soon. In a separate patch here.
* As a by-product of using users.conf -style config parsing, unknown
keywords will be silently ignored.
Issue History
Date Modified Username Field Change
======================================================================
03-05-08 19:01 tzafrir Note Added: 0083522
======================================================================
More information about the asterisk-bugs
mailing list