The Contact hdr is not relevant for TM, still it is if you are using
nathelper (for pinging) or dialog support with topo hiding (where the Ct
must be retained).
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 15.01.
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 registrati
Thanks,
I've tried to use them, but seems they are taking for both expressions,
regex and glob not looking in Header values, but names only
When looking at the code, my suspicion getting stronger
https://github.com/OpenSIPS/opensips/blob/224a3236cbeaeb06a897cb3beab8c3a0c3d5903f/modules/sipmsg
Thank you Bogdan,
It seems that replacing remove_hf with uac_replace_from has resolved the
issue.
Just a quick question: if I use remove_hf("Contact") during INVITE, will TM
become aware of this change?
Regards,
Jason
On Fri, 5 Jan 2024 at 23:55, Bogdan-Andrei Iancu
wrote:
> Hi Jason,
>
> Fo
hi all,
for your information:
**Sending a push notification to an iOS device using a Bash script**
https://medium.com/@egzon.arifi/sending-a-push-notification-to-an-ios-device-using-a-bash-script-96c056c1544c
I hope the pn in opensips only requires the route to the apn:
https://api.development.pu
Adrian, thank you for the explanation. It is clear to me now. I will firstly go
with a solution completely within openSIPS.
Regards,
Ronald
January 15, 2024 at 8:59 AM, "Adrian Georgescu" wrote:
>
> OpenSIPS handles the SIP traffic, of course. The push server just handles
> multiple comb
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
#
Hello Igor,
these functions - isn't it what you need?
remove_hf_re(hname_expr) [1]
remove_hf_glob(hname_pattern) [2]
1. https://opensips.org/docs/modules/3.4.x/sipmsgops.html#func_remove_hf_re
2. https://opensips.org/docs/modules/3.4.x/sipmsgops.html#func_remove_hf_glob
--
best regards, Alexe
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
OpenSIPS handles the SIP traffic, of course. The push server just handles
multiple combinations of apps/ push services in an easier way. You could do a
lot or all that its needed just from within OpenSIPS but as the number of
combinations of apps and services grow another layer of abstraction ma
Hi Bogdan,
Thanks for your answer.
Issue opened : #3285
Regards,
Guillaume Desgeorge
De : Bogdan-Andrei Iancu
Envoyé : mercredi 10 janvier 2024 17:28
À : OpenSIPS users mailling list ; DESGEORGE
Guillaume INNOV/IT-S
Objet : Re: [OpenSIPS-Users] DNS could not resolve hostname in dispatcher
11 matches
Mail list logo