Summary:	ASTERISK-08659: inuse counter not decreased after hanging up a call during which caller is put on hold
Reporter:	Alex H (alexh42)	Labels:
Date Opened:	2007-01-25 06:20:42.000-0600	Date Closed:	2007-01-25 11:39:12.000-0600
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	This bug happens with all the IP telephones we have here.  A particular example is the Grandstream GXP-2000. I receive a call to this telephone (call may be coming from another SIP phone, or Zaptel).  I put the caller on hold (using the 'Hold' button on the telephone).  I then take the caller off hold, and hang up the call. After the call is finished, when I type 'sip show inuse', the column 'In use' shows '1/0'. If I repeat the steps above, after the second call the counter will now show '2/0'. After I have received and hung up five calls which I have placed on hold during the call, the counter is now 5.  In sip.conf, I have incominglimit=5 This means that after placing five calls on hold (and hung each of them up), Asterisk reports that the useage limit for the telephone is reached, and does not put the call through to my phone. As the telephone user, I am unaware that people are trying to ring me but cannot get through. When I delete the line 'incominglimit=5' from sip.conf this problem disappears. ****** ADDITIONAL INFORMATION ****** sip.conf entry: ; Grandstream GXP-2000 [6100] type=friend context=my-context secret=secret username=6100 callerid="6100" <6100> host=dynamic nat=no canreinvite=no dtmfmode=info restrictcid=yes incominglimit=5 disallow=all allow=alaw mailbox=2006100@company
Comments:	By: Clod Patry (junky) 2007-01-25 08:01:13.000-0600 file: that bug isnt fixed after the bug we discovered 2 days ago (inuse and loader stuff)? By: Alex H (alexh42) 2007-01-25 10:36:51.000-0600 This is my first bug posting - I did try searching for related issues but did not find anything that seemed quite the same (0007744 was the closest I found).  Perhaps I didn't use the right search terms. Can you give me a reference to this other bug please? By: Joshua C. Colp (jcolp) 2007-01-25 11:18:52.000-0600 Fixed in 1.4 as of revision 52208 and trunk as of revision 52209. Thanks! If you have more inuse issues, please check the other bugs just in case.