Perhaps you also need to look at the refresh time too... How many seconds left in the current registration before attemtping to register again. Perhaps slightly increasing that value with registration time "back" to 3600 will present a better offer that the phone won't see its registration expire. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431
Email: tgrazi...@myitdepartment.net LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: sipx-users-boun...@list.sipfoundry.org <sipx-users-boun...@list.sipfoundry.org> To: Danny Shay <ds...@norlemtc.com>; sipx-users@list.sipfoundry.org <sipx-users@list.sipfoundry.org> Sent: Wed Sep 08 12:40:33 2010 Subject: Re: [sipx-users] BLF lights constantly flashing LIP-68xx ________________________________________ From: sipx-users-boun...@list.sipfoundry.org [sipx-users-boun...@list.sipfoundry.org] On Behalf Of Danny Shay [ds...@norlemtc.com] BLF worked when we first installed 4.2.0, but failed shortly thereafter. I think it failed after I set the phones to request a shorter registration timeout than 3600 seconds. I changed it to 900 seconds because they constantly expired after 1 or 2 cycles when set to 3600. We did not immediately see the problem so I am speculating as far as a correlation between registration timeout and presence subscription goes. ________________________________________ That makes sense. It looks like the minimum subscription time allowed by the RLS is 1800 seconds. (If you look at the SIP signaling, you'll see if the RLS is returning a "subscription time too short" error.) A subscription time of 3600 seconds should work fine, and will create less overhead. (In most sipXecs systems, the bulk of the system load is re-registrations and re-subscriptions, not calls, and increasing registration/subscription times helps with that.) If you are having problems maintaining subscriptions, you should investigate that. (Generally, the best way is to set all logging to DEBUG, wait for the problem to appear, and take a snapshot covering at least the past 3 hours.) Dale _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
