<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="monospace">Hi rvg,</font></p>
<p><font face="monospace">I took a look at the logs you provided
and, indeed, your "rvg" AoR has exactly 1 contact registered,
with flags value of "4" in the MI ul_dump, confirming that it is
RFC 8599 PN enabled. Now, regarding the INVITE looping, if you
still have this issue, make sure to avoid t_relay() after the
lookup, as discussed earlier.</font></p>
<p><font face="monospace">Finally, if the call does not connect...
that's because, logically speaking, there is *always* a need to
generate a Push Notification on *every* call attempt. While I
do agree this might be a bit of overkill, it is the only way to
cover all timing-related corner-cases (imagine this race
condition: the phone registered 1.5 minutes ago or earlier, but
the NAT pinhole only lasts for 1 minute, so by the time you
call, it is unreachable). So please make sure to get your <b>PN_SEND</b>
route to actually do the work -- send the PN, wake up the app
and get it to Re-REGISTER, which will cause OpenSIPS to <i>inject</i>
an INVITE over to it.</font></p>
<p><font face="monospace">Alternatively, if you just want to play
with the Push Notification support <i>without sending Push
Notifications</i>... try to bump the registrar's <a
href="https://opensips.org/docs/modules/3.5.x/registrar.html#param_pn_skip_pn_interval">pn_skip_pn_interval</a>
setting to some ridiculous value like <b>600</b> seconds,
causing the module to refrain from mandating any Push
Notification to be sent in the first 10 minutes following the
app's REGISTER, as it delivers calls straight-through to the
app.</font></p>
<p><font face="monospace">Best regards,<br>
</font></p>
<pre class="moz-signature" cols="72">Liviu Chircu
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/liviuchircu">www.twitter.com/liviuchircu</a> | <a class="moz-txt-link-abbreviated" href="http://www.opensips-solutions.com">www.opensips-solutions.com</a>
OpenSIPS Summit 2024 Valencia, May 14-17 | <a class="moz-txt-link-abbreviated" href="http://www.opensips.org/events">www.opensips.org/events</a></pre>
<div class="moz-cite-prefix">On 09.03.2024 15:46, <a class="moz-txt-link-abbreviated" href="mailto:rvg@rvgeerligs.nl">rvg@rvgeerligs.nl</a>
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:a8d2f3e21c206d8e1506055671139205a3f189b0@rvgeerligs.nl">
<div>I still have problems with opensips3.4 push notifications:</div>
<div><br>
</div>
<div>Somehow INVITEs keep looping and get rejected.</div>
</blockquote>
</body>
</html>