[asterisk-bugs] [Asterisk 0015319]: busylevel does not work with realtime

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15319 
====================================================================== 
Reported By:                timking
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15319
Category:                   Channels/chan_sip/DatabaseSupport
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.0.5 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.0 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-06-12 11:34 CDT
Last Modified:              2009-08-25 03:24 CDT
====================================================================== 
Summary:                    busylevel does not work with realtime
Description: 
The code that checks for busy_level is within a lookup for its name that
excludes realtime support "because it would break rtautoclear".
Certain aspects of call limit also affected, but call limit (mostly?)
works because it's done in update_call_counter.

Suspect busy_level should be checked in update_call_counter as well.
====================================================================== 

---------------------------------------------------------------------- 
 (0109577) timking (reporter) - 2009-08-25 03:24
 https://issues.asterisk.org/view.php?id=15319#c109577 
---------------------------------------------------------------------- 
I can't fix this myself as I don't understand the issue that is documented
in sip_devicestate, which is:
/* If find_peer asks for a realtime peer, then this breaks rtautoclear. 
This
* is because when a peer tries to autoexpire, the last thing it does is
to
* queue up an event telling the system that the devicestate has changed
* (presumably to unavailable).  If we ask for a realtime peer here, this
would
* load it BACK into memory, thus defeating the point of trying to clear
dead
* hosts out of memory.
This documents the reason why busylevel does not work with realtime peers
given the current implementation. The third argument to find_peer is false
which means it doesn't look for realtime peers. But it would be nice if
busylevel *did* work with realtime peers [or at the very least it was
documented elsewhere the restriction]. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-25 03:24 timking        Note Added: 0109577                          
======================================================================