<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font face="monospace">Hi Ronald,<br>
<br>
Thanks to the "notify_on_event", whenever there is a new
registration (see E_UL_CONTACT_INSERT) for that user (see the
$avp(filter)), the "fork_call" route will be execute and a new
branch (for that call) will be create toward the new registration
- see the t_inject_branches() docs.<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>
<a class="moz-txt-link-freetext" href="https://www.siphub.com">https://www.siphub.com</a></pre>
<div class="moz-cite-prefix">On 15.01.2024 23:12, <a class="moz-txt-link-abbreviated" href="mailto:rvg@rvgeerligs.nl">rvg@rvgeerligs.nl</a>
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:a1babe16207cd061e6a5c6c603981163e8a36e0b@rvgeerligs.nl">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div>Hi openSIPS team,</div>
<div><br>
</div>
<div>I do not understand the documentaion (opensips version 3.4
manual) on the event_routing module.</div>
<div><br>
</div>
<div>The example given 1.6.1 push notification does not seem to do
just that.</div>
<div><br>
</div>
<div>It says:</div>
<div>"</div>
<div>1.6.1. <code class="function">Push Notification</code></div>
<p
style="font-family: Helvetica, Arial; font-size: 12px; text-align: justify; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">We
use<span class="emphasis"><i>notify_on_event</i></span>to
capture the events on new contact registrations for callee. Once
the call is sent to callee, based on the notification (for new
contacts) we inject the newly registered contacts as new
branches in the ongoing transaction.</p>
<p
style="font-family: Helvetica, Arial; font-size: 12px; text-align: justify; color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Schematics
: when we send a call to a user, we subscribe to see any new
contacts being registered by the user. On such a notification,
we add the new contact as a new branch to the ongoing
transaction (ringing) to user.</p>
<div>"</div>
<div>It seems this has to do with notify_on_event.</div>
<div>It may be that the new branches are be added with device
information for the push notification, but I do not see that in
the example given.</div>
<div><br>
</div>
<div>Please advise,</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Ronald Geerligs</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</body>
</html>