|
Joined: Dec 2006
Posts: 108
Member
|
Member
Joined: Dec 2006
Posts: 108 |
We have an IP Office system that is about 3 years old. Since it's install it has had intermitent problems with disconnect supervision.
It happens most times on an outgoing call but can also happen when the attendant has mutiple incomming lines ringing at the same time and a caller hangs up without being answered.
Most times I will find a line showing on the monitor as being in a DISC but still showing time runing. It will hang there forever, pulling the bridging clips should provide a disconnect but it does not. When called from the outside the hung line sounds like it is ringing but it is not in the IP Office (it can be answered with a buttset at the terminal)
Times when it hangs on mutiple incoming calls the attendants station will continue to ring and can only be stoped by rebooting the system.
Tech support has never been able to duplicate the condition and wants us to leave it hung till they respond. Wish I could do that but we are a Fire Department Dispatch office and I cannot have an incoming line disabled for any length of time.
This started out happening about once a month when it was first installed and has been geting worse (3 times this week)
Nothing in the system has changed since the install, the Dispatch position (attendant) does not even have Voice Mail (VM Pro). It's a simple system.
Any Ideas, is this a common IP Office problem?
|
|
|
|
Joined: Feb 2007
Posts: 2,473
Member
|
Member
Joined: Feb 2007
Posts: 2,473 |
Usually it is not a telephone system problem. Most of the time it is Provider(Verizon) or IP lines. Call telephone company and let them know.
|
|
|
|
Joined: Dec 2006
Posts: 108
Member
|
Member
Joined: Dec 2006
Posts: 108 |
It would look like a verizon disconnect problem on the surface but.
I have verifyed that the loop current drops to 0 for about 500ms when the outside caller hangs up first. Have also pulled the bridging clips on a hung line to simulate a verizon disconnect and the IP Office ignores it. The disconnect time in IP Office is set at 200ms and has been tryed at lower settings without any change.
|
|
|
|
Joined: Feb 2007
Posts: 2,473
Member
|
Member
Joined: Feb 2007
Posts: 2,473 |
Go to Lines set up in the Manager and make sure that Line Disconnect Clear option is clicked.
|
|
|
|
Joined: Dec 2006
Posts: 108
Member
|
Member
Joined: Dec 2006
Posts: 108 |
Disconnect clear is checked. What a fun day this has been, 50 to 60mph winds the FD has had over 150 calls today and I have rebooted this thing 4 times to unlock a ringing line.
|
|
|
|
Joined: Jan 2009
Posts: 79
Member
|
Member
Joined: Jan 2009
Posts: 79 |
I suggest you look into you trunk wiring from dmarc to ip office. Replace that and make sure you dont have other devices using that line. You have a short somewhere.
|
|
|
|
Joined: Dec 2006
Posts: 108
Member
|
Member
Joined: Dec 2006
Posts: 108 |
Wiring from the Verizon demarc to the system consists of 3 year old 25 pair straight from the demarc to the patch panel located in the IP Office rack. It's in much better shape than Verizon's outside plant.
I hate the term SHORT, If I had a short tip to ring I would have a dead line. If tip or ring was shorted to ground or another pair I would have a hum.
I do not see this as a line problem as when it hangs you can pull the bridging clips (should look like a disconnect to IP Office) and the line remains hung
|
|
|
|
Joined: Jul 2001
Posts: 3,347 Likes: 10
Moderator-Avaya-Lucent, Antique Tele
|
Moderator-Avaya-Lucent, Antique Tele
Joined: Jul 2001
Posts: 3,347 Likes: 10 |
It's not a common problem. Who is the Business Partner that you work with? What is the equipment, the releases, the firmware version you are running? Have you opened a ticket with Avaya (or Catalyst or Jenne)? Have you changed the Analog options on the lines? Is it always the same line? Have you frogged the lines? Have you swapped hardware?
|
|
|
|
Joined: Nov 2009
Posts: 21
Member
|
Member
Joined: Nov 2009
Posts: 21 |
What is the current release the IPO is currently ON, I faced this issue when the system was ON 3.XX release and was able to fix it in 4.X release...
Check the Hardware where the trunk lines gets terminated and the trunk configuration settings if it is an PSTN line..
Try to upgrade the server to latest release if you are on a very older release...
|
|
|
|
Joined: Jan 2009
Posts: 79
Member
|
Member
Joined: Jan 2009
Posts: 79 |
Trunk might be crossed with another trunk. Try CSS's solution as step 1. Throw trunk on another feed pair. Replace line cord. Then if you have a problem bother Verizon about disconnect supervision. Call us we are in NY if you need proffesional help.
|
|
|
Forums84
Topics94,494
Posts639,872
Members49,836
|
Most Online5,661 May 23rd, 2018
|
|
|
|