<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Matt,<br>
<br>
<br>
On 11/25/2011 03:21 PM, Matt Hamilton wrote:
<blockquote cite="mid:BAY170-W386E076FB2A2297FF47C27B3CF0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
<div dir="ltr">
Thanks a lot Bogdan.<br>
<br>
Is it possible to use another ds_select_dst in the failure_route
to redistribute failed node's calls to remaining Active nodes?
Even if I can do that, it has to be in the probing_mode=0, am I
right? I assume I can't "catch" the failure and manually adjust
the destination in probing_mode=1.<br>
</div>
</blockquote>
no, you cannot do that as ds_select_xxx() is all the time done over
the original set (like all destinations are active). So you cannot
do a dispatching only over the active ones - dispatcher will compute
the hash, it will identify the corresponding destination and, if
failed, it will shift to the next one.<br>
<br>
Regards,<br>
Bogdan<br>
<blockquote cite="mid:BAY170-W386E076FB2A2297FF47C27B3CF0@phx.gbl"
type="cite">
<div dir="ltr"><br>
If I can use another ds_select_dst, can it be algorithm 7 with a
different PV in the failure_route?<br>
<br>
Thanks,<br>
Matt<br>
<br>
<br>
<br>
<div>
<hr id="stopSpelling">Date: Fri, 25 Nov 2011 13:17:08 +0200<br>
From: <a class="moz-txt-link-abbreviated" href="mailto:bogdan@opensips.org">bogdan@opensips.org</a><br>
To: <a class="moz-txt-link-abbreviated" href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>
CC: <a class="moz-txt-link-abbreviated" href="mailto:mistral9999@hotmail.com">mistral9999@hotmail.com</a><br>
Subject: Re: [OpenSIPS-Users] hash and dispatcher on failover<br>
<br>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft SafeHTML">
Hi Matt,<br>
<br>
If Asterisk 4 is down, the hash will not be recalculated, but
the calls that should go to Asterisk 4 will simply be pushed
to the next available entry in the dispatcher list.<br>
<br>
Regards,<br>
Bogdan<br>
<br>
On 11/25/2011 07:58 AM, Matt Hamilton wrote:
<blockquote
cite="mid:BAY170-W39BEB7CBEBCCF85A1F13D0B3CF0@phx.gbl">
<style>
.ExternalClass .ecxhmmessage P
{padding:0px;}
.ExternalClass body.ecxhmmessage
{font-size:10pt;font-family:Tahoma;}
</style>
<div dir="ltr"> I'm new to dispatcher - wanted to clarify
couple of things...<br>
<br>
<br>
<br>
I'm using algorithm 7 (hash over the content of PVs
string) to pick a destination.<br>
<br>
<br>
modparam("dispatcher", "hash_pvar", "$pvar")<br>
ds_select_dst("1", "7");<br>
<br>
<br>
Let's say the probing_mode is 1, and based on the value of
$pvar (A, B, C, etc.), incoming requests are dispatched
in the following fashion:<br>
<br>
<br>
A -> Asterisk1<br>
B -> Asterisk1<br>
C -> Asterisk2<br>
D -> Asterisk3<br>
E -> Asterisk4<br>
F -> Asterisk4<br>
<br>
<br>
What happens to E, F if Asterisk4 fails? Are they
distributed among the remaining servers or do they all go
to the same server? <br>
<br>
Do A, B, C, D still go to the same servers? In other
words, is the hash recalculated?<br>
<br>
<br>
Can hash_pvar be changed; e.g. use $si for route[1], use
$ci for failure_route[1]?<br>
<br>
<br>
Thanks,<br>
Matt<br>
</div>
<pre><fieldset class="ecxmimeAttachmentHeader"></fieldset>
_______________________________________________
Users mailing list
<a moz-do-not-send="true" class="ecxmoz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a moz-do-not-send="true" class="ecxmoz-txt-link-freetext" 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 class="ecxmoz-signature">--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
OpenSIPS solutions and "know-how"</pre>
</div>
</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
OpenSIPS solutions and "know-how"</pre>
</body>
</html>