Hi Ronald,
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.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 15.01.2024 23:12, r...@rvgeerligs.nl wrote:
Hi openSIPS team,
I do not understand the documentaion (opensips version 3.4 manual) on
the event_routing module.
The example given 1.6.1 push notification does not seem to do just that.
It says:
"
1.6.1. |Push Notification|
We use/notify_on_event/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.
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.
"
It seems this has to do with notify_on_event.
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.
Please advise,
Regards,
Ronald Geerligs
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
