How to configured Two Nams 1

[jr6674]

Hello everyone,
I know this post is the continuation of a previouse post I had put about a week, where I was advised to use two separete NAMs, one for voicemail and one for ACD,instead of just one NAM CO-resident with voicemail and ACD. Well I have to admit I have never done this before and I am having problems setting it up, both of the NAMs are conflicting with each other, both of them work fine when only one is running at a time , but when I run both at the same time they start to restart automatically, can some who has succesfully done this advised me on how to properly configured both of the NAMs, one for voicemail and one for ACD. Currently both of the NAMs are 4.1


Thanks

 

[NTL555]

Currently both of the NAMs are 4.1" as quoted above.

Both NAMs are conflicting because you can not have 2 voicemails on one system. You must have one Voicemail and one stand alone unit. You ordered the NAM incorrectly, talk to you distributor and request a stand alone NAM.

NTL555

 

[jr6674]

Thanks,
I will do that.

 

[luv2ski]

did you do this based on what was said on this forum or did you contact a vendor and cintech and try and resovle the issue????i have a bunch of co-res sites that with the help of nortel and cintech have resolved..nortel will support anything they sold for 5 years after retirement and any good vendor will try and fix before they just replace..if you found cross linked files there is a 40 step process to repair them

ski season has started

 

[jr6674]

Luv2ski,
all the co-residents NAMs that you have setup with voicemail and acd are all of them 4.1 for voicemail and cinphony 3.60.0027? because prior to upgrading the voicemail to 4.1 and acd cinphony II to 3.60.0027 we never had any problems dealing with the Nam, everything had work fine for about 5 years until we upgraded. Just want to compare apples to apples, thanks.

 

[luv2ski]

all were upgraded to the levels 4.1 nam 3.60.0027 acd no issues... is the nam on a network there is a virus that infected a bunch we maintained

ski season has started

 

[jr6674]

yes it is on a network were they access the ACD through Infocus, a Lan with about 120 pc's. So all system that you have upgraded to 4.1 and acd 3.60.0027, you had never had and issued with them.

Let me explain the problems that we are having.

1.cannot access voicemail features(ex.981,983,915 etc) for periods of 3 to 10 minutes(sometimes it does not come back at all), this was happenning once a week at first, but now it is happenning every day, all day long.

2.during this same period, if any calls from the outside come in, the AA does not pick, then suddenly everything comes back normal and works for some time and then does the same again.

3.I am not so sure about the ACD, all I know is people compalin about getting log out automatically all day, and then having to log back in to the acd.


Do you think this problems are really due to me upgrading to 4.1 and acd 3.60.0027? or do you think I may be facing hardware failures? and which hardware specific?(I was pretty sure it was the harddrive inside the Nam?) or could it be a virus, since I am on a network.

I had bought a harddrive to replace the one thats inside the nam, but then was advised to separete both the voicemail and acd, but since you said that you have had no problems running co-residents, I am not sure which way to go.Please advised and all opinions and personal experience are welcome.

 

[luv2ski]

what did vendor say....and what access version are you at on vm

ski season has started

 

[jr6674]

Well I was told by my vendor that it was most likely the harddrive, and now that I have done more research on what exactly happens when a file is cross linked within the harddrive of the Nam, I am going to say that my main issue right now is hardware failure due to the symptoms that I am getting

FYI
cross-linked file reference

The file allocation table (FAT) includes an entry for each cluster. Each cluster's entry includes either a code specifying that it is the last cluster in the file, or the number of the next cluster used by the file. Clusters can also be marked unusable, which CHKDSK reports as bad sectors.

Cross-linked files occur when two or more files are both marked as "owning" the same cluster. Usually, the last file updated is correct; the other is correct except for the cluster's worth that is part of the other file.

For example, suppose you have two files, each 512 bytes in size. Each file requires one cluster. If both files are marked as being located in cluster 5, then cluster 5 probably contains the file with the later date. You can confirm this by looking at it (if it's a data file) or running it (if it's a program).

How Are Cross-linked Files Fixed?
The only way to fix the FAT in this case is to delete BOTH files. When you delete the file, each cluster assigned to that file is marked "free to be used." If only one file is deleted, the cluster on which the cross-link occurred is marked unused, but the file system still shows that cluster as belonging to the "good" file. This causes another error (for example, CHKDSK may report a file allocation error, size adjusted or file allocation error, or file truncated). You also lose access to the file from the part that was stored in the beginning of the cross-linked cluster to the end of the file.

 

[luv2ski]

do you have cross linked files? there is a 39 step procedure to remedy it if you do

ski season has started

 

[jr6674]

Well I am not sure if I do or if I dont, what would the symptoms be if I do have cross linked files?and where can I get those 30 steps to fixing croos linked files.

Thanks

 

[FletcherP]

Run "chkdsk" on C: drive (ACD/NAM monitor)

This will come up with the cross link file problem if you have it.

 

[jr6674]

Well I just wanted to update this and let you'll know that I have setup the voicemail and ACD in the same Nam as co-resident and its been about two weeks and all the problems that I had with the other Nam are all gone, everything is working wonderful and better than ever.