Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Intermittent call release failures 1

Status
Not open for further replies.
May 25, 2017
38
US
I have an avaya IP office system with 10. 1. 0. 3.0 built to software. This system has embedded voicemail. I am having problems with intermittent call disconnect failures. The system has only three trunks. Occasionally all three lines will be seized. customer will be presented with waiting for line prompt on their phone when attempting to make a call out. This is in the United States. Disconnect clear is checked units is currently 500 milliseconds we are trying to change that to 250 milliseconds. one thing that we have noticed in system status, a voicemail message will not disconnect for 5 minutes. The system timer for Max record time is 120 seconds. Could embedded voicemail be keeping the calls offhook? Is there any way to do a supervised disconnect in the United States?
 
You can do a force disconnect in system status, but you have to sit and watch as calls sit for XYZ length. Temporary, inefficient workaround.
It could be something on the carrier end as that's generally not normal behavior. Call the carrier and check to make sure that their settings on the line match yours. Alternatively, increase their call capacity with a SIP trunk or PRI from the same or different provider.
 
You could use the "Busy Tone Detection" found in System - Telephony - Tone & Music
that will hopefully help a bit but still might not solve it completely.

Also the lowering of the disconnect clear timer might help if you are far away from the CO and the signal gets distorted due to high mF induced by the line.

Joe
FHandw, ACSS (SME)

Remembering intrigrant 2019
 
Thanks, Nutritional Info and, Westi! This is a small site. There is not a Vendor or programmer on-site permanently who could monitor and disconnect calls. We have tried to shorten the disconnect clear timer from 500ms to 250ms. The busy Tone Detection sounds like a great idea. I will try it once on-site again. Is the loss of loop current the only parameter that the IP office looks for when trying to disconnect a trunk? The trunk is fed by a near-by SLC system. Loop capacitance should not be an issue. But the loop current does not fall all the way to zero. Could this cause the failure of release?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top