<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body>
<font face="monospace">That's only for BLF (dialog/info presence),
nothing to do with the calling.<br>
<br>
Regards,<br>
</font>
<pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
OpenSIPS Summit 27-30 Sept 2022, Athens
<a class="moz-txt-link-freetext" href="https://www.opensips.org/events/Summit-2022Athens/">https://www.opensips.org/events/Summit-2022Athens/</a></pre>
<div class="moz-cite-prefix">On 10/10/22 10:13 PM, Bela H wrote:<br>
</div>
<blockquote type="cite"
cite="mid:SY4P282MB225201ED6AE675FC4D96323BC0209@SY4P282MB2252.AUSP282.PROD.OUTLOOK.COM">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}.MsoChpDefault
{mso-style-type:export-only;}div.WordSection1
{page:WordSection1;}</style>
<div class="WordSection1">
<p class="MsoNormal">Or is the
dialoginfo_set_branch_callee(callee) function the key here?</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div
style="mso-element:para-border-div;border:none;border-top:solid
#E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="border:none;padding:0cm"><b>From:
</b><a href="mailto:hobe69@hotmail.com"
moz-do-not-send="true">Bela H</a><br>
<b>Sent: </b>Tuesday, 11 October 2022 08:09<br>
<b>To: </b><a href="mailto:bogdan@opensips.org"
moz-do-not-send="true">Bogdan-Andrei Iancu</a>; <a
href="mailto:users@lists.opensips.org"
moz-do-not-send="true">
OpenSIPS users mailling list</a><br>
<b>Subject: </b>Re: [OpenSIPS-Users] Request-Disposition:
no-fork</p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks Bogdan!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">However, I am talking about serial forking,
call forwarding busy/no answer scenario.<o:p></o:p></p>
<p class="MsoNormal">Is there a way to avoid that in the cfg
without messing up with the to tags?<o:p></o:p></p>
<pre><span style="font-family:"Calibri",sans-serif">How do I achieve “</span>proxy to only a single address ("no-fork")”? </pre>
<p class="MsoNormal">According to fork-directive in
<a class="moz-txt-link-freetext" href="https://www.rfc-editor.org/rfc/rfc3841#section-9.1">https://www.rfc-editor.org/rfc/rfc3841#section-9.1</a>.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
<p class="MsoNormal">Bela<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From: </b><a
href="mailto:bogdan@opensips.org" moz-do-not-send="true">Bogdan-Andrei
Iancu</a><br>
<b>Sent: </b>Tuesday, 11 October 2022 01:49<br>
<b>To: </b><a href="mailto:users@lists.opensips.org"
moz-do-not-send="true">OpenSIPS users mailling list</a>;
<a href="mailto:hobe69@hotmail.com" moz-do-not-send="true">Bela
H</a><br>
<b>Subject: </b>Re: [OpenSIPS-Users] Request-Disposition:
no-fork<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-family:"Courier New"">Hi Bela,<br>
<br>
What you are trying to do (messing with the TO-tags) is a
bad idea, as you will be breaking the upstream parallel
forking.<br>
<br>
If the GW does not support forking, what you can do is to
avoid doing parallel forking in your cfg (like when routing
to users via lookup). You do not need any special support.<br>
<br>
Best regards,</span><o:p></o:p></p>
<pre>Bogdan-Andrei Iancu</pre>
<pre><o:p> </o:p></pre>
<pre>OpenSIPS Founder and Developer</pre>
<pre> <a href="https://www.opensips-solutions.com" moz-do-not-send="true">https://www.opensips-solutions.com</a></pre>
<pre>OpenSIPS Summit 27-30 Sept 2022, Athens</pre>
<pre> <a href="https://www.opensips.org/events/Summit-2022Athens/" moz-do-not-send="true">https://www.opensips.org/events/Summit-2022Athens/</a></pre>
<div>
<p class="MsoNormal">On 9/29/22 7:10 AM, Bela H wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal">Hello,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">I have call forwarding busy/no answer
scenario: A number is from a gateway, B and C numbers are
our own subs.<o:p></o:p></p>
<p class="MsoNormal">The gateway is sending us the INVITE
message with “Request-Disposition: no-fork” header field.<o:p></o:p></p>
<p class="MsoNormal">That means we must use one dialog for the
mentioned scenario.<o:p></o:p></p>
<p class="MsoNormal">Currently the To tag we are sending to
the GW in the first 180 ringing/181 Call is being forwarded
messages are different to the To tag in the second 180
ringing and 200 OK (SDP).<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Gateway OpenSips<o:p></o:p></p>
<p class="MsoNormal"> INVITE<o:p></o:p></p>
<p class="MsoNormal">------------------------------------------><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="text-indent:36.0pt">100 GIVING IT
A TRY<o:p></o:p></p>
<p class="MsoNormal"><--
-----------------------------------------<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> 180 RINGING<o:p></o:p></p>
<p class="MsoNormal"><-
-------------------------------------------<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">181 CALL IS BEING FORWARDED<o:p></o:p></p>
<p class="MsoNormal"><-
-------------------------------------------<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> 180 RINGING<o:p></o:p></p>
<p class="MsoNormal"><-
-------------------------------------------<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> 200 OK (SDP)<o:p></o:p></p>
<p class="MsoNormal"><-
-------------------------------------------<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">What would be the easiest way from
OpenSIPS to send the same To tag (it should be the same from
the first 180 ringing through to the 200 OK) and using one
dialog for this scenario?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
<p class="MsoNormal">Bela<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<pre>_______________________________________________</pre>
<pre>Users mailing list</pre>
<pre><a href="mailto:Users@lists.opensips.org" moz-do-not-send="true">Users@lists.opensips.org</a></pre>
<pre><a 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>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<br>
</body>
</html>