[SR-Users] Advice on placement of t_replicate (REGISTER)

[Daniel-Constantin Mierla]

Hello,

it is up to you how you want it, could be better to do it if save()
succeeds, for consistency, but then the replicated one may fail on the
second server.

There is no drawback from kamailio instance point of view, in any of the
cases.

Cheers,
Daniel

On Wed, Mar 7, 2012 at 3:48 PM, Asgaroth <00asgaroth00 at gmail.com> wrote:

> Hi Guru's,
>
> I'd just like some advice on t_replace and its placement in the routing
> script.
>
> A lot of examples show the following setup:
>
> save("location");
> t_replicate("backup_server");
>
> Would it not be wiser to have something like:
>
> if (save("location")) {
>  t_replcate("backup_server");
> }
>
> Would there be any scenario where you would want to t_replicate if
> save("location") fails for some reason? The configuration I refer to is if
> the location database is in memory. I suspect you may want to replicate all
> if location is going to db core in case of external failure. But would it
> matter on the placement if the location was in memory?
>
> Thanks
>
> ______________________________**_________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/**cgi-bin/mailman/listinfo/sr-**users<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>
>



-- 
Daniel-Constantin Mierla
  http://www.asipto.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20120309/eced66b5/attachment.htm>