|
|
|
|
Joined: Apr 2009
Posts: 446
Member
|
|
Member
Joined: Apr 2009
Posts: 446 |
line was ok for 3 months, this week went on hold again, made loop timer changes will see what happens.
Gary S.
Gary Stevens
|
|
|
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.
|
|
|
|
Joined: Dec 2001
Posts: 352
Member
|
|
Member
Joined: Dec 2001
Posts: 352 |
I had a similar problem with a port on the DTIB going bad. One phone was having a problem 'talking' back to the KSU. It was almost as though it was at the distance limit length from the KSU. It didn't always update the display. It grabbed inactive lines and put them on hold, called other stations and kept them off hook. In this instance we could see what extension/port was causing the issue.
We ended up moving the extension to a different port and DTIB card, did 636 swap and the problem disappeared. We ended up pulling out the DTIB and replacing it.
If you are able to do a config when the line is on hold, see what phone ext put it on hold. You might find the rogue phone. Does it ever HOLD time out back to an operator station?
You might want to check voltages on some of the digital ports at the block. If they are not all in the same ball park, some ports on the DTIB card may be going bad.
Tip and ring, the work of the devil!
|
|
|
|
Forums84
Topics94,465
Posts639,682
Members49,828
| |
Most Online5,661
May 23rd, 2018
|
|
|
|
|
|
