NCFW on ACD

[omarrj]

I wonder if anyone has had this problem, I have 3 mer-1 switches 1 op-81 and 2 op 11's all are running release
23.35 software. At one time or another throughout the last 3 months the ncfw on acd ques has stopped working and only an ini could fix it. I was reading release note on rls 25.40
and there is a patch for this problem, but I was wondering if rlse 23 had a patch also.It seems if rls 25.40 needs a patch rlse 23 should to.
Any help would be appreciated
Also anyone know where I can check what patches are available, my vendor always says there is none

 

[Sennback]

AS you can see I am another vendor..and I agree there is no patches for 23.35 that in any way correct any problems with ncfw.

You didn't say what processortype your machine has but I guess these kind of problems is basicly the same.

What to do then?
Well, it's not normal to have this kind of problems.
S0 - do they have the same night number? any problems there?
Do you actually use the ncfw parameter or nacd night tables?

Do you have the most recent patch pakages for your solution?

You have to be a vendor to have access to the Nortel patch library.

 

[Avaya911PLM]

Just a quick comment about patches. If patch is written for one release, this is no indication if it is written for another relese or not.

Some bugs creep in in later versions, that don't exist in previous versions, some things in one releasse are fixed inthe next, some are never fixed.

If a patch is written for a particular problem, it gets a PRS number assigned to it, and that PRS stays with the problem, regarless of the release. There are a few PRS's that are closed and when the problem is found again later a new PRS may be opened. In this case there *may* be a different patch number, but usually the patch numbers stay with the problem regardless of the release.

So, to make a longer story short, if you find a patch for a later release, chances are if the problem exists in an earlier release, the patch can be found under the same MPLR number.

If it doesn't exist for the earlier release, then one of the following has happened:

1.) You are the first to find it in that release
2.) The problem may be under a different patch number if the cause is different, even though the effect is the same

2 cents of info for those interested......... --
Fletch

http://PBXTech.Net