Kevin P. Fleming
2005-Mar-03 14:46 UTC
[Asterisk-Users] [Asterisk-Dev] CVS-HEAD change: queue/agent persistence
For anyone using CVS HEAD, if you are using queue member persistence or agent persistence, your next update will cause the persistence to break. The storage format for these elements has been changed so that it can be more easily extended in the future, but this required breaking compatibility. This should be the last time these features will be broken by an upgrade :-) _______________________________________________ Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev Spam detection software, running on the system "zeus.avanzada7.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: For anyone using CVS HEAD, if you are using queue member persistence or agent persistence, your next update will cause the persistence to break. The storage format for these elements has been changed so that it can be more easily extended in the future, but this required breaking compatibility. This should be the last time these features will be broken by an upgrade :-) Asterisk-Dev mailing list Asterisk-Dev@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev [...] Content analysis details: (0.1 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.1 FORGED_RCVD_HELO Received: contains a forged HELO
Guido Hecken
2005-Mar-04 03:23 UTC
[Asterisk-Users] CVS-HEAD change: queue/agent persistence
> For anyone using CVS HEAD, if you are using queue member persistence or > agent persistence, your next update will cause the persistence to break. > The storage format for these elements has been changed so that it can be > more easily extended in the future, but this required breaking > compatibility. This should be the last time these features will be > broken by an upgrade :-)Thanks for these informations. But what does it mean exactly "update will cause the persistence to break". Which actions are required to maintain this feature after updating? Regards, Guido Hecken
Kevin P. Fleming
2005-Mar-04 07:58 UTC
[Asterisk-Users] CVS-HEAD change: queue/agent persistence
Guido Hecken wrote:> But what does it mean exactly "update will cause the persistence to break". > Which actions are required to maintain this feature after updating?It will break one time only. There is no action required on your part; when you bring up the new version of Asterisk you will likely have none of your persistent members/agents restored. From then on, the persistence behavior will work again across future restarts.