atcomsystems.ca/forum Forums TDM Business Telephone Systems Panasonic Telephones & Systems 1232 Caller ID - now answer time related

Okay... slightly new twist on a Caller ID problem I've been chasing. The problem is actually related to when the 1232 recognizes the incoming call. On lines 2 through 8 the 1232 recognizes an incoming call on the 1st or 2nd ring every time. On Line 1, it is very random (doesn't matter what CO port it is in) and the 1232 recognizes the call on the 2nd to 4th ring. Here are the measurements I got Friday:

Lines 2 thru 8 = 78ma loop current (all work fine)
Line 1 = 49ma loop current

Ring voltage on all 8 lines is about 92V

My perceived CID problem was actually related to when the 1232 recognizes the call. If it shows up on the 2nd ring, I have CID... any ring after that, I lose the CID string obviously.

Any thoughts? Naturally, Qwest says it is a CPE problem...

Thanks,
JJJ

I'dd put a buttset accross line one and listen if caller id fsk squeal comes in between the first and second ring every time if it doesn't
it wont work right and i'dd point the finger @ quest btw 24-28 ma is what panasonic
would like to see.

CID "squeal" is in between the 1st and 2nd rings every time.

I'm debating on what to do about the loop current. The seven lines that are at 78ma have worked fine for two years. It's the "low" one at 49ma that is giving me grief... perhaps unrelated, but Qwest claims their spec is anything above 23ma and below 90ma... They also have no suggestions as to why the 1232 won't recognize ringing on Line 1 with any regularity. This is irrespective of which CO port I have it into...

Color me baffled... I'm about ready to order up another line and, assuming it does not exhibit the same problem, simply disconnect the first and have the phone number changed on the new line!

Thanks
JJJ

is there a alarm jack on the line ahead of
the equipment?

No alarm... straight from the DMARC to me... I'm going to get access to the telco closet tomorrow and do some testing from the DMARC and see what I get. I can't imagine it's a pair problem up from there, but you never know.

Thx
JJJ

who knows just being tiped over could possibly cause problems

JJJ: You don't happen to be using a solid-state protection device on the lines are you? I had something similar occur on my KX-TD because I was using LED bridging clips so I could see line in use indication at the blocks. They messed up the caller ID. Also, a defective solid-state protector can have the same effect. Just an idea.

Nothing but copper between the DMARC and the 1232... Hmmm... I wonder if something has possibly been bridged across this line (or even half of it) at the DMARC? At the very least, I'm going to try a different house pair and see what happens. I can't get back there now until Friday, but I'll keep you guys posted on what I find... if anything.

Thanks for the suggestions
JJJ

Well... I managed to sneak back over today. The DSL was removed from the line in question last night so I was just curious. Amazingly, the 1232 now recognizes incoming calls on the 1st ring and CID has returned as expected. I'll be bum-fuzzled (technical term) if I can explain it, but all seems well now... go figure. I suppose the DSL signal was having some sort of effect on the 1232...

Again, thanks for all of the suggestions and help!

JJJ