[asterisk-bugs] [Asterisk 0009503]: [patch] separate sections in zapata.conf

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9503 
====================================================================== 
Reported By:                tzafrir
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   9503
Category:                   Channels/chan_zap
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     new
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:              11-19-2007 11:54 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 - 11-19-07 11:54  
---------------------------------------------------------------------- 
Part of the ugliness and non-intiutiveness of zapata.conf is because spans
are configured through channels.

Many of the parameters that really only affect spans must be sent
indirectly through channels. Should we have separate section(s) for spans?


(ab)use the existing trunkgroups ? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-19-07 11:54  tzafrir        Note Added: 0073969                          
======================================================================