Issue with Subscribers mailbox

[usmamo]

Hello,

I have a subscriber who's voicemail recently stopped working and I'm having troubles finding a solution. When you dial the user directly it gets to MM and just plays the default welcome message "Welcome to Avaya messaging please enter the # of the person you are calling or press * for the company directory" instead of connecting and playing his greeting.

I looked to OHV as it's helped me with similar issues in the past, but I'm getting the following error and am unsure what to do next.

OHV Error: ERROR NT significant event with ID '3221227185' was reported with strings '17974\nUMOBJECTGUID=65A80408F92B11E28203000423D43EE3,OU=PEOPLE,DC=AVAYA || UMOBJECTGUID=A6E7FA5C94F411DF98DD000423D43EE3,OU=PEOPLE,DC=AVAYA\n'.

We have 2 MAS servers connect with the MSS running MM 5.6.1

Any help would be greatly appreciated,

MAMO

 

[texeric]

I didn't know there was a 5.6 version of MM. In any case if you look at the application event log of the MAS that took that call you referenced in your OHV, it will probably say that number matches to multiple mailboxes and it doesn't know what mailbox to answer the call with. Make sure it isn't occurring on both of your MAS servers. If it is occurring on both MAS servers then the results will be consistent no matter which MAS took the call. If it is only occuring on one MAS then 50% (depending on how your integration is setup) of the calls will have this issue and 50% will not.

You probably need to have your FEDB rebuilt/resynced on the MAS where this is occurring. Usually if I do that, I try to do it on every MAS in the system. That way I know each MAS is up to date with the same information.

 

[kepetersen]

It sounds like the caller is coming through the auto-attendant. Is the number that is calling sent to the pilot number of voicemail or could this be a caller application? If so, have there been changes to the Association table for the Caller Application Editor?

 

[KenMeans]

The Event above indicates that there is indeed a duplicate entry in the FEDB for that number as it gives 2 GIUD numbers.

As Texeric said the only way to fix that is to rebuild the FEDB.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)