I wish to build an Asterisk server for my home. The purpose is to record all calls.The choice to go with current versions of CentOS is power and ssd-optimizations not found in version 5.
If you just install Asterisk gui 2.o from:
svn checkout http://svn.digium.com/svn/asterisk-gui/branches/2.0
And got a 404 URL not found <asterisk server> typing http://ip_machine:8088/static/config/index.html
and already did the “make checkconfig” cmd getting an “everything seems good” output.
and already Checked in Asterisk CLI:
I am using Asterisk 126.96.36.199 for call handling. I am using 6 port ( 180 channels) to handle the calls. When call volume is around 140 to 150 my asterisk gets killed without any error message even when we enabled the full log in asterisk logger.conf file. 16GB RAM is available in the asterisk running machine. In out of 16GB, 5GB free space also available when asterisk gets killed.
when I issue an '/etc/init.d/asterisk start' or 'service asterisk start' command, nothing happens, except for the single process 'astcanary /var/run/asterisk/alt.asterisk.canary.tweet.tweet.tweet 21756' briefly visible in the 'ps ax' output.
I checked /var/log/messages, syslog, daemon.log, asterisk/messages - there is nothing whatsoever.
I can run asterisk normally, and if I issue part of
I need to be able to collect core dumps, but since Asterisk's CWD is / (so claims procfs), it'll never be able to write them. I've confirmed my suspicions by allowing world write to / and SIGABRT the process, lo and behold, I had a core.
I can obviously use core_pattern to override system-wide, but I rather like the default behavior of dumping core to the cwd.