No Asterisk Dadhi Help?
If Asterisk is running and you can't see the Dadhi help commands from the Asterisk CLI ("help dahdi"), it means that there is a misconfiguration between /etc/dahdi/system.conf, the hardware and/or the Asterisk Dahdi configuration files. Most often it is a registration error. For example: the card uses one type of signaling like fxsks and /etc/dahdi/system.conf configures it as fxoks. Sometimes it can be as simple as a typo in one of the files. Unfortunately, Asterisk does not report misconfiguration errors on either the Asterisk or Linux command line!
You can find out more about what isn't working by viewing the /var/log/asterisk/full text file. I suggest using Webmin's File Manager program for viewing this file. The file /var/log/asterisk/full logs all of Asterisk's activities when it loads. Warning it is a large file! Search for the term "dadhi" and look for registration information for clues as to what has happened.
This is a failed registration, channel 5 is physically a FXO-LS (loop start) and it has been configured as a FXO-KS (kewlstart). This could be in /etc/dadhi/system.conf, /etc/chan_dadhi_additional.conf or /etc/asterisk/chan_dahdi_custom.conf. Asterisk rejects the Dadhi configurations and fails to load ALL of the channels including the good ones!
This is a successful registration. The Red alarm is from the T1 line - it indicates that the T1 line is not receiving a clock. In this case, it was physically disconnected. Once you determine what the misconfiguration is and correct it, you may be able to reload the new Dahdi configuration by typing the reload commands at the Asterisk CLI:
pbx*CLI>: restart gracefully
Or exiting and issuing the amportal restart command at the Linux command prompt:
root@pbx:~ $ amportal restart
If that doesn't work, you will have to reboot your server gracefully.
