[asterisk-dev] Urgent development consultancy wanted

Mark Michelson mmichelson at digium.com
Tue May 22 09:43:34 CDT 2012

On 05/22/2012 09:07 AM, Alistair Cunningham wrote:
> On 22/05/12 15:44, Kevin P. Fleming wrote:
>> It is possible that the patch in revision 365896 could be related,
>> although the symptoms sound slightly different.
> Kevin,
> Thank you, that does sound similar. Do you know if it's been included 
> in any 1.8.X versions? I'm never quite sure how to determine this.
That revision is not in any released version of 1.8. It will be in, I believe.

However, let me note that I doubt this will fix the issue for you. The 
issue being fixed by that revision was one where SIP dialogs were 
sticking around forever. In those cases, a "core show channels" CLI 
command would not list any hung channels, but a "sip show channels" CLI 
command would show SIP dialogs still around.

I have a second suggested revision that may be the problem-solver you 
are looking for, though. I fixed an issue where hangup frames were being 
"missed" sometimes, leading to stuck channels in revision 357761. This 
change is present in Asterisk

I don't necessarily know that this revision will fix your problems, but 
it's better than offering nothing, though :)

If you have debug logging on, and you are not using native bridging (I 
assume this because a local channel is involved), you should typically 
see a level 1 debug message from ast_generic_bridge() that says "Didn't 
get a frame from channel: blah" when a channel hangs up. If you *don't* 
see this message on the calls that correspond to the stuck channels, 
then there's a good chance the revision I pointed to would fix the problem.


More information about the asterisk-dev mailing list