Stuck Analog Lines

[jrtudor]

One of the 6 systems I manage is on analog lines, the other 5 are on PRI.

The analog system will about once a week or two have one or more lines get stuck when a caller disconnects.

The CLEC is Verizon. Avaya has told me to be sure that Verizon has reliable disconnect implemented on all the lines, and Verizon says they to.

The only solution I have found to this so far is to reboot the system when the lines are hung.

A user in another thread posted that a reboot should never be the solution to a problem, so I ask, what else can I do to unstick stuck lines, and what else can I do to keep them from sticking.

I keep recommending to management that they need to put in a PRI, but they don't want to spend the money at that location.

IP Office 406
3.2 (55)
VM Pro 3.2.28 (not central)
6 WAN connected locations, no SCN

 

[ProviderReborn]

Caller disconnect is the key to this issue.
Get your line provider to confirm what they are.

ACA - IP Office Implement
ACA - IP Telephony
CCENT - Cisco ICND1
CCNA - Working towards.

 

[mforrence]

Go on site with a butt set and multimeter. Disconnect line from IPO and with butt set call someone. Put meter across Tip & Ring -set to DC Volts. Have the far end disconnect while you remain off-hook. Watch meter. It should go to zero momentarily (1/2 second or so). If it does, trouble is IPO, if it doesn't, trouble is VZ.
Mike

 

[aarenot]

Are these POTS copper, or off of a channel bank?

 

[Drew2400]

jrtudor:

I think you need to follow mforrence's plan for testing. In the mean time, use the System Status application, view active calls, and click on the disconnect button for all of the latent inactive calls.

Of course, maybe I should have read your post a little better as I believe System Status will not work on 3.2.

The fact that it only happens once in a while is troubling. In most cases it's an all or nothing deal. What is your Disconnect Clear timing setting under the Analog Options tab for each analog line? Are the lines pretty clear? Check all connections and grounding.

As a last resort, you could nudge the Disconnect Clear timing down a little and see if that solves it. The general Disconnect Clear timing is one 1/2 second (500 milliseconds). Keep in mind, if the Disconnect Clear timing is too little, you may dump calls and too much will result in more calls hanging on.

I have a system which is fed off of a ATA port from the cable company and they don't even support Reliable Disconnect. Extremely annoying.

Thought about upgrading to 4.1 and see if that solves it? SIP may be an option too. Features of PRI at a cheaper price.

Drew

 

[mattKnight]

Reliable disconnect...

Rather than just accepting the bland assurance fro verizon that "reliable disconnect is implemented on all the lines", ask them what value it is set to.

The value set by the provider needs to be set in the analogue lines but at least 150ms less...

I.e. Verizon cay 500ms, set IPO to 350ms

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[ronromano]

Did you recently switch to FIOS? I am having an issue like this on IPO with a customer newly on FIOS.

http://www.nu-tel.com

 

[mitchatwrk]

I had the same issue with Bellsouth. Avaya replaced the system 3 times as Bellsouth was blaming Avaya ect... After many attempts to resolve the issue with both vendors we decided to put in a PRI, so far so good.

 

[aarenot]

channel bank?

 

[jrtudor]

There is no FIOS, not even available in Marion NC, Verizon will not even offer a static IP address on Business DSL in Marion.

I woudl love ot put in a PRI, and Have been trying to convince management to make that change for months, just not getting anywhere with it.

I will try the suggestions above next time I am on site, probably early next week, and post the results here.

IP Office 406
3.2 (55)
VM Pro 3.2.28 (not central)
6 WAN connected locations, no SCN

 

[ZebrAYA]

We have five IPO’s deployed, anywhere you have analog lines you’ll get issues of stuck lines.
Curiously at our own ip office (SOE) I fixed the problem altering the
System \ telephony \ busy tone detection
Default was 440 Hz, I put it to 430, and wow, it’s done, no more stuck calls for voicemail nor for conference.
note: our provider is the same for all analog trunks **
I recommend you to perform and upgrade to 4.0 release, since you will get the SSA, the evolution of call status, where you can not-only view active calls, but also kill active calls, namely the stuck calls. You could remotely (wan/lan) cut the stuck lines.
Also, I’m trying to set an absolute SHORTCODE (I mean, for all trunks in the system) that cut the call when timer exceeds 100 minutes. That would be a brute force effective method.
** Avaya has a big lack in the analog settings, since every provider slightly differs its busy tone (and other time parameters) from the other, but you can set only one frecuency for all the system, so if you have different analog providers, like ATA’s, GSM gateways, old analog PBX’s you will tune one, and let the others likely stuck.


[Always Close your threads for avoiding other people to entangle]

 

[aarenot]

You can use the "steal call" function as well to hang up on lines that get stuck.

 

[ZebrAYA]

Quoting
aarenot (Vendor) 30 May 08 22:07
You can use the "steal call" function as well to hang up on lines that get stuck.

But, could one choose the line to be hanged?

[Always Close your threads for avoiding other people to entangle]

 

[kwing112000]

You could use system status as well. then you can see the call and click disconnect.

Kevin Wing
ACA- Implement IP Office
Carousel Industries