Actually, you know, I can't STOP it from caching. I have rtcacheusers=no (or
whatever it's called. I'm not in front of the system right now) and it's still
populating astdb with registration entries. Hmmm.
-----Original Message-----
From: Kevin P. Fleming [mailto:[EMAIL PROTECTED]
Sent: Sun 12/11/2005 3:51 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Cc:
Subject: Re: [Asterisk-Users] Realtime Subscribecontext
Douglas Garstang wrote:
> Thanks.... while we're on the topic of realtime. Can realtime
sipusers be shared amongst multiple Asterisk boxes, to share a common location
database? I'm sitting here on a Sunday jerking around with it, having problems.
I'd like to know before I spend more Sundays doing the same thing if it's even
supposed to work or not.
Uhhh... you already quoted my previous message on that topic stating
that it was not supported at this time. In any given situation, it may
or may not work properly, depending on exactly what the servers and
clients are doing.
Even if the code had been written, there will still be many issues
involved in actually implementing it, including (but not limited to) NAT
traversal, call limit handling, registration expiration and others. It
also mandates that there can be _no_ caching of peer/user information in
memory, which currently means there is no 'qualify' or MWI notification
possible.
_______________________________________________
--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
