I am having the same problem too!! At first, I had two SERs (with the same domain name) sharing the same database, then this problem occured, then I thought maybe two SERs with the same domain can't have access to the same database at the same time, so I duplicated another database for the other SER, and run synchronization, however this problem still exist. And the other strange thing is that, when I m trying to do cross proxy call, For example, UA 1 registered at SER A, UA 2 registered at SER B, When UA 2 trying to call UA1 (via SER B), the contact is found, but call unsuccessful, and SER B will bind UA 1 ... Could it be mysql problem?? Or any part of the script we need to modify when running a few SER together? Regards, Chia -----Original Message----- From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Jack Wei Sent: Saturday, July 09, 2005 3:26 AM To: serusers(a)lists.iptel.org Subject: [Serusers] ser mysql/cache sync i am running a cluster with 2 sers. i start the 1st ser and several users registers. the users show up in both the cache and the mysql db. then i start the 2nd ser, and it loads the db into the cache. when the cache entries in the 2nd server times out, the entries are deleted from the db. however, when the users registers in the 1st ser, they aren't entered into the db. how do i fix this problem? the db_mode is set to "2" w/ timer_interval at "10". i've even tried setting the db_mode to "1", but that didn't help. Jack Wei __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Serusers mailing list serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Jack Wei wrote: Write-through DB mode will write all usrloc changes to the DB. However, all locations are cached in ser memory. This means that there is no way a secondary ser can reload a location from DB. If a location is not found in memory, it is assumed not there. A new caching approach has been discussed previously on this list (or was it serdev?). You can do the following: - Use write-through DB mode to the shared SQL DB - Use t_replicate to the secondary ser - On the secondary ser, call save_memory() instead of save() (as the location has already been saved in DB) This only works for deployment scenarios where EUCs are not NATed. The reason is that the secondary ser will have another public IP address than the primary and restricted NATs will not accept incoming packets from other IPs than the one the EUC has registered to. The way to solve this is to either route all INVITEs coming to the secondary through the primary (ex. using Path) or to set up LVS (or similar) where both SERs have the same IP address. However, currently LVS does not do Call-id based load balancing and people who report this scenario have patched LVS or use a commercial load balancing solution. g-)