Hi rvg,
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()
Hello rvg,
Please find some answers below.
On 09.03.2024 15:46, r...@rvgeerligs.nl wrote:
I still have problems with opensips3.4 push notifications:
Somehow INVITEs keep looping and get rejected.
If the INVITE loops to your server, then you likely have an undesired
t_relay() operation after
Hi,
In the log snippet, I do not see any of the xlogs you have after the
lookup()
Regards
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 09.03.2024 15:46, r...@rvgeerligs.nl wrote:
Hi All,
I still have problems
Adding:
event_route[E_UL_CONTACT_REFRESH]
{
route(pm_send, $(param(uri){param.value,pn-provider}),
$(param(uri){param.value,pn-prid}),
$(param(uri){param.value,pn-param}));
# $callid;
# $param(callid);
}
#--
route [pm_send]
{
# exec(marg.sh)
Hi All,
I still have problems with opensips3.4 push notifications:
Somehow INVITEs keep looping and get rejected.
Code:
...
route{
...
if (has_totag()) {
...
if (!is_method("ACK"))
async (pn_process_purr("location"), resume_route);
...
}
...
# do lookup with method filtering
#--
