Hello Bodgan,<div><br></div><div>The problem is sequential requests in that dialog would not be delivered to the end-user, since the server would have gone down. BYE and re-INVITE messages wouldn't be relayed, affecting billing and features like call hold and call transfer. Also, we wouldn't be able to release media gateways resources.<div>
<br></div><div>Despite all this, you sound like this is not an appropriate solution. If so, what other directions would you suggest?</div><div><br></div><div>Thanks for your help!</div><div>Mariana.<br><br><div class="gmail_quote">
On Fri, Mar 9, 2012 at 2:12 PM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>
<div bgcolor="#ffffff" text="#000000">
Hello Mariana,<br>
<br>
Currently there is no way you can share the dialog state between 2
running instances of opensips. Probably this will be available in
the next versions (1.9 maybe ?).<br>
<br>
But my question is how comes you have such a scenario that requests
of the same dialog end up on different servers ?? may you such
consider fixing that part.<br>
<br>
Regards,<br>
Bogdan<div><div><br>
<br>
On 03/09/2012 02:36 PM, Mariana Arduini wrote:
</div></div><blockquote type="cite"><div><div>Hello,
<div><br>
</div>
<div>I've been searching a lot on how to have more than one
OpenSIPS handling messages from the same dialog (for example,
the initial request goes to server #1 and the sequential
requests go to server #2, in case server #1 goes down). I've
tried pointing the db_url to the same database on both servers,
setting db_mode parameter to 1 (flush all dialog data into DB
immediately), setting the db_update_period to a smaller value
than the default but didn't work, except for when we stop server
#1 smoothly. Even so, some header translations we should do were
not performed.</div>
<div><br>
</div>
<div>I'm supposed to find out how a distributed key-value store
like Redis can be useful on that. I've seen the example in the
Key-value Interface Tutorial but I have no idea on how to
transfer dialog <span style="font-family:Helvetica,Arial;font-size:12px">values,
flags </span><span style="font-family:Helvetica,Arial;font-size:12px">along
with other dialog state information</span><span style="font-family:Helvetica,Arial;font-size:12px"> from the database to a KVP store. Would it
be something like having a whole new dialog module that uses a
distributed cache_db instead? Sounds hard to accomplish...</span></div>
<div><span style="font-family:Helvetica,Arial;font-size:12px"><br>
</span></div>
<div><span style="font-family:Helvetica,Arial;font-size:12px">Is this </span><a href="http://lists.opensips.org/pipermail/users/2012-February/020657.html" target="_blank">http://lists.opensips.org/pipermail/users/2012-February/020657.html</a> supposed
to do what I need? Is there any example of use anywhere? What I
got from it is just profiling distribution, I don't get how
could this allow all dialog state to be shared...</div>
<div><br>
</div>
<div>Thanks a lot for any pointer or help.</div>
<div>Mariana.</div>
</div></div><pre><fieldset></fieldset>
_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><span><font color="#888888">
</font></span></pre><span><font color="#888888">
</font></span></blockquote><span><font color="#888888">
<br>
<br>
<pre cols="72">--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
</font></span></div>
</blockquote></div><br></div></div>