How to – Fix Dahdi errors(no sounds) in relation to Vicidial

How to – Fix Dahdi errors(no sounds) in relation to Vicidial

What is Dahdi’s function in Vicidial?

Dahdi is essentially what controls the meet-me conferences(Vicidial Conferences as shown below) for Vicidial. So when this is not running, you will get all types of errors, such as, time sync errors, “no one in your session” , no sound and other various issues. If you do not hear the “You’re the only one in this conference” sound when you login or any customer voice, then dahdi is probably not loaded correctly. The reason for this is because the meetme conferences link the audio channel from the carrier to the meetme conference. With no meetme confernce(dahdi) then the system will not work correctly.

Typical Error: WARNING[5123][C-00000007]: app_meetme.c:1663 build_conf: Unable to open DAHDI pseudo device

[Feb 12 15:21:47] == Using SIP RTP CoS mark 5
[Feb 12 15:21:47] -- Called 1001
[Feb 12 15:21:47] -- SIP/1001-00000003 is ringing
[Feb 12 15:21:47] -- SIP/1001-00000003 is ringing
[Feb 12 15:21:51] > 0x7fa04800f470 -- Strict RTP learning after remote address set to: 192.168.0.1:29040
[Feb 12 15:21:51] -- SIP/1001-00000003 answered
[Feb 12 15:21:51] -- Executing [8600051@default:1] MeetMe("SIP/1001-00000003", "8600051,F") in new stack
[Feb 12 15:21:51] WARNING[5123][C-00000007]: app_meetme.c:1663 build_conf: Unable to open DAHDI pseudo device

What to do? Well, first let’s check if dahdi is running by using the command “dahdi_cfg -vvv” which should output as below after seeing the above error:

So how do we fix it? Type “modprobe dahdi” and check again

Now this status shows we have Dahdi running correctly in Linux. So lets make sure this doesn’t happen anymore. Add this following line to your crontab:

* * * * * /usr/sbin/modprobe dahdi

This will attempt to run dahdi every minute in the case it does crash from now on, it will automatically recover. I hope this article helps.

-Nox