Displaying 4 results from an estimated 4 matches for "_procfs_interface_proc_dahdi".
2011 Jun 14
1
Dahdi 2.4.0 and Squeeze [SOLVED]
...here = 0, tmp->channel = 1, channel = 1
> > [Jun 14 15:41:53] ERROR[8150]: chan_dahdi.c:14229 build_channels: Unable
> to
> > register channel '1-2'
> >
> > Suggestions ?
>
> What is the output of lsdahdi?
>
> http://docs.tzafrir.org.il/dahdi-linux/#_procfs_interface_proc_dahdi
>
--
> 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
>
> --
> _________________________________________...
2015 Feb 04
2
When are /proc/dahdi files created
Can someone tell me when the /proc/dahdi files are created for spans? Are they created when asterisk starts (or the asterisk init script) - if not what script creates them?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20150204/f14ae5a2/attachment.html>
2011 Jun 14
2
Dahdi 2.4.0 and Squeeze
Hi,
I'm using a two-years old installation script for the first time on a
Squeeze (linux 2.6.32) platform.
For an unknown reason (might be an obvious one), Dahdi can't be loaded
anymore.
1. First of all, it seems /dev/dahdi content was previously (ie in Lenny)
owned by asterisk:asterisk (asterisk is run as asterisk).
Now it is owned by root.
Any clue about this ?
2. Secondly, I changed
2010 Apr 13
2
cat /proc/zaptel/*
Hi all,
On an Asterisk/Zaptel 1.4 system, one way to gather diagnostic info is:
~# cat /proc/zaptel/*
Span 1: ZTHFC1 "HFC-S PCI A Zaptel Driver card 0 [TE]" (MASTER) AMI/CCS
1 ZTHFC1/0/1 Clear (In use)
2 ZTHFC1/0/2 Clear (In use)
3 ZTHFC1/0/3 HDLCFCS (In use)
Span 2: ZTHFC2 "HFC-S PCI A Zaptel Driver card 1 [TE]" AMI/CCS
4 ZTHFC2/0/1 Clear
5 ZTHFC2/0/2