Voicemail Pro Issues after migration from 8.1 to 9.1

[jhengel]

Hey all,

We migrated a 4 site SCN (Centralized Voicemail) from R8.1 to R9.1SP1 with an incremental upgrade to R9 in the middle of that process (no calls were ever made on the R9 system). After the upgrade to R9.1 the customer began experiencing issues with voicemail lights attached to users across the SCN whom are utilizing the HExtn source number. Lights were not always lighting properly and the number of voicemails showing on the first screen of visual voice were often times different from the actual number of voicemails inside the box. Dialing *17 and accessing voicemail seems much more reliable but customer not happy about having to do that (and they shouldn't have to). I know during the migration process from 8.1 up to 9.1 the lines were automatically changed from H323 lines to IP Office lines (everything appeared to happen properly from what we could tell). It is also important to note that we went from 8.1 to R9 to R9.1SP1 and when these problems cropped up we upgraded to R9.1SP3 thinking it may have been a firmware issue. I know R9.1SP4 is out now but I am not confident that would solve the issue.

We were also experiencing issues originally with voicemail pro "Accounts" folders not properly migrating when a user was renamed but renaming the user folder to username.old and restarting the voicemail pro service seemed to fix those issues.

Looking for guidance with the (Primarily) visual voicemail issues across the SCN. Customer has MPLS between locations and all traffic is trusted and properly being QoS'd.

 

[intrigrant]

I have no experience with ditributed VM on R9.1 but I do know that there is a lot wrong in the VMPro R9.1.any SP.
As VMPro always has been reliable it looks like Avaya moved the source code to the same programmers who made the IP Office firmware as buggy as it is.

 

[amriddle01]

Indeed, the one thing you could always rely on to work as it should was VM pro and you could often use it to circumvent system bugs, now thats no longer the case and that's a huge loss. As is the farce that is the new Help files, but that's another story

 

[jhengel]

I was able to make it out to this location to do further testing and clarification. This problem actually did exist prior to the migration from 8.1 when the customer presses the visual voicemail button, it takes about 5 minutes to list the number of Voicemail in a group mailbox that lives in another site over the SCN. Once that number finally populates, it is inaccurate. Because the number is showing wrong at this layer, the light is incorrectly lit on the phone. If you click on that specific group mailbox it shows the correct number of unread, unsaved and saved messages however when you press the button to play unread messages for example nothing happens.

Further, this hub site I was at today does not see any of the hunt groups built in the main system except for one. Exclude from Directory is not checked for any of the groups. I do not understand how it could see one group but not the other 19. This hub site does see all of the Group's in the other hubsites. If you dial *17 voicemail functions perfectly well.

 

[intrigrant]

The next excel matrix will be downstreamed as well as "most information is in the knowledge base" and "we are shortstaffed at the moment" which equals "Avaya has fired 60% of our collegues due to a reorganisation"....
I know, but it is so f*ing hard to find wile it is clearly presented in the excel matrix.

 

[jhengel]

With the idea that this issue has been around through the migration of three major releases, I am open to thoughts on where to turn. I had originally thought firmware but if this was happening in 8.1 and still exists through 9 onto 9.1 that seems drastically less likely.

 

[joe2938]

If you have Avaya IPOSS then open up a case with them and let them figure this out, I as well have same issues and do have an open case logged with Avaya on this, But do open a case with Avaya.

 

[liquidshokk]

Out of curiosity does the light come on correctly if visual voice is disabled? I'm experiencing a very similar issue and was going to disable visual voice as a temporary work around.

 

[jhengel]

That is unfortunately something I wouldn't be able to try for this company. They have several hundred users and they rely on VV pretty heavy. Local system groups seem to show accurately

 

[jhengel]

Avaya had provided a custom patch for this but the custom bug fix is now in 9.1.5

Will be testing the 9.1.5 shortly to see if it indeed fixed the issue there as well.

 

[NYSTECH]

I also have similar issue but with 9.0.5. they had me upgrade a 16 site SCN to latest release .9. I think and problem still exists. Still working with them on it

 

[jhengel]

Problem still in place after upgrade to R9.1.5 - back to Avaya we go.

There are a few different bugs affecting visual voicemail from what I have seen.