VM Patch 3.2.15

[adirondackman]

I've seen the VM service on 3.2.15 giving errors and shutting down. Is this patch intended to fix this issue? I didn't see any pdf regarding the download and what it addresses.

 

[tlpeter]

the patch is to fix the problem with OS that is other than englisch
nothing more

 

[MarkToo]

Interesting... however, before I read this reply we applied this patch to a US 3.2 VMPro Server that was shutting down more than once an hour... There were no notes on the Avaya download page for this patch at the time.

Anyway, since we applied this patch the server hasn't shut down once and it's been over 6 hours... Hopefully this isn't just a coincidence!

MarkToo

 

[racom]

I have two systems running 3.2 doing the exact same thing. Both systems around 9:30 - 10:30 every day the voicemail pro service shuts down. I tried that patch, and it still continues. Has anyone talked with Avaya about this issue yet? I would, but I have had a case open on another issue with Avaya and am not getting any call backs. I don't have time to chase their issues!!!!

 

[aarenot]

Racom, have you uninstalled VMPRO, and reinstalled it?

You do not always get what you pay for, but you never get what you do not pay for.

 

[IPOUK]

I keep getting "There was an error opening the call flow database" every time I open the VM GUI

Reboot and all is fine for a few hours!

Anyone else got that?

 

[MrIPO]

We have this issue raised with Avaya, Can I confirm are you seeing Dr Watson errors when the Vm stops in the Event Viewer ? Have you provided AVAYA with a Level 9 Debug View Trace when you raised> ??

http://www.iporesource.com

"Launching late 2006

 

[racom]

Yes, I get the Dr. Watson message.

No, I have given up on creating cases. I have to fight, scratch, and even beg to get a resolve, and in the end, they make me wait for the next available release. I don't have the time or resources to get Avaya to respond. As you can see, I am very frustrated with Avaya right now. I think they forget we are on their side!

So in the end I check the forums for common issues and hope that Avaya is watching so they can put 2 and 2 together.

 

[kanskid]

We have had the same problem and Avaya is no help.
But the fix seems to be backup the vmpro and reload it from
a New image

 

[ronromano]

We had a customer with the 3.2 VM pro stopping. Opened a ticket with avaya and got the 3.2.1501 patch and cleared the problem. It appears, although I was not able to replicate it, that an undefined digit in a callflow, when chosen, will cause the service to stop at certain times when certain conditions are met. You might try to set all your menu choices with all digits going to something and see if it helps.

 

[aarenot]

?

as an option would probably suffice.

You do not always get what you pay for, but you never get what you do not pay for.

 

[adirondackman]

The "?" is a resolution issued by Catalyst to bug that has been seen in VM whereby if a caller selects an undefined option in the VM Call flows (AutoAttendant) the VM may crash.

Just a "?" looped to the beginning of the Menu corrects this.

 

[aarenot]

I hsve not run into this, but think I will start adding a ? to all call flows in the future which leads to the same menu.
Thanks for the info from Catalyst.

You do not always get what you pay for, but you never get what you do not pay for.

 

[superikey]

FYI you cant put a ? in a menu t hat has a 4??? in it. If you do then you cant dial 4xxx extension.
Am I missing something?

 

[MrIPO]

Strange thing is I have a site with no Call flows (aa's) and VM Pro was stopping, since applying 3.2.1501 Patch no problems. VM Pro was in IPO mode however....

http://www.iporesource.com

"Launching late 2006

 

[MarkToo]

Superikey,

We've been using the "$" symbol for the undefined option and it works great!

FWIW,
Mark