Jev, the usrloc table is filled with register contents first in memory table, if you think deploy a farm of proxy servers you need learn about the t_replycate() function of SER to comunicate the registration to other servers in the farm. You must implement a centralized database to storage billing, subscribers, etc. For mor information in this type of architecture you can see the "3.2.5. Reliability" Section at the SER Admin Guide.

----- Original Message ----- From: "Jev" jev@ecad.org To: serusers@lists.iptel.org Sent: Friday, June 25, 2004 4:58 PM Subject: [Serusers] ser farms / architecture

Hi SerUsers,

I want to try and understand the issues involved in having a farm of SER servers.

For shared usr_loc data service, is there another way for the servers to share the usr_loc datasource, besides running usr_loc dbmode at 3 and having all ser instances updating and querying the same DB?

I would also like to segregate my registrar server from my proxy machine, but I still want my registrar to see invites and byes for billing purposes. Basically to separate all stateful proxying and rtp poxying (keeping it on one or more front end servers) from my registrar/billing server. So far I have been playing with proxying REGISTER and INVITE operations from the front end server(s) to a back end, and attempting to do call routing at the front end. Has anyone done something similar to this in the past? I'd be interested to hear peoples thoughts on this layout.

Thanks, -Jev

---

Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers