sundance-communications.com/forum Forums TDM Business Telephone Systems Comdial Telephones & Systems DX120 PRI problem

10 days with no failure thus far.

So at this point you're running F20 with the F05 chip?

Justin

Yes. F20 F05 and no failure with the PRI. However, the VM is again not responding randomly. They have to reboot it to get it back online. This problem vertical tech support told me was a hardware failure issue. This 'hardware failure'didn't happen the entire time we were running the F22 F07 combo, but then the switch was being rebooted often (once a week or more)to correct the PRI.

After looking back through my email on this issue, it does appear that the PRI problem started within 2 week after upgrading to the F22/F07. It went over 3 months with no failure when we upgraded software to f20/f07 as per vertical support to correct the VM issue. It was after vertical told me to uprgade the cpm to F22 to further address the VM issue when the PRI first failed.

Have you replaced the dx80.hex file (if it's a 7271C) on the vmail?

As far as I know F20 and F22 are identical except for some minor PRI tweaks. It sounds to me more and more like there's some kind of cabinet issue. There's a chance the cabinet has a bad memory segment or the clocking circuit is faulty.

Yes. I replaced the Hex file when we went to the F22/F07. VM stopped answering the next morning. Vertical support had me remove it (the hex file) and replace the original hex and cited the problem as hardware failure due to a code in the error log.

I thought for sure it was a cabinet problem too. But since the F20/F05 is in it, no failure on the PRI going on the 3rd week now. Before, it wouldn't make it 6 days before failing.

Ok...it's been a year with no PRI issues. The CPM crashed last week and we replaced KSU1 and the PRI card.
Everything came up fine with no problems...until today. Again, calling in we get nothing...no ring...no busy...just dead air. HOWEVER, if I call in and get dead air and make a second call, it rings in fine. If the first channel is busy, the rest work fine.

HELP!!! I don't think I want to waste time calling tech support because last time they did nothing to help.

Card is programmed ESF B8ZF (manual says to keep at SF but I believe the carrier required ESF)

A couple things...
This new system is F22 with 07 on the PRI. The same combination that failed on the old system. I uploaded the saved database from the f20/05 that was stable for the past year.

I have 2 common denominators in this problem with f22/07...
The carrier and the CSU. The carrier is telepacific and the CSU is an adtran ACE.

Adtran claims their equipment can not cause this issue.
Seem obvious at this point something downstream from the DX doesn't like the F22/07...6 days after working fine!!!

new info...
What is causing the failure this time is...

Call to a fax via DID. Fax doesn't answer, call goes to VM. If I press 0 for operator, my call goes to modem or fax tone. Hang up, call back and get dead air...the first channel is now locked up. Reset switch and all is fine.
This time, this is what the issue is as customer complained that fax number was not ringing to fax. I called in last night on the fax line, got VM, hit 0, got fax/modem tone, hung up, called back and got dead air.

Just need to find where the call is going when i press 0 from VM that gives me tone!!

Found the problem...
In a word, HACKED!!

Someone had place a phone number, 91800XXXX in box 888 (my press 0 box)where we had ext. 101. Also, they had created another box (699)with that same number in the same field. When you call the number you get ATT.
Apparently the 9 at the beginning of the number causes the lockup with F22/F07 but no issue with F20/F05. Like I mentioned before, if you pressed 0 from VM you get this DTMF tone (not modem) and then callers would get dead air unless someone was already calling into the PRI, channel 1.

Resetting just the CSU clears the problem for 1 or 2 calls, then it will lockup again. Resetting the KSU clears the problem with no failure after.

Since no complaints about pressing 0 for the operator were ever reported to me or to my customer, I'd never dreamed that pressing 0 has been the trouble all along!!