Summary:	ASTERISK-07478: Ghost blf inuse bug... An easy way to not get calls at work...
Reporter:	none (algorithmn)	Labels:
Date Opened:	2006-08-07 15:05:30	Date Closed:	2006-09-06 10:44:31
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I recently noticed this weird blf issue.  Currently, there is the inherent ability to force certain blf lines to inuse while they are idle. ****** ADDITIONAL INFORMATION ****** Take a working system with blf enabled.  Set up your hard phones (tested with grandstream 2k's) with blf.  Unplug your phone.  Pick up the phone next to your phone and dial your recently disconnected (still registered) phone and hit your blf button.  Your light will go on and never go off.  When I issue a 'show hints' command, it displays your extension as inuse.  Which would differ from your actual idle (which it should then be). I would easily describe it as hanging blf on certain extensions.  There would probably be a 1 line of code solution upon hang failure reset registry to unavailable and not just blf.
Comments:	By: none (algorithmn) 2006-08-07 15:09:46 restarting asterisk solves this issue.. although bug ASTERISK-7468 deletes your subscriptions and then all phones have to be reset. By: Olle Johansson (oej) 2006-08-07 15:10:13 What do you exactly mean with "blf enabled" ? According to the bug guidelines, we need a SIP debug output to show this behaviour. Please upload one file that shows this. By: none (algorithmn) 2006-08-08 11:31:48 as far as BLF Enabled, I refer to it simply as a sip domain with blf enabled..  For greater detail, I have an extension that has all the hint extensions in them.  The hard phones are linked though their subscribed extension via an include.  As far as further explination... blf enabled could simple be considered an * box with a set of hard phones that utilizes BLF. I must have missed that section of the guidelines, sorry about that.  Unfortunatly, I don't wish to purposly crash my clients network.  If I get the opportunity, I will.  I presume you would take the debug output and trace exactly where, within the call setup, this problem occurs.  This may take a week or two for me to procure. If there is any other means till then, it could be beneficial. By: Serge Vecher (serge-v) 2006-08-08 13:41:29 algorithm: follow these instructions to produce the output oej is looking for: 1) Prepare test environment (reduce the ammount of unrelated traffic on the server); 2) Make sure your logger.conf has the following line:   console => notice,warning,error,debug 3) restart Asterik. 4) Enable SIP transaction logging with the following CLI commands: set debug 4 set verbose 4 sip debug 5) Save complete console log to file and _attach_ said file to the bug. By: Serge Vecher (serge-v) 2006-08-08 13:41:48 make sure you update to 1.2.10 as well. By: Serge Vecher (serge-v) 2006-09-06 10:44:31 no response from reporter for a month now. Please reopen the bug if you are able to reproduce this with latest Asterisk 1.2 branch code (r>42000) and have the debugging information available as requested.