[asterisk-dev] Zaptel patch advice needed
Tzafrir Cohen
tzafrir.cohen at xorcom.com
Mon Dec 10 09:22:55 CST 2007
On Mon, Dec 10, 2007 at 09:07:10AM -0600, critch wrote:
> On Mon, 2007-12-10 at 19:37 +0500, Anton wrote:
> > Hi!
> > I've came to a requirement to have over 256 /dev/zap/x
> > device files (512) to have 16E1's accessible (one of the
> > third party channel drivers - chan_ss7) addresses old-style
> > and needs this device files).
> >
> > Any advice how to do this possible highly appreciated!
>
> Without having looked into chan_ss7, wouldn't it be better to fix
> chan_ss7 to use the current method of addressing more than 254 channels
> instead of trying to patch up the zaptel driver.
>
Sure.
Though a thought comes to mind: what if we do want to allow more than
249 zaptel channel device files (let's assume for the moment we will
have a way to work around the "hole" in 250-255) and start actually
referring to the from userspace by name?
This means that I can set the order of channels (e.g: allocate channel
numbers to a card with a specific range, regardless of the arbitrary
loading and scanning order).
Is there anything equivalent to the arbitrary mapping of udev in
FreeBSD? Solaris? Elsewhere zaptel is used?
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen at xorcom.com
+972-50-7952406 mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
More information about the asterisk-dev
mailing list