Voicemail Pro issue with IP OFFICE 406 V2

[peterv05]

We use the IP OFFICE 406 with 3x 5420 as main phones in combination with Econsole software and about 60x 5410 phones for the users since november 2005. The Voicemanager Pro is installed so that calls for our main number are routed through the VM server (for specific day/night service feature and the possibility of using a custom auto attendant message).
Over the last 3 weeks we experience problems in de the communication between the Voicemanager Server and the IP OFFICE itself, because calls are no longer presented on the 5420 phones, they are still visible in the Econsole and some othere strange things happens with calls when transferred, you can not hear the other side for example. When the Voicemanager server has been restarted, everything works fine again. The first time we experienced this problem was on 23 december, the second time 2 januari, and today on the 6th. An other problem with the Voicemail Pro application spotted earlier, was that when other applications are running during daytime operation, the Voicemail processes are peaking at 100% CPU load.

We are using the IP OFFICE version/Voice Pro version prior to the Avaya maintenance release of 16 december 2005.

Does anyone have a clue what to do about this problem, because it is really affecting our normal business.

 

[sizbut]

What versions are you using, as there are 2.1, 3.0DT, 3.0 and 3.1 software streams at the moment.

Not seen your issue but concerned that your message implies that you are running other business app on the same PC as the Voicemail Pro.

The Voicemail Pro server PC really should be dedicated to that task and that task only. Occasionally running another app on it is okay but not regularly doing so.

Also eConsole is no longer supported by Avaya (unless you meant to say SoftConsole). Both the above issues will limit your chances of getting any support from Avaya.

 

[peterv05]

With EConsole I meant SoftConsole, my mistake. We are running on 3.1 software at the moment, release prior to the maintenance release of 16 december 2005. The Voicemail Pro server is a dedicated HP ML-server, and is only running software like logme-in for remote support issues and Deltaserver for creating caller-logfiles.

Since whe seen the server crashing the first time, when for example the IP management client was used, the server has been left alone so that it could to the task it was created for, but since the 23th of december it somehow loses synchronizity with the IP OFFICE 406 V2 and calls are not handled like they should. Restarting the server solves this matter, but that is not a solution.

 

[IPOdan]

The first 3.1 was riddled with bugs. I would first suggest upgrading to 3.1.48 or downgrading to 3.0.69. I had major problems with calls that were suppossed to route to reception randomly going to night ring. Also, check the docs on the maximum number of SoftConsoles. I think a max of two are supported, but I could be wrong.

 

[peterv05]

When I read Avaya technical bulletin 56 for the 3.1.48 release I cannot find much problems solved with this release in regard to the Voicemanager Pro software, besides a problem with a beep. What other bugs are solved you are referring to?