<meta http-equiv="content-type" content="text/html; charset=utf-8">Hi Bogdan,<div><br></div><div>Thank you for pointing the possible issues in our solution :)</div><div><div><br></div><div>The initial idea is to use load balancers running on a HA set. Our OpenSIPS instances will connect 2 network domains. We'll need a load balancer in front of each one of the network domains, as in this figure: <a href="http://s7.postimage.org/a5ex6dqgr/arch.jpg">http://s7.postimage.org/a5ex6dqgr/arch.jpg</a></div>
<meta http-equiv="content-type" content="text/html; charset=utf-8"><div><br></div><div>Besides running the load_balance module, edge servers would detect when instance 1 goes down and "transfer" all dialogs to another instance. I'm aware that this is not implemented in the current OpenSIPS code, but keeping all the established calls and being able to handle sequential requests on them is a requirement in our project and we'll have to find out how to do this. First thoughts may include making some changes on load_balance module, but so far we don't have a defined strategy. By the way, would you have any clue on this?<br>
</div><div><br></div><div>Considering everything I've read in this users list and the way the load_balance module works (i.e. it just relays all of the sequential requests to the same server, whatever it is its status), I feel the current OpenSIPS implementation is not worried about loosing established ongoing calls in case of one of the instances fails, besides the usual lost of early state calls. Is it a common solution in SIP systems or is there any planning for improving this in OpenSIPS on the next releases?</div>
<div><br></div><div>Thanks a lot again!</div><span class="HOEnZb"><font color="#888888"><div>Mariana</div></font></span></div><br><div class="gmail_quote">On Mon, Mar 12, 2012 at 12:14 PM, Mariana Arduini <span dir="ltr"><<a href="mailto:marianarduini@gmail.com">marianarduini@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Bogdan,<div><br></div><div>Thank you for pointing the possible issues in our solution :)</div><div><div><br></div><div>
The initial idea is to use load balancers running on a HA set. Our OpenSIPS instances will connect 2 network domains. We'll need a load balancer in front of each one of the network domains, as in this figure:</div>
<div><br></div><div><br></div><div><br></div><div>
Besides running the load_balance module, edge servers would detect when instance 1 goes down and "transfer" all dialogs to another instance. I'm aware that this is not implemented in the current OpenSIPS code, but keeping all the established calls and being able to handle sequential requests on them is a requirement in our project and we'll have to find out how to do this. First thoughts may include making some changes on load_balance module, but so far we don't have a defined strategy. By the way, would you have any clue on this?</div>
<div><br></div><div>Considering everything I've read in this users list and the way the load_balance module works (i.e. it just relays all of the sequential requests to the same server, whatever it is its status), I feel the current OpenSIPS implementation is not worried about loosing established ongoing calls in case of one of the instances fails, besides the usual lost of early state calls. Is it a common solution in SIP systems or is there any planning for improving this in OpenSIPS on the next releases?</div>
<div><br></div><div>Thanks a lot again!</div><span class="HOEnZb"><font color="#888888"><div>Mariana</div></font></span><div><div class="h5"><div><br></div><div><br></div><div><br><div class="gmail_quote">On Mon, Mar 12, 2012 at 9:08 AM, 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">
Hi Mariana,<br>
<br>
Well, before considering how opensips can "see" the dialogs created
by other opensips instance, you should consider how the sequential
request will get to the other instance.<br>
Let me explain:<br>
(1) dialog is created through instance X with IP1, so call is
record routed with this IP1<br>
(2) instance X goes down, but you have another instance Y up and
running with IP2<br>
(3) considering that sequential requests tries to go to IP1, how
do you make them being routed (Ip level) to IP2 where the Y instance
is running ?<br>
<br>
Regards,<br>
Bogdan<div><div><br>
<br>
<br>
On 03/09/2012 09:18 PM, Mariana Arduini wrote:
<blockquote type="cite">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:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<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>
</blockquote>
<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>
</div></div></div>
</blockquote></div><br></div></div></div></div>
</blockquote></div><br>