Am 02.02.2011 15:24, schrieb Alex Hermann: > On Wednesday 02 February 2011, you wrote: >> Am 27.01.2011 13:05, schrieb Alex Hermann: >>> On Thursday 27 January 2011, Klaus Darilion wrote: >>>> Am 27.01.2011 11:21, schrieb Danny Dias: >>>>> I've read some difficulty in the synchronisation of registrations >>>>> because Kamailio works best when it stores registrations in memory >>>>> and registrations are constantly changing - they expire and are >>>>> renewed, as well as new ones joining and old ones leaving. To make >>>>> the failover solution function seamlessly, it is necessary to >>>>> synchronise the in-memory registrations between the primary and the >>>>> backup server . This can be done by forking a copy of the >>>>> registration request to the backup server, but there are some >>>>> practical problems in doing this, has anyone do something with this? >>> >>> What problems are you referring to? I use this for some years now >>> without any problems. >> >> Alex, what happens if one server is down. There will be lots of >> "replication transactions" which will timeout. Can this cause any >> problems if there are too many open transactions (retransmissions ...)? > > I just forward() them.
Interesting. So, do you have some logic to drop the response from the "backup" registrar? Or will the client receive 2 responses? Or will the "backup" server not response at all? I guess the last option would be the simplest one... regards klaus _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users