Voicemail Pro service stopping intemittent 11.1.2.4

[lleeNC]

All,

I know this has been an issue on 11.1.2.2 and I believe 11.1.2.3. This was supposedly fixed on 11.1.2.4 but I have a customer whose Voicemail Pro service keeps stopping intermittently every few days.

Anyone have this issue on 11.1.2.4 yet? They are on Server Edition

I started a monitor trace to see if I can find anything. Hesitant on opening an Avaya ticket as their services have degraded heavily since going private.

Wondering if this is SMTP related,

Current SMTP setup,

localhost localhost 25 vmpro@192.168.1.10
domainname1.net 192.168.1.98 25 voicemail@example.org
domainname2.net 192.168.1.98 25 voicemail@example.org
domainname3.net 192.168.1.98 25 voicemail@example.org
domainname4.net 192.168.1.98 25 voicemail@example.org

Backing up to the Secondary Server

 

[Westi]

if I am not mistaken then those releases have some issues with the service stopping.
You can look in the tech bulletin for 11.1.3 as it should mention the fixes.

Joe
FHandw, ACSS, ACIS

 

[lleeNC]

I'll look at it shortly here and see if I can find anything on the tech bulletin.

 

[Westi]

Just had a look and there is no service restart issue on the tech bulletin that is fixed from 11.1.2.4 to 11.1.3

these seem to be the only ones that are mentioned but that doesn't mean that it actually is the only stuff fixed ;-)

IPOFFICE-171296 User Voicemail status do not sync between Primary and Secondary/Backup VMPRO in a resiliency setup
IPOFFICE-171146 VMPro client unable to open Custom Prompt directory on server
IPOFFICE-171061 Unable to add/modify voicemail 'Module' on French/German language PC using Voicemail Pro Client
IPOFFICE-171376 When Call recordings done during failover, are moved from secondary VMPRO to Primary the Media Manager is unable to show those and generates and error message as no valid license

Joe
FHandw, ACSS, ACIS

 

[lleeNC]

True. Thanks for looking, I also didn't find anything on it.

Currently running a continuous Monitor trace on it. Hopefully I can catch what is causing this.

As always, i'll post a resolution here if/when I find out the cause and solution.