Bogdan,
Thanks for sharing. I was hoping to do something similar with http_db and sql by treating new posts with php and replicating them on a remote mysql db which will then be queried for location type requests. In your solution are employing DB_Cache module? Also are you using a queuing solution for events? Thanks, Tito On Wed, Jun 25, 2014 at 5:38 AM, Bogdan-Andrei Iancu <[email protected]> wrote: > Hi Tito, > > What I do for clustering usrloc is something like this: > - each node manages the registrations independently (there is no > usrloc replication between nodes) > - I have a nosql cluster available for all nodes > - I use the AOR related events+routes to push/remove into the nosql db > the AOR (only) available on each node > - basically the nosql "knows" which AORs are registered on which node > - when a node handles a call, it looks into nosql to see which are the > nodes having registrations for the needed AOR -> call is parallel forked to > local registrations (if any) and to the other nodes (based on nosql info) > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developerhttp://www.opensips-solutions.com > > On 24.06.2014 15:27, Tito Cumpen wrote: > > Rik, > > > > > My deployment is not dependant on virtual IP. Since the failover and > load balancing logic resides on the client and I intend to use srv records > to define the weight of proxies. The problem comes to surface if a user > makes an attempt to register and finds himself on server A. Soon after > makes an attempt to register and finds the second client on server b. If a > Ruri request sources from server B how can I fork the request in parallel > to the first entry in server A? > Thanks for your reply but I have raised the question of using contact > replication before please see below: > > > > ---------- Forwarded message ---------- > From: Liviu Chircu <[email protected]> > Date: Wed, Jun 11, 2014 at 1:29 PM > Subject: Re: [OpenSIPS-Users] binary replication > To: [email protected] > > > Hello Tito, > > Both dialog and user location replication were actually designed to work > with VIPs only! From the moment the "receiving" instance takes over, it > should have the same pool of registered users as instance #1, and it should > be able to process all existing dialogues. > > Best regards, > > Liviu Chircu > OpenSIPS Developerhttp://www.opensips-solutions.com > > On 06/11/2014 03:27 PM, Tito Cumpen wrote: > > Group, > > Playing with the idea of using binary replication. Just curious if > anyone can provide a use case. Would this coupled with a virtual ip? I am > not certain how the instance that accepts replications would take over. > > > Thanks, > Tito > > > _______________________________________________ > Users mailing > [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > On Tue, Jun 24, 2014 at 5:35 AM, Rik Broers <[email protected]> wrote: > >> I’m was also looking into this problem, which is very similar to yours. >> >> >> >> I found this and it is a perfect solution to my problem. >> >> Think this would help you too. >> >> >> >> http://www.opensips.org/html/docs/modules/devel/usrloc#usrloc-replication >> >> >> >> >> >> Vriendelijke groet, >> >> *Rik Broers* >> Voice Engineer >> >> *Van:* [email protected] [mailto: >> [email protected]] *Namens *Tito Cumpen >> *Verzonden:* dinsdag 24 juni 2014 04:54 >> *Aan:* OpenSIPS users mailling list >> *Onderwerp:* [OpenSIPS-Users] Distributed deployment >> >> >> >> Hello group, >> >> >> >> >> >> I am reaching out to you because I am hitting a roadblock in designing a >> distributed deployment. Currently I am entertaining the idea of using DNS >> srv for the sake of load balancing and availability. The main problem is >> sharing aors among the proxies. My requirement is to allow proxies to fork >> requests to remote proxies in which a user could be registered to in >> addition to the local server. The binary replication component will not >> suffice because it is tailored to virtual ip. I've noticed that opensips >> has a recursive timer that runs at every second to verify which >> registration expires with the intent of removing it. Assuming a shared >> mysql instance is the only option each proxy will be querying mysql which >> seems like a ton of activity. Can anyone advise what the best practice for >> scaling would be? >> >> >> >> >> >> Thanks, >> >> Tito >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > > > _______________________________________________ > Users mailing > [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
