Constant ringing on line 2 1

[rpmcomm]

I have a Partner II module with two 206's attached and VM.

Plugged into a surge protector.

Yesterday the %&^*$ in the lot next to our office managed to dig up the power lines with a backhoe, cutting off power to an entire complex. He was fine, but I was hoping he would get a little bit of a jolt out of the deal.

Once power was restored, line 2 started phantom ringing on all extensions like there was an incoming call. Rebooting didn't do the trick. Unplugging line 2 from the 206 module stops the ringing, but swapping line 2 and any other line still results in line 2 ringing constantly. In other words I've pretty much narrowed down the problem to line 2 on the phone system, no matter what is plugged into it.

I removed the VM module and that didn't help at all, which leads me to the 206 modules or the main processor.

Any ideas for a fix? All lines 1-4 are used.

Thanks in advance.

 

[skip555]

If Im understanding you if you unplug the co line from two it stops ?

if you swap the lines from the co 2 to 4 does 4 now start or does it stay on 2 ?

sounds like a telco issue if I understand correctley .

to check the system

swap the 206 modules , if line 4 now starts ringing then its the 206 , if it stays at line two then its the processor

 

[rpmcomm]

Yes, if I unplug the telco line from the 206 module (was in port 2), the ringing stops but only after that particular call cycles through.

UPDATED INFO:
If I swap the suspect telco line from port 2 with another telco line (say, the one plugged into port 1), port 2 goes completely dead (very odd that it doesn't constant ring), but port 1 works fine. Thus, when plugged into a known good port all telco lines seem to be working properly. So from my view port 2 seems to have a problem.

Putting all telco lines back to their original ports results in the constant ringing once again on port 2's line on all extensions.

I will try swapping the 206's this evening when phone traffic is minimal. I assume this will tell me if the 206 is bad or the partner processor is bad?

 

[TouchToneTommy]

I've seen the problem in the past, it's a bad CO port on the 206 module.

Do you have any spare CO ports? Move line 2 to another port, then use #301 to remove CO2 from the phones, and reassign the new CO in its place. Don't forget to add the line to the Auto Attendant in #206-7

 

[rpmcomm]

Ah the bad news I was hoping not to get. Thanks for the help. I will likely just buy a new 206 module, as all ports are being used.

If I swap the old 206 with a newer one in the same position in the box, do I still need to reprogram or will the processor not notice the difference?

 

[BigWill]

It sounds like a bad 206 module to me also. I had one unique situation where a tech didn't do a system erase before installing a new system and the corruption that resulted removed my ability to change the ringing on that line until I used #301 to remove and readd that line to the phones manually. If that "jolt" corrupted the software affiliated with line 2 and didn't necessarily break the module you could try to unassign and reassign it.