NAM trouble - not configured?

[phoneauthority]

We have a client with a fiber NAM 4.1, connected to an MICS with 7.0XC software.

Ran for years on the 6.1 software, upgraded it to 7.0XC 4 months ago, and it ran fine for 4 months.

Today, customer had a major power outage - power off for an hour, and the UPS failed.

When power came back, NAM is posessed by the devil.

We have spent the day troubleshooting it, and this is what we have found.

- Once booted up, the NAM operates fine for 10 minutes or so, the auto attendant answers, people's voice mails work, etc.

- After about 10 minutes of functionality, the NAM stops behaving.

During the 10 minutes where it is operational, the Feature-916 check shows that all of the ports are "...." meaning that they are running fine.

After the 10 minutes, when the NAM stops working, the ports all show in F-916 as being "aaaa" meaning "connected to KSU but not configured for voice mail".

Anybody seen that before, and do you have a solution or an idea of where to from here ?

The customer wants functionality tomorrow morning, and it's almost midnight now. Help is appreciated.

Thanks in advance.

Dave
The Phone Authority
Portland, OR / Toronto CAN

 

[NorstarOption]

I would turn the NAM off. Reseat the cards and turn it back on again.

 

[phoneguy427]

Do you have an acd? Try shutting off set relocation if it is on.

 

[lugerlover]

go 1 step further get a can of air and remove cards from nam ,blow all dirt out, and power down ksu and reseat fiber card and patch ..make sure if u have a 2nd nam for acd that autoset is off and reboot in sequence...first ksu when ksu is functional then vm ..when vm is up then acd..if no acd let ksu come up then power up nam