<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Hi Chad,<br>
<br>
No, the functionality, as it is now, does not provide any feedback
on the reply codes you received on the replicated forks.<br>
<br>
Best regards,<br>
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a>
OpenSIPS Bootcamp 2017, Houston, US
<a class="moz-txt-link-freetext" href="http://opensips.org/training/OpenSIPS_Bootcamp_2017.html">http://opensips.org/training/OpenSIPS_Bootcamp_2017.html</a>
</pre>
<div class="moz-cite-prefix">On 07/07/2017 06:49 PM, Chad Attermann
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:D060D6B6-8A45-4578-AFBB-59FBB81295A8@gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div class=""><br class="">
</div>
<div class="">Thanks Bogdan, I had seen that function and was
wondering if it might be applicable. I don’t suppose there wold
be a way to track the responses from each destination, and have
some logic like if all designations fail, then return failure
code to orig side, otherwise if at least one destination
succeeds then send success to orig?</div>
<div class=""><br class="">
</div>
<div class="">Thanks again,</div>
<div class=""><br class="">
</div>
<div class="">Chad.</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jun 30, 2017, at 2:06 AM, Bogdan-Andrei Iancu
<<a href="mailto:bogdan@opensips.org" class=""
moz-do-not-send="true">bogdan@opensips.org</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type" class="">
<div bgcolor="#FFFFFF" text="#000000" class=""> <tt
class="">Hi Chad,<br class="">
<br class="">
I would say the t_replicate() is what you are looking
for :<br class="">
<a class="moz-txt-link-freetext"
href="http://www.opensips.org/html/docs/modules/2.3.x/tm.html#treplicate"
moz-do-not-send="true">http://www.opensips.org/html/docs/modules/2.3.x/tm.html#treplicate</a><br
class="">
<br class="">
Regards,<br class="">
</tt>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com/" moz-do-not-send="true">http://www.opensips-solutions.com</a>
OpenSIPS Bootcamp 2017, Houston, US
<a class="moz-txt-link-freetext" href="http://opensips.org/training/OpenSIPS_Bootcamp_2017.html" moz-do-not-send="true">http://opensips.org/training/OpenSIPS_Bootcamp_2017.html</a>
</pre>
<div class="moz-cite-prefix">On 06/29/2017 07:31 PM, Chad
Attermann wrote:<br class="">
</div>
<blockquote
cite="mid:657253FA-AD35-4CCD-8FE2-53EB88350983@gmail.com"
type="cite" class="">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8" class="">
Hi All,
<div class=""><br class="">
</div>
<div class="">I would like to be able to “broadcast”
some non-INVITE requests (like NOTIFY and MESSAGE) to
multiple registered endpoints. The problem with using
parallel forking is that the request is not reliably
delivered to all registered endpoints since
retransmission of the request stops after the first
success response is received. What I need is some
hybrid of parallel and serial forking, where requests
to all registered are sent at once, but each is
treated as a separate transaction so that the message
is sent (or at least attempted) reliably to each
endpoint.</div>
<div class=""><br class="">
</div>
<div class="">This sort of situation is mentioned in the
docs for the TM module…</div>
<div class=""><br class="">
</div>
<div class="">"<span style="font-family: Helvetica,
Arial; font-variant-ligatures: normal; orphans: 2;
text-align: justify; widows: 2; background-color:
rgb(255, 255, 255);" class="">UAC--it is a very
simplistic code which allows you to generate your
own transactions. Particularly useful for things
like NOTIFYs or </span><acronym class="acronym"
style="font-family: Helvetica, Arial;
font-variant-ligatures: normal; orphans: 2;
text-align: justify; widows: 2; background-color:
rgb(255, 255, 255);">IM</acronym><span
style="font-family: Helvetica, Arial;
font-variant-ligatures: normal; orphans: 2;
text-align: justify; widows: 2; background-color:
rgb(255, 255, 255);" class=""> gateways.”</span></div>
<div class=""><span style="font-family: Helvetica,
Arial; font-variant-ligatures: normal; orphans: 2;
text-align: justify; widows: 2; background-color:
rgb(255, 255, 255);" class=""><br class="">
</span></div>
<div class=""><span style="font-family: Helvetica,
Arial; font-variant-ligatures: normal; orphans: 2;
text-align: justify; widows: 2; background-color:
rgb(255, 255, 255);" class="">… but there is no
mention of *how* to use it. I’m sure there is
probably a simple script for this, but I haven’t had
any success searching the mailing list or the
Internet at large for details. I would appreciate
if anybody could provide details or a sample script
demonstrating how to create a separate transaction
for each branch.</span></div>
<div class=""><span style="font-family: Helvetica,
Arial; font-variant-ligatures: normal; orphans: 2;
text-align: justify; widows: 2; background-color:
rgb(255, 255, 255);" class=""><br class="">
</span></div>
<div class=""><span style="font-family: Helvetica,
Arial; font-variant-ligatures: normal; orphans: 2;
text-align: justify; widows: 2; background-color:
rgb(255, 255, 255);" class="">Thanks!</span></div>
<br class="">
<fieldset class="mimeAttachmentHeader"></fieldset>
<br class="">
<pre class="" wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org" moz-do-not-send="true">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" moz-do-not-send="true">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</blockquote>
<br>
</body>
</html>