Summary:	ASTERISK-06416: Congestion function can hang system by consuming all available bandwidth
Reporter:	Nik Middleton (middletn)	Labels:
Date Opened:	2006-02-24 16:49:31.000-0600	Date Closed:	2011-06-07 14:10:26
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	If the congestion function is used in a timeout, and the caller doesn't hang up the phone, the session is maintained.  If the the same user, repeats the exercise, using a new session, the bandwidth can be rapidly consumed. Suggestion:  Make congestion have a specified timeout by default (15?)
Comments:	By: Tilghman Lesher (tilghman) 2006-02-24 17:20:42.000-0600 And how, pray tell, does it do that? By: Nik Middleton (middletn) 2006-02-24 17:31:57.000-0600 Good question. The phones in question are running the lasted version for the grandstream gxp2000's. All I can say, looking at the logs, is that a new session is initiated which creates a new session ID.  These sessions ran for some 4 hours, before I could get access to the the * PC and reboot it.  My guess is that the phone simply picked another line, as it's a multi-line phone.  This happened on two phones at different locations. However, the fact remains, that if the user doesn't replace the handset correctly, no timeout condition exists to get out of the congestion status unless explicitly set. By: Tilghman Lesher (tilghman) 2006-02-25 10:26:41.000-0600 Yes, but how does that consume all available bandwidth? By: Andrey S Pankov (casper) 2006-03-01 22:04:50.000-0600 That's the same as with Busy application. You should specify a timeout if you do not want the application to "wait until the calling channel hangs up" (from 'show application' output).