sundance-communications.com/forum Forums TDM Business Telephone Systems Panasonic Telephones & Systems 624 & 1232-Loosing Talk Battery

Telephone System: 2---KX-TA624-3 w/ 7030 phones
1---KX-TA1232 w/ 7030 & 7730 phs.
I have 2 customers with KX-TA624-3 each & 1 customer with a KX-TA1232. They are all served by the same ATT central office.( same town )
One of the 624 & the 1232 are mainly on feeder-1..fiber PainGain Systems w/ 1000 ft. of feeder-2 copper ca.prs. and the other 624 is on straight copper ca.prs.( app. 1 mile fr. co. )
My customers are all complainting of loosing the communication @ times ( not on all calls , maybe 5 % of call traffic ) with their customers. This happens on all lines, incoming or outgoing calls.
The talk battery & caller is lost for app. 2 seconds & return after the 2 seconds.
ATT has tested all of the lines and they say all lines are testing good. I can't seem to find out what could be causing this common problem!!!
I have changed out KSU, Cards, Modular connections, phones,cables, cords,etc...
I don't thing I have a Panasonic problem here. Does anyone have any suggestions? Please >>>HELP!!..tks.........

Inadvertent call waiting assigned by screwed up co translations? How's that for a WAG? I gotta know what the cure is on this one! 'Course if it's a C.O. problem, when they find and fix it, they'll deny it. John

It is obviously a carrier issue, but like John said, they will deny it, especially ATT. They never do anything wrong.

It's about high time that the carriers start paying for a tech to sit there all day and monitor these problems like they expect us to do.

Two different systems, different addresses, same carrier and CO switch. Seems like a no brainer to me. Stick to your guns with them, bill the customer with a "gentleman's" invoice and if they get reimbursed by the carrier, you might get paid.

Still, keep track of names of all parties involved and take plenty of notes. You will need them, if for no other reason than to get this problem fixed. Worry about getting paid later. This will be greatly appreciated.

We have a customer that has a 624. Sometimes the customer picks up the phone and there is someone on the line that just called in. The phone never rang. We put a sl phone before the ksu, and sometimes the sl phone rings but not the ksu. We changed out the ksu, same problem. We changed the ksu a 3rd time, same problem. Customer thinks it's still the ksu.

That close to the CO it could very well be high loop current.
Maybe the pairs aren't loaded properly.
you can try loop current regulators from Sandman.
https://www.sandman.com/loopcur.html
MrG

The opposite may be true, Marginal ring voltage. It has happened to me more than once. You'll probably have an area supervisor out there before it gets fixed, if thats the problem. Installer hears the 'putter' on his buttset and says 'it's good', but half the time it won't ring a plain 'ol 2500 set! Remember, The c.o. should be able to ring at least 3 plain old 2500 sets on the line, day, nite, weekend, weekday, anytime. If it can't, treatment for distance, or repair is required. The LEC's DO have standards they have to meet. If all else fails, your P.U.C. (or whatever it is in your state) is the last resort. Some are useful, others, leave off the 'ful'. John

Or, especially if it is Northern Telecom DMS C. O., a bad line card. NOT TOO Unusual. And SBC,nee AT&T, will deny it to the very end.

KLD

I thank you all for your help. I will keep you posted , as to what I find.

Are these lines suplied by the rboc or are they supplied by a different carrier (for example SBC/ATT of XO???). If they are a different carrier that bring service to a co-lo cage and then to your prem, It has all the systems of a dirty high cap facility. Basically the carrier brings the service from their switch on a series of t1's and then breaks them down into copper (GR 303). Most of the time unless you get a decent tech they will just test the copper loop and never look at the facilities, well untill it either goes down hard or they strat getting multiple complaints. To me this sounds like a co issue