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 184.108.40.206 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!
The current Asterisk AUR PKGBUILD is up-to-date for the latest version of Asterisk (Asterisk-12), but the FreePBX AUR PKGBUILD is out of date. Recently, FreePBX released (beta) their long anticipated version FreePBX-12 that is compatible with Asterisk-12. I also have FreePBX / Asterisk running on Debian, but I would love to see an ArchLinux version of FreePBX to go with the PKBBUILD fo
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.