Re: [OpenSIPS-Users] Qrouting : qr_reload --> invalid values with opensips-cli -x mi qr_reload
And for history_span = 60 minutes and for 10307 rules, it takes about 20G of shared memory. Le mer. 3 mars 2021 à 19:59, Abdoul Osséni a écrit : > Hi Chircu, > > Thank you for this fix. > > I notice qrouting module consumes a lot of memory (shared memory) in > proportion to the value of the "history_span" parameter. > For example, for history_span = 30 minutes and for 10307 rules, it takes > about 10G of shared memory. > > select count(*) from dr_rules where sort_alg = "Q"; > +--+ > | count(*) | > +--+ > |10307 | > +--+ > > Regards > Abdoul OSSENI > > Le mer. 3 mars 2021 à 18:58, Liviu Chircu a écrit : > >> On 03.03.2021 19:46, Liviu Chircu wrote: >> > Let's see what this is all about... >> >> Fixed [1] on both master and 3.1! >> >> [1]: https://github.com/OpenSIPS/opensips/commit/39e5dfd6d395 >> >> Cheers, >> >> -- >> Liviu Chircu >> www.twitter.com/liviuchircu | www.opensips-solutions.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
Re: [OpenSIPS-Users] Qrouting : qr_reload --> invalid values with opensips-cli -x mi qr_reload
Hi Chircu, Thank you for this fix. I notice qrouting module consumes a lot of memory (shared memory) in proportion to the value of the "history_span" parameter. For example, for history_span = 30 minutes and for 10307 rules, it takes about 10G of shared memory. select count(*) from dr_rules where sort_alg = "Q"; +--+ | count(*) | +--+ |10307 | +--+ Regards Abdoul OSSENI Le mer. 3 mars 2021 à 18:58, Liviu Chircu a écrit : > On 03.03.2021 19:46, Liviu Chircu wrote: > > Let's see what this is all about... > > Fixed [1] on both master and 3.1! > > [1]: https://github.com/OpenSIPS/opensips/commit/39e5dfd6d395 > > Cheers, > > -- > Liviu Chircu > www.twitter.com/liviuchircu | www.opensips-solutions.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
[OpenSIPS-Users] Qrouting : qr_reload --> invalid values with opensips-cli -x mi qr_reload
Hello Team, opensips-cli -x mi qr_reload takes invalid values when changing default warn_penalty_xxx and crit_penalty_xxx. Examples: -> database values id: 1 profile_name: QOS ROUTING warn_threshold_asr: 0.2 warn_threshold_ccr: 0.2 warn_threshold_pdd: -1 warn_threshold_ast: -1 warn_threshold_acd: 120 crit_threshold_asr: 0.1 crit_threshold_ccr: 0.1 crit_threshold_pdd: -1 crit_threshold_ast: -1 crit_threshold_acd: 30 warn_penalty_asr: 0.7 warn_penalty_ccr: 0.5 warn_penalty_pdd: 0.5 warn_penalty_ast: 0.5 warn_penalty_acd: 0.5 crit_penalty_asr: 0.1 crit_penalty_ccr: 0.05 crit_penalty_pdd: 0.05 crit_penalty_ast: 0.05 crit_penalty_acd: 0.05 When I execute opensips-cli -x mi qr_reload, I got invalid value for all penalities: Mar 3 14:37:54 sd-68704 /usr/local/sbin/opensips[28847]: DBG:qrouting:qr_reload: qr_profile (1, QOS ROUTING) thresholds: [0.20 0.20 -1.00 -1.00 120.00] [0.10 0.10 -1.00 -1.00 30.00] Mar 3 14:37:54 sd-68704 /usr/local/sbin/opensips[28847]: DBG:qrouting:qr_reload: qr_profile (1, QOS ROUTING) penalties: [0.70 0.70 0.70 0.70 0.70] [0.10 0.10 0.10 0.10 0.10] Regards Abdoul. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Qrouting question
Hello, How to ban a gateway for a period? Is it possible to add the band period time to this function func_qr_disable_dst? https://opensips.org/html/docs/modules/3.2.x/qrouting.html#func_qr_disable_dst Regards Abdoul ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip message
Hello Team, Any chance to get an update? Thank you. Abdoul OSSENI Le mer. 18 nov. 2020 à 10:49, Abdoul Osséni a écrit : > Hello, > > When topology_hiding module is enable, we have somes errors: > > Nov 18 10:47:17 sd-105918 /usr/local/sbin/opensips[32484]: > ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip > message: HEP3#004% > Nov 18 10:47:20 sd-105918 /usr/local/sbin/opensips[32486]: > ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip > message: HEP3#002? > Nov 18 10:47:20 sd-105918 /usr/local/sbin/opensips[32486]: > ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip > message: HEP3#002o > Nov 18 10:47:20 sd-105918 /usr/local/sbin/opensips[32486]: > ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip > message: HEP3#002 > Nov 18 10:47:20 sd-105918 /usr/local/sbin/opensips[32486]: > ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip > message: HEP3#002? > Nov 18 10:47:26 sd-105918 /usr/local/sbin/opensips[32484]: > ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip > message: HEP3#002? > Nov 18 10:47:26 sd-105918 /usr/local/sbin/opensips[32484]: > ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip > message: HEP3#004#027 > > It seems this issue was fixed on opensips 3.1.1 but it persists. > > ~# opensips -V > version: opensips 3.1.1 (x86_64/linux) > flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, > Q_MALLOC, F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT > ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, > MAX_URI_SIZE 1024, BUF_SIZE 65535 > poll method support: poll, epoll, sigio_rt, select. > git revision: 229ec0793 > main.c compiled on 22:30:49 Nov 17 2020 with gcc 6.3.0 > > Regards > > > Abdoul OSSENI > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip message
Hello, When topology_hiding module is enable, we have somes errors: Nov 18 10:47:17 sd-105918 /usr/local/sbin/opensips[32484]: ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip message: HEP3#004% Nov 18 10:47:20 sd-105918 /usr/local/sbin/opensips[32486]: ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip message: HEP3#002? Nov 18 10:47:20 sd-105918 /usr/local/sbin/opensips[32486]: ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip message: HEP3#002o Nov 18 10:47:20 sd-105918 /usr/local/sbin/opensips[32486]: ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip message: HEP3#002 Nov 18 10:47:20 sd-105918 /usr/local/sbin/opensips[32486]: ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip message: HEP3#002? Nov 18 10:47:26 sd-105918 /usr/local/sbin/opensips[32484]: ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip message: HEP3#002? Nov 18 10:47:26 sd-105918 /usr/local/sbin/opensips[32484]: ERROR:topology_hiding:topo_callid_post_raw: could not parse resulted sip message: HEP3#004#027 It seems this issue was fixed on opensips 3.1.1 but it persists. ~# opensips -V version: opensips 3.1.1 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll, sigio_rt, select. git revision: 229ec0793 main.c compiled on 22:30:49 Nov 17 2020 with gcc 6.3.0 Regards Abdoul OSSENI ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Question about qrouting module
Hello Liviu,
Thank you for your mail.
If I understand well, with dynamic-weights algorithm, for example if I set:
- warn_threshold_asr = 40
- warn_penalty_asr = 1
So, if the gateway defined on each rule has an ASR < 40, so the gateway
will have a penality = 1.
and when I call do_routing() function, qrouting choose the gw that has the
lowest score.
am I right?
Regards
Abdoul.
https://www.africallshop.com/
Le jeu. 27 févr. 2020 à 16:45, Liviu Chircu a écrit :
> On 27.02.2020 17:26, Abdoul Osséni wrote:
>
> I want to test qrouting module.
> Do you have some qrouting configs examples?
> Regards
>
> Hey, Abdoul!
>
> It's quite an "out-of-the-box" solution, you'd be surprised. Here are
> some provisioning tips:
>
> * provision any qrouting profiles you want to play with in the
> "qr_profiles" table [1]
> * in dr_rules, make sure to set the "sort_alg" column to 'Q' in order to
> enable qrouting for each rule
> * in dr_rules, for each 'Q'-enabled rule, set the "sort_profile" to your
> desired profile "id" taken from the "qr_profiles" table
>
> From here on, it's just a matter of loading up the modules and setting up
> the "db_url" modparams. The modules will complain if something is missing
> and tell you what to load anyway! :)
>
> Regarding the script: nothing changes. Just call do_routing() [2] as
> usual, and it will both collect stats and sort the destinations based on
> quality. If you want to integrate with custom stats, check out the module
> docs [3], there is plenty of help. Below is the module configuration --
> everything else is just drouting!
>
> Best regards,
>
> [1]:
> https://github.com/OpenSIPS/opensips/blob/master/scripts/mysql/qrouting-create.sql
>
> [2]: https://opensips.org/docs/modules/3.1.x/drouting.html#func_do_routing
>
> [3]: https://opensips.org/docs/modules/3.1.x/qrouting.html
>
> --- qrouting.cfg
>
> loadmodule "db_mysql.so"
>
> loadmodule "drouting.so"
> modparam("drouting", "use_partitions", 1)
> modparam("drouting", "rule_id_avp", "$avp(ruleid)")
> modparam("drouting", "gw_id_avp", "$avp(gwid)")
> modparam("drouting", "db_partitions_url",
> "mysql://root:xx@10.0.0.10/opensips"
> )
>
> loadmodule "qrouting.so"
> modparam("qrouting", "algorithm", "dynamic-weights")
> modparam("qrouting", "history_span", 30)
> modparam("qrouting", "extra_stats", "+mos/1; +r_factor/1")
>
> # for fast testing
> modparam("qrouting", "min_samples_asr", 0)
> modparam("qrouting", "min_samples_ccr", 0)
> modparam("qrouting", "min_samples_pdd", 0)
> modparam("qrouting", "min_samples_ast", 0)
> modparam("qrouting", "min_samples_acd", 0)
> modparam("qrouting", "decimal_digits", 3)
>
> modparam("qrouting", "db_url",
> "mysql://root:xx@10.0.0.10/opensips"
> )
>
> --
> Liviu Chircuwww.twitter.com/liviuchircu | www.opensips-solutions.com
>
> OpenSIPS Summit, Amsterdam, May 2020
> www.opensips.org/events
> OpenSIPS Bootcamp, Miami, March 2020
> www.opensips.org/training
>
> ___
> 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] Question about qrouting module
Hello, I want to test qrouting module. Do you have some qrouting configs examples? Regards Abdoul OSSENI https://www.africallshop.com/ Le jeu. 13 févr. 2020 à 15:15, Liviu Chircu a écrit : > On 13.02.2020 16:02, Abdoul Osséni wrote: > > Congratulations for the work done. In my opinion, it is a big feature. > Thank you! Over the years, there were lots of discussions on this > topic. To quote Linus > Torvalds: "Talk is cheap. Show me the code." -- that'spretty much what > we finally decided to do. > > > I have a question about replication of qmodule data (signaling > > statistics) in a Opensips cluster. > > If I have 2 active nodes in the cluster. Is the both nodes will share > > qmodule data? > > Is it done automatically or I need to make something ? > > The qrouting module is currently not cluster aware, so no qrouting > statistics will be shared > between your nodes. The gatewaydisabling logic [1] is not even restart > persistent, so there are > plentyof work and ideas to put into the module! > > [1]: > https://opensips.org/docs/modules/3.1.x/qrouting.html#func_qr_disable_dst > > -- > Liviu Chircu > www.twitter.com/liviuchircu | www.opensips-solutions.com > > OpenSIPS Summit, Amsterdam, May 2020 >www.opensips.org/events > OpenSIPS Bootcamp, Miami, March 2020 >www.opensips.org/training > > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Question about qrouting module
Hello team, I just read your works ( https://blog.opensips.org/2020/02/13/quality-based-pstn-routing-in-opensips-3-1-lts/) about grouting module. Congratulations for the work done. In my opinion, it is a big feature. I have a question about replication of qmodule data (signaling statistics) in a Opensips cluster. If I have 2 active nodes in the cluster. Is the both nodes will share qmodule data? Is it done automatically or I need to make something ? Regards Abdoul OSSENI AfriCallShop: https://www.africallshop.com/ ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] How to check the transport of the RTP sessions?
Hello, I try to detect the transport of the RTP session. Examples:detect if - RTP/SAVP - RTP/SAVPF - RTP/AVP - RTP/AVPF Can you help me? Regards Abdoul AfriCallShop https://www.africallshop.com/ ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Opensips3: segfaults
Hi, New crash on opensips3. Syslog: May 4 00:10:00 sd-131841 /usr/local/sbin/opensips[20910]: INFO:core:handle_sigs: child process 20937 exited by a signal 11 May 4 00:10:00 sd-131841 /usr/local/sbin/opensips[20910]: INFO:core:handle_sigs: core was generated May 4 00:10:00 sd-131841 /usr/local/sbin/opensips[20910]: INFO:core:handle_sigs: terminating due to SIGCHLD May 4 00:10:00 sd-131841 /usr/local/sbin/opensips[20912]: INFO:core:sig_usr: signal 15 received Crashdump: Please find attached. Thanks. Abdoul OSSENI Ingénieur DevOps chez Néo-Soft Co-Fondateur de ON SERVICES Tél : +33 601 135 167 Le mar. 23 avr. 2019 à 17:40, Abdoul Osséni a écrit : > Hello, > > I am testing Opensips3 (last commit from github) and I encounter an issue: > > dmesg: > [Tue Apr 23 17:03:27 2019] traps: opensips[16387] general protection > ip:7f86ed1a2676 sp:7ffef01c70b8 error:0 > > below is the log of opensips > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16387]: > CRITICAL:core:sig_usr: segfault in process pid: 16387, id: 28 > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:handle_sigs: child process 16387 exited by a signal 11 > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:handle_sigs: core was not generated > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:handle_sigs: terminating due to SIGCHLD > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16360]: > INFO:core:sig_usr: signal 15 received > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 7(16366) [SIP receiver > udp:x.x.x.x:5060] terminated, still waiting for 27 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16362]: > INFO:core:sig_usr: signal 15 received > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 3(16362) [timer] terminated, still > waiting for 26 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 5(16364) [SIP receiver > udp:x.x.x.x:5060] terminated, still waiting for 25 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 6(16365) [SIP receiver > udp:x.x.x.x:5060] terminated, still waiting for 24 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 12(16371) [SIP receiver > hep_udp:x.x.x.x:6060] terminated, still waiting for 23 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 14(16373) [SIP receiver > hep_udp:x.x.x.x:6060] terminated, still waiting for 22 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 15(16374) [SIP receiver > hep_udp:x.x.x.x:6060] terminated, still waiting for 21 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 17(16376) [SIP receiver > hep_udp:x.x.x.x:6060] terminated, still waiting for 20 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 18(16377) [SIP receiver > hep_udp:x.x.x.x:6060] terminated, still waiting for 19 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 19(16378) [SIP receiver > hep_udp:x.x.x.x:6060] terminated, still waiting for 18 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16361]: > INFO:core:sig_usr: signal 15 received > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 2(16361) [time_keeper] terminated, > still waiting for 17 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 20(16379) [TCP receiver] terminated, > still waiting for 16 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 21(16380) [TCP receiver] terminated, > still waiting for 15 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 22(16381) [TCP receiver] terminated, > still waiting for 14 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 23(16382) [TCP receiver] terminated, > still waiting for 13 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 24(16383) [TCP receiver] terminated, > still waiting for 12 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 25(16384) [TCP receiver] terminated, > still waiting for 11 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 26(16385)
Re: [OpenSIPS-Users] Opensips3: segfaults
:N:rRvdDFEVhw:t:u:g:p:P:G:W:o:a:k:s:" ret = -1 seed = 3719096875 rfd = 3 __FUNCTION__ = "main" I hope it will help. Abdoul OSSENI Ingénieur DevOps chez Néo-Soft Co-Fondateur de ON SERVICES Tél : +33 601 135 167 Le mar. 23 avr. 2019 à 18:35, Bogdan-Andrei Iancu a écrit : > Hi Abdoul, > > Unfortunately without the corefile, it is almost impossible to > troubleshoot this. > > For the future, see > https://opensips.org/Documentation/TroubleShooting-Crash to understand > how to properly get the core files. > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 04/23/2019 06:40 PM, Abdoul Osséni wrote: > > Hello, > > I am testing Opensips3 (last commit from github) and I encounter an issue: > > dmesg: > [Tue Apr 23 17:03:27 2019] traps: opensips[16387] general protection > ip:7f86ed1a2676 sp:7ffef01c70b8 error:0 > > below is the log of opensips > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16387]: > CRITICAL:core:sig_usr: segfault in process pid: 16387, id: 28 > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:handle_sigs: child process 16387 exited by a signal 11 > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:handle_sigs: core was not generated > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:handle_sigs: terminating due to SIGCHLD > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16360]: > INFO:core:sig_usr: signal 15 received > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 7(16366) [SIP receiver > udp:x.x.x.x:5060] terminated, still waiting for 27 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16362]: > INFO:core:sig_usr: signal 15 received > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 3(16362) [timer] terminated, still > waiting for 26 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 5(16364) [SIP receiver > udp:x.x.x.x:5060] terminated, still waiting for 25 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 6(16365) [SIP receiver > udp:x.x.x.x:5060] terminated, still waiting for 24 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 12(16371) [SIP receiver > hep_udp:x.x.x.x:6060] terminated, still waiting for 23 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 14(16373) [SIP receiver > hep_udp:x.x.x.x:6060] terminated, still waiting for 22 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 15(16374) [SIP receiver > hep_udp:x.x.x.x:6060] terminated, still waiting for 21 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 17(16376) [SIP receiver > hep_udp:x.x.x.x:6060] terminated, still waiting for 20 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 18(16377) [SIP receiver > hep_udp:x.x.x.x:6060] terminated, still waiting for 19 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 19(16378) [SIP receiver > hep_udp:x.x.x.x:6060] terminated, still waiting for 18 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16361]: > INFO:core:sig_usr: signal 15 received > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 2(16361) [time_keeper] terminated, > still waiting for 17 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 20(16379) [TCP receiver] terminated, > still waiting for 16 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 21(16380) [TCP receiver] terminated, > still waiting for 15 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 22(16381) [TCP receiver] terminated, > still waiting for 14 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 23(16382) [TCP receiver] terminated, > still waiting for 13 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: process 24(16383) [TCP receiver] terminated, > still waiting for 12 more > Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: > INFO:core:shutdown_opensips: proces
[OpenSIPS-Users] Opensips3: segfaults
Hello, I am testing Opensips3 (last commit from github) and I encounter an issue: dmesg: [Tue Apr 23 17:03:27 2019] traps: opensips[16387] general protection ip:7f86ed1a2676 sp:7ffef01c70b8 error:0 below is the log of opensips Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16387]: CRITICAL:core:sig_usr: segfault in process pid: 16387, id: 28 Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:handle_sigs: child process 16387 exited by a signal 11 Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:handle_sigs: core was not generated Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:handle_sigs: terminating due to SIGCHLD Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16360]: INFO:core:sig_usr: signal 15 received Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 7(16366) [SIP receiver udp:x.x.x.x:5060] terminated, still waiting for 27 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16362]: INFO:core:sig_usr: signal 15 received Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 3(16362) [timer] terminated, still waiting for 26 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 5(16364) [SIP receiver udp:x.x.x.x:5060] terminated, still waiting for 25 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 6(16365) [SIP receiver udp:x.x.x.x:5060] terminated, still waiting for 24 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 12(16371) [SIP receiver hep_udp:x.x.x.x:6060] terminated, still waiting for 23 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 14(16373) [SIP receiver hep_udp:x.x.x.x:6060] terminated, still waiting for 22 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 15(16374) [SIP receiver hep_udp:x.x.x.x:6060] terminated, still waiting for 21 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 17(16376) [SIP receiver hep_udp:x.x.x.x:6060] terminated, still waiting for 20 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 18(16377) [SIP receiver hep_udp:x.x.x.x:6060] terminated, still waiting for 19 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 19(16378) [SIP receiver hep_udp:x.x.x.x:6060] terminated, still waiting for 18 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16361]: INFO:core:sig_usr: signal 15 received Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 2(16361) [time_keeper] terminated, still waiting for 17 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 20(16379) [TCP receiver] terminated, still waiting for 16 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 21(16380) [TCP receiver] terminated, still waiting for 15 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 22(16381) [TCP receiver] terminated, still waiting for 14 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 23(16382) [TCP receiver] terminated, still waiting for 13 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 24(16383) [TCP receiver] terminated, still waiting for 12 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 25(16384) [TCP receiver] terminated, still waiting for 11 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 26(16385) [TCP receiver] terminated, still waiting for 10 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 27(16386) [TCP receiver] terminated, still waiting for 9 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 29(16388) [TCP main] terminated, still waiting for 8 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 16(16375) [SIP receiver hep_udp:x.x.x.x:6060] terminated, still waiting for 7 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 4(16363) [SIP receiver udp:x.x.x.x:5060] terminated, still waiting for 6 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 11(16370) [SIP receiver udp:x.x.x.x:5060] terminated, still waiting for 5 more Apr 23 17:04:11 sd-152273 /usr/local/sbin/opensips[16359]: INFO:core:shutdown_opensips: process 13(16372) [SIP receiver hep_udp:x.x.x.x:6060]
[OpenSIPS-Users] sst module : update method instead of invite
Hello group, Is is possible to configure sst module to send update method intead invite method? Why? because a gateway does not support in dialog INVITE but only INVITE. Thanks. Abdoul. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Round Robin alg and drouting
With cachedb_local module, I was able to implement this. Regards Abdoul OSSENI 2018-06-05 16:16 GMT+02:00 Abdoul Osséni : > Hello list, > > Since a few days, I am looking for a solution to my problem without > success. > > Any help will be appreciated. > > My question is how implemented round robin algo with drouting? > > For each prefix in dr_rule table, I try to make: > >1. first call -> gw1 >2. next call -> gw2 >3. after call -> gw1 >4. next call -> gw2 > > Regards > > Abdoul OSSENI > Ingénieur DevOps chez Néo-Soft > Co-Fondateur de ON SERVICES > Tél : +33 601 135 167 > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Round Robin alg and drouting
Hello list, Since a few days, I am looking for a solution to my problem without success. Any help will be appreciated. My question is how implemented round robin algo with drouting? For each prefix in dr_rule table, I try to make: 1. first call -> gw1 2. next call -> gw2 3. after call -> gw1 4. next call -> gw2 Regards Abdoul OSSENI Ingénieur DevOps chez Néo-Soft Co-Fondateur de ON SERVICES Tél : +33 601 135 167 ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] timeout between the invite and the sip message after the "180 trying"?
Yes between 100 trying or 180 ringing? or between 100 trying or 183 sdp progress? Abdoul 2018-04-25 15:10 GMT+02:00 Russell Treleaven <rtrelea...@bunnykick.ca>: > Do you mean 100 trying or 180 ringing? > > On Wed, Apr 25, 2018, 9:03 AM Abdoul Osséni <abdoul.oss...@gmail.com> > wrote: > >> Hello list, >> >> Is it possible to set the timeout between the invite and the sip message >> after the "180 trying"? >> >> Best regards >> Abdoul. >> ___ >> 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 > > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] timeout between the invite and the sip message after the "180 trying"?
Hello list, Is it possible to set the timeout between the invite and the sip message after the "180 trying"? Best regards Abdoul. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] drouting: need more information about a feature
Hi, I hope, it will be completed in the future. Thank you for your feedback. Abdoul OSSENI Ingénieur DevOps chez Néo-Soft Co-Fondateur de ON SERVICES Tél : +33 601 135 167 Le jeu. 12 avr. 2018 à 22:03, Bogdan-Andrei Iancu <bog...@opensips.org> a écrit : > Hi, > > This module was never completed and never pushed to the public tree. Maybe > in the future :) > > Best regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > OpenSIPS Summit 2018 > http://www.opensips.org/events/Summit-2018Amsterdam > > On 04/09/2018 11:53 AM, Abdoul Osséni wrote: > > Hello Dear list, > > According to this email > https://opensips.org/pipermail/users/2014-September/029817.html, drouting > can reorder the gateways according PDD, ASR and ACD stats. > > Can you explain me how it works and how can I enable this feature? > > Thank you for your works. > > Abdoul. > > > ___ > Users mailing > listUsers@lists.opensips.orghttp://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] ASR & ACR per country/destination
Hi Dan, Thank you for your feedback. If I understood, I must: - Install cdrstats? - use cgrates module with the function cgrates_acc? How can I install only cdrstats? Thank you. Abdoul OSSENI Ingénieur DevOps chez Néo-Soft Le mar. 3 avr. 2018 à 20:55, Dan-Cristian Bogos <danb.li...@gmail.com> a écrit : > Hi Abdoul, > > If no other/simpler way to do it, you can use StatS subsystem in CGRateS > on top of CDRs coming from OpenSIPS to aggregate stats on the filter you > need. On top of that you have another subsystem, ThresholdS, which can > notify you when your supplier starts misbehaving. > > DanB > > Message: 1 >> Date: Fri, 30 Mar 2018 17:06:23 + >> From: Abdoul Osséni <abdoul.oss...@gmail.com> >> To: OpenSIPS users mailling list <Users@lists.opensips.org> >> Subject: [OpenSIPS-Users] ASR & ACR per country/destination >> Message-ID: >> <CABc7nxuFFOM_TO_w+acfnn__w7MRQGbufs6hOkuSzfsReZ=+ >> w...@mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" >> >> Hello dear list, >> >> I am looking for a tool that will provide me call statistics (ASR and ACD) >> by destination/country with alerting by emails. >> I try to detect when a sip provider does not work well in order to route >> the traffic to another sip provider. >> >> Thank you. >> >> Abdoul OSSENI >> AfriCallShop >> -- next part -- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.opensips.org/pipermail/users/attachments/20180330/a966401d/attachment-0001.html >> > >> >> -- >> >> Subject: Digest Footer >> >> ___ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> -- >> >> End of Users Digest, Vol 116, Issue 68 >> ** >> > ___ > 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] drouting: need more information about a feature
Hello Dear list, According to this email https://opensips.org/pipermail/users/2014-September/029817.html, drouting can reorder the gateways according PDD, ASR and ACD stats. Can you explain me how it works and how can I enable this feature? Thank you for your works. Abdoul. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] ASR & ACR per country/destination
Hello dear list, I am looking for a tool that will provide me call statistics (ASR and ACD) by destination/country with alerting by emails. I try to detect when a sip provider does not work well in order to route the traffic to another sip provider. Thank you. Abdoul OSSENI AfriCallShop ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Dectect FAS: False Answer Supervision
Thank you for your feedback. Abdoul OSSENI Ingénieur DevOps chez Néo-Soft Co-Fondateur de ON SERVICES Tél : +33 601 135 167 2018-02-05 16:57 GMT+01:00 Bogdan-Andrei Iancu <bog...@opensips.org>: > Hi Abdoul, > > AFAIK, you cannot detect FAS from signaling level. Even by looking at the > RTP level it will be difficult. > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > OpenSIPS Summit 2018 > http://www.opensips.org/events/Summit-2018Amsterdam > > On 02/05/2018 05:02 PM, Abdoul Osséni wrote: > > Hello guys, > > Is there a method to detect FAS (False Answer Supervision) in OpenSips ? > > Regards > > Abdoul OSSENI > Ingénieur DevOps chez Néo-Soft > Co-Fondateur de ON SERVICES > Tél : +33 601 135 167 > > > ___ > Users mailing > listUsers@lists.opensips.orghttp://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] Dectect FAS: False Answer Supervision
Hello guys, Is there a method to detect FAS (False Answer Supervision) in OpenSips ? Regards Abdoul OSSENI Ingénieur DevOps chez Néo-Soft Co-Fondateur de ON SERVICES Tél : +33 601 135 167 ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] False Answer Supervision
Hello guys, Is there a method to detect FAS (False Answer Supervision) in OpenSips ? Regards Abdoul OSSENI Ingénieur DevOps chez Néo-Soft Co-Fondateur de ON SERVICES Tél : +33 601 135 167 ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Asterisk and options
Hello, Is there a tutorial to implement OpenSIPS and Asterisk Realtime Integration but using Asterisk Database? Thanks. Abdoul. ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] LCR based on ACD or Gatework QoS?
Hi, Thank you for your feedback. Regards Abdoul OSSENI 2017-10-26 12:09 GMT+02:00 Bogdan-Andrei Iancu <bog...@opensips.org>: > Hi, > > OpenSIPS does not directly implements are cost or quality related concepts > when comes to routing. What OpenSIPS can do is to route (based on prefixes) > to lists of GWs - see the drouting module. So, what you have to do is to be > sure to properly arrange the GW list to reflect cost or quality. > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 10/26/2017 12:59 PM, Abdoul Osséni wrote: > > Hello all, > > I am new in OpenSIPS. > > I am looking for a LCR based on ACD or Gatework QoS? > > Can we do it with OpenSIPS? > > Thank you in advance for your feedback. > > Regards > Abdoul OSSENI > > > ___ > Users mailing > listUsers@lists.opensips.orghttp://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] LCR based on ACD or Gatework QoS?
Hello all, I am new in OpenSIPS. I am looking for a LCR based on ACD or Gatework QoS? Can we do it with OpenSIPS? Thank you in advance for your feedback. Regards Abdoul OSSENI ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
