My problem is that i have an asterisk pbx running on centos 4.8, my problem is that asterisk stop working and asterisk's experts say that the problem is in the network, so im checking just to ... [by DANNDP]
on 02/16/2010 – Made popular on 02/16/2010
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
Everything works, tested on CSipSimple. But there is one problem: not much clients support TLS with client certs (Microsip and blink do not support)
How can I make asterisk do not require client certificates for TLS?
I am using Asterisk 220.127.116.11 and a MySQL database connected via ODBC to store CDRs. When my MySQL database isn't available when Asterisk starts or has an outage while Asterisk is running, I would expect Asterisk to retry to connect to the database, but this doesn't happen!
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.
I am using Asterisk 18.104.22.168 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.