[asterisk-users] chan_dahdi missing in * 1.6.1.1

[Danny Nicholas]

My .02 - It is really easy to miss/mess up the supporting files when
upgrading.  Make sure you are using a segregated tree to compile from.

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Moises Silva
Sent: Tuesday, June 09, 2009 9:32 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] chan_dahdi missing in * 1.6.1.1

On Tue, Jun 9, 2009 at 12:31 AM, Steve Repo<scmuser at gmail.com> wrote:
>>> What is the magic to compile chan_dahdi.so in asterisk 1.6.1.x?  I'm
>>> on centos 5.3.
>>>
>>> Also, asterisk 1.4.25 cannot compile chan_dahdi as well while the
>>> previous versions do. What changed or what am i missing?
>>
>> There probably isn't magic. If you post the errors you got during the
>> compile we'll be more likely to be able to tell you what's going
>> wrong.
>>
>> Specifically the stuff you got when you said you cannot compile
>> chan_dahdi.so would be important to post.
>
>
> Ah, there are no errors as such during compile or atleast I didn't
> seem to notice any. However, I do not see chan_dahdi.so in
> lib/asterisk/modules/ after asterisk install.
>
> Attached are some info and config.log from asterisk 1.6.1.1..
>
> # /opt/dahditools/sbin/dahdi_hardware
> pci:0000:03:04.0     wanpipe-     1923:0040 Sangoma Technologies Corp.
> A200/Remora FXO/FXS Analog AFT card
>
> # /opt/dahditools/sbin/dahdi_scan
> [1]
> active=yes
> alarms=UNCONFIGURED
> description=wrtdm Board 1
> name=WRTDM/0
> manufacturer=
> devicetype=
> location=
> basechan=1
> totchans=24
> irq=0
> type=analog
> port=1,none
> port=2,none
> port=3,FXO
> port=4,FXO
> port=5,none
> port=6,none
> port=7,none
> port=8,none
> port=9,none
> port=10,none
> port=11,none
> port=12,none
> port=13,none
> port=14,none
> port=15,none
> port=16,none
> port=17,none
> port=18,none
> port=19,none
> port=20,none
> port=21,none
> port=22,none
> port=23,none
> port=24,none
>
> # cat /proc/dahdi/1
> Span 1: WRTDM/0 "wrtdm Board 1" (MASTER)
>
>          1 WRTDM/0/0
>          2 WRTDM/0/1
>          3 WRTDM/0/2
>          4 WRTDM/0/3
>          5 WRTDM/0/4
>          6 WRTDM/0/5
>          7 WRTDM/0/6
>          8 WRTDM/0/7
>          9 WRTDM/0/8
>         10 WRTDM/0/9
>         11 WRTDM/0/10
>         12 WRTDM/0/11
>         13 WRTDM/0/12
>         14 WRTDM/0/13
>         15 WRTDM/0/14
>         16 WRTDM/0/15
>         17 WRTDM/0/16
>         18 WRTDM/0/17
>         19 WRTDM/0/18
>         20 WRTDM/0/19
>         21 WRTDM/0/20
>         22 WRTDM/0/21
>         23 WRTDM/0/22
>         24 WRTDM/0/23
>
> I does not matter if i pass --with-dahdi to ./configure script or not.
>

After running ./configure you will get an output file named
config.log, that file has the details about which tests were performed
during the configuration to determine which headers and libraries were
present in the system. You should pastebin that file and post here a
link to it.

Also, what do you see when you do make menuselect -> channel drivers
-> chan_dahdi? if Asterisk see dahdi, then you should see it marked
for compilation.

-- 
Moises Silva
Software Developer
Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON
L3R 9T3 Canada
t. 1 905 474 1990 x 128 | e. moy at sangoma.com

_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users