On 01/05/2011 09:39 AM, Bryan Field-Elliot wrote:
We have one table which is serving both purposes (peers and reg). When we want to route a call to an ATA, we first look up that ATA's regserver in that table, and then construct a SIP URI based upon that regserver address. In that way, we route the call through the server to which the ATA is currently registered. So I guess we're covered already in the scenario you describe. It seems like not a great design to have to have a private sipregs table for every server in our pool, especially given that the pool will grow (or maybe shrink) over time. Is that really the recommended design? I haven't seen any articles describing that setup for RealTime in a multi-server environment.
Asterisk Realtime was designed to make dynamic configuration possible, and then later extended to provide a way to store *some* data outside of astdb. It was never intended to provide a failover or data-sharing mechanism, and none of the code attempts to take that into account.
-- Kevin P. Fleming Digium, Inc. | Director of Software Technologies 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA skype: kpfleming | jabber: kflem...@digium.com Check us out at www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users