I have an extension that goes offhook to line one, about every 15-20 minutes. I've replaced the 206 module, the phone, and the cable. This same extension is programmed to select CO's 10, 9, 8, 7, 6, 5, 4, 3, 2, 1 for auto line select. Has anyone seen this before?
What I would do is swap the cable to another port at the KSU that is not having the problem If that telephone still has the problem then you are looking at something environmental. If the station that it was swapped with starts acting up then look at the 206 (replaced) then look at the slot of the cab.
Richard S. McCranie
CoMatrix Southeast
richm@comatrix.com
The line eventually goes to the telco recording "...please hangup..." The extension is number 30 on module 3, which is a 206. If the extension is not plugged in, the port does not go offhook.
Did you try plugging the partner phone directly into the port......this would determine wether it is an equipment or wiring issue. I have seen some of the wierdest things. Such as a cust complained that every thursday his phone was dead and on Friday it was fine. Turns out there was a crack in the sheath in the wire and it was laying in a support beam. They would powerwash the place on Wed night and the water would lay in the support causing a short, by Friday the water would evaperate. I would try that to see what happens. Might be a bad phone as well, the damn switchhook sensors. Good luck.
I've had allot like that, too. Usually people will leave the mounting cord (because a desk or cube is in the way) and swap the phone ... when it was the cord the whole time.
Replaced the cabinet, and defaulted the processor then restored the database. Same offhook with line one. Corrupted database????? Could there be an action that causes an extension to go offhook with a line, intiated from another extension?
Hi alebe,
Try to default the processor again and manually program the system (simple, basic setup). Do this after hours and see if the system still acts up. You can restore the original program if the result is the same. I had a similar thing happen after an upgrade. It turned out to be a corrupted program. I was lucky and found the corrupted bits.
-Chris
Hi Chris,
Yeah, I'm going this Sunday to default and reprogram. The only thing about leaving the system in default with a basic program is the time frame for this trouble to recur. After replacing the cabinet, defaulting and restoring the database, it took a week or more for it to happen again (unless the customer held off from calling me).
I will look for erroneous data in programming before defaulting and reprogramming. And I may leave a basic program in for a day since Monday is a Holiday and they are closed. I will post next week.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.