[asterisk-dev] Deprecating sip call-limit

BJ Weschke bweschke at gmail.com
Wed Nov 21 07:56:57 CST 2007


Olle E Johansson wrote:
> 20 nov 2007 kl. 22.58 skrev BJ Weschke:
>
>   
>> Johansson Olle E wrote:
>>     
>>> Friends,
>>>
>>> Blitzrage and I had a discussion about busylevel and call-limit in
>>> chan_sip on the IRC I wanted to expand to the rest of you deveopers
>>> out there...
>>>
>>>
>>> My proposal in this discussion was:
>>>
>>> - deprecate call-limit in chan_sip. No other channel driver has a
>>> built-in call limit
>>>    and we now favour groupcount and dialplan control instead of
>>> embedding this
>>>    into channel drivers.
>>>    The call-limit is history that has survived too long.
>>>
>>> - implement a new option to enable call counters for the subscribe/
>>> notify event system in chan_sip (channel specific)
>>>
>>> - implement busy-level in more channel drivers
>>>
>>> - implement a DEVICE() dial plan function that is cross-channel, like
>>> CHANNEL(),
>>>   so we can check busylevel in chan_iax2 and other channels that can
>>> handle multiple
>>>    channels per device. Busylevel can now be checked in the SIPPEER()
>>> function only.
>>>
>>>
>>> I know this is a lot of stuff at the same time, but it kind of  
>>> belongs
>>> together.
>>>
>>> /O
>>>
>>>       
>> Olle / Leif -
>>
>> What are we going to do about things like app_queue that resolve on  
>> call-limit and limitonpeers being set correctly in order to make a  
>> proper response back to app_queue that the device is or is not busy  
>> to receive a queue call?
>>     
>
> App_queue doesn't do anything with the actual limit, but it needs the  
> call counter that is the basis behind the call limit. That counter  
> will stay, but get a new name. The actual enforcement of any call  
> limits in chan_sip will go.
>
>   
 Ah! Ok. In that case, then yes, +1.

-- 
--
Bird's The Word Technologies, Inc.
http://www.btwtech.com/






More information about the asterisk-dev mailing list