No Asterisk Zap Help?
If Asterisk is running and you can't see the zap help commands, it means that there is a misconfiguration between /etc/zaptel.conf and the hardware. Most often it is a registration error. For example: the card uses one type of signaling like fxsks and /etc/zaptel.conf configures it as fxoks. 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 zapata 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/zaptel, /etc/asterisk/zapata-auto.conf or /etc/asterisk/zapata_custom.conf. Asterisk rejects the zaptel configurations and fails to load ALL of the channels including the good ones!
This is a successful registration but something is screwy with a second registration of Channels 1, 5 and 6. This requires looking into!
Once you determine what the misconfiguration is and correct it, you may be able to reload the new Zaptel configuration by typing one of the following 3 commands at the Asterisk CLI:
pbx*CLI>: zap restart
pbx*CLI>: reload chan_zap.so
pbx*CLI>: module reload chan_zap.so
Or exiting and stopping asterisk, restarting zaptel then starting asterisk at the Linux command prompt:
root@pbx:~ $ amportal stop
root@pbx:~ $ service zaptel restart
root@pbx:~ $ amportal start
If that doesn't work, you will have to reboot your server gracefully.
