BLF And Call-limit In 1.8

Home » Asterisk Users » BLF And Call-limit In 1.8
Asterisk Users 7 Comments

Hello

We have recently upgraded our internal PBX from 1.4 to 1.8. This made the BLF lamps on our Polycom phones stop working. After a lot of googling and a lot of testing, I have been unable to find a solution.

I did try to change the call-limit value from 4 to 1, and this actually made BLF work (noone suggested this, and what documantation I can find states that this option is deprecated). This change has other implications, however. Call waiting stops working, queues don’t offer calls if the user is in a private call etc.

We have customers that require both BLF and call waiting at the same time.

We are running Asterisk 1.8.11-cert7

I’ve made the following additions to sip.conf [general]:
callcounter=yes counteronpeer=yes (undocumented? Supposed to replace limitonpeers?)

(old relevant values, unchanged)
allowsubscribe=yes subscribecontext=blf notifyringing=yes notifyhold=yes limitonpeers=yes

I also tried may other suggestions I’ve found like placing the hints in the same context as the extensions and removing subscribecontext.

Is there something I’m missing? Is something not working correctly?

Thanks in advance, Pan

7 thoughts on - BLF And Call-limit In 1.8

  • Not sure about this since I use the 10/11 branches and not 1.8, but I think you need to use the deprecated call-limit for BLF and the new busylimit for the other features you need.

    http://www.voip-info.org/wiki/view/Asterisk+config+sip.conf

    From: asterisk-users-bounces@lists.digium.com
    [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Pan B. Christensen Sent: Thursday, December 06, 2012 9:50 AM
    To: Asterisk Users Mailing List – Non-Commercial Discussion Subject: [asterisk-users] BLF and call-limit in 1.8

    Hello

    We have recently upgraded our internal PBX from 1.4 to 1.8. This made the BLF lamps on our Polycom phones stop working. After a lot of googling and a lot of testing, I have been unable to find a solution.

    I did try to change the call-limit value from 4 to 1, and this actually made BLF work (noone suggested this, and what documantation I can find states that this option is deprecated). This change has other implications, however. Call waiting stops working, queues don’t offer calls if the user is in a private call etc.

    We have customers that require both BLF and call waiting at the same time.

    We are running Asterisk 1.8.11-cert7

    I’ve made the following additions to sip.conf [general]:

    callcounter=yes counteronpeer=yes (undocumented? Supposed to replace limitonpeers?)

    (old relevant values, unchanged)

    allowsubscribe=yes

    subscribecontext=blf

    notifyringing=yes notifyhold=yes limitonpeers=yes

    I also tried may other suggestions I’ve found like placing the hints in the same context as the extensions and removing subscribecontext.

    Is there something I’m missing? Is something not working correctly?

    Thanks in advance,

    Pan

  • 6 dec 2012 kl. 16:54 skrev Danny Nicholas :

    Call-limit is the limit on the number of calls you can take and also sets a device to BUSY. Since you want to be able to transfer calls, you need at least two. But this did not set the phone to busy on one call. That’s why we added busy-limit that can be set to the level you want device states to signal busy, but still give the ability to the phone to set up more calls.

    counteronpeer is the same as limitonpeer, just a new name.

    /O

  • But Asterisk doesn’t send ANY notification regarding change of state (like ringing) unless call-limit is 1. In my opinion, ringing status (and probably several others) shouldn’t take into consideration at what point a device is considered as busy. This worked fine in 1.4 (we skipped 1.6) and seems broken in 1.8. Busy-level is 1 in both configurations.

    After some more investigation, I may have found a clue. When I type sip show peer , the following values are reported:
    With DB value 4 or 3 or 2 or 0:
    Call limit : 0
    With DB value 1:
    Call limit : 2147483647

    This doesn’t look correct to me…

    -Pan
    —– Original Message —

  • When you enable call-limit globally for all peers, it sets the call-limit for all peers to INT_MAX. Hence why each device can accept quite a few calls.

    The setting you’re actually toggling is ‘callcounter’. When its enabled
    (boolean true), it sets call-limit to INT_MAX. If not present, then the call-limit value is used. This is why every setting but ‘1’ set the call-limit to 0.

    Since you’re using Realtime, there me a number of issues at play. Do you have this problem with a peer defined in sip.conf?

  • It seems I only assumed a call-limit value of 1 in the DB would make call waiting not work. I tested it now, and because that sets the value in Asterisk to INT_MAX, a call-limit value of 1 in the DB does allow for call waiting. The same value in sip.conf does not.

    -Pan

    —– Original Message —

  • I finally found the real culprit. The call-limit DB field was mapped to both call-limit and callcounter in the view asterisk uses. The latter is what caused the strange behaviour. Removed both and everything works as expected now.

    -Pan

    —– Original Message —