Re: [OpenSIPS-Users] Implementation of RFC 8599
Hi Volkan, I implemented the scripting from sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-ii/ in opensips 3.4.0. As the send pn to apple or googlei s not defined I fail to get the parameters passed to the send pn to apns script which I also have. I seem to have lost the device-ID in opensips or in any INVITE somewhere as I do not understand the RFC certainly not towards the device_ID or token. Or this ID is stored on registration at the proxy? srcipt to directly talk to apple: https://medium.com/@egzon.arifi/sending-a-push-notification-to-an-ios-device-using-a-bash-script-96c056c1544c Please keep me posted on what you find. Regards, Ronald February 2, 2024 at 6:01 AM, "johan" wrote: > > send a query directly to apple or to google for waking them up. I did > something like that in an external lua script. > > > On 2/02/2024 09:49, Volkan Oransoy wrote: > > > > > > Hi all, > > > > I am working on implementing RFC 8599 and have an architectural question. > > I followed the blog > > posthttps://blog.opensips.org/2020/06/03/sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-ii/ > > and it works. Based on the rfc and the implementation of Opensips, the UA > > should have a valid registration throughout the process. When a lookup > > performed, opensips finds the pn-enabled record, triggers the PN and after > > a re-registration of the UA, it proxies the call. This process works > > without an issue. But when we kill the UA on the client device (the client > > is connected via WSS), after the registration expires, the call can't be > > proxied since there is no registration. > > I want to wake up the UA even if there is no registration on the proxy and > > suspend the call until the UA registers to the system. Should I handle this > > scenario with a custom setup? How do you handle this scenario on your > > setups? Or do I misinterpret the rfc? > > > > Thanks > > > > > > > > > > > > > > Volkan > > > > > > > > > > ___ > > 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
Re: [OpenSIPS-Users] load_balancer usage counter
Hi Callum, I can confirm the module increments its internal load with each call, so you are good to go. Still, I do not understand why using the FS heartbeat here? are the FS servers receiving calls from other destination than OpenSIPS too ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com https://www.siphub.com On 30.01.2024 16:27, Callum Guy wrote: Hi All, I'm implementing the load_balancer module on a very busy system where thousands of calls may arrive in a matter of seconds. The module is configured to receive heartbeats every 1 second from many freeswitch servers, I have this set as a low value to try and keep OpenSIPs up to date with the real call load, as close to real time as possible. All servers exist in a single group "channels" to keep the initial implementation simple. When I kick off the session I use lb_start(1, "channels", "rs") and if that destination fails I use lb_is_started() and lb_next() to select the next destination. With the high call rate I'm concerned that the load values acquired 1 second ago will be used for the entirety of the following second which would likely lead to a highly imbalanced load. If 1000 calls arrive in that second I need them spread evenly over the freeswitch servers which can only happen if OpenSIPs is counting each call as its allocated. My hope is that the module increments its counters each time a call is allocated to a destination; however I have been unable to isolate the line of code which performs this operation so I'm reaching out for confirmation. I can see the module adding the dialogs to profiles and that a separate lb_count_call() method is provided for counting calls but I'm unclear on the exact usage although it certainly encourages me that this counting is taking place somewhere. Thanks for reading, Callum ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] dialog termination.
Hi Johan, That's actually the default behavior if you do not use the "B" flag upon creating the dialog - when the dialog times out, it will be silently discarded from memory. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com https://www.siphub.com On 01.02.2024 18:55, Johan De Clercq wrote: Is there a way to configure dialog module so that it upon timeout it flushes the dialog without sending bye ? ___ 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
Re: [OpenSIPS-Users] Implementation of RFC 8599
send a query directly to apple or to google for waking them up. I did something like that in an external lua script. On 2/02/2024 09:49, Volkan Oransoy wrote: Hi all, I am working on implementing RFC 8599 and have an architectural question. I followed the blog post https://blog.opensips.org/2020/06/03/sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-ii/ and it works. Based on the rfc and the implementation of Opensips, the UA should have a valid registration throughout the process. When a lookup performed, opensips finds the pn-enabled record, triggers the PN and after a re-registration of the UA, it proxies the call. This process works without an issue. But when we kill the UA on the client device (the client is connected via WSS), after the registration expires, the call can't be proxied since there is no registration. I want to wake up the UA even if there is no registration on the proxy and suspend the call until the UA registers to the system. Should I handle this scenario with a custom setup? How do you handle this scenario on your setups? Or do I misinterpret the rfc? Thanks Volkan ___ 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
[OpenSIPS-Users] Implementation of RFC 8599
Hi all, I am working on implementing RFC 8599 and have an architectural question. I followed the blog post https://blog.opensips.org/2020/06/03/sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-ii/ and it works. Based on the rfc and the implementation of Opensips, the UA should have a valid registration throughout the process. When a lookup performed, opensips finds the pn-enabled record, triggers the PN and after a re-registration of the UA, it proxies the call. This process works without an issue. But when we kill the UA on the client device (the client is connected via WSS), after the registration expires, the call can't be proxied since there is no registration. I want to wake up the UA even if there is no registration on the proxy and suspend the call until the UA registers to the system. Should I handle this scenario with a custom setup? How do you handle this scenario on your setups? Or do I misinterpret the rfc? Thanks Volkan ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
