Askozia Forums
May 17, 2012, 01:39:49 pm *
Welcome, Guest. Please login or register.

Login with username, password and session length
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: 2.0rc2 BLF, Subscriptions: extensions are always showed as idle  (Read 1060 times)
Scapal
Full Member
***

Karma: 4
Posts: 58



View Profile
« on: March 23, 2010, 01:33:38 pm »

Since I ventured into the 2.0 snapshots, the BLF feature on my phones isn't working anymore.
After a quick diagnostic, here is what I found, the subscriptions are working fine but AskoziaPBX keeps seeing the extensions as IDLE.

pbx*CLI> sip show channels
Peer             User/ANR         Call ID          Format           Hold     Last Message    Expiry
10.25.9.196      820              4192275274@10_2  0x4 (ulaw)       No       Rx: ACK                   
10.25.9.60       850              505ed0b32d776cc  0x4 (ulaw)       No       Tx: ACK                   
2 active SIP dialogs

pbx*CLI> sip show subscriptions
Peer             User             Call ID          Extension        Last state     Type            Mailbox    Expiry
10.25.9.192      810              38f1f907-c7c4ba  850@SIP-PHONE-1  Idle           dialog-info+xml <none>     001200
10.25.9.192      810              e265384-72555a6  820@SIP-PHONE-1  Idle           dialog-info+xml <none>     001200
2 active SIP subscriptions
 
Just to check the hint info : dialplan show 850@SIP-PHONE-1509994276497f5a82e776e
[ Included context 'internal' created by 'pbx_config' ]
  '850' =>          hint: SIP/850                                 [pbx_config]

Logged
Scapal
Full Member
***

Karma: 4
Posts: 58



View Profile
« Reply #1 on: March 23, 2010, 01:53:58 pm »

Ok, maybe I used the 'bug' word a little too fast   Undecided
The BLF will only work if the call-limit of the subscribed extensions is not 0.
I just had to set it to a non zero value for the BLF to work again.

I could be a good idea to put a non zero default value like it was in the 1.x versions and show this in the phone configuration.
Logged
Michael
Askozia Staff
Hero Member
*

Karma: 49
Posts: 1020


View Profile
« Reply #2 on: March 23, 2010, 03:06:24 pm »

Another report of BLF subscriptions failing was resolved by killing snomd. Could you try, with your "default" config, executing "killall snomd" from the console in the Integrator Panel. Open the Integrator Panel by pressing 'ESC' anywhere in the gui.

That call-limit setting is actually deprecated and was, therefore, removed. It has yet to be replaced on a system-wide level with device state functions in the dial plan.
Logged
Scapal
Full Member
***

Karma: 4
Posts: 58



View Profile
« Reply #3 on: March 24, 2010, 08:26:17 am »

I found a lot of valuable information on this page: http://www.voip-info.org/wiki/view/Asterisk+standard+extensions

Quote
For hints/BLF to work as expected in Asterisk 1.4 you need to ensure that the following configuration items are set in sip.conf:
  • Asterisk sip call-limit must be set for every extension. Usually set this to a large arbitrary number such as 100. (or 1 if you don't want another call to be received when the extension is on the phone)
  • Asterisk sip notifyringing should be set to "yes".
  • If you're using RealTime, ensure you have both rtcachefriends and rtupdate set to "yes".
  • limitonpeers must be set to "yes" - this is the most likely culprit since it's missing from the 1.4 default config files

Quote
Related options in sip.conf: notifyringing, notifyhold, limitonpeers, subscribecontext, busy-level(1.6.x only), call-limit

There are also things like automated hint generation starting with Asterisk 1.6.1:
Code:
exten => _XXX,hint,SIP/${EXTEN}

The remaining of this article is quite interesting and bring some light on Asterisk 1.6.1 features regarding BLF.
Logged
Scapal
Full Member
***

Karma: 4
Posts: 58



View Profile
« Reply #4 on: March 24, 2010, 08:28:09 am »

Killing snomd didn't change anything
Logged
Scapal
Full Member
***

Karma: 4
Posts: 58



View Profile
« Reply #5 on: March 24, 2010, 09:34:24 am »

Ok, I found the correct 1.6.1 way to do this:

Just set callcounter = yes in the global sip settings.
This will set a Call Limit : 999 for every sip device instead of leaving a Call Limit : 0.
The explicit use of call-limit is deprecated but seems to be still used for subscription devices state.

Logged
Michael
Askozia Staff
Hero Member
*

Karma: 49
Posts: 1020


View Profile
« Reply #6 on: March 24, 2010, 03:57:16 pm »

Changed in trunk:
 - https://wush.net/trac/askozia/changeset/1430

Nice work looking into this!
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
Page created in 0.13 seconds with 19 queries.