Norstar Voicemail 4.0 freezes 1

[Uraby]

Hi everyone,

I have a Norstar voicemail 4.0 that periodically freezes (no one can access). We've run reports since the last time and the Port Usage Report doesn't show much activity but on the day it 'freezes' the report shows all ports were 100% busy. It isn't the same time of day that it happens. There was over 1000 minutes left for usage in the system. The only thing we have noticed is that on the same day we've had some noise on our backdoor lines. I would have thought if the lines were the problem then they would remain busy with the ports but when we notice the voicemail not working the backdoor lines ring no answer. Any suggestions or knowledge from someone that has had experience with this type of situation would be greatly appreciated!!

Oh, and we reported the noise problem to the company that supports our lines but they said it would be difficult to track when the noises don't remain on the lines.

Uraby

 

[telemarv]

You'll have to explain beter what you mean by freezing. Does the voice mail stop working or are the ports to the voice mail locked up? Ie when press F981 do you get a message that says "voice mail busy" or "Feature Inactive"? Is this a fibre or copper NAM?

 

[Uraby]

Hi Telemarv,

By freezing we mean users cannot access mailboxes - telephone displays show feature 981 and it just sits there. And incoming lines do not get answered by the Automated Attendant - they ring no answer or get answered by reception. We've always had to reboot by unplugging and plugging by in (the voicemail system that is). The Norstar system is a 4.1. I hope this helps you help me.

Thanks,

Uraby

 

[telemarv]

You need to call vendor

 

[exsmogger]

Check your voicemail version. Login to F983, then press 9 to display version. If it shows R4.0.04a you need to upgrade to at least R4.0.04c to fix the channels going to sleep problem.

Brian Cox

http://www.jandjcommunications.com

 

[rhowlett]

You can get a replacement HD to upgrade if you need to.

Have you tried going into F915? You might be able to tell it to reboot that way. I think there is some error logging in there also.

 

[Uraby]

Thanks everyone!

Apparently this problem has been occuring since the system was installed. It's unfortunate it wasn't taken care of years ago.

Uraby

 

[curlycord]

Default/Re-install the NAM and start from scrath is one option as it may have contracted a bug at or near day one.

Go into the OS and do a defrag might also help.

Check all connections are tight.

Do as exsmogger suggests.