web statisticsweb stats

Business Phone Systems

Previous Thread
Next Thread
Print Thread
Rate Thread
Page 1 of 4 1 2 3 4
#42393 05/25/10 02:03 AM
Joined: May 2010
Posts: 25
Member
Member
Offline
Joined: May 2010
Posts: 25
Has anyone come across this:

DX120 with a PRI that has intermittent all busy or no ring at all for inbound callers. Outbound calls are fine.
This problem started after upgrade to F22/F.07. Tech support had me re-install F22 and install a new F.07 chip. After 6 days, problem started again.

Edit: This system was working fine for 2 years prior to the upgrade.

Thanks.

Atcom VoIP Phones
VoIP Demo

Best VoIP Phones Canada


Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.

#42394 05/25/10 02:44 AM
Joined: Feb 2007
Posts: 903
Retired Moderator
*****
Retired Moderator
*****
Joined: Feb 2007
Posts: 903
You might try putting F20 and your old firmware chip back in. I seriously doubt this is the problem though. Did you download the database and upload it when you updated the software? It's possible it's corrupted. Secondly I've never seen a DX PRI work for a few days then fail. I'm a bit more inclined to think something may have happened to the cabinet versus a fault in F22 or the PRI card if in fact it's the DX-120. To date EVERY single PRI issue I've ever seen with the DX-120 has been the LEC except for one cabinet that had a faulty clocking source and another that had a bad memory segment. We have better than 60 PRI installs.

I would go ahead and and put your spare cabinet and PRI card in and see what happens. If it still occurs then you pretty much know where the trouble lies. Check your distributor for PRI card prices. I went ahead and put another six on my shelf.

#42395 05/25/10 04:02 AM
Joined: May 2010
Posts: 25
Member
Member
Offline
Joined: May 2010
Posts: 25
Yes...I downloaded then uploaded after cold start. I was thinking corrupt database as well, because this was working fine for 2 years. The carrier did do extensive testing for about 4 days and came up clean. On the clocking...the DX is supposed to be the slave, correct?

Unfortunately, I had left the telecom business to take a job offer with a client of mine for about 2 years...I'm now back in telecom but sold off all my spare everything!!

#42396 05/25/10 04:13 AM
Joined: May 2010
Posts: 25
Member
Member
Offline
Joined: May 2010
Posts: 25
Question...
Could I default the system, upload the database prior to the f22 upgrade, then do the upgrade to f22 while still leaving in the f.07 PRI chip in place? I no linger have the .05 chip. Or, should I just build the database from scratch?

#42397 05/25/10 04:17 AM
Joined: May 2010
Posts: 25
Member
Member
Offline
Joined: May 2010
Posts: 25
One other item...

When I had originally upgraded the system, it was to f20. But, on the advise from a Vertical tech, I had the installed f.07 chip at that time. I later upgrade to f22.

#42398 05/25/10 12:53 PM
Joined: Feb 2007
Posts: 903
Retired Moderator
*****
Retired Moderator
*****
Joined: Feb 2007
Posts: 903
Reinitialize the system and reprogram. F22 with F07 has been very stable.

#42399 05/25/10 01:09 PM
Joined: May 2010
Posts: 25
Member
Member
Offline
Joined: May 2010
Posts: 25
Yep...going to stare and compare. Thanks!!

#42400 06/03/10 12:13 PM
Joined: May 2010
Posts: 25
Member
Member
Offline
Joined: May 2010
Posts: 25
Ok, so that didn't work...hand packed data base, same thing. Now tech support wants me to downgrade to f19 and the f.03 PRI chip and push the old f17 database in. Sounds like throwing darts for a solution.

Question: Would having the co lines Ans. Pos. for the PRI pointing to ext. 101 WHILE using DID's that point to UCD or user ext's cause my problem? It worked fine this way for the first 2 years, but after the upgrade to F22/F07 I get the failure. Could the F22/F07 not like this conflict

Tech support thinks the carriers equipment doesn't like the F07 and/or F22.

#42401 06/04/10 08:10 AM
Joined: Feb 2007
Posts: 903
Retired Moderator
*****
Retired Moderator
*****
Joined: Feb 2007
Posts: 903
I think tech support is nuts. If it worked fine with F20 and F.03 then why do they say F19?

Did you reload F20 with F03 like it was before the problems? If so and it still isn't working then replace the cabinet with a different one with F20 and F03. If it still doesn't work then something changed at the carrier. It is "slightly" possible the cabinet went wacko. I've only seen it once but something happened to clocking on one of my cabinets causing all kinds of erratic operation.

As far as the CO lines pointing to 101 it "might" be possible this is causing an issue. Regardless I would exclusively use the translate table for incoming ringing. It's kind of why it's there.

Frankly with the issues showing up after six days or so I'm leaning to errors on the circuit and not the DX. Have you had the carrier check for slips, CRC errors, etc? Is it a fractional PRI? I've had faulty Adtran or Cisco interfaces cause whacked out problems with the PRI. Is it possible you were on an old school C.O. phone switch like a #5ESS and they switched it over to a soft switch? I've had that happen to me too.

Tough deal to really isolate if you don't have spares.

#42402 06/04/10 11:25 AM
Joined: May 2010
Posts: 25
Member
Member
Offline
Joined: May 2010
Posts: 25
It was on f17/f.03 when it was stable. I had a problem with the modem not answering when I was told I needed to upgrade to resolve the problem. Now that f17 cpm software is not available, they wanted me to go with f19/f03.

At this point I've not downgraded anything. Only gone from f17/f03 to f20/f07 then f22 only (kept same f07 in PRI) then a reload of f22 and a new f07 chip then cold start and new database...all on the advise of tech support.

Carrier has checked everything. Not a fractional PRI, have a smart jack 6' from my switch into a adtran, then the DX. I've pulled the adtran out and still had the failure.

I did remove the ans. pos. for the PRI trunks yesterday...now we wait.
I'm going to get the carrier involved again and check what they're using on their side.

I agree...a pain without spares.

One other thing...Tech support is now saying the f22/f07 was developed only to address the problem the DX/PRI was having with soft switches. In other words, I really didn't need to upgrade a damn thing in the first place.

Page 1 of 4 1 2 3 4

Link Copied to Clipboard
Newest Topics
Change desi-less label from a phone
by Yoda - 02/26/25 06:26 PM
SBX IP320
by johnp - 02/18/25 03:02 PM
SMT-i5210 SOFTWARE
by NateBates - 02/14/25 02:47 PM
Bogen amp keeps tripping reset
by Yoda - 02/12/25 12:40 PM
Forum Statistics
Forums84
Topics94,490
Posts639,857
Members49,833
Most Online5,661
May 23rd, 2018
Newest Members
hayl, kosia, LJetronic, CLKAHCK, B. Vignesh
49,833 Registered Users
Top Posters(30 Days)
dexman 11
Toner 9
pvj 5
Yoda 5
dans 4
Who's Online Now
2 members (BobRobert, Toner), 696 guests, and 162 robots.
Key: Admin, Global Mod, Mod
Contact Us | Sponsored by Atcom: One of the best VoIP Phone Canada Suppliers for your business telephone system!| Terms of Service

Sundance Communications is not affiliated with any of the above manufacturers. Sundance Phone System Forums - VOIP & Cloud Phone Help
©Copyright Sundance Communications 1998 - 2025
Powered by UBB.threads™ PHP Forum Software 8.0.0