VICIDIAL HELP And Consulting
watch asterisk messages thru linux cli
tail -f /var/log/asterisk/messages
# apache tools
check web connections: netstat -tuna | grep “:80” | wc -l
Useful Vicidial Commands for Linux
/usr/share/astguiclient/ADMIN_keepalive_ALL.pl –cu3way
/usr/share/astguiclient/AST_manager_listen.pl –debugX
/usr/share/AST_DB_action.pl –debugX
Check if Dahdi(Meetme/Vicidial Conferences) is running
dahdi_cfg -vv
If its not run this command:
modprobe dahdi
enable dahdi on boot
systemctl enable dahdi
check keepalives
cat /etc/astguiclient.conf | grep VARactive_keepalives
viciphone time for autologin
$webphone_call_seconds = ‘5 ; in options.php in agc dir
upgrade vici
cd /usr/src/astguiclient
svn checkout svn://svn.eflo.net:3690/agc_2-X/trunk
cd trunk
perl install.pl
mysql -p -f –database=asterisk < /usr/src/astguiclient/trunk/extras/upgrade_2.14.sql
certbot renewal command
certbot certonly –cert-name
to check whats eating all the ram
ps aux | awk ‘{print $2, $4, $11}’ | sort -k2rn | head -n 20
cpu usage
ps -eo pcpu,pid,user,args | sort -k 1 -r | head -11
check HDD space
df -h
check processors
grep processor /proc/cpuinfo | wc -l
tcp dump for ports(change accordingly)
tcpdump -nttv -s 0 -i eth0 port 80
check connections to a port
netstat -tuna | grep “:5038” | wc -l
clear dns cache
/etc/init.d/nscd restart
For a “live” view showing the logic involved in dialing:
screen -r ASTVDauto
ctrl-a – ctrl-d to get out of it.
perl install based on asterisk version
perl install.pl –copy_sample_conf_files –asterisk_version=16.X
start up asterisk
/usr/share/astguiclient/start_asterisk_boot.pl
/usr/share/astguiclient/ADMIN_keepalive_ALL.pl –cu3way
VOLUME FOR AST13
With Asterisk 13, the mechanism in Asterisk that allowed for volume changes and muting of meetme participants had been causing random crashes in Asterisk. We now disable this functionality by default, but if you want to enable it, all you have to do is use the agc/options.php setting of “$ast13_volume_override = ‘1’;”
USEFUL SVN TOOLS
Beware of the version in system settings. To be absolutely certain to version match:
SVN is used to manage the “install directory” (/usr/src/astguiclient/trunk)
The install directory has a group of sql files that are used to upgrade from the first version to NOW (based on the svn revision level presently in THAT directory).
When your last sql upgrade file has a last line indicating that the db schema value should be what is presently shown in your System Settings … you have a match. All your code will match your entire DB if you run install.pl with that version loaded.
Anything else is more of a “sort of” match. That’s the only truly reliable method. How you get there is a matter of experience and knowledge of svn. But upgrading/downgrading that svn repository until you get lucky and it matches is the easiest amateur way to get a lock-on match of your present db schema.
start here:
CODE:
tail /usr/src/astguiclient/trunk/extras/upgrade_2.14.sql | grep db_schema_version
mysql -u cron -p1234 asterisk -e “select * from system_settings\G” | grep schema
cd /usr/src/astguiclient/trunk
svn info | grep Revision
Compare the db schema in system settings to the db schema in the upgrade.sql file.
Note the svn revision level.
Increase or decrease the svn revision level with “svn up -r ####” and … try again until the db schema in the sql file and system settings match. Example:
svn up -r 2946
Then run perl install.pl. Example:
CODE: SELECT ALL
cd /usr/src/astguiclient/trunk
perl install.pl –copy_sample_conf_files
Note that –copy_sample_conf_files will overwrite the .conf files presently in the system. Any that you have edited will need to be re-edited. Such as externip=xxx.xx.xx.x in sip.conf. While updating these isn’t always necessary, NOT updating them has been known to blow an entire workday for simple “missed” change that’s very difficult to find otherwise. Skip copy_sample_conf_files at your own risk. 😎
for webrtc phone issue with chrome 87 update
zypper in ncurses-devel libxml2-devel sqlite-devel libsrtp-devel libuuid-devel openssl-devel
Whitelist IP’s on in inbound servers
firewall-cmd –zone=trusted —add-source=192.168.1.40 –permanent