NEAX 2000IVS with bad memory

[rfcomm2k]

I have a customer with a NEAX 2000IVS that developed a problem about 7 years ago and was never fixed. Back then the customer was covered by a contract with a large telco which I will not name but for whom I worked. Contract covered labor only on this site, and when the problem was discovered the customer could not afford to replace hardware. Since then, I have left the employ of that company after they dropped almost all of their PBX customers because the CEO decided they did not want to be in the PBX business any more. I am now taking care of this customer as a self employed person.

The trouble is that any type of call forwarding cannot be set on the system any more. Either by dialing the access code or by using a button on the phone. All the phones started out forwarded to a vmail extension on another site, and that worked fine. But one day I received a complaint about a phone that was not forwarding, and I found that the forward had been cancelled, probably accidently by the user either dialing the cancel code or by pressing the button on the phone by mistake.

When I tried to set forward to vmail again, it failed. I get reorder tone whether I use the button on the phone or if I use the access code.

We have tried restarting the KSU by shutting down power, but that did not help. We would like to have someone from NEC get into the system and use the BAID tool to fix this problem, but the system is long past the EOL support date.

I am hoping that a former NEC employee that is familiar with this tool will see this post and offer some help.

 

[belevedere]

On the old IVS system you were limited to 96 call forwards off premisis. If you cancel one you might be able to set another up to the 96 limit. The way we got around it was to set one virtual to forward where you want, then forward the extensions to that virtual. Usually in a CCIS nwetwork.

 

[rfcomm2k]

There are only 17 extensions forwarded and only 32 total. No virtual extensions exist.

 

[belevedere]

I worked on this system since it's introduction and I am not aware of any BAID programming. Make sure that the class of service still allows setting call forwarding. If this is a US system, my first suggestion is to write down the IVR number from CMD F83. If your CPU is a CP-00/03/14/16 and you default the system the IVR number will be lost and it cannot be regenerated. CP-24/26 cards retained the IVR number. It can be re-input if you have it. If you have the old DOS MAT or an early version of MatWorX, get a copy of the database. You may have to try defaulting the CPU, test at default, then re-load your database (after re-typing the IVR number) to see if it is a bad CPU or corrupt database. The last time I found a corrupt database, it showed up in system speed dial memory as random hex code instead of phone numbers. I also had to reprogram by hand since the back up was corrupt. Note: after re-inputting the IVR number you must reset the system.

 

[OzzieGeorge]

What do you see in the display of the phone when you try to set a forward? One trap for the unwary is that if there is a call back set, you can't set a call forward and you will get restricted in the display.

 

[rfcomm2k]

Good info both of you. Ozzie, I will need to go back and look at the display when the error occurs. Will update here soon.

 

[belevedere]

I forgot about that trap, thanks Ozzie.
Look for an access code in CMD 200 set for A003 = callback cancel. Dial it several times since there may be up to 5 callbacks set.