[asterisk-bugs] [Asterisk 0016788]: [regression] Realtime agents Device state always Not in use

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Mar 3 11:21:20 CST 2010


The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16788 
====================================================================== 
Reported By:                sum
Assigned To:                mmichelson
====================================================================== 
Project:                    Asterisk
Issue ID:                   16788
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.6.2.2 
JIRA:                       SWP-886 
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-02-08 19:16 CST
Last Modified:              2010-03-03 11:21 CST
====================================================================== 
Summary:                    [regression] Realtime agents Device state always Not
in use
Description: 
I have SIP realtime agents that are always in use, this dind't happend on
previous SVN and RC versions 
====================================================================== 

---------------------------------------------------------------------- 
 (0118865) mmichelson (administrator) - 2010-03-03 11:21
 https://issues.asterisk.org/view.php?id=16788#c118865 
---------------------------------------------------------------------- 
This is not a bug in Asterisk. SIP bases its device state on the call-limit
(or countcalls) setting in sip.conf or in realtime. A misconfigured table
will result in the behavior you saw. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-03 11:21 mmichelson     Note Added: 0118865                          
2010-03-03 11:21 mmichelson     Status                   acknowledged =>
resolved
2010-03-03 11:21 mmichelson     Resolution               open => no change
required
2010-03-03 11:21 mmichelson     Assigned To               => mmichelson      
======================================================================




More information about the asterisk-bugs mailing list