Dear Warren; Yes, first thing I do is the make all and make install for dahdi, then I do ./configure and make and make install for asterisk. But I do not find the chan_dahdi under the /usr/lib/asterisk/modules. WHY? If I used asterisk 1.8, then I do not have any problem. What I am missing? Do I have to do dahdi_gencof before starting the compilation and installation of asterisk 1.4? Regards Bilal -------------> > > Hi All; > > > > Is it normal if I used asterisk 1.4 and dahdi, then I > will not find > > chan_dahdi under /usr/lib/asterisk/modules? And I will > not be able to type > > dahdi commands (dahdi restart for example) in the > asterisk CLI? > > > > Actually what I found only the following: > > > > app_dahdibarge.so? app_dahdiras.so? > app_dahdiscan.so? codec_dahdi.so > > > > So, it is available only with asterisk 1.8? > > > > Well, does this mean it is preferred to use zaptel with > asterisk 1.4? > > > > > Did you compile asterisk with DAHDI support?? i.e Did > you install DAHDI, > then run ./configure on Asterisk Source and then > install?? Or did you > install asterisk first, then DAHDI?? I've successfully > used DAHDI with > Asterisk 1.4, so there must be some issue.? Please give > us information > about how you installed everything. > > -- > Thanks, > --Warren Selby, dCAP > http://www.SelbyTech.com <http://www.selbytech.com>
Dear Warren; Yes I am compiling and installing dahdi first and then I start by asterisk 1.4.39 but I do not find chan_dahdi under /usr/lib/asterisk/modules, but if I used asterisk 1.8, it is working fine.
On 04/18/2012 06:43 PM, bilal ghayyad wrote:> Dear Warren; > > Yes I am compiling and installing dahdi first and then I start by asterisk 1.4.39 but I do not find chan_dahdi under /usr/lib/asterisk/modules, but if I used asterisk 1.8, it is working fine. > > From the other side: I tried asterisk 1.4.44 and same thing (I am not able to see the chan_dahdi) !! > > By the way, I am using ubuntu. > > Which asterisk 1.4 version that you tried it with dahdi and you were able to find the chan_dahdi? > > Really I tried too many attempts and until now I am not able to find a solution ! What I am missing?You are asking people to help you guess what is wrong, instead of looking at the output of the Asterisk configure script. When the configure script checks for DAHDI, if that process fails for some reason, it will tell you why. That information is required for anyone to be able to help you. -- Kevin P. Fleming Digium, Inc. | Director of Software Technologies Jabber: kfleming at digium.com | SIP: kpfleming at digium.com | Skype: kpfleming 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at www.digium.com & www.asterisk.org
On Wed, 18 Apr 2012 06:12:45 -0700 (PDT) bilal ghayyad <bilmar_gh at yahoo.com> wrote:> Yes, first thing I do is the make all and make install for dahdi, > then I do ./configure and make and make install for asterisk. But I > do not find the chan_dahdi under the /usr/lib/asterisk/modules. WHY?You probably need to run make menuselect after ./configure and before make to select dahdi for building & installation. -- C. Chad Wallace, B.Sc. The Lodging Company http://www.lodgingcompany.com/ OpenPGP Public Key ID: 0x262208A0
Dear; Well, I did make menuselect and I really found the XXX and did not get the ability to select the channel. So what could be the reason?
Dear; The output of the ./configure that is related to dahdi is: checking for DAHDI_RESET_COUNTERS in dahdi/user.h... yes checking dahdi/tonezone.h usability... yes checking dahdi/tonezone.h presence... yes checking for dahdi/tonezone.h... yes And the dependecies of the chan_dahdi as I saw in the make menuselect is (but really I do not know what the M and E means, and how I can be sure if they are existed or not)? Depends on: res_smdi(M), dahdi(E), tonezone(E), res_features(M), pri(E) Any help? Regards Bilal ---------------> > Well, I did make menuselect and I really found the XXX > and did not get the ability to select the channel. So what > could be the reason? > > When you are in menuselect, looking at the 'channels' page, > scroll the > cursor down to chan_dahdi (marked with 'XXX'), and look at > the bottom of > the window/screen. In that area there will be information > about the > chan_dahdi dependencies that were or were not found by the > the configure > script. If you can copy and paste that information here, we > can try to > help you figure out what is going on. It's quite strange > that > codec_dahdi successfully built but chan_dahdi did not; the > problem is > likely not related to DAHDI, but due to some other > dependency that > chan_dahdi has. As I said before, what we really should be > looking at is > the configure script output that indicates what it was able > to find and > what it was not able to find, but the menuselect information > is a > reasonable next step. > > > As Kevin said, you need to check the out put when you run > ./configure.? > You could pipe it through less or copy-and-paste it into a > text editor > to search it for anything about dahdi.? It should tell > you what's wrong.