<div>
<div>
<div>Now wouldn't that be a whole lot nicer. Allow RT to cache while a users session is active but as soon as the user becomes UNREACHABLE or UNREGISTERED, remove their cache. Or as Atis said, simply update the cache every time there is a REGISTRATION attempt by the specific user. I could see issues developing this only because Asterisk will check it's cache for a hit before checking a database. But that functionality could be changed to check the database first for any RT users with that name and then check the cache.
</div></div>
<div> </div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Yes, but that's not the realtime-way, i'm used to. Wouldn't it be<br>better for asterisk to cache only keep-alives and status (and maybe
<br>even update availability status in db, the same way as it does with<br>regseconds), but re-read peer upon call - the same way as it's without<br>RTCacheFriends.<br><br>Btw, this is developers ML (however topic is quite user-oriented).
<br>What do you guys think, of changing this behavior?<br><br>Regards,<br>Atis</blockquote>
<div> </div><br> </div>