NAM Co-resident Problems

[vcsltd]

We have installed a NAM c/w Voice Mail version 4.0.04e and ACD version 3.50.0038.
Sometimes, when the customer is performing some normal task, the Voice Mail Application will lockup and fail, leaving the customer without an AA until the NAM can be rebooted.
One such task was when a voice mail user attempted to copy a message from his own mailbox to someone elses. As soon as he pressed the button on his phone to copy, the Voice Mail Application locked up and failed.
Another instance was when the system administrator was setting up a mailbox with dialout access. As soon as the administrator told the mailbox it could use Pool 1, the system lockedup and failed.
We have found cross linked files by running "chkdsk" which are;
c:\st\stlog.out cross-linked on cluster 2515 and c:\st\sysdir.40 on the same cluster.

The 'not so funny' part is that Nortel is stating that they would prefer if we installed two separate NAMs instead of operating co-resident... which we know is crazy and incorrect. There are hundreds of co-resident NAMs operating in North America. Why should ours be special.

If anyone can help, please let me know.
Thanks in advance.

 

[jerryreeve]

I found out that more memory is better with the NAM. even though you may have the recomended memory for the applications you are using you may want to spring for 64mb instead of 32mb etc. etc. The NAM can do some wierd things and increasing memory can help. JerryReeve
Communications Systems Int'l
com-sys.com

 

[lowradiation]

When you install ACD on a co-resident NAM you should bring up Voice Mail first - F983 - config etc., then install the ACD application, then perform a F983 - 1 - REINSTALL.
This will prevent corruption in the voicemail 'st' data block.

 

[lowradiation]

I had what sounds like exactly the same thing happen about 18 months ago. The voicemail application would lock up doing various normal tasks. Rebooting the NAM would bring it back up, but on the 6th or 7th reboot both the ACD and voice mail applications failed to come up... Ended up getting a new NAM shipped, but didn't want the same thing to happen again. I found the above information on a Norstar troubleshooting website (now password protected -DOH!) Performed the REINSTALL command immediately after setting the channel allocation for each application in F915.
Then I redid the F983 -config. After doing this I have not had any trouble with the voice mail locking up. Now, I don't know if doing a REINSTALL will help once the corruption has happened. It will mean you'll have to redo the mailboxes and AA, but it may be worth a try in case it is the same thing and the whole NAM ends up crashing.

 

[vcsltd]

Well, we were able to solve this problem, but olny by holding Nortel to task.
After two months of struggling and reinstalling 6 times on new NAMs. we finally managed to get Nortel to agree to send us a second NAM at their cost. Now we have two NAMs operating on the MICS. The first one is running 8-channels of Voice Mail and the second one is running 8-channels of ACD (Cinphony 1)
I guess I am Bragging a little bit, but I am also notifying anyone interested that it is not a good idea to try to run co-resident appications on a NAM. Both Nortel and Cintech have stated the same thing now.
Thanks for eveyones help on this project.