Actually, I have tested this here with an Aastra 9133i and an [EMAIL PROTECTED] server, and the 9133i will re-subscribe on its own after an Asterisk reboot, if you wait long enough. It took on the order of an hour to do so. Of course, a phone reboot will get it done faster, if necessary, but it _will_ eventually re-subscribe on its own.
In another thread, I've seen a response that the GXP2000 does the same. |-----Original Message----- |From: [EMAIL PROTECTED] |[mailto:[EMAIL PROTECTED] On Behalf Of |mustardman29 |Sent: 24 March 2006 01:10 |To: 'Asterisk Users Mailing List - Non-Commercial Discussion' |Subject: RE: [Asterisk-Users] Re: Fw: anybody has SIP realtime |working ? |Importance: High | |So your Polycom 501's will eventually re-subscribe and BLF |will eventually |start working again after a reboot using your patch? How long |will that |take? Is the time to re-subscribe something you can set on the phone? | |That would be quite acceptable to me if the phone eventually |re-subscribed |on it's own without requiring a reboot. What I am saying is |that my Aastra |9133i and Grandstream GXP2000 NEVER re-subscribe after a reboot with or |without the patch. I tried lot's of different settings to try make it |happen unless I am doing something wrong or not waiting long |enough for the |phones to re-subscribe. I must have tested it for at least 3 |hours and BLF |never came back. I confirmed it with the Asterisk CLI as well. | |> -----Original Message----- |> From: BJ Weschke [mailto:[EMAIL PROTECTED] |> Sent: Thursday, March 23, 2006 5:34 PM |> To: Asterisk Users Mailing List - Non-Commercial Discussion |> Subject: Re: [Asterisk-Users] Re: Fw: anybody has SIP |> realtime working ? |> |> On 3/23/06, mustardman29 <[EMAIL PROTECTED]> wrote: |> > Thanks BJ, |> > |> > I tried your patch and it worked fine for me so thank you |> so much for |> > the effort. It is very much appreciated. Especially since |> I am not |> > capable of coding myself. |> > |> > Unless I can get a total solution so that it just works no |> matter if I |> > reload or reboot then it's not really a solution for me. I have to |> > either not implement BLF for install something other than Asterisk. |> > |> > Telling the client that all they have to do is reboot their phone |> > everytime BLF stops working is not the sort of impression |I want to |> > make. Yes, it will probably be rare if the system is rock |> solid with |> > no nightly/weekly cron jobs to reboot at night and UPS'ed |> etc. but a |> > phone system feature has to either just work always or not |> be used at all IMHO. |> > |> > As far as I'm concerned, BLF simply does not work because |> of this :(. |> > |> |> Well - here's the thing. Using the code/approach in 6047, |> the Polycom and other devices never get the message that |> appears to be the kiss of death for the subscription to go |> away and not come back. Using this approach, it's certainly |> true that immediately after a restart of Asterisk (not a |> reload - reloads are fine now with this code) the |> subscription will not work, but like registrations, |> subscriptions expire and the phone will sign up again and the |> subscription will get renewed and become active again after |> restart. Unfortunately, unlike registrations, there's no |> guick/tactical way for us to keep track and "reseed" a |> subscription immediately after a restart as we do with registrations. |> |> -- |> Bird's The Word Technologies, Inc. |> http://www.btwtech.com/ |> |> |_______________________________________________ |--Bandwidth and Colocation provided by Easynews.com -- | |Asterisk-Users mailing list |To UNSUBSCRIBE or update options visit: | http://lists.digium.com/mailman/listinfo/asterisk-users | _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
