Odd, I've been using realtime for thousands of users with an average of
many calls per second using realtime sip. Now, I don't use
realtime extensions, which may be what you are talking about because I
can't add contexts easily in realtime. Having to have a switch
statement in a static file (which means a reload on adding a context)
makes it non-realtime for our purposes. (And, last time I checked
it still did the same query at least 3x in a row each time as a
hold-over from the IAX switch, gah!)<br><br><div><span class="gmail_quote">On 9/13/05, <b class="gmail_sendername"><a href="mailto:alex@pilosoft.com">alex@pilosoft.com</a></b> <<a href="mailto:alex@pilosoft.com">alex@pilosoft.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Tue, 13 Sep 2005, Sherwood McGowan wrote:<br><br>> That's too simple mate, Asterisk RealTime.... use multiple servers with
<br>> a common database interface for configurations. I personally like using<br>> MySQL clustering, but you could use whatever... Or, you could code your<br>> interface to allow for selecting what user is on a server by extension,
<br>> area code, exchange, whatever. I already do this to a small degree and<br>> I'm working to make ARTCP (Asterisk RealTime Control Panel) have this<br>> functionality.<br>good luck scaling realtime to hundreds of channels.
<br><br>realtime, as currently implemented, is very inefficient for high loads.<br><br>-alex<br><br>_______________________________________________<br>Asterisk-Dev mailing list<br><a href="mailto:Asterisk-Dev@lists.digium.com">
Asterisk-Dev@lists.digium.com</a><br><a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-dev">
http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br></blockquote></div><br>