divyeshpatel
Vendor
Hi Guys.
We've got an Avaya IPO500 with 70 x IP Extensions. The kit also has 1 x PRI30 and an 8-port analogue extension card with fax machines plugged into all the extensions. 3 of the analogue ports seem to have developed a fault recently whereby the fax machines would not release the line. I initially thought that this may be due to faulty devices, however it seems like the extension ports are to blame.
We've replaced one of the extensions with a new fax machine and the fault still remains. Re-patching other devices / analogue phones produces the same results. After we've made an inbound/outbound call and hung up, the line still remains open and the call will not disconnect.
Looking at SSA, the extensions in question will show line seized/connected while the call is open and on hanging up on the device the extension shows as Disconnected however the call does not actually clear. The call will drop after a random interval.
Anyone else seen this kind of a behaviour before? Is this a hardware failure? I've restarted the system a couple of times but this doesn't seem to resolve the issue.
Thanks!
We've got an Avaya IPO500 with 70 x IP Extensions. The kit also has 1 x PRI30 and an 8-port analogue extension card with fax machines plugged into all the extensions. 3 of the analogue ports seem to have developed a fault recently whereby the fax machines would not release the line. I initially thought that this may be due to faulty devices, however it seems like the extension ports are to blame.
We've replaced one of the extensions with a new fax machine and the fault still remains. Re-patching other devices / analogue phones produces the same results. After we've made an inbound/outbound call and hung up, the line still remains open and the call will not disconnect.
Looking at SSA, the extensions in question will show line seized/connected while the call is open and on hanging up on the device the extension shows as Disconnected however the call does not actually clear. The call will drop after a random interval.
Anyone else seen this kind of a behaviour before? Is this a hardware failure? I've restarted the system a couple of times but this doesn't seem to resolve the issue.
Thanks!