Re: [asterisk-users] BLF and call-limit in 1.8
- Original Message - From: Matthew Jordan mjor...@digium.com To: Asterisk Users Mailing List - Non-Commercial Discussion asterisk-users@lists.digium.com Sent: Saturday, December 08, 2012 12:43 AM Subject: Re: [asterisk-users] BLF and call-limit in 1.8 Thanks for your reply. I just tested creating a peer in sip.conf and that works as it should. In addition, the value of call-limit in sip show peer peer is correct (the same as in sip.conf, which in this case is 4). -Pan 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? -- Matthew Jordan Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com http://asterisk.org -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] BLF and call-limit in 1.8
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 - From: Pan B. Christensen p...@ibidium.no To: Asterisk Users Mailing List - Non-Commercial Discussion asterisk-users@lists.digium.com Sent: Monday, December 10, 2012 11:54 AM Subject: Re: [asterisk-users] BLF and call-limit in 1.8 Thanks for your reply. I just tested creating a peer in sip.conf and that works as it should. In addition, the value of call-limit in sip show peer peer is correct (the same as in sip.conf, which in this case is 4). -Pan -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] BLF and call-limit in 1.8
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 - From: Pan B. Christensen p...@ibidium.no To: Asterisk Users Mailing List - Non-Commercial Discussion asterisk-users@lists.digium.com Sent: Monday, December 10, 2012 12:13 PM Subject: Re: [asterisk-users] BLF and call-limit in 1.8 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 -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] BLF and call-limit in 1.8
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 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 - From: Olle E. Johansson To: Asterisk Users Mailing List - Non-Commercial Discussion Sent: Friday, December 07, 2012 8:20 AM Subject: Re: [asterisk-users] BLF and call-limit in 1.8 6 dec 2012 kl. 16:54 skrev Danny Nicholas da...@debsinc.com: 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 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 From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@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 -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users-- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] BLF and call-limit in 1.8
On 12/07/2012 06:16 AM, Pan B. Christensen wrote: 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 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... 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? -- Matthew Jordan Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com http://asterisk.org -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[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-- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] 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-boun...@lists.digium.com [mailto:asterisk-users-boun...@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 -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] BLF and call-limit in 1.8
6 dec 2012 kl. 16:54 skrev Danny Nicholas da...@debsinc.com: 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 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 From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@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 -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users