[asterisk-bugs] [JIRA] (ASTERISK-29367) Core Reload causes voicemail taskprocessor overload
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Wed Mar 24 08:42:15 CDT 2021
[ https://issues.asterisk.org/jira/browse/ASTERISK-29367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asterisk Team updated ASTERISK-29367:
-------------------------------------
Status: Waiting for Feedback (was: Waiting for Feedback)
> Core Reload causes voicemail taskprocessor overload
> ---------------------------------------------------
>
> Key: ASTERISK-29367
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-29367
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Applications/app_voicemail
> Affects Versions: 16.14.0
> Environment: Centos 7 x64
> Reporter: Luke Escude
> Assignee: Asterisk Team
>
> We have the default taskprocessor queue size configured for VM: Low is 450, High is 500.
> We have a higher-volume instance (typically around 35 simul calls at 11am on weekdays) of Asterisk 16.14 that appears to be hitting the high water mark whenever a Core Reload occurs.
> I'm looking around to try and find out what exactly the Voicemail module is doing but I can't find any diagnostic commands to run for you guys.
> There are only like maybe 30 voicemail boxes configured for this system. Additionally, the following parameters in voicemail.conf exist:
> {noformat}
> pollmailboxes=yes
> pollfreq=60
> maxsecs=600
> maxsilence=10
> minsecs=1
> serveremail=no-reply at domain
> attach=yes
> fromstring=From
> emailsubject=New Voicemail
> emailbody=Body
> externnotify=sh /primevox_scripts/voicemail_notify.sh
> externpassnotify=sh /primevox_scripts/update_vm_password.sh
> odbcstorage=vmodbc
> odbctable=vm_table
> {noformat}
> So we're using ODBC for voicemail storage. Newest MariaDB Connector and UnixODBC 2.3.9 compiled.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list