asterisk users - Mar 2017 - How to install and configure Dahdi from Debian Stretch repo ?

2017-03-14 15:26 GMT+01:00 Tzafrir Cohen <tzafrir.cohen at xorcom.com>:
> On Tue, Mar 14, 2017 at 02:58:07PM +0100, Olivier wrote:
> > 2017-03-14 13:08 GMT+01:00 Tzafrir Cohen <tzafrir.cohen at
xorcom.com>:
> >
> > > On Tue, Mar 14, 2017 at 11:10:57AM +0100, Olivier wrote:
> > > > Hello,
> > > >
> > > > After all these years installing from source, I'm giving
Dahdi
> package
> > > > installation a try on a recent Stretch box.
> > > >
> > > > Google over the web, I didn't find too many doc on this
topic.
> > > >
> > > > 1. Is this one [1] up-to-date ?
> > >
> > > Not exactly.
> > >
> > > > Reading Stretch I would say a single asterisk-dahdi would be
enough
> to
> > > > install asterisk dahdi and libpri.
> > >
> > > Almost. Except the kernel modules. For those:
> > >
> > >   apt install dahdi-source
> > >   # also install module-assistant, if it wasn't installed
already
> > >   m-a a-i dahdi
> > >   # Should also install linux-headers-`uname -r`, IIRC
> > >
> > > >
> > > > 2. On my box, the following fails. What would you suggest ?
Re-base
> > > > everything on Jessie ?
> > > > apt-get install linux-headers-`uname -r`
> > >
> > > That should not happen. What is the output of uname -r #?
> > >
> >
> > # uname -r
> > 4.8.0-2-686-pae
> >
> > # apt-get install linux-headers-`uname -r`
> > ...
> > E: Couldn't find any package by glob
'linux-headers-4.8.0-2-686-pae'
> >
> > # apt-cache show linux-headers-4.8
> > ...
> > N: Couldn't find any package by glob 'linux-headers-4.8'
> > ...
> >
> > # apt-cache show linux-headers-4.9
> > Package: linux-headers-4.9.0-2-686
> > Source: linux
> > ...
> >
> > It looks like linux-headers-4.8 are currently missing in Stretch repo
> > though currently installed kernel is 4.8.
> > This issue seems quite independant from asterisk, anyway.
>
> You probably started working on this box a while ago. Streetch's
current
> kernel is 4.9.0-2 (it changed shortly before the freeze). It is now
> frozen and won't change (barring a really good reason).
>
> >
> >
> > I started all over with a Jessie box.
>
> I recommend to go back to Stretch and just upgrade the kernel. In other
> words: keep the software up-to-date.
>
> > Relating to [1], I could positively run:
> > # m-a a-i dahdi
> > ...
> >
> > But # dahdi_genconf required a reboot to run OK.
>
> Certainly not. See below.
>
> > Though this worries me as I need to script the whole install process,
I
> can
> > leave it aside at the moment.
> >
> >
> >
> > > >
> > > > 3. How is dahdi started-stopped in Stretch ? (I can't
find any
> > > > /etc/init.d/dahdi file after apt-get install
asterisk-dahdi).
> > >
> > > Started: should be automatically at boot.
> >
> >
> > Shall I find an /etc/init.d/dahdi file or equivalent ?
> > If positive which command produces this file ?
> > I would expect dahdi-linux or dahdi packages to install these file.
> >
> >
> > > Waht hardware device do you
> > > have?
> > >
> >
> > # dahdi_hardware
> > pci:0000:04:05.0     wctdm24xxp+  d161:8007 HA8-0000
>
> Traditionally dahdi has been shipped with a modprobe.d configuration
> file to blacklist all of the PCI cards. This was because the order in
> which they were loaded was not well-defined.
>
> This is irrelevant on a system with a single device. And anyway,
> irrelevant in a system configured (as is in the Debian packages) with
> auto_assign_spans=0 . In such a system, devices register automatically,
> but their spans are not assigned span and channel numbers unless they
> are configured in /etc/dahdi/assigned-spans.conf .
>
> So try:
>
>   dahdi_span_assignment auto
>   dahdi_genconf
>
>
This "dahdi_span_assignments auto" stratement was missing in my
installation script.

This one is now:


    DAHDI_MODULES="wctdm24xxp"
    apt-get -s install asterisk-dahdi module-assistant
linux-headers-$(uname -r) dahdi-source
    m-a a-i dahdi
    modprobe ${DAHDI_MODULES}
    dahdi_span_assignments auto

    ... edit asterisk and dahdi config files

    dahdi_cfg -vvvvvvvvv

Thank you very much for letting me know about this dahdi_span_assignments
command.

May I add I've still got no /etc/init.d/dahdi file or equivalent though
dahdi channels seems OK within Asterisk ?
I'll learn a bit deeper into dahdi_span_assignments to clarify my further
questions, if any.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20170320/fd25377f/attachment.html>

Thanks to Tzafrir help, Now I have an Asterisk-Dahdi system installed from
Stretch repository.
This system has a Digium HX8 card with BRI modules, Asterisk 13.14.0, Dahdi
2.11.1.
BRI spans appears as up and active but I've not tested them yet:
CLI> pri show spans
PRI span 1/0: Up, Active
PRI span 2/0: Up, Active
PRI span 3/0: Up, Active


I'm still having some questions:

1. I can't find any /etc/init.d/dahdi file in my newly built system so
"service dahdi status" (or systemctl status dahdi) fails with:
Unit dahdi.service could not be found.
Shall I worry about this ?

2. Where can Dahdi 2.11.1 Changelog file be found ?
In http://downloads.asterisk.org/pub/telephony/ ?

Best regards


2017-03-20 16:25 GMT+01:00 Olivier <oza.4h07 at gmail.com>:
>
>
> 2017-03-14 15:26 GMT+01:00 Tzafrir Cohen <tzafrir.cohen at
xorcom.com>:
>
>> On Tue, Mar 14, 2017 at 02:58:07PM +0100, Olivier wrote:
>> > 2017-03-14 13:08 GMT+01:00 Tzafrir Cohen <tzafrir.cohen at
xorcom.com>:
>> >
>> > > On Tue, Mar 14, 2017 at 11:10:57AM +0100, Olivier wrote:
>> > > > Hello,
>> > > >
>> > > > After all these years installing from source, I'm
giving Dahdi
>> package
>> > > > installation a try on a recent Stretch box.
>> > > >
>> > > > Google over the web, I didn't find too many doc on
this topic.
>> > > >
>> > > > 1. Is this one [1] up-to-date ?
>> > >
>> > > Not exactly.
>> > >
>> > > > Reading Stretch I would say a single asterisk-dahdi
would be enough
>> to
>> > > > install asterisk dahdi and libpri.
>> > >
>> > > Almost. Except the kernel modules. For those:
>> > >
>> > >   apt install dahdi-source
>> > >   # also install module-assistant, if it wasn't installed
already
>> > >   m-a a-i dahdi
>> > >   # Should also install linux-headers-`uname -r`, IIRC
>> > >
>> > > >
>> > > > 2. On my box, the following fails. What would you
suggest ? Re-base
>> > > > everything on Jessie ?
>> > > > apt-get install linux-headers-`uname -r`
>> > >
>> > > That should not happen. What is the output of uname -r #?
>> > >
>> >
>> > # uname -r
>> > 4.8.0-2-686-pae
>> >
>> > # apt-get install linux-headers-`uname -r`
>> > ...
>> > E: Couldn't find any package by glob
'linux-headers-4.8.0-2-686-pae'
>> >
>> > # apt-cache show linux-headers-4.8
>> > ...
>> > N: Couldn't find any package by glob
'linux-headers-4.8'
>> > ...
>> >
>> > # apt-cache show linux-headers-4.9
>> > Package: linux-headers-4.9.0-2-686
>> > Source: linux
>> > ...
>> >
>> > It looks like linux-headers-4.8 are currently missing in Stretch
repo
>> > though currently installed kernel is 4.8.
>> > This issue seems quite independant from asterisk, anyway.
>>
>> You probably started working on this box a while ago. Streetch's
current
>> kernel is 4.9.0-2 (it changed shortly before the freeze). It is now
>> frozen and won't change (barring a really good reason).
>>
>> >
>> >
>> > I started all over with a Jessie box.
>>
>> I recommend to go back to Stretch and just upgrade the kernel. In other
>> words: keep the software up-to-date.
>>
>> > Relating to [1], I could positively run:
>> > # m-a a-i dahdi
>> > ...
>> >
>> > But # dahdi_genconf required a reboot to run OK.
>>
>> Certainly not. See below.
>>
>> > Though this worries me as I need to script the whole install
process, I
>> can
>> > leave it aside at the moment.
>> >
>> >
>> >
>> > > >
>> > > > 3. How is dahdi started-stopped in Stretch ? (I
can't find any
>> > > > /etc/init.d/dahdi file after apt-get install
asterisk-dahdi).
>> > >
>> > > Started: should be automatically at boot.
>> >
>> >
>> > Shall I find an /etc/init.d/dahdi file or equivalent ?
>> > If positive which command produces this file ?
>> > I would expect dahdi-linux or dahdi packages to install these
file.
>> >
>> >
>> > > Waht hardware device do you
>> > > have?
>> > >
>> >
>> > # dahdi_hardware
>> > pci:0000:04:05.0     wctdm24xxp+  d161:8007 HA8-0000
>>
>> Traditionally dahdi has been shipped with a modprobe.d configuration
>> file to blacklist all of the PCI cards. This was because the order in
>> which they were loaded was not well-defined.
>>
>> This is irrelevant on a system with a single device. And anyway,
>> irrelevant in a system configured (as is in the Debian packages) with
>> auto_assign_spans=0 . In such a system, devices register automatically,
>> but their spans are not assigned span and channel numbers unless they
>> are configured in /etc/dahdi/assigned-spans.conf .
>>
>> So try:
>>
>>   dahdi_span_assignment auto
>>   dahdi_genconf
>>
>>
>
> This "dahdi_span_assignments auto" stratement was missing in my
> installation script.
>
> This one is now:
>
>
>     DAHDI_MODULES="wctdm24xxp"
>     apt-get -s install asterisk-dahdi module-assistant
> linux-headers-$(uname -r) dahdi-source
>     m-a a-i dahdi
>     modprobe ${DAHDI_MODULES}
>     dahdi_span_assignments auto
>
>     ... edit asterisk and dahdi config files
>
>     dahdi_cfg -vvvvvvvvv
>
> Thank you very much for letting me know about this dahdi_span_assignments
> command.
>
> May I add I've still got no /etc/init.d/dahdi file or equivalent though
> dahdi channels seems OK within Asterisk ?
> I'll learn a bit deeper into dahdi_span_assignments to clarify my
further
> questions, if any.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20170321/224e5162/attachment.html>

On Tue, Mar 21, 2017 at 09:36:21AM +0100, Olivier wrote:
> Thanks to Tzafrir help, Now I have an Asterisk-Dahdi system installed from
> Stretch repository.
> This system has a Digium HX8 card with BRI modules, Asterisk 13.14.0, Dahdi
> 2.11.1.
> BRI spans appears as up and active but I've not tested them yet:
> CLI> pri show spans
> PRI span 1/0: Up, Active
> PRI span 2/0: Up, Active
> PRI span 3/0: Up, Active
> 
> 
> I'm still having some questions:
> 
> 1. I can't find any /etc/init.d/dahdi file in my newly built system so
> "service dahdi status" (or systemctl status dahdi) fails with:
> Unit dahdi.service could not be found.
> Shall I worry about this ?
No. As I mentioned, that is meaningless.

There are various commands that show the status at various levels:

lsmod | grep ^wctdm24xxp
dahdi_hardware | grep 'wctdm24xxp\+'
dahdi_span_assignments list
lsdahdi
asterisk -rx 'pri show spans'

What exactly do you consider as "status of dahdi"?
> 
> 2. Where can Dahdi 2.11.1 Changelog file be found ?
> In http://downloads.asterisk.org/pub/telephony/ ?
git log #?

The tarball has no changelog and thus it is not packaged. Sorry.

-- 
               Tzafrir Cohen
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com