[asterisk-dev] A plan for span

Oron Peled oron.peled at xorcom.com
Tue Jul 8 14:42:09 CDT 2008

On Tuesday, 8 בJuly 2008, Shaun Ruffell wrote:
> If the registration utility only registers devices that are configured
> (and  they have to be configured anyway in some form to work with
> asterisk), and if all devices that are dahdi compliant only registers
> themselves on command, adding a new device wouldn't cause any problems
> since it would never be registered until configured to do so and then
> presumably the administrator would add it to the end of the list
> of devices.

How the administrator is going to specify *it* when *it* has no name?
The main problem is that "Span 5" does not identify any specific
piece of equipment.

Do you think that uniquely naming spans and exposing this via sysfs
as I proposed is a major complexity challenge? I don't think
so and we will be happy to do this if needed.

Oron Peled                             Voice/Fax: +972-4-8228492
oron at actcom.co.il                  http://www.actcom.co.il/~oron
3Com only purchased rights to the numbers '3' '5' and '9', Intel
owns '4', '8', '6', and '2'. '0' and '1' are still in the public
domain ;-)
         -Donald Becker

More information about the asterisk-dev mailing list