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
