vicidial.org

I was excited for vicidial 9 but unfortunately it gave me nightmare. There is a issue with frequent asterisk crash. I am not able to find the reason of crash in logs. System is build to handle just 20 agents | 100 trunks.
I am successfully running vicidial 8.1.2 in cloud without any problem from last 1 year. so i think issue with version 9

Installation info
-----------------
Source file: ISO file directly from vicidial website "ViciBox_v9.x86_64-9.0.0.iso"
Installation method: vicidial-express

Single Server | Cloud based

Hardware Info:
vicibox9:~ # lscpu
Architecture: x86_64
Byte Order: Little Endian
Address sizes: 40 bits physical, 48 bits virtual
CPU(s): 3
CPU MHz: 3792.000

Storage: 250 GB NVMe SSD

RAM: 8 GB

Vicidial Version : VERSION: 2.14-718a | BUILD: 190902-0839
SVN: 3134

Asterisk version: 13.27.0

No Extra software after installion.

There is a issue with frequent asterisk crash

,
If you dont post the log after or before the crash, there is nothing we can do..

As I already told I dint find any anomaly in logs. Let me know which log should I post

Is it /var/log/asterisk/messages?

To me it seems you are trying it on VPS , even i have tried it on vps, but v9 doesn't even boot some time . try it on Dedicated server .

Hello,

We have same issue on:
- ViciBox v.9.0.0 190913-1108, Asterisk 13.27.0-vici, SVN: 3149
- ViciBox v.9.0.1 191123-0203, Asterisk 13.29.2-vici, SVN: 3179

No issue on:
- ViciBox v.9.0.0 190913-1108, Asterisk 13.27.0-vici, SVN: 3136
- ViciBox v.8.1.2 181002 apgraded to openSUSE Leap 15.1, Asterisk 13.27.0-vici, SVN: 3130

All systems use WebRTC ViciPhone as a SIP-client.


Asterisk crash suddenly, no dependencies found.
It can work fine and stable for several weeks, and after that restart several times in an hour, and after that it works stably again few days.
We use Auto-Restart Asterisk: Y in server setings, that helps a little.

areon wrote:Hello,

We have same issue on:
- ViciBox v.9.0.0 190913-1108, Asterisk 13.27.0-vici, SVN: 3149
- ViciBox v.9.0.1 191123-0203, Asterisk 13.29.2-vici, SVN: 3179

No issue on:
- ViciBox v.9.0.0 190913-1108, Asterisk 13.27.0-vici, SVN: 3136
- ViciBox v.8.1.2 181002 apgraded to openSUSE Leap 15.1, Asterisk 13.27.0-vici, SVN: 3130

All systems use WebRTC ViciPhone as a SIP-client.


Asterisk crash suddenly, no dependencies found.
It can work fine and stable for several weeks, and after that restart several times in an hour, and after that it works stably again few days.
We use Auto-Restart Asterisk: Y in server setings, that helps a little.

Zypper ref
Zyppper up -y

Make sure to update server asterisk version too under Admin > Servers.

We have noted for some clients that Asterisk may crash if an agent uses the volume controls on the agent screen. In these cases, we comment out the following lines in "/etc/asterisk/extensions.conf" for all dialers and reload Asterisk:

; MeetMe Adjustment Extensions
exten => _X48600XXX,1,MeetMeAdmin(${EXTEN:2},T,${EXTEN:0:1})
exten => _X48600XXX,2,Hangup()

exten => _X38600XXX,1,MeetMeAdmin(${EXTEN:2},t,${EXTEN:0:1})
exten => _X38600XXX,2,Hangup()

exten => _X28600XXX,1,MeetMeAdmin(${EXTEN:2},m,${EXTEN:0:1})
exten => _X28600XXX,2,Hangup()

exten => _X18600XXX,1,MeetMeAdmin(${EXTEN:2},M,${EXTEN:0:1})
exten => _X18600XXX,2,Hangup()

Matt, thanks!

In our servers we comented only extensions that control volume.
No more crashes observed last week.

; MeetMe Adjustment Extensions
;exten => _X48600XXX,1,MeetMeAdmin(${EXTEN:2},T,${EXTEN:0:1})
;exten => _X48600XXX,2,Hangup()

;exten => _X38600XXX,1,MeetMeAdmin(${EXTEN:2},t,${EXTEN:0:1})
;exten => _X38600XXX,2,Hangup()

Thanks for the feedback!

Is there any more information on this? I know for certain that our client is using the volume control and they consider it quite important too. It worked fine on asterisk 11 but the current upgrade to 13.34.0 seems to be crashing a bit.

It is an issue with one of the many core changes from Asterisk 11 to 13, so we don't have many options to fix it. We have found that while it does affect a significant number of Asterisk 13 VICIdial installs, it does not affect all of them. You can try re-enabling volume controls by adding the following variable to your agc/options.php file:

$ast13_volume_override = '1';

mflorell wrote:It is an issue with one of the many core changes from Asterisk 11 to 13, so we don't have many options to fix it. We have found that while it does affect a significant number of Asterisk 13 VICIdial installs, it does not affect all of them. You can try re-enabling volume controls by adding the following variable to your agc/options.php file:

$ast13_volume_override = '1';

We are about to invest a bit of time into fixing it. Are you aware if it has been fixed in future versions, we are currently on 13.34, do you know if an update to 13.38 would help, if so, is there a quick link to the vicidial patches that I can apply? Alternatively, is vicidial in a state where we can consider deploying Asterisk 16 instead, if so where? Pretty comfortable with asterisk so happy enough to test and revert back if there's an issue.

Since Asterisk 13 is in security-maintenance-mode, I doubt any recent updates to that branch would include bug fixes.

As for Asterisk 16, we've been testing that for the last couple of weeks, and we should have a beta-build ready that is VICIdial-approved within a couple weeks. We have not specifically tested the meetme-volume-change bug, but I can add that to the list.