3300 6.0 CO Trunks Not Disconnecting

[mevans1974]

Hi All,
I have a 3300 6.0 and we are using AMB. I notice the lines are not disconnecting as they should. Disconnect supervision are on the lines from the CO however the lines would not disconnect.

Any help would  be great.

[ralph]

Check the timers in the circ descriptor of the trunk.   Try lowering them by half and retest.

Ralph

[jovan]

Hi there,
I am having this problem myself and tried all that you suggested with the timers without success.
Is there anything else that can stop the disconnection.

Help!!

J

[johnp]

Is there anything else that can stop the disconnection.

Jovan, Are you having a problem where calls don't hang up? The above doesn't makes sense to me.

[acejavelin]

I have noticed disconnect issues (rather, a lack of disconnect) on lines on ASUs since upgrading to 6.0, although these are connected to paging controllers in both instances... Not sure if it is related but I moved them to the internal LS ports and have had no issues since then.

[jovan]

I see why my post may be confusing.

I have 3 LS analog trunks on my 3300 CX controller running MCD 6.0. 

When the caller hangs up the system doesnt release the trunk and it stays busy.  That trunk cant be used again for up to an hour unless I manually disconnect it or "return them to service" through the command line.

Ive lowered the timers as mentioned by Ralph in the circuit descriptors to no avail.

[jovan]

Exactly Johnp:  I am having a problem where calls don't hang up when the caller hangs up and the trunks remains 'busy'

[johnp]

Have you verified that the CO is opening the circuit?

[jovan]

Have you verified that the CO is opening the circuit?

They (the CO) claim that they are.  Is there a way to verify?

I did try it out on an LS trunk that had a 200 ICP which was disconnecting the calls without a hitch.
But it didnt hang up the calls at all.

[LoopyLou]

if the trunk is expecting disconnect supervision and its not getting it then it won't hang up. Try flipping tip and ring. To test I think if you check with a volt meter you can see the disconnect.

[acejavelin]

Put a voltmeter or tone generator w/LED (anything capable of letting you know voltage is there) across the line, call in to the system from a cell phone and have someone put you hold, then hang up and watch the meter... within about 15 seconds you should see the voltage drop to zero for approximately a second, this will confirm that the central office sending you a disconnect signal.

Note you might want a cheap analog volt meter, some digital meters are too slow to report the voltage drop. You can usually get them at your local hardware or electronics superstore (Lowe's, Menards, Home Depot, Micro Center, Fry's, etc) for around $10.

[ralph]

I agree with the analog volt meter.   I've never had a digital meter that was fast enough to catch the voltage change.

Ralph

[jovan]

Ok. Thanks all for the info.  Will do and report on my findings tomorrow

[LoopyLou]

Interesting that both people with the issue are from the Carribbean. Wonder if its a trait of CO's in that area?

[jovan]

Interesting that both people with the issue are from the Caribbean. Wonder if its a trait of CO's in that area?

I didnt take you long to figure that out my friend and you are correct.  The Telco staff have a major 'issue' providing information on the trunk settings.  They sell the systems too and when they havent provided the system they are like talking to a brick wall for info such as trunk settings.

My problem hasnt gone away.  I disabled the voicemail settings sine that was where the calls were held up.  I lowered the timers to the min and still no joy. 

Im trying to figure out if there is a way to detect the line settings with some device or something. 

Perhaps Im wasting time, but the line provider just isnt forth coming with the info and we dont even have a dispute with them.  Last time I asked what was the disconnect timer setting the response was "milliseconds, its milliseconds"

Sorry to vent.  Perhaps I just needed to.  Lol

Suggestions on the next step are still welcome