Thanks a lot to everyone for their answers,<br><br>I've got the whole picture about how it works and the available tools. Maybe using dlg_db_sync with some special handling of the SIP routing will do the trick.<br><br>
Best regards,<br>Samuel.<br><br><div class="gmail_quote">On 9 January 2013 20:03, 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">
<tt>yes, using that MI function make sense only if you have an
already running server that needs to take over the calls (like an
active-active setup or cluster setup).<br>
<br>
Also be careful as moving the dialog from one server to another
should be done with preserving the IP of the server, otherwise
in-dialog routing will not work at all.<br>
<br>
Regards,<br>
</tt><div class="im">
<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>
<br></div><div><div class="h5">
On 01/09/2013 04:43 PM, Max Mühlbronner wrote:
<blockquote type="cite">
<div>Hi,<br>
<br>
<br>
If the second server is started on-demand (e.g. keepalived) the
dialogs are loaded into memory from the DB (where the other
opensips stored the dialogs , by db_mode realtime..).<br>
<br>
So there would be no need to use dlg_db_sync in this simple
failover scenario, right?<br>
<br>
<br>
Best regards<br>
<br>
Max M.<br>
<br>
On 01/09/2013 02:30 PM, Bogdan-Andrei Iancu wrote:<br>
</div>
<blockquote type="cite">
<tt>See the MI command dlg_db_sync<br>
<a href="http://www.opensips.org/html/docs/modules/1.8.x/dialog.html#id295605" target="_blank">http://www.opensips.org/html/docs/modules/1.8.x/dialog.html#id295605</a><br>
<br>
Regards,<br>
</tt>
<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>
<br>
On 01/09/2013 02:59 PM, samuel wrote:
<blockquote type="cite">
<p dir="ltr">My point was exactly what you state in the last
sentence about failover scenario. Is there some way to use
current dialog module to handle these scenarios?</p>
<p dir="ltr">Thanks a lot,<br>
Samuel</p>
<div class="gmail_quote">El 09/01/2013 12:50, "Bogdan-Andrei
Iancu" <<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>>
va escriure:<br type="attribution">
<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"> <tt>Hi Samuel,<br>
<br>
For dialog module, the primary storage (for dialog
info) is all the time the mem cache. DB is only a
secondary storage and data is flushed from mem to DB.
At runtime, opensips never reads from DB, but only
from mem (the primary storage). (db mode REALTIME
means the DB storage is updated in realtime from mem
cache)<br>
<br>
So, you cannot have 2 opensips sharing dialog info via
DB. Or you want to implement a failover kind of
scenario (like shifting dialogs from one box to
another) ?<br>
<br>
Regards,<br>
</tt>
<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>
<br>
On 01/07/2013 07:59 PM, samuel wrote:
<blockquote type="cite">Hi folks,<br>
<br>
I'm started reading about dialog module and how to use
it in a distributed environment. I've read about the
'B' flag and how it can be used to send BYEs to the
end-points. My question is whether, using db_mode
REALTIME, another instance of opensips can use the
information stored in the database to send the BYE to
a dialog created in another opensips instance. <br>
<br>
The scenario is the next one: <br>
1.several opensips sharing the database and one of
them receives an INVITE.<br>
2.It creates the dialog and sets the B flag. The
parameter timeout is then set to the corresponding
value. <br>
3.Another opensips uses the information from the
dialog table to send the BYE either forced by an
external t_dlg command or reading from the database (I
guess the period can be controlled with the
db_update_period parameter).<br>
<br>
Is this possible with the current version?<br>
<br>
Thank you very much in advance and congratulations,<br>
Samuel.<br>
<br>
<br>
<br>
<br>
<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>
</pre>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
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>
</pre>
</blockquote>
<br>
<br>
<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>
</pre>
</blockquote>
</div></div></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br>