The opensip register module states the following:1.3.23. pn_providers (string)
A list of supported Push Notification providers. While only
three
possible values are defined by RFC 8599 ("apns", "fcm" and
"webpush"),
non-standard values may be specified as well.
Default value is NULL
(not set). 1.3.24.
pn_ct_match_params (string)
The minimally required list of RFC 8599 parameters
(custom ones are
accepted as well) which must be present in a Contact
URI and
identically match an existing binding in order for the
binding
to be refreshed during a SIP re-REGISTER. If at least
one such
parameter is missing from a Contact header field URI,
the module
will fall back to performing regular contact matching.
Note that if all above PN Contact URI parameters match
an existing
binding, the match is considered to be successful
regardless if
other parts of the SIP URI do not match (e.g. hostname,
port,
other URI parameters, etc.).
After calling lookup() or
pn_process_purr(), the above PN-related
parameters will be automatically stripped from the
resulting
Request and Contact URI event parameter, respectively.
Default value is
"pn-provider, pn-prid,
pn-param". https://opensips.org/docs/modules/3.3.x/registrar.htmlLinphone,
depending how far back you go, is not rfc 8599 compliant. It uses a nonstandard
way of supporting push notifications using their own proxy flexisip.The 4.56
version does support the rfc 8599 but it does not do the re-register event that
is required in order to be fully compliant with the rfc and opensips. You will
actually have to compile linphone changing three lines of code to make it do
the REGISTER request. I found that on Google about a year ago (will look for
and send later if you need it). Linphone doesn't support +sip.pnsreg feature so
you will rely on the pn_trigger_interval in opensips (read module link I sent
above regarding it).
-------- Original message --------From: HS <[email protected]> Date: 2/22/23
1:56 AM (GMT-06:00) To: OpenSIPS users mailling list
<[email protected]> Subject: [OpenSIPS-Users] Push Notification -
Location table has flag 0 v3.3 Hi all.I am starting to implement push
notifications on Opensips v3.3, using an old Linphone version that sends out
parameters in the following format:pn-type instead of pn-providerfirebase
instead of fcmapp-id
instead of
pn-parampn-tok
instead of
pn-pridLocation table has flag 0 (I think it should be 4). I tried adding
pn-type, app-id in pn_ct_match_params, but didn't seem to work (flag is still
0).modparam("registrar", "pn_providers", "apns, fcm,
firebase")modparam("registrar", "pn_ct_match_params", "pn-provider, pn-prid,
pn-param, pn-type, pn-tok, app-id")Is v3.3 incompatible with the old
nomenclature or am I missing something?Thanks.
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
