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

[Tilghman Lesher]

On Tuesday 13 December 2005 15:18, Kevin P. Fleming wrote:
> Kristian Kielhofner wrote:
> >     I suppose.  However, as of this moment I like having to
> > manually specify module load order, because I can guarantee what
> > order my zap channels are going to appear.  How could this be done
> > %100 automatically?  I fear a situation where a new card is added
> > to a system, the zap channels get renumbered, and you spend the
> > next 30 minutes figuring out which card is which, re-writing
> > zap*.conf, etc. That doesn't seem easier! :)
>
> The udev rules could be written based on slot positions, and ztcfg
> could be modified to do some new things: only initialize a given
> card, and use a particular starting channel number for that card.
> This would require some additional information to be put into
> zaptel.conf, to then be interpreted when udev sees the card become
> available.
>
> With those changes, channel assignments actually become controllable,
> even if a card is removed, moved around, or cards are added. Wouldn't
> it be nice to be able to temporarily remove one of a pair of TDM400Ps
> and have the channel numbers on the remaining card still be 5-8,
> instead of changing into 1-4?

Why stop there?  Why not have all analog cards configure to channels in
the 1-999 range, and all digital cards configure to channels above 1000?
Then, there's never a conflict.

modprobe wctdm slot=0x3 basechannel=46
modprobe wc4xxp slot=0xb basechannel=2032

-- 
Tilghman