Error Missing /dev/dahdi Debian
Contents |
time. I knew it had to be installed for timing purposes, but not having the need to use it explicitly I never gave it a second thought. However recently I thought I might get conferences up and running which need DAHDI.
Line 0: Unable To Open Master Device '/dev/dahdi/ctl'
when I issue CLI> dahdi show status, I get: "No DAHDI found. Unable to open dahdi: unrecognized service /dev/dahdi/ctl: No such file or directoryCommand 'dahdi show status' failed." At the command prompt if I type service dahdi status I get how to check dahdi version nothing returned back. However if I try to start or restart the service using service dahdi start I get: "Loading DAHDI hardware modules:FATAL: Module dahdi not found. Error: missing /dev/dahdi!" I then checked the DAHDI config files
Install Dahdi-tools
in etc/dahdi and commented out the devices, not being used. Still no dice. So then (thinking it was a good idea at the time) I thought I'd try reinstalling DAHDI using yum, yum install asterisk-dahdi This went ahead and installed asterisk-dahdi package. It also installed the dependencies (as it should) including: asterisk x86_64 1.8.7.1-1.el6 epel 3.0 M dahdi-tools x86_64 2.1.0.2-8.el6 epel 134 k dahdi-tools-libs x86_64 2.1.0.2-8.el6 epel 25 k libpri x86_64 1.4.12-1.el6 epel 179 k
Download Dahdi
libresample x86_64 0.1.3-12.el6 epel 24 k libsrtp x86_64 1.4.4-4.20101004cvs.el6 epel 273 k libss7 x86_64 1.0.2-1.el6 epel 53 k So foolishly I had overwritten my otherwise working (and patched) Asterisk 1.8.7.0 install. Thankfully however yum had not overwritten the existing config file (merely appended .rpmnew to those it had installed), so getting my system back simply involved an Asterisk reinstall from my source files. I suppose the good thing is that all the requisite DAHDI pre-requsities, like libss7 are now installed without doubt, however DAHDI is still not working for me. Any ideas as to what I should try next? Thanks simcity 2012-03-16 22:15:44 UTC #2 Apparently "DAHDI is a kernel module, which means you need a version that exactly matches your kernel version". Following advice located on the Digium forums I found that I had a mismatch between my current kernel and the version for which DAHDI had been installed... run uname -a to get the kernel version Confirm the DAHDI modules are installed for your kernel version, go to /lib/modules/[kernel version]/dahdi/ They should all be there. In my case they weren't there, they were in the /lib/modules directory for an older kernel (that I think I had installed when I first compiled/installed DAHDI initially). So simple fix was to recompile and re-install DAHDI (for me from source): cd /usr/src/wget http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/releases/dahdi-linux-complete-2.6.0+2.6.0.tar.g
» [SOLVED] Error DAHDI Added by Thiago Anselmo about 3 years ago reinstall dahdi Personal Help! I installed 3.0 on GoAutoDial virtuakbox and it
/etc/init.d/dahdi: No Such File Or Directory
worked 100% ... But when I install on a real machine, gives error dahdi. The bash /etc/init.d/dahdi no such file or directory agent enters the conference room and after 4 seconds the connection is desigada. and the error that appears in the Asterisk CLI is: "Unable http://community.freepbx.org/t/solved-dahdi-install-issues/13565 to open DAHDI pseudo device" And when I dahdi renicializo the error is: Loading DAHDI hardware modules:FATAL: Module dahdi not found. Error: missing / dev / dahdi! I have updated the system: yum update and it worked. Help! Replies (7) RE: Error DAHDI - Added by Thiago Anselmo about 3 http://goautodial.org/boards/3/topics/1569 years ago My mistake, it's like this! > Channel SIP/8001-00000002 was answered.
[Jun 19 21:07:51] Manager 'sendcron' logged off from 127.0.0.1
[Jun 19 21:07:51] -- Executing [8600052@default:1] MeetMe("SIP/8001-00000002", "8600052|F") in new stack
[Jun 19 21:07:51] Parsing '/etc/asterisk/meetme.conf': [Jun 19 21:07:51] Found
[Jun 19 21:07:51] Parsing '/etc/asterisk/meetme-vicidial.conf': [Jun 19 21:07:51] Found
[Jun 19 21:07:51] WARNING[8490]: app_meetme.c:829 build_conf: Unable to open DAHDI pseudo device
[Jun 19 21:07:51] --
[Jun 19 21:07:55] Spawn extension (default, 8600052, 1) exited non-zero on 'SIP/8001-00000002'
[Jun 19 21:07:55] -- Executing [h@default:1] DeadAGI("SIP/8001-00000002", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[Jun 19 21:07:55] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------- completed, returning 0 Remembering that I am not using any card FXO/FXS/E1I'm just using a SIP trunk. RE: Error DAHDI - Added by Demian Biscocho about 3 years ago Vicidial uses Asterik's meetme rooms for normal calling. That's why DAHDI is essential in running Vicidial
Tue, 23 Apr 2013 22:45:02 UTC Severity: important Found in version dahdi-tools/1:2.5.0.1-2 Fixed in version dahdi-tools/1:2.7.0.1-1 Done: Mark Purcell