Hi Alexey,
I noticed those too, but I do not understand the following code:
event_route [E_UL_CONTACT_REFRESH]
{
route(PN_SEND, $(param(uri){param.value,pn-provider}),
$(param(uri){param.value,pn-prid}),
$(param(uri){param.value,pn-param}));
}
# $param(1) - PN provider
# $param(2) - PN PRID
# $param(3) - PN param
What is this doing? Is the contents of this part lacking? Is it the normal
routing code, but the actual pn send is lacking? How do i write exec(what
client) or rest_client?
route [PN_SEND]
{
# send a PN using, for example, **exec** or **rest_client**
}
# how do we actually send the PN?
Regards,
Ronald
January 15, 2024 at 10:57 AM, "Alexey" <slackway...@gmail.com> wrote:
>
> Hello,
>
> there are two tutorials in the official blog:
>
> part I :
> https://blog.opensips.org/2020/05/07/sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-i/
>
> part II :
> https://blog.opensips.org/2020/06/03/sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-ii/
>
> --
> best regards, Alexey
> https://alexeyka.zantsev.com/
>
> _______________________________________________
> 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
