Avaya IP Office Voicemail Pro - Sorting Voicemail messages 1

[Scotty_IT]

Hi All,

We recently did an upgrade of our IP Office & Voicemail Pro systems. But now I'm getting users stating they can't access their properly, and what is meant by that is the users have several vm's in their inboxes, and it appears they are now sorting from oldest to newest.

I've been going over manuals for a method on sorting these, but have come up empty.

Does anyone know of a way to get these to sort, whether from newest to oldest or anyway possible?

 

[AACon]

Administration, preferences, general, housekeeping.
Change playback order for new messages from FIFO to LIFO

-Austin
I used to be an ACE. Now I'm just an Arse.

 

[Scotty_IT]

Hi AACon,

I've changed the New messages to sort LIFO, but it didn't seem to make a difference. So I also changed Unopened messages to LIFO, but again the new messages are sorting with the oldest on top.

 

[IPGuru]

What version did you upgrade from & what version did you upgrade to?
Has the VM remained on he same PC or have you replaced the server?
if you have replaced the server what operating system?

i sounds like something has gone wrong with the VM installation but it is difficult to advise if you don't provide full information on all that has been done



Do things on the cheap & it will cost you dear

 

[Scotty_IT]

Hi IPGuru,

We upgraded from version 9.0.4.0 build 965 to version 10.0.0.2.0 build 10 (for the IP Office) and for Voicemail pro, we upgraded from 9.0.4 to 10.0.0.2.0. We decided to setup a separate voicemail pro server for a 2nd IP office system (at a different location), but the original on the same server, just upgraded the software. Both are running on Server 2008 R2. Both are having issues with the sorting, in terms of me changing the playback order and the end user not seeing a change.

 

[IPGuru]

Are these 2 systems isolated systems or are they connected Via SCN?


I recently had an issue with an VM Pro that simply would not switch to IP office mode from intuity mode, no Idea why, i suspect it is something to do with permissions & writing to the registry.

To be honest these days I would strongly recommend that VM Pro be installed as an application server unless using feature not available on the Linux platform.





Do things on the cheap & it will cost you dear

 

[Scotty_IT]

these systems are connected via SNC, with the vm pro running in intuity mode online over lan. We've never come across this issue until this upgrade. Currently the VM Pro is the only thing installed and running on the server.

 

[Westi]

You have 2 VmPro servers in the SCN?

here what the manual says about it

15.5.1 Centralized Voicemail Pro Server
Centralized Voicemail Pro uses a single voicemail server to provide voicemail services for all IP Offices in the Small
Community Network. Except for use of ContactStore, only the central IP Office hosting the voicemail server requires
licensing for Voicemail Pro operation and features.
15.5.2 Distributed Voicemail Server
For IP Office Release 6.0 and later, remote IP Offices in the Small Community Network can be associated with another
voicemail server in addition to the centralized voicemail server. The additional distributed server then provides all
voicemail services (except message storage and collection) for that IP Office. This requires the remote IP Office to have
licenses for voicemail operation and the features it requires.

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[IPGuru]

Scotty
As per your other thread
Ip offices in a SCN MUST use centralised/distributed VM. stand alone VM Pro servers are not supported.
I don't see how this would be causing your current issue but I would still recommend correctly configuring the VM for distributed operation on the Linux Application server platform (It is far easier to install & get working than the Windows Variant).


Do things on the cheap & it will cost you dear

 

[Scotty_IT]

not easier if you don't know anything about linux

so even the other 2 systems we have that use embedded voicemail need to be switched over to either centralized or distributed? this would require additional licensing correct? as well as changes to the auto attendant/call flows for those locations?

 

[snowman50]

No
Centralised voicemail creates a "Virtual Preferred licence" on the Other system that is set to Centralised.

Centralized Voicemail Pro uses a single voicemail server to provide voicemail services for all IP Offices in the Small
Community Network. Except for use of ContactStore, only the central IP Office hosting the voicemail server requires
licensing for Voicemail Pro operation and features.

 

[TomMills]

not easier if you don't know anything about linux "

Honestly it's fine. I don't know much about anything but the app server is a breeze.

APSS/ACIS/ACSS-SME
not arrogant, just succinct.

 

[IPGuru]

not easier if you don't know anything about linux

Actually Yes it is
The Linux application server Needs Zero Linux knowledge to install. in fact it needs LESS knowledge to install than the windows variant (especially when you need to setup IIS web & SMTP Services ), try it & I guarantee you will never look back.

Basic process
Boot from install DVD
answer 1/2 dozen question relating to the network setup (Ip address etc.)
specify a few passwords
wait until it finishes
web browse to the ip address specified & select the mode of operation (apps server or Full Server edition)
all admin is now done from a web browser interface.

No need to access the underlying operating system anywhere unless you really want to or are doing something really special.





Do things on the cheap & it will cost you dear

 

[Scotty_IT]

So I've been continuing to look at both the issues. The one issue seems to be an issue with voicemail not resetting itself until another voicemail is left, once that's done, it clears the light and all is good in the world. However the sorting still seems to be an issue. No matter what way i put the order, its stuck in FIFO for everything. and yet everything else works as expected, all the call flows for the AA, and reading when the voicemail boxes are accessed lasted, and what messages are currently in new/old/saved.... is this still something that should be expected with the setup i currently have, although its the wrong way?