<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="monospace">Hi Giovanni, Johan, Antonios,<br>
<br>
Talking about the PRACK, yes, it sounds like a good idea to get
such support in the dialog module. And yes, we need to start with
drafting the functionality to be provided - should we do this over
the #2076 github ticket (mentioned by Giovanni) or open new thread
here, backed-up by a GH wiki page to aggregate the requirements ?<br>
<br>
Best regards,</font><br>
<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>
<a class="moz-txt-link-freetext" href="https://www.siphub.com">https://www.siphub.com</a></pre>
<div class="moz-cite-prefix">On 14.11.2025 11:30, Giovanni
Maruzzelli wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALXCt0pZ8JPd=aB0cz_+By_h01Ojn2MD1F5+HdzmBDoM4jPLAg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>> It really is a mess, to me it seems that IMS guys are
scared of rtp</div>
<div>+1 it is an endpoint thing, trunk providers are wrong to
ask for it (what do they get from it?)<br>
</div>
<div><br>
</div>
<div>when you (trunk provider) know that the phone is actually
ringing, what do you gain? It has meaning when you control the
whole chain, end-to-end (carriers, IMS) not at all for
deskphone->itsp->trunk->whatever->carrier->endphone</div>
<div><br>
</div>
<div>But I know they (trunk providers) start to *REQUIRE* PRACK</div>
<div><br>
</div>
<div>So, probably a module, or an extension of an existing
module, can be warranted and welcome</div>
<div><br>
</div>
<div>Possibly on 3.6.X (that's the last LTS of the 3.0.0 series)</div>
<div><br>
</div>
<div>Let's open a thread on what functionalities can be useful
in it?</div>
<div><br>
</div>
<div>-giovanni</div>
<div><br>
</div>
<br>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr" class="gmail_attr">On Fri, Nov 14, 2025 at
10:21 AM Johan De Clercq <<a
href="mailto:Johan@democon.be" moz-do-not-send="true"
class="moz-txt-link-freetext">Johan@democon.be</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">+1. I totally agree with you. <br>
<div>It really is a mess, to me it seems that IMS guys are
scared of rtp. </div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Op vr 14 nov 2025 om
10:03 schreef Walter Schober <<a
href="mailto:walter.schober@neotel.at" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">walter.schober@neotel.at</a>>:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div lang="DE">
<div>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,sans-serif">Hi!</span></p>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,sans-serif"> </span></p>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,sans-serif" lang="EN-US">I
also want to point out that its not done with
PRACK handling alone. Followup (multiple)
UPDATE with codec changes must be handled,
too. Sometimes that lead into
AMR(WB)/PCMA/G722/OPUS transcoding in early
state. Including all the DTMF PT issues.</span></p>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,sans-serif" lang="EN-US">It is
definitely a endpoint / softswitch feature.
</span></p>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,sans-serif" lang="EN-US"> </span></p>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,sans-serif" lang="EN-US">I
know those ignorant IMS guys pushing out their
internal mess to plain RFC3261 interconnects
and forcing tasks previously done by an MSC to
the rest of the world.</span></p>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,sans-serif" lang="EN-US"> </span></p>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,sans-serif" lang="EN-US">Br</span></p>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,sans-serif" lang="EN-US">Walter
</span></p>
<p class="MsoNormal"><span
style="font-size:11pt;font-family:Calibri,sans-serif" lang="EN-US"> </span></p>
<div
style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:11pt;font-family:Calibri,sans-serif">Von:</span></b><span
style="font-size:11pt;font-family:Calibri,sans-serif"> Users <<a
href="mailto:users-bounces@lists.opensips.org" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">users-bounces@lists.opensips.org</a>>
<b>Im Auftrag von </b>Johan De Clercq<br>
<b>Gesendet:</b> Donnerstag, 13. November
2025 16:29<br>
<b>An:</b> <a
href="mailto:gmaruzz@opentelecom.it"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">gmaruzz@opentelecom.it</a>;
OpenSIPS users mailling list <<a
href="mailto:users@lists.opensips.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">users@lists.opensips.org</a>><br>
<b>Betreff:</b> Re: [OpenSIPS-Users] 100rel
/ PRACK Interworking</span></p>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">Giovanni on a side note,
what to do with update ? do you handle it
locally or do you forward it to your endpoint
? </p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">BR, Johan. </p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">Op do 13 nov 2025 om
15:54 schreef Giovanni Maruzzelli <<a
href="mailto:gmaruzz@gmail.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">gmaruzz@gmail.com</a>>:</p>
</div>
<blockquote
style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">Antonio, you may want
to update this feature request from
Johan: <a
href="https://github.com/OpenSIPS/opensips/issues/2076" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/OpenSIPS/opensips/issues/2076</a></p>
</div>
<p class="MsoNormal"> <br>
</p>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
</body>
</html>