Help with Avaya Aura Messaging v6

[heathersuzanne]

Hi everyone!

If anyone can help me please let me know.

As of yesterday afternoon, our Aura Messaging Server started acting up - it will not light message lights or allow any of our global users to Delete voicemails. When we access the system and put in our password credentials we get a message stating that Some features may not be available at this time. If we listen to a voicemail and try to delete it, we hear the message that the message delete feature is temporarily unavailable, and that we should contact the administrator. We hae been up all night with Avaya and they cannot figure it out, so I was wondering if anyone has seen this before and had any tips for me. Avaya is leaning toward an issue with IMAP and SMNP but they dont sound sure....

Any advice appreciated.

We are version 6 with all the latest service packs, running a message store too. We have CM 5.2.

Thanks!

 

[redphone]

I ran into the same issue on my first install of Aura Messaging. Found out that the IMAP port was disabled by default. I am sure Avaya checked this first, but you never know. Under System Ports and Access, make sure IMAP4 Port is enabled.

 

[heathersuzanne]

Hello,

Thank you for responding.

Yes, this was checked and it is enabled.

Over the weekend Avaya was able to get it workign again but never told us what was wrong, and now thismorning it is failing again. Now the issue is that the system will not record anything - messages, names, greetings, etc. We dont get the message that 'features may not be available' anymore, but still, this system is not working properly and I'm wondering why its keeps going in and out of service. This is the 3rd time since last wednesday. Each time avaya says they fix it, and then hours later its broken again.

Any advice is appreciated.

 

[heathersuzanne]

Okay, we found our issue and I wanted to share it with everyone, in case it happens to you!

Aura Messaging is not quite 'ready' for primetime as far as I'm concerned, if you require multiple language packs. The reason for our outage was the language packs that our BP installed back in August. The AM server can only support up to 3 languages! The fix will be (from what I hear) in release 6.2.

Dissapointing since we only agreed to go to this server if it was capable of handling all our language requirements for a global deployment with one server. But hopefully the fix will come soon. Till then, I guess everyone has to speak English...

Hope you can avoid it!

Heather