[asterisk-dev] /dev/zap/(channel no) ends on 255 and unable to
make more
Anton VG
anton.vazir at gmail.com
Fri Dec 22 12:49:14 MST 2006
in fact chan_ss7 uses this method to access a channel which
provides the signalling link. And if I use that on the
span>8 ... so than I can't use chan_ss7. Matthew, looking
for a time when you'll sync your libss7 with 1.4 ;) Until
now have to stick with chan_ss7. Not sure, but is this a
limitation of DEVFS?
2006/12/23, Matthew Fredrickson <creslin at digium.com>:
>
> On Dec 22, 2006, at 11:49 AM, Anton wrote:
>
> > Guys,
> >
> > In a system with more than 8xE1 it's impossible to access
> > to /dev/zap/(channel no) channels higher than 255. ZAPTEL
> > Makefile generates only 255 instances and adjusting
> > Makefile to be generating more of them, makes any nodes
> > over 255 to be anyway dead (attempt to access returns (for
> > instance 256's node) "Cannot open "256" No such device or
> > address (6)" error. If someone could please give a clue how
> > to make them accessible, it will be highly appreciated. Is
> > it a linux limitation or just a variable in Zaptel sources?
> > Please help.
>
> What do you need this for? If this is for asterisk, then you don't
> have anything to worry about. A very cursory overlook of chan_zap
> shows that it does not open the zap devices by those means. There is
> another mechanism for opening zap channels provided through
> /dev/zap/channel that gets around the limitation with devices nodes.
>
> Matthew Fredrickson
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-dev
>
More information about the asterisk-dev
mailing list