I was searching about a couple of issues we've experienced with R11.0.4 SP1 and I'm starting to think we shouldn't be running this version in production.
First there's oddities with Voicemail - if the primary node gets restarted voicemail switches over to the secondary node. The challenge is that some number of phones stop accessoing voicemail properly - they seem to have not switched over to the second voicemail node - The Voicemail Light/Message Waiting Indicator's (MWI's) do switch on/off consistently. I haven't figured out a real way to consistently identify when a phone's ended up in this state, but a user cannot retrieve new voicemail messages, and visual voicemail shows "busy". Sometimes the phone's involved will "fix" themselves at some point later.
Second some administrative functions cause the web interface to hang. The number one that I can point at that always works is that editing a hunt group will cause the web UI to hang.
And then there's the issue that I've posted about elsewhere where a call that connects from one site to another site routing (E129 -> 500v2 -> 500v2 -> 9608 then transferred to another E129 will auto hang up after 35 seconds... every time - there's been a ticket open with Avaya on this issue since mid December).
Feels like switching from R10.1 up to R11.0 was a BAD idea.
First there's oddities with Voicemail - if the primary node gets restarted voicemail switches over to the secondary node. The challenge is that some number of phones stop accessoing voicemail properly - they seem to have not switched over to the second voicemail node - The Voicemail Light/Message Waiting Indicator's (MWI's) do switch on/off consistently. I haven't figured out a real way to consistently identify when a phone's ended up in this state, but a user cannot retrieve new voicemail messages, and visual voicemail shows "busy". Sometimes the phone's involved will "fix" themselves at some point later.
Second some administrative functions cause the web interface to hang. The number one that I can point at that always works is that editing a hunt group will cause the web UI to hang.
And then there's the issue that I've posted about elsewhere where a call that connects from one site to another site routing (E129 -> 500v2 -> 500v2 -> 9608 then transferred to another E129 will auto hang up after 35 seconds... every time - there's been a ticket open with Avaya on this issue since mid December).
Feels like switching from R10.1 up to R11.0 was a BAD idea.
