[Asterisk-Users] BLF not working after reload

[mustardman29]

Thanks for pointing that bug out to me BJ.  At least I understand what is
going on now.  It's definitely not limited to the Polycom Phones. 

> -----Original Message-----
> From: BJ Weschke [mailto:bweschke at gmail.com] 
> Sent: Monday, February 27, 2006 3:57 AM
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [Asterisk-Users] BLF not working after reload
> 
> On 2/26/06, mustardman29 <mustardman29 at hotmail.com> wrote:
> > According to this blurb I found on the Asterisk Wiki, it 
> was supposed 
> > to be fixed so it still works after a reload.  Your 
> suggestion is all 
> > fine and dandy but does nothing to rectify a server reboot. 
>  If phones 
> > have to be rebooted everytime the Asterisk server is 
> rebooted or the 
> > sip.conf is reloaded just to allow BLF to keep working then 
> this is a 
> > show stopper for me!
> >
> > "Update Aug. 2005 (for Asterisk 1.2.0) After months in the 
> bug tracker 
> > (bug 3644), we've finally committed a lot of changes to the SIP 
> > Subscribe subsystem in Asterisk cvs head:
> >
> > It now works even if you reload the dial plan It does not accept 
> > subscriptions to extensions without hints It will terminate 
> > subscriptions if the hint does not exist after a dialplan reload
> >
> > To get this to work properly, you
> >
> > Add a hint to the dialplan for the extension
> > Optional: Configure incominglimit for the device (renamed to 
> > "call-limit" in Asterisk v.1.2)
> > Optional: Enable "notifyringing = yes" if you'd also like 
> to see the 
> > RINGING state to be notified"
> >
> > > -----Original Message-----
> > > From: Douglas Garstang [mailto:dgarstang at oneeighty.com]
> > > Sent: Sunday, February 26, 2006 12:19 PM
> > > To: Asterisk Users Mailing List - Non-Commercial Discussion
> > > Subject: RE: [Asterisk-Users] BLF not working after reload
> > >
> > > If you do a 'reload' in Asterisk, it deletes all the sip 
> > > subscriptions. Do a 'sip show subscriptions' before and after a 
> > > reload command. They will disappear. I've been bitching 
> about this 
> > > for a while, and asking why subscriptions can't be stored 
> in astdb 
> > > like registrations.
> > >
> > > If you reboot the phone, it sends the SIP SUBSCRIBE message to 
> > > Asterisk again, which remembers it until the next reload.
> > > If you reboot the Astrisk server, you obviously lose it as well, 
> > > because Asterisk is storing them in memory (not astdb).
> > >
> > > One workaround, is to not issue 'reload' commands. Just 
> reload the 
> > > module you've changed. I think reloading SIP will delete the 
> > > subscriptions. For example, if you change the dial plan 
> just issue 
> > > an 'extensions reload'. Your subscriptions should remain.
> > >
> > > Lets just hope it's a long time for you between alternations to 
> > > sip.conf!
> > >
> 
>  See Bug #6047 pls. It's got a pointer to a branch of /trunk 
> that does fix this with regard to subscriptions surviving a reload.
> 
> --
> Bird's The Word Technologies, Inc.
> http://www.btwtech.com/
> 
>