[Asterisk-Dev] The Zaptel init scripts must die!

[Tzafrir Cohen]

On Wed, Dec 14, 2005 at 11:13:47AM -0600, Kevin P. Fleming wrote:
> Tzafrir Cohen wrote:
> 
> >How do you guarantee that span and channel numbers continue being
> >non-varianting?
> 
> Because they would be manually configured in zaptel.conf, not 
> auto-configured.

So you would still have unnecessary manual work. This is bad.

> 
> Something like this:
> 
> [pci0000:00:04.0]

typo prone. This begs for auto-generation.

> spanmap=1,12
> spanmap=2,13
> spanmap=3,14
> spanmap=4,15

Two lists of numbers that need to be incremented together (else: strange
breakage). Information is duplicated. Again: begs for auto-generation.

> channelmap=1-96,200
> 
> This would map the four spans from this card to Zaptel spans 12-15, and 
> the channels from this card to channels 200-295. This would happen as 
> long as the card is in that slot, regardless of what else is in the 
> system or what modules are loaded.

Don't you want to map them to separate namespaces? Instead of just one
list of channels, each span will be its own list of channels with some
properties exposed through, e.g. , sysfs . userspace (e.g: chan_zap) can
use those properties for their own maps, if they choose so.

A sysfs/procfs is also a nicer interface than ioctls for all of the
small utilities. Some of them could be converted to shell scripts.

-- 
Tzafrir Cohen     icq#16849755  +972-50-7952406
tzafrir.cohen at xorcom.com  http://www.xorcom.com