>>>>> "AK" == Andrew Kohlsmith <[EMAIL PROTECTED]> writes:
AK> There is no mechanism in place for the DB to tell Asterisk that a AK> row changed and that the cache is invalid. If you are using the AK> cache in Asterisk you must manually clear out the peer entry to AK> get the new value, or simply wait for the new registration. I AK> can't think of any other system which magically knows when the DB AK> changes from underneath it and it's been explicitly told to cache AK> the entry. In a slightly more ideal world, asterisk could be told: reload sip peer whatever, and would only update the changed values while retaining MWI and qualify information etc. In a more ideal world, asterisk would only cache stuff that isn't kept in the database at all -- the stuff it needs for MWI and qualify etc. That way everything would always be up-to-date, and MWI would still work. In an even more ideal world, asterisk would keep everything in the database, including the stuff it needs for MWI etc. There are performance reasons to not do that, of course. Perhaps they can be overcome. I hope those proposals are constructive. (The next objection is "where's the patch", and I do apologise for not including one.) /Benny _______________________________________________ --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
