NAM 4.0 "Invalid Extension" w/MICS 4.1

[daveybc]

I have a client with a MICS 4.1 rel.1 ram cartridge as well using the older caller ID cards, working with a NAM V2G 4.0 fiber voicemail using standard AA with # for match both directory, 4 digit DN's. THe customer is complaining about alot of people unable to enter extensions as well spell the name after pushing #. The "you have entered an invalid extension" promt apparently comes up. Of coarse I havn't been able to recreate the problem. Since the problem has been reported I have tried. Resetting, reseat the card off the mother board backup and reinstalling. Still problems. As well swapping the entire unit with a known working one from my shelf. The one I put in off the shelf was a fiber NAM V3G w/4.0. I copied from disk all the menu and mailbox's from te previous system. With in a day more complaints. So we did a reinstall, thinking something bad was copied over. As the system was being reprogrammed the client noticed many of the mailboxes she couldn't add. Turned out many of them wern't deleted during the reinstall "mailbox allready exist". Rather than reinstalling again and having to to record the menu we just left it. Still problems being reported and I feel a little stumped. Should I try to reinstall again, did something go wrong with my reinstall!! The mailboxes left behind seems odd. Wouldn't want to order a version 4.1 hardrive and still have problems. Any ideas. Thanks

 

[thebiggerhalf]

Had this exact same problem. A nortel factory tech told me it is a sequencing problem between the MICS and the NAMs. I changed the customers voice mial to a CAll Pilot 150 and the problem disappeared.

 

[daveybc]

I replaced the NAM with a Call Pilot 150 and have not heared of any problems for 2 weeks. Excellent!!

 

[socalnorteltech]

I had a similar problem with a customer with basically the same hardware as your customer. I solved the problem by clearing the NAM and starting with a fresh system. First, I cleared their existing NAM and then reloaded their data. Problem continued. Then I replaced their existing NAM with a known working NAM, loaded their data, problem continued. Reinstalled their existing NAM cleared of all data and programmed from scratch. Almost a year now and not a single problem.