We do this by using SERs replicate function to replicate all registration transactions from one SER server to the other. We use this functionality for failover between ser-server1, and ser-server2 but it sounds like you could us it similarly in your situation.

Just do something like this in your ser.cfg. (I am assuming that the IP of your 2nd server is 192.168.0.1 in this example).

if (method=="REGISTER") { if (src_ip!=192.168.0.1) { # authenticate all requests not coming from the secondary ser server if (!www_authorize("my.sipdomain.com", "subscriber")) { www_challenge("my.sipdomain.com", "0"); break; }; }; save("location");

# replicate the registration to secondary ser server - if it did not originate from ser-server2 if (src_ip!=192.168.0.1) { t_replicate("192.168.0.1","5060"); };

break; };

Hope this helps.

Darren Nay VOIP Network Administrator Ionosphere, Inc. dnay@ionosphere.net

_____

From: Jacob Bøg Albers [mailto:jacob@storskoven.dk] Sent: Friday, October 15, 2004 8:42 AM To: serusers@lists.iptel.org Subject: [Serusers] Peering

Hey

I need to do peering between two SER SIP networks (and later on of course other routers) but ... Anybody have a pointer as to how I set that up ? I tried finding it in the admin guide, but my knowledge apparently isn't good enough yet ;-)

Two-way peering - so network 1 can call through network 2, but network 2 can also call through network 1.