Unable to create channel of type 'DAHDI' (cause 34)

Hi!

I have a small asterisk box with a TDM 403P card, working for abouth a month. Today, I restarted asterisk (v. 1.614), and DAHDI (v. 2.2.0.2), and since then, I can only use channel 3; every time I try to make a call while channel 3 is busy, I get the following error:

WARNING[7454]: app_dial.c:1518 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 34 - Circuit/channel congestion) == Everyone is busy/congested at this time (1:0/1/0)

If I restart DAHDI, I get the following:

Destroying channels and reloading DAHDI configuration. > Initial softhangup of all DAHDI channels complete. > Final softhangup of all DAHDI channels complete. == Unregistered channel 1 == Unregistered channel 2 == Unregistered channel 3 == Parsing '/etc/asterisk/chan_dahdi.conf': == Found == Parsing '/etc/asterisk/users.conf': == Found -- Reconfigured channel 3, FXS Kewlstart signalling [Sep 29 10:06:14] WARNING[7193]: chan_dahdi.c:4664 handle_alarms: Detected alarm on channel 2: Red Alarm -- Reconfigured channel 2, FXS Kewlstart signalling -- Reconfigured channel 1, FXS Kewlstart signalling [Sep 29 10:06:14] WARNING[7193]: chan_dahdi.c:14992 process_dahdi: Ignoring any changes to 'userbase' (on reload) at line 23. [Sep 29 10:06:14] WARNING[7193]: chan_dahdi.c:14992 process_dahdi: Ignoring any changes to 'vmsecret' (on reload) at line 31. [Sep 29 10:06:14] WARNING[7193]: chan_dahdi.c:14992 process_dahdi: Ignoring any changes to 'hassip' (on reload) at line 35. [Sep 29 10:06:14] WARNING[7193]: chan_dahdi.c:14992 process_dahdi: Ignoring any changes to 'hasiax' (on reload) at line 39. [Sep 29 10:06:14] WARNING[7193]: chan_dahdi.c:14992 process_dahdi: Ignoring any changes to 'hasmanager' (on reload) at line 47.

Every time I stop or restart asterisk, I get the following:

ska5:~# /etc/init.d/asterisk stop open error on /dev/dahdi/1: Device or resource busy Stopping Asterisk PBX: asterisk.

It doesn’t matter if I restart the server unload DAHDI, or restart DAHDI. I always get an error as if the channel was busy.

Thank you for your kind help,

Diego Madiedo
dmadiedoATskinatech.com