From van_der_starre at compuserve.com Mon Jan 2 15:28:01 2017 From: van_der_starre at compuserve.com (Jaap van der Starre) Date: Mon, 2 Jan 2017 21:28:01 +0100 Subject: [OpenSIPS-Users] opensips-cp missing Message-ID: After upgrade from wheezy to jessie opensips-cp is missing while my grandstream HT503 is still registered to opensips, I cannot use the control panel anymore obviously. Not Found The requested URL /opensips-cp was not found on this server. ------------------------------------------------------------------------ Apache/2.4.10 (Debian) Server at 192.168.2.12 Port 80 My opensips installation is 1.10. Because it is not supported anymore I should at least migrate to 1.11 now. This will only change the database and Script migration. Would it bring back opensips-cp in Apache? jaap -------------- next part -------------- An HTML attachment was scrubbed... URL: From trance_maniak at o2.pl Tue Jan 3 03:13:25 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Tue, 3 Jan 2017 01:13:25 -0700 (MST) Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server Message-ID: <1483431205315-7605411.post@n2.nabble.com> I use Opensips 1.6.2 on my server. I want to add BLF function to it but I don't know how. I have config where I route calls to asterisk. There are tutorials where I can set Opensip Presence Server as standalone, with OpenXcap as well, but there's nowhere config how to set Opensips to work on one machine as Presence Server, and also as a Proxy at same Opensips instance - in one config. How can I make it? Ok, I can set one Opensips as a proxy, and other Opensips (on another machine) as a Presence Server. But how can I connect them so that they work together? -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From razvan at opensips.org Tue Jan 3 03:35:02 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Tue, 3 Jan 2017 10:35:02 +0200 Subject: [OpenSIPS-Users] opensips-cp missing In-Reply-To: References: Message-ID: <29f4d762-df46-0740-3253-c05404a8ea26@opensips.org> Hi, Jaap! How did you initially install opensips CP? Because most likely it is was a manual install, and you will need to restore the apache config file. You can use this example[1]. PS: please subscribe to the mailing list, otherwise you won't get further replies. [1] https://github.com/OpenSIPS/opensips-cp/blob/abafe7503dd8ad089b834cfcb7058deeda30375e/INSTALL#L30 Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/02/2017 10:28 PM, Jaap van der Starre wrote: > > After upgrade from wheezy to jessie opensips-cp is missing > > while my grandstream HT503 is still registered to opensips, I cannot > use the control panel anymore obviously. > > > Not Found > > The requested URL /opensips-cp was not found on this server. > > ------------------------------------------------------------------------ > Apache/2.4.10 (Debian) Server at 192.168.2.12 Port 80 > > My opensips installation is 1.10. > Because it is not supported anymore I should at least migrate to 1.11 now. > This will only change the database and Script migration. > Would it bring back opensips-cp in Apache? > > jaap > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Tue Jan 3 03:40:22 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Tue, 3 Jan 2017 10:40:22 +0200 Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <1483431205315-7605411.post@n2.nabble.com> References: <1483431205315-7605411.post@n2.nabble.com> Message-ID: <4fa36195-2654-2697-ebb1-e55314b58147@opensips.org> Hello! Basically merging the two separate configs together should do the trick. If you follow this[1] example, change your Proxy config as it follows: When an initial INVITE comes in, create the dialog and publish the information: if (is_method("INVITE")) { create_dialog(); # publish for both legs dialoginfo_set("AB"); } When a publish or subscribe methods come in handle them accordingly: ... if (is_method("PUBLISH|SUBSCRIBE")) { route(handle_presence); exit; } ... route[handle_presence] { if(!t_newtran()){ sl_reply_error(); exit; } if (is_method("PUBLISH")) { handle_publish(); } else if (is_method("SUBSCRIBE")) { handle_subscribe(); } exit; } [1] http://www.opensips.org/Documentation/Tutorials-Presence-PuaDialoinfoConfig PS: Please subscribe on the mailing list, otherwise you will loose further replies Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/03/2017 10:13 AM, maatohewetbi wrote: > I use Opensips 1.6.2 on my server. I want to add BLF function to it but I > don't know how. I have config where I route calls to asterisk. There are > tutorials where I can set Opensip Presence Server as standalone, with > OpenXcap as well, but there's nowhere config how to set Opensips to work on > one machine as Presence Server, and also as a Proxy at same Opensips > instance - in one config. How can I make it? Ok, I can set one Opensips as a > proxy, and other Opensips (on another machine) as a Presence Server. But how > can I connect them so that they work together? > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Tue Jan 3 03:44:54 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Tue, 3 Jan 2017 10:44:54 +0200 Subject: [OpenSIPS-Users] opensips for windows In-Reply-To: References: Message-ID: <018d1124-20cd-0547-4bd4-33758b542212@opensips.org> Hi, Mohsin! OpenSIPS was designed to work on Unix systems, I never tried to compile it on Windows. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 12/31/2016 12:32 PM, Mohsin Barbhaiwala wrote: > can this opensips be compiled & run on windows. if so does anybody know ? > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From trance_maniak at o2.pl Tue Jan 3 08:00:15 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Tue, 3 Jan 2017 06:00:15 -0700 (MST) Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <4fa36195-2654-2697-ebb1-e55314b58147@opensips.org> References: <1483431205315-7605411.post@n2.nabble.com> <4fa36195-2654-2697-ebb1-e55314b58147@opensips.org> Message-ID: <1483448415681-7605416.post@n2.nabble.com> It doesn't work. If I call number B, it rings, and BLF LED is blinking, but after picking up the phone, call is without audio and LED is still blinking event I disconnect call. Then If I try to call again, call freezes like if it's routing in loop, and B side doesn't ring at all. I heve to restart Opensips. Here is my config: ................. Modules, general config .................. # ------------------------- request routing logic ------------------- route{ if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; if (nat_uac_test("3")) { if (is_method("REGISTER") || !is_present_hf("Record-Route")) { log("LOG:Someone trying to register from private IP, rewriting\n"); fix_nated_contact(); if ( is_method("INVITE") ) { fix_nated_sdp("1"); }; force_rport(); setbflag(6); setbflag(8); }; }; if (loose_route()) { append_hf("P-hint: rr-enforced\r\n"); if(src_ip == 'YYY.YYY.YYY.YYY'){ route(1); }else{ route(2); } exit; }; if (!is_method("REGISTER")) record_route(); if (!uri==myself) { append_hf("P-hint: outbound\r\n"); if(src_ip == 'YYY.YYY.YYY.YYY'){ route(1); }else{ route(2); } exit; }; if (uri==myself) { if (is_method("REGISTER")) { if (!www_authorize("", "subscriber")) { www_challenge("", "0"); return; }; save("location"); exit; }; lookup("aliases"); if (!uri==myself) { append_hf("P-hint: outbound alias\r\n"); if(src_ip == 'YYY.YYY.YYY.YYY'){ route(1); }else{ route(2); } exit; }; alias_db_lookup("dbaliases","d"); if (!lookup("location")) { route(2); exit; }; }; if (is_method("INVITE")) { create_dialog(); dialoginfo_set(); } if (is_method("PUBLISH|SUBSCRIBE")) { route(handle_presence); exit; } append_hf("P-hint: usrloc applied\r\n"); if(src_ip == 'YYY.YYY.YYY.YYY'){ route(1); }else{ route(2); } } route[handle_presence] { if(!t_newtran()){ sl_reply_error(); exit; } if (is_method("PUBLISH")) { handle_publish(); } else if (is_method("SUBSCRIBE")) { handle_subscribe(); } exit; } route[1] { if (uri=~"[@:](192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.)" && !search("^Route:")){ sl_send_reply("479", "We don't forward to private IP addresses"); exit; }; if (isbflagset(6)) { force_rtp_proxy(); }; t_on_reply("1"); if (!t_relay()) { sl_reply_error(); }; } route[2] { force_rtp_proxy(); rewritehostport ("YYY.YYY.YYY.YYY:xx"); t_relay(); } onreply_route[1] { if (isbflagset(6) && status =~ "(183)|2[0-9][0-9]") { fix_nated_contact(); force_rtp_proxy(); } else if (nat_uac_test("1")) { fix_nated_contact(); }; } -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605416.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From ionutionita at opensips.org Tue Jan 3 10:03:56 2017 From: ionutionita at opensips.org (Ionut Ionita) Date: Tue, 3 Jan 2017 17:03:56 +0200 Subject: [OpenSIPS-Users] OpenSIPS crashes on sip_capture() In-Reply-To: References: Message-ID: <45ab2341-c7ce-5f7c-fb28-c39b763207af@opensips.org> Hi Schneur, I've got a few questions for you: 1) Do you have a separate capturing node, using siptrace for sending and sipcapture for recieving? 2) If so what protocol are you using for sending the packets? Do you use proto_hep? 3) Are you calling sip_capture function in one of your request routes? 4) Can you send me your debug logs? Regards, Ionut Ionita OpenSIPS Developer On 12/29/2016 04:10 PM, Schneur Rosenberg wrote: > I just added modparam("sipcapture", "hep_capture_on", 1) and its not > crashing anymore but now my syslog gets flooded with the following error > > WARNING:sipcapture:w_sip_capture: not a hep message! > > On Thu, Dec 29, 2016 at 3:34 PM, Schneur Rosenberg > > wrote: > > I'm trying to use Homer on OpenSIPS 2.2 and when I call > sip_capture() the system crashes without creating a dump and this > is what I find in my syslog file > > Dec 29 08:28:52 sip /sbin/opensips[15524]: > CRITICAL:sipcapture:ip_addr2a: unknown address family 825112372 > Dec 29 08:28:52 sip /sbin/opensips[15524]: > CRITICAL:sipcapture:ip_addr2a: unknown address family 775435057 > Dec 29 08:28:52 sip kernel: [675596.209597] opensips[15524]: > segfault at 40 ip 00007f361a810e46 sp 00007ffcd8f850a0 error 4 in > sipcapture.so[7f361a7fc000+26000] > > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From vanderstar at solnet.ch Tue Jan 3 10:22:09 2017 From: vanderstar at solnet.ch (Jakob van der Starre) Date: Tue, 3 Jan 2017 16:22:09 +0100 Subject: [OpenSIPS-Users] opensips-cp missing In-Reply-To: <29f4d762-df46-0740-3253-c05404a8ea26@opensips.org> References: <29f4d762-df46-0740-3253-c05404a8ea26@opensips.org> Message-ID: <79e5b3f2-0952-3551-cbc7-7252c2af6ee6@solnet.ch> hello Razvan, I installed opensips manually using the video "2012-05-17 18.02 OpenSIPS Kick Start" because I am not familiar with linux and opensips. I will try your example. Because there were bounces from compuserve.com I changed my email to solnet.ch and subscribed with this new email address but I made an error by still using my old email address. On 1/3/2017 9:35 AM, Răzvan Crainea wrote: > Hi, Jaap! > > How did you initially install opensips CP? Because most likely it is > was a manual install, and you will need to restore the apache config > file. You can use this example[1]. > > PS: please subscribe to the mailing list, otherwise you won't get > further replies. > > [1] > https://github.com/OpenSIPS/opensips-cp/blob/abafe7503dd8ad089b834cfcb7058deeda30375e/INSTALL#L30 > > Best regards, > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > On 01/02/2017 10:28 PM, Jaap van der Starre wrote: >> >> After upgrade from wheezy to jessie opensips-cp is missing >> >> while my grandstream HT503 is still registered to opensips, I cannot >> use the control panel anymore obviously. >> >> >> Not Found >> >> The requested URL /opensips-cp was not found on this server. >> >> ------------------------------------------------------------------------ >> Apache/2.4.10 (Debian) Server at 192.168.2.12 Port 80 >> >> My opensips installation is 1.10. >> Because it is not supported anymore I should at least migrate to 1.11 >> now. >> This will only change the database and Script migration. >> Would it bring back opensips-cp in Apache? >> >> jaap >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 3 16:24:44 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 3 Jan 2017 23:24:44 +0200 Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <1483448415681-7605416.post@n2.nabble.com> References: <1483431205315-7605411.post@n2.nabble.com> <4fa36195-2654-2697-ebb1-e55314b58147@opensips.org> <1483448415681-7605416.post@n2.nabble.com> Message-ID: Were your calls properly working before adding the BLF and presence scripting ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 03.01.2017 15:00, maatohewetbi wrote: > It doesn't work. If I call number B, it rings, and BLF LED is blinking, but > after picking up the phone, call is without audio and LED is still blinking > event I disconnect call. Then If I try to call again, call freezes like if > it's routing in loop, and B side doesn't ring at all. I heve to restart > Opensips. Here is my config: > > ................. > Modules, general config > .................. > > > # ------------------------- request routing logic ------------------- > route{ > if (!mf_process_maxfwd_header("10")) { > sl_send_reply("483","Too Many Hops"); > exit; > }; > > if (msg:len >= 2048 ) { > sl_send_reply("513", "Message too big"); > exit; > }; > > if (nat_uac_test("3")) { > if (is_method("REGISTER") || !is_present_hf("Record-Route")) { > log("LOG:Someone trying to register from private IP, rewriting\n"); > fix_nated_contact(); > if ( is_method("INVITE") ) { > fix_nated_sdp("1"); > }; > force_rport(); > setbflag(6); > setbflag(8); > }; > }; > > if (loose_route()) { > append_hf("P-hint: rr-enforced\r\n"); > > if(src_ip == 'YYY.YYY.YYY.YYY'){ > route(1); > }else{ > route(2); > } > > exit; > }; > > if (!is_method("REGISTER")) > record_route(); > > if (!uri==myself) { > append_hf("P-hint: outbound\r\n"); > > if(src_ip == 'YYY.YYY.YYY.YYY'){ > route(1); > }else{ > route(2); > } > > exit; > }; > > if (uri==myself) { > > if (is_method("REGISTER")) { > if (!www_authorize("", "subscriber")) { > www_challenge("", "0"); > return; > }; > save("location"); > exit; > }; > > lookup("aliases"); > if (!uri==myself) { > append_hf("P-hint: outbound alias\r\n"); > > if(src_ip == 'YYY.YYY.YYY.YYY'){ > route(1); > }else{ > route(2); > } > > exit; > }; > alias_db_lookup("dbaliases","d"); > if (!lookup("location")) { > route(2); > exit; > }; > }; > > > if (is_method("INVITE")) { > create_dialog(); > dialoginfo_set(); > } > if (is_method("PUBLISH|SUBSCRIBE")) { > route(handle_presence); > exit; > } > > > > append_hf("P-hint: usrloc applied\r\n"); > if(src_ip == 'YYY.YYY.YYY.YYY'){ > route(1); > }else{ > route(2); > } > > > } > > > route[handle_presence] > { > if(!t_newtran()){ > sl_reply_error(); > exit; > } > > if (is_method("PUBLISH")) { > handle_publish(); > } else > > if (is_method("SUBSCRIBE")) { > handle_subscribe(); > } > > exit; > } > > > > route[1] > { > if (uri=~"[@:](192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.)" && > !search("^Route:")){ > sl_send_reply("479", "We don't forward to private IP addresses"); > exit; > }; > > if (isbflagset(6)) { > force_rtp_proxy(); > }; > > t_on_reply("1"); > > if (!t_relay()) { > sl_reply_error(); > }; > } > > route[2] { > force_rtp_proxy(); > rewritehostport ("YYY.YYY.YYY.YYY:xx"); > t_relay(); > } > > onreply_route[1] { > if (isbflagset(6) && status =~ "(183)|2[0-9][0-9]") { > fix_nated_contact(); > force_rtp_proxy(); > } else if (nat_uac_test("1")) { > fix_nated_contact(); > }; > } > > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605416.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From m.zielinski at easycall.pl Wed Jan 4 02:57:13 2017 From: m.zielinski at easycall.pl (=?UTF-8?B?TWFyY2luIFppZWxpxYRza2k=?=) Date: Wed, 04 Jan 2017 08:57:13 +0100 Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: References: <1483431205315-7605411.post@n2.nabble.com> <4fa36195-2654-2697-ebb1-e55314b58147@opensips.org> <1483448415681-7605416.post@n2.nabble.com> Message-ID: <586CAAD9.5060906@easycall.pl> That's right. All calls were working well before I add these lines. I noticed, that when I erase these lines *if (is_method("PUBLISH|SUBSCRIBE")) { ** ** route(handle_presence); ** ** exit; ** ** } *problem is gone, and all calls goes smoothly.* * > Were your calls properly working before adding the BLF and presence > scripting ? > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 03.01.2017 15:00, maatohewetbi wrote: >> It doesn't work. If I call number B, it rings, and BLF LED is >> blinking, but >> after picking up the phone, call is without audio and LED is still >> blinking >> event I disconnect call. Then If I try to call again, call freezes >> like if >> it's routing in loop, and B side doesn't ring at all. I heve to restart >> Opensips. Here is my config: >> >> ................. >> Modules, general config >> .................. >> >> >> # ------------------------- request routing logic ------------------- >> route{ >> if (!mf_process_maxfwd_header("10")) { >> sl_send_reply("483","Too Many Hops"); >> exit; >> }; >> if (msg:len >= 2048 ) { >> sl_send_reply("513", "Message too big"); >> exit; >> }; >> >> if (nat_uac_test("3")) { >> if (is_method("REGISTER") || !is_present_hf("Record-Route")) { >> log("LOG:Someone trying to register from private IP, >> rewriting\n"); >> fix_nated_contact(); >> if ( is_method("INVITE") ) { >> fix_nated_sdp("1"); >> }; >> force_rport(); >> setbflag(6); >> setbflag(8); >> }; >> }; >> >> if (loose_route()) { >> append_hf("P-hint: rr-enforced\r\n"); >> >> if(src_ip == 'YYY.YYY.YYY.YYY'){ >> route(1); >> }else{ >> route(2); >> } >> >> exit; >> }; >> >> if (!is_method("REGISTER")) >> record_route(); >> >> if (!uri==myself) { >> append_hf("P-hint: outbound\r\n"); >> >> if(src_ip == 'YYY.YYY.YYY.YYY'){ >> route(1); >> }else{ >> route(2); >> } >> >> exit; >> }; >> >> if (uri==myself) { >> >> if (is_method("REGISTER")) { >> if (!www_authorize("", "subscriber")) { >> www_challenge("", "0"); >> return; >> }; >> save("location"); >> exit; >> }; >> >> lookup("aliases"); >> if (!uri==myself) { >> append_hf("P-hint: outbound alias\r\n"); >> >> if(src_ip == 'YYY.YYY.YYY.YYY'){ >> route(1); >> }else{ >> route(2); >> } >> >> exit; >> }; >> alias_db_lookup("dbaliases","d"); >> if (!lookup("location")) { >> route(2); >> exit; >> }; >> }; >> >> >> if (is_method("INVITE")) { >> create_dialog(); >> dialoginfo_set(); >> } >> if (is_method("PUBLISH|SUBSCRIBE")) { >> route(handle_presence); >> exit; >> } >> >> >> >> append_hf("P-hint: usrloc applied\r\n"); >> if(src_ip == 'YYY.YYY.YYY.YYY'){ >> route(1); >> }else{ >> route(2); >> } >> } >> >> >> route[handle_presence] >> { >> if(!t_newtran()){ >> sl_reply_error(); >> exit; >> } >> >> if (is_method("PUBLISH")) { >> handle_publish(); >> } else >> >> if (is_method("SUBSCRIBE")) { >> handle_subscribe(); >> } >> >> exit; >> } >> >> >> >> route[1] >> { >> if (uri=~"[@:](192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.)" && >> !search("^Route:")){ >> sl_send_reply("479", "We don't forward to private IP addresses"); >> exit; >> }; >> >> if (isbflagset(6)) { >> force_rtp_proxy(); >> }; >> >> t_on_reply("1"); >> >> if (!t_relay()) { >> sl_reply_error(); >> }; >> } >> >> route[2] { >> force_rtp_proxy(); >> rewritehostport ("YYY.YYY.YYY.YYY:xx"); >> t_relay(); >> } >> >> onreply_route[1] { >> if (isbflagset(6) && status =~ "(183)|2[0-9][0-9]") { >> fix_nated_contact(); >> force_rtp_proxy(); >> } else if (nat_uac_test("1")) { >> fix_nated_contact(); >> }; >> } >> >> >> >> >> -- >> View this message in context: >> http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605416.html >> Sent from the OpenSIPS - Users mailing list archive at Nabble.com. >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Z poważaniem Marcin Zieliński easyCALL.PL S.A. ul. Pianistów 2 02-403 Warszawa -------------- next part -------------- An HTML attachment was scrubbed... URL: From rrobson at greenlightcrm.com Wed Jan 4 05:17:16 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Wed, 4 Jan 2017 10:17:16 +0000 Subject: [OpenSIPS-Users] cache_fetch always returning true Message-ID: <756e3b41-9537-104f-0efe-02c6120b32d1@greenlightcrm.com> Hi, I'm Getting a true value back on a cahce fetch when I know the cache is empty and should be returning false. This is causing the AVP's to be NULL and then the subsequent logic fails this is the code if(!cache_fetch("local","customerratelimit_$avp(accountcode)",$avp(customerratelimit)) && cache_fetch("local","customerchannellimit_$avp(accountcode)",$avp(customerchannellimit))){ ### if not cached then get details avp_db_query("select customerratelimit,customerchannellimit from subscriber where username=$avp(accountcode)", "$avp(customerratelimit);$avp(customerchannellimit)"); xlog("rate limit : $avp(customerratelimit)"); xlog("channel limit : $avp(customerchannellimit)"); ### and store them cache_store("local","customerratelimit_$avp(accountcode)","$avp(customerratelimit)",1200); xlog("Caching: local,customerratelimit_$avp(accountcode),$avp(customerratelimit)"); cache_store("local","customerchannellimit_$avp(accountcode)","$avp(customerchannellimit)",1200); xlog("Caching: local,customerchannellimit_$avp(accountcode),$avp(customerchannellimit)"); } xlog("rate limit : $avp(customerratelimit)"); xlog("channel limit : $avp(customerchannellimit)"); There are no values in the cache at this point and taking out the ! gives the same result. this is the only output from the xlog whether the if is negated or not I'd expect the lack of cached values to cause the !false to trigger the db query and then store the values. I never seams to get there so I know there are no values. Regards, -- Richard Robson Greenlight Support 01382 843843 support at greenlightcrm.com From rrobson at greenlightcrm.com Wed Jan 4 05:20:18 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Wed, 4 Jan 2017 10:20:18 +0000 Subject: [OpenSIPS-Users] cache_fetch always returning true In-Reply-To: <756e3b41-9537-104f-0efe-02c6120b32d1@greenlightcrm.com> References: <756e3b41-9537-104f-0efe-02c6120b32d1@greenlightcrm.com> Message-ID: Its version 2.2.2 On 04/01/2017 10:17, Richard Robson wrote: > Hi, > > > I'm Getting a true value back on a cahce fetch when I know the cache > is empty and should be returning false. > > This is causing the AVP's to be NULL and then the subsequent logic > fails > > > this is the code > > > if(!cache_fetch("local","customerratelimit_$avp(accountcode)",$avp(customerratelimit)) > > && > cache_fetch("local","customerchannellimit_$avp(accountcode)",$avp(customerchannellimit))){ > ### if not cached then get details > avp_db_query("select > customerratelimit,customerchannellimit from subscriber where > username=$avp(accountcode)", > "$avp(customerratelimit);$avp(customerchannellimit)"); > > xlog("rate limit : > $avp(customerratelimit)"); > xlog("channel limit : > $avp(customerchannellimit)"); > ### and store them > cache_store("local","customerratelimit_$avp(accountcode)","$avp(customerratelimit)",1200); > > xlog("Caching: > local,customerratelimit_$avp(accountcode),$avp(customerratelimit)"); > cache_store("local","customerchannellimit_$avp(accountcode)","$avp(customerchannellimit)",1200); > > xlog("Caching: > local,customerchannellimit_$avp(accountcode),$avp(customerchannellimit)"); > } > > xlog("rate limit : $avp(customerratelimit)"); > xlog("channel limit : > $avp(customerchannellimit)"); > > There are no values in the cache at this point and taking out the ! > gives the same result. > > > this is the only output from the xlog whether the if is negated or not > > > > > I'd expect the lack of cached values to cause the !false to trigger > the db query and then store the values. I never seams to get there so > I know there are no values. > > > Regards, > -- Richard Robson Greenlight Support 01382 843843 support at greenlightcrm.com From rrobson at greenlightcrm.com Wed Jan 4 05:25:37 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Wed, 4 Jan 2017 10:25:37 +0000 Subject: [OpenSIPS-Users] cache_fetch always returning true SOLVED In-Reply-To: References: <756e3b41-9537-104f-0efe-02c6120b32d1@greenlightcrm.com> Message-ID: I've just spottted MY mistake. The Neagation was only on one of the cache_fetch not Both On 04/01/2017 10:20, Richard Robson wrote: > Its version 2.2.2 > > On 04/01/2017 10:17, Richard Robson wrote: >> Hi, >> >> >> I'm Getting a true value back on a cahce fetch when I know the cache >> is empty and should be returning false. >> >> This is causing the AVP's to be NULL and then the subsequent logic >> fails >> >> >> this is the code >> >> >> if(!cache_fetch("local","customerratelimit_$avp(accountcode)",$avp(customerratelimit)) >> >> && >> cache_fetch("local","customerchannellimit_$avp(accountcode)",$avp(customerchannellimit))){ >> ### if not cached then get details >> avp_db_query("select >> customerratelimit,customerchannellimit from subscriber where >> username=$avp(accountcode)", >> "$avp(customerratelimit);$avp(customerchannellimit)"); >> >> xlog("rate limit : >> $avp(customerratelimit)"); >> xlog("channel limit : >> $avp(customerchannellimit)"); >> ### and store them >> cache_store("local","customerratelimit_$avp(accountcode)","$avp(customerratelimit)",1200); >> >> xlog("Caching: >> local,customerratelimit_$avp(accountcode),$avp(customerratelimit)"); >> cache_store("local","customerchannellimit_$avp(accountcode)","$avp(customerchannellimit)",1200); >> >> xlog("Caching: >> local,customerchannellimit_$avp(accountcode),$avp(customerchannellimit)"); >> } >> >> xlog("rate limit : $avp(customerratelimit)"); >> xlog("channel limit : >> $avp(customerchannellimit)"); >> >> There are no values in the cache at this point and taking out the ! >> gives the same result. >> >> >> this is the only output from the xlog whether the if is negated or not >> >> >> >> >> I'd expect the lack of cached values to cause the !false to trigger >> the db query and then store the values. I never seams to get there so >> I know there are no values. >> >> >> Regards, >> > > -- Richard Robson Greenlight Support 01382 843843 support at greenlightcrm.com From dan at ag-projects.com Wed Jan 4 07:36:04 2017 From: dan at ag-projects.com (Dan Pascu) Date: Wed, 4 Jan 2017 14:36:04 +0200 Subject: [OpenSIPS-Users] Sip trunk and mediaproxy In-Reply-To: <60965dce-31d1-3c01-4ebd-b5f752942107@enigmedia.es> References: <60965dce-31d1-3c01-4ebd-b5f752942107@enigmedia.es> Message-ID: <8C21F721-0675-4F9E-94DE-75727D23E523@ag-projects.com> On 28 Dec 2016, at 13:37, Saioa Perurena wrote: > Hello, > > We already have a communications infrastructure composed by 2 opensips > servers in different domain with 1 mediaproxy each and interconnected by > a TLS trunk. We managed to interconnect both SIP networks and it does > work. ICE is also working so when sip clients are in the same network > then the call goes point to point between caller and callee. > > The problem is when we want to use mediaproxy to relay media, let's say > when sip clients are in different networks. Each opensips server passes > its mediaproxy candidate to their clients. So opensips-1 passes > mediaproxy-1 to client-1 and opensips-2 passes mediaproxy-2 to client-2. > Then when the call is done client-1 will use mediaproxy-1 and client-2 > will use mediaproxy2 and therefore voice in going on diversion, each > takes its own way. > > Question: how to deal with this? Media relays can be chained without problems and automatically, unless they are behind NAT or if they have IP addresses in the private ranges (10.x.x.x, 192.168.x.x, ...) However it is a bit wasteful to have more than one in the path. One way to deal with this is to only engage the media relay on one of the proxies (the originator or the destination) if the call goes between users on the same platform. -- Dan From denis7979 at mail.ru Wed Jan 4 10:24:38 2017 From: denis7979 at mail.ru (=?utf-8?B?0JTQtdC90LjRgSDQn9GD0YLRj9GC0L4=?=) Date: Wed, 04 Jan 2017 18:24:38 +0300 Subject: [OpenSIPS-Users] rtpproxy and record calls In-Reply-To: <983901482839033@web9o.yandex.ru> References: <983901482839033@web9o.yandex.ru> Message-ID: <8121831483543478@web10h.yandex.ru> An HTML attachment was scrubbed... URL: From razvan at opensips.org Wed Jan 4 10:52:49 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Wed, 4 Jan 2017 17:52:49 +0200 Subject: [OpenSIPS-Users] rtpproxy and record calls In-Reply-To: <8121831483543478@web10h.yandex.ru> References: <983901482839033@web9o.yandex.ru> <8121831483543478@web10h.yandex.ru> Message-ID: Hi, Denis! Regarding 1, did you try to run rtpproxy_start_recording() for both INVITE and 200 OK? Regarding 2, '/' is a valid character in Call-id. Therefore the problem is at the RTPProxy side - before writing the CDR they should escape (or transform somehow) the '/' character in something else. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/04/2017 05:24 PM, Денис Путято via Users wrote: > Hello! > > Is there any information about the problem? > > Thank you. > > -- > С уважением, > Путято Денис > Best regards, Denis > > 14:47, 27 декабря 2016 г., Denis via Users : > > Hello! > I try to use rtpproxy for call recording and have two problems > 1) rtpproxy records only one way of the call (from callee to > caller). For starting rtp proxy i use > rtpproxy_engage("conrf",,"1",) function. > 2) i am using top_hiding with "C" flags (which should change > callid) and i noticed, that sometime the function generates callid > with such form (for example) > DLGCH_fRUAW2B/M2NiSV1WYWRhYX9ASFowK2J+f0JXXmt5MWspSVEM. > I want to pay attention to "/" character. As i understand, because > of this character i got such error from rtpproxy > ERR:DLGCH_fRUAW2B/M2NiSV1WYWRhYX9ASFowK2J+f0JXXmt5MWspSVEM:rtpp_record_open: > can't open file > /mnt/callrecords//DLGCH_fRUAW2B/M2NiSV1WYWRhYX9ASFowK2J+f0JXXmt5MWspSVEM=cU7ZHtge63paN.a.rtp > for writing: No such file or directory (2) > rtpproxy: 2.2.alpha.20160822 > Opensips: Server:: OpenSIPS (2.2.2 (x86_64/linux)) > Thank you for any help. > -- > С уважением, Денис. > Best regards, Denis > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From xaled at web.de Wed Jan 4 14:19:47 2017 From: xaled at web.de (xaled) Date: Wed, 4 Jan 2017 20:19:47 +0100 Subject: [OpenSIPS-Users] How to parse XML Body? Message-ID: <012c01d266bf$841c7590$8c5560b0$@web.de> Hi, What is the best way to parse xml body in an INVITE request? I want to access geographic location information gml:Coordinates or gml:pos from xml body and do some routing. I've seen the emergency module, but it is too specific to be useful in my basic scenario. Content-Type: multipart/mixed;boundary=ssboundary-1_ Content-Type: application/pidf+xml . XYZ XYZ . -------------- next part -------------- An HTML attachment was scrubbed... URL: From alain.bieuzent at free.fr Thu Jan 5 05:19:41 2017 From: alain.bieuzent at free.fr (Alain Bieuzent) Date: Thu, 05 Jan 2017 11:19:41 +0100 Subject: [OpenSIPS-Users] Codecs Order Message-ID: <25F32300-8069-4319-84EA-52F39B23D571@free.fr> Hi all, Is there a way to know the order of the codecs? For exemple in this SDP : m=audio 13406 RTP/AVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 How i know that the prefered codec is PCMA ? Regards, Alain -------------- next part -------------- An HTML attachment was scrubbed... URL: From aqsyounas at gmail.com Thu Jan 5 05:35:56 2017 From: aqsyounas at gmail.com (Aqs Younas) Date: Thu, 5 Jan 2017 15:35:56 +0500 Subject: [OpenSIPS-Users] Codecs Order In-Reply-To: <25F32300-8069-4319-84EA-52F39B23D571@free.fr> References: <25F32300-8069-4319-84EA-52F39B23D571@free.fr> Message-ID: media line(m) shows codec preference in order. m=audio 13406 RTP/AVP 8 0 101 8 for PCMA 0 for PCMU On 5 January 2017 at 15:19, Alain Bieuzent wrote: > Hi all, > > > > Is there a way to know the order of the codecs? > > > > For exemple in this SDP : > > m=audio 13406 RTP/AVP 8 0 101 > > a=rtpmap:8 PCMA/8000 > > a=rtpmap:0 PCMU/8000 > > a=rtpmap:101 telephone-event/8000 > > > > How i know that the prefered codec is PCMA ? > > > > Regards, > > > > Alain > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Thu Jan 5 05:38:46 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Thu, 5 Jan 2017 12:38:46 +0200 Subject: [OpenSIPS-Users] How to parse XML Body? In-Reply-To: <012c01d266bf$841c7590$8c5560b0$@web.de> References: <012c01d266bf$841c7590$8c5560b0$@web.de> Message-ID: <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> Hi, What version of OpenSIPS are you using ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 04.01.2017 21:19, xaled wrote: > > Hi, > > What is the best way to parse xml body in an INVITE request? > > I want to access geographic location information gml:Coordinates or > gml:pos from xml body and do some routing. I’ve seen the emergency > module, but it is too specific to be useful in my basic scenario. > > Content-Type: multipart/mixed;boundary=ssboundary-1_ > > Content-Type: application/pidf+xml > > … > > XYZ > > XYZ > > … > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From alain.bieuzent at free.fr Thu Jan 5 05:42:52 2017 From: alain.bieuzent at free.fr (Alain Bieuzent) Date: Thu, 05 Jan 2017 11:42:52 +0100 Subject: [OpenSIPS-Users] Codecs Order In-Reply-To: References: <25F32300-8069-4319-84EA-52F39B23D571@free.fr> Message-ID: Ok, but how can i extract the value of first codec, Actually i’m using codec_exist function, but this one only retrun TRUE or FALSE, but in case of true, i want know if it’s the first codec or no. Regards De : Users au nom de Aqs Younas Répondre à : OpenSIPS users mailling list Date : jeudi 5 janvier 2017 à 11:35 À : OpenSIPS users mailling list Objet : Re: [OpenSIPS-Users] Codecs Order media line(m) shows codec preference in order. m=audio 13406 RTP/AVP 8 0 101 8 for PCMA 0 for PCMU On 5 January 2017 at 15:19, Alain Bieuzent wrote: Hi all, Is there a way to know the order of the codecs? For exemple in this SDP : m=audio 13406 RTP/AVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 How i know that the prefered codec is PCMA ? Regards, Alain _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From xaled at web.de Thu Jan 5 05:57:20 2017 From: xaled at web.de (xaled) Date: Thu, 5 Jan 2017 11:57:20 +0100 Subject: [OpenSIPS-Users] How to parse XML Body? In-Reply-To: <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> References: <012c01d266bf$841c7590$8c5560b0$@web.de> <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> Message-ID: <018601d26742$7d877ee0$78967ca0$@web.de> Hi Bogdan; opensips-2.2.2 Thanks. From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Donnerstag, 5. Januar 2017 11:39 To: OpenSIPS users mailling list ; xaled Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi, What version of OpenSIPS are you using ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 04.01.2017 21:19, xaled wrote: Hi, What is the best way to parse xml body in an INVITE request? I want to access geographic location information gml:Coordinates or gml:pos from xml body and do some routing. I’ve seen the emergency module, but it is too specific to be useful in my basic scenario. Content-Type: multipart/mixed;boundary=ssboundary-1_ Content-Type: application/pidf+xml … XYZ XYZ … _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Thu Jan 5 06:19:04 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Thu, 5 Jan 2017 13:19:04 +0200 Subject: [OpenSIPS-Users] How to parse XML Body? In-Reply-To: <018601d26742$7d877ee0$78967ca0$@web.de> References: <012c01d266bf$841c7590$8c5560b0$@web.de> <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> <018601d26742$7d877ee0$78967ca0$@web.de> Message-ID: <4936e66b-ae31-a9fa-e260-a87ef6b24b20@opensips.org> You can use the $(rb[n]) to access a specific body part. see: http://www.opensips.org/Documentation/Script-CoreVar-2-2#toc65 Once you get the XML body, you can use some regexp in order to extract the needed info from the the XML (unfortunately thers is no way to parse XML at script level). See the "re" transformation : http://www.opensips.org/Documentation/Script-Tran-2-2#toc82 $var(reg) = "/gml:pos>(.*) > Hi Bogdan; > > opensips-2.2.2 > > Thanks. > > *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] > *Sent:* Donnerstag, 5. Januar 2017 11:39 > *To:* OpenSIPS users mailling list ; xaled > > *Subject:* Re: [OpenSIPS-Users] How to parse XML Body? > > Hi, > > What version of OpenSIPS are you using ? > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 04.01.2017 21:19, xaled wrote: > > Hi, > > What is the best way to parse xml body in an INVITE request? > > I want to access geographic location information gml:Coordinates > or gml:pos from xml body and do some routing. I’ve seen the > emergency module, but it is too specific to be useful in my basic > scenario. > > Content-Type: multipart/mixed;boundary=ssboundary-1_ > > Content-Type: application/pidf+xml > > … > > XYZ > > XYZ > > … > > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From xaled at web.de Thu Jan 5 06:22:29 2017 From: xaled at web.de (xaled) Date: Thu, 5 Jan 2017 12:22:29 +0100 Subject: [OpenSIPS-Users] How to parse XML Body? In-Reply-To: <4936e66b-ae31-a9fa-e260-a87ef6b24b20@opensips.org> References: <012c01d266bf$841c7590$8c5560b0$@web.de> <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> <018601d26742$7d877ee0$78967ca0$@web.de> <4936e66b-ae31-a9fa-e260-a87ef6b24b20@opensips.org> Message-ID: <019a01d26746$00669460$0133bd20$@web.de> Hi Bogdan, that is enough for me! Thanks. From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Donnerstag, 5. Januar 2017 12:19 To: OpenSIPS users mailling list ; xaled Subject: Re: [OpenSIPS-Users] How to parse XML Body? You can use the $(rb[n]) to access a specific body part. see: http://www.opensips.org/Documentation/Script-CoreVar-2-2#toc65 Once you get the XML body, you can use some regexp in order to extract the needed info from the the XML (unfortunately thers is no way to parse XML at script level). See the "re" transformation : http://www.opensips.org/Documentation/Script-Tran-2-2#toc82 $var(reg) = "/gml:pos>(.*) ; xaled Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi, What version of OpenSIPS are you using ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 04.01.2017 21:19, xaled wrote: Hi, What is the best way to parse xml body in an INVITE request? I want to access geographic location information gml:Coordinates or gml:pos from xml body and do some routing. I’ve seen the emergency module, but it is too specific to be useful in my basic scenario. Content-Type: multipart/mixed;boundary=ssboundary-1_ Content-Type: application/pidf+xml … XYZ XYZ … _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From xaled at web.de Thu Jan 5 06:38:01 2017 From: xaled at web.de (xaled) Date: Thu, 5 Jan 2017 12:38:01 +0100 Subject: [OpenSIPS-Users] How to parse XML Body? In-Reply-To: <019a01d26746$00669460$0133bd20$@web.de> References: <012c01d266bf$841c7590$8c5560b0$@web.de> <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> <018601d26742$7d877ee0$78967ca0$@web.de> <4936e66b-ae31-a9fa-e260-a87ef6b24b20@opensips.org> <019a01d26746$00669460$0133bd20$@web.de> Message-ID: <01b601d26748$2bebb6e0$83c324a0$@web.de> Hi Bogdan, Well - almost enough ;) $var(reg) = "/gml:Coordinates>(.*)(.*) Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi Bogdan, that is enough for me! Thanks. From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Donnerstag, 5. Januar 2017 12:19 To: OpenSIPS users mailling list >; xaled > Subject: Re: [OpenSIPS-Users] How to parse XML Body? You can use the $(rb[n]) to access a specific body part. see: http://www.opensips.org/Documentation/Script-CoreVar-2-2#toc65 Once you get the XML body, you can use some regexp in order to extract the needed info from the the XML (unfortunately thers is no way to parse XML at script level). See the "re" transformation : http://www.opensips.org/Documentation/Script-Tran-2-2#toc82 $var(reg) = "/gml:pos>(.*) ; xaled Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi, What version of OpenSIPS are you using ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 04.01.2017 21:19, xaled wrote: Hi, What is the best way to parse xml body in an INVITE request? I want to access geographic location information gml:Coordinates or gml:pos from xml body and do some routing. I’ve seen the emergency module, but it is too specific to be useful in my basic scenario. Content-Type: multipart/mixed;boundary=ssboundary-1_ Content-Type: application/pidf+xml … XYZ XYZ … _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From flavio at voffice.com.br Thu Jan 5 06:59:55 2017 From: flavio at voffice.com.br (Flavio Goncalves) Date: Thu, 5 Jan 2017 09:59:55 -0200 Subject: [OpenSIPS-Users] CRITICAL:core:timer_ticker: timer handler Message-ID: Hi, I'm getting some errors like below (2 simultaneous calls). No stress test. pkmem is ok, shmem is ok. CRITICAL:core:timer_ticker: timer handler lasted (5030000 us) for more than timer tick (1000000 us) -> potential timer shifting. Anyone with the same problem? Flavio E. Goncalves -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Thu Jan 5 07:11:49 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Thu, 5 Jan 2017 14:11:49 +0200 Subject: [OpenSIPS-Users] How to parse XML Body? In-Reply-To: <01b601d26748$2bebb6e0$83c324a0$@web.de> References: <012c01d266bf$841c7590$8c5560b0$@web.de> <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> <018601d26742$7d877ee0$78967ca0$@web.de> <4936e66b-ae31-a9fa-e260-a87ef6b24b20@opensips.org> <019a01d26746$00669460$0133bd20$@web.de> <01b601d26748$2bebb6e0$83c324a0$@web.de> Message-ID: <01428a9e-5f55-5a7e-154d-59c2f8e96ef0@opensips.org> Try $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 05.01.2017 13:38, xaled wrote: > > Hi Bogdan, > > Well - almost enough ;) > > $var(reg) = "/gml:Coordinates>(.*) > xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); > > 2017-01-05T12:28:34.923153+01:00 ivr01 > /usr/local/sbin/opensips[32257]: ERROR:core:subst_parser: unknown flag > m in /gml:Coordinates>(.*) > 2017-01-05T12:28:34.923507+01:00 ivr01 > /usr/local/sbin/opensips[32257]: ERROR:core:tr_eval_re: Can't compile > regexp > > Thanks > > *From:*Users [mailto:users-bounces at lists.opensips.org] *On Behalf Of > *xaled > *Sent:* Donnerstag, 5. Januar 2017 12:22 > *To:* 'OpenSIPS users mailling list' > *Subject:* Re: [OpenSIPS-Users] How to parse XML Body? > > Hi Bogdan, > > that is enough for me! > > Thanks. > > *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] > *Sent:* Donnerstag, 5. Januar 2017 12:19 > *To:* OpenSIPS users mailling list >; xaled > > *Subject:* Re: [OpenSIPS-Users] How to parse XML Body? > > You can use the $(rb[n]) to access a specific body part. see: > http://www.opensips.org/Documentation/Script-CoreVar-2-2#toc65 > > Once you get the XML body, you can use some regexp in order to extract > the needed info from the the XML (unfortunately thers is no way to > parse XML at script level). See the "re" transformation : > http://www.opensips.org/Documentation/Script-Tran-2-2#toc82 > > $var(reg) = "/gml:pos>(.*) xlog("Position is $(rb[0]{re.subst,$var(reg)})\n"); > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 05.01.2017 12:57, xaled wrote: > > Hi Bogdan; > > opensips-2.2.2 > > Thanks. > > *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] > *Sent:* Donnerstag, 5. Januar 2017 11:39 > *To:* OpenSIPS users mailling list > ; xaled > > *Subject:* Re: [OpenSIPS-Users] How to parse XML Body? > > Hi, > > What version of OpenSIPS are you using ? > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > > http://www.opensips-solutions.com > > On 04.01.2017 21:19, xaled wrote: > > Hi, > > What is the best way to parse xml body in an INVITE request? > > I want to access geographic location information > gml:Coordinates or gml:pos from xml body and do some routing. > I’ve seen the emergency module, but it is too specific to be > useful in my basic scenario. > > Content-Type: multipart/mixed;boundary=ssboundary-1_ > > Content-Type: application/pidf+xml > > … > > XYZ > > XYZ > > … > > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From flavio at voffice.com.br Thu Jan 5 07:12:17 2017 From: flavio at voffice.com.br (Flavio Goncalves) Date: Thu, 5 Jan 2017 10:12:17 -0200 Subject: [OpenSIPS-Users] ERROR:drouting:populate_dr_bls: Something went wrong in add_rule_to_list Message-ID: Hi, I'm getting some errors on drouting and I got some routes sent to wrong gateways (some gateways being skipped). It seems a fail to insert in the blacklist, but never saw this message before, opensips 1.11. I don't know if the problems are correlated. Att, Flavio E. Goncalves V.Office Redes e Telecomunicações Ltda. Fone 48 33328590 Skype:flaviogoncalves1 Linkedin: www.linkedin.com/in/flavioegoncalves -------------- next part -------------- An HTML attachment was scrubbed... URL: From xaled at web.de Thu Jan 5 07:33:01 2017 From: xaled at web.de (xaled) Date: Thu, 5 Jan 2017 13:33:01 +0100 Subject: [OpenSIPS-Users] How to parse XML Body? In-Reply-To: <01428a9e-5f55-5a7e-154d-59c2f8e96ef0@opensips.org> References: <012c01d266bf$841c7590$8c5560b0$@web.de> <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> <018601d26742$7d877ee0$78967ca0$@web.de> <4936e66b-ae31-a9fa-e260-a87ef6b24b20@opensips.org> <019a01d26746$00669460$0133bd20$@web.de> <01b601d26748$2bebb6e0$83c324a0$@web.de> <01428a9e-5f55-5a7e-154d-59c2f8e96ef0@opensips.org> Message-ID: <01f101d2674f$dadadee0$90909ca0$@web.de> Hi Bogdan, $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); DBG:core:subst_run:matched shows the needed XML element, but not the value. The xlog output shows the whole XML body without gml:Coordinates. 2017-01-05T13:23:23.104982+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:tr_eval_re: Trying to apply reg exp [/gml:Coordinates>(.*)<\/gml:Coordinates/\1/] on : [#015#012#015#012 #015#012 #015#012 #015#012 #015#012 #015#012 #015#012 12.32 34.24#015#012 #015#012 #015#012 #015#012 #015#012 no#015#012 #015#012 #01 5#012 #015#012 #015#012 2016-8-02T04:13:23Z#015#012 #015#0 12#015#012#015#012] 2017-01-05T13:23:23.107376+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:tr_eval_re: we must compile the regexp 2017-01-05T13:23:23.107903+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_parser: ok, se is 0x7f39a 5d0a1f0 2017-01-05T13:23:23.108241+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_run: running. r=0 2017-01-05T13:23:23.111918+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_run: matched (404, 45): [ gml:Coordinates>12.32 34.24#015#012#015#0 12 #015#012 #015#012 #015#012 #015#012 #015#012 #015#012 <12.32 34.24>#015#012 #015#012 #015#012 #015#012 #015#012 no#015#012 #015#012 #015# 012 #015#012 #015#012 2016-8-02T04:13:23Z#015#012 #015#012 Thanks From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Donnerstag, 5. Januar 2017 13:12 To: OpenSIPS users mailling list ; xaled Subject: Re: [OpenSIPS-Users] How to parse XML Body? Try $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 05.01.2017 13:38, xaled wrote: Hi Bogdan, Well - almost enough ;) $var(reg) = "/gml:Coordinates>(.*)(.*) Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi Bogdan, that is enough for me! Thanks. From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Donnerstag, 5. Januar 2017 12:19 To: OpenSIPS users mailling list >; xaled > Subject: Re: [OpenSIPS-Users] How to parse XML Body? You can use the $(rb[n]) to access a specific body part. see: http://www.opensips.org/Documentation/Script-CoreVar-2-2#toc65 Once you get the XML body, you can use some regexp in order to extract the needed info from the the XML (unfortunately thers is no way to parse XML at script level). See the "re" transformation : http://www.opensips.org/Documentation/Script-Tran-2-2#toc82 $var(reg) = "/gml:pos>(.*) ; xaled Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi, What version of OpenSIPS are you using ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 04.01.2017 21:19, xaled wrote: Hi, What is the best way to parse xml body in an INVITE request? I want to access geographic location information gml:Coordinates or gml:pos from xml body and do some routing. I’ve seen the emergency module, but it is too specific to be useful in my basic scenario. Content-Type: multipart/mixed;boundary=ssboundary-1_ Content-Type: application/pidf+xml … XYZ XYZ … _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From rrobson at greenlightcrm.com Thu Jan 5 08:45:13 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Thu, 5 Jan 2017 13:45:13 +0000 Subject: [OpenSIPS-Users] transaction module and Auto 100 reply Message-ID: <25d3f7c2-e1f3-24fd-488d-fd7f62dcfff7@greenlightcrm.com> Hi, I've just notices that our opensips (2.2.2) is not sending a 100 back automatically on an INVITE Some calls are ok, others are not. This is probably because I'm doing a fair bit of processing before the t_relay is called. Am I better turning off the Auto 100 reply and sending the 100 manually with modparam("tm", "auto_100trying", 0) and t_reply("100", "Trying") when handling the initial invite after it has been authenticated/accepted? -- Richard Robson Greenlight Support 01382 843843 support at greenlightcrm.com From liviu at opensips.org Thu Jan 5 09:16:41 2017 From: liviu at opensips.org (Liviu Chircu) Date: Thu, 5 Jan 2017 16:16:41 +0200 Subject: [OpenSIPS-Users] transaction module and Auto 100 reply In-Reply-To: <25d3f7c2-e1f3-24fd-488d-fd7f62dcfff7@greenlightcrm.com> References: <25d3f7c2-e1f3-24fd-488d-fd7f62dcfff7@greenlightcrm.com> Message-ID: Hi Richard, Yes, that's one of the problems "auto_100trying" is meant to solve, besides avoiding duplicate 100 Trying replies in some scripts. Regards, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 05.01.2017 15:45, Richard Robson wrote: > Hi, > > > I've just notices that our opensips (2.2.2) is not sending a 100 back > automatically on an INVITE Some calls are ok, others are not. This is > probably because I'm doing a fair bit of processing before the t_relay > is called. > > Am I better turning off the Auto 100 reply and sending the 100 > manually with modparam("tm", "auto_100trying", 0) and t_reply("100", > "Trying") when handling the initial invite after it has been > authenticated/accepted? > > From razvan at opensips.org Thu Jan 5 10:57:17 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Thu, 5 Jan 2017 17:57:17 +0200 Subject: [OpenSIPS-Users] Codecs Order In-Reply-To: References: <25F32300-8069-4319-84EA-52F39B23D571@free.fr> Message-ID: Hi, Alain! You could use the SDP transformations combine with regular expresions. I am thinking at something like: if ($(rb{sdp.line,m}) =~ "AVP\s*8") xlog("PCMA is first codec!\n"); Hope this is useful :) Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/05/2017 12:42 PM, Alain Bieuzent wrote: > > Ok, but how can i extract the value of first codec, > > Actually i’m using codec_exist function, but this one only retrun TRUE > or FALSE, but in case of true, i want know if it’s the first codec or no. > > Regards > > *De : *Users au nom de Aqs Younas > > *Répondre à : *OpenSIPS users mailling list > *Date : *jeudi 5 janvier 2017 à 11:35 > *À : *OpenSIPS users mailling list > *Objet : *Re: [OpenSIPS-Users] Codecs Order > > media line(m) shows codec preference in order. > > m=audio 13406 RTP/AVP 8 0 101 > > 8 for PCMA > > 0 for PCMU > > On 5 January 2017 at 15:19, Alain Bieuzent > wrote: > > Hi all, > > Is there a way to know the order of the codecs? > > For exemple in this SDP : > > m=audio 13406 RTP/AVP 8 0 101 > > a=rtpmap:8 PCMA/8000 > > a=rtpmap:0 PCMU/8000 > > a=rtpmap:101 telephone-event/8000 > > How i know that the prefered codec is PCMA ? > > Regards, > > Alain > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Thu Jan 5 10:58:23 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Thu, 5 Jan 2017 17:58:23 +0200 Subject: [OpenSIPS-Users] CRITICAL:core:timer_ticker: timer handler In-Reply-To: References: Message-ID: Hi, Flavio! Is it the latest OpenSIPS version? How many children are you using? Can you send over the output of "opensipsctl ps"? Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/05/2017 01:59 PM, Flavio Goncalves wrote: > Hi, > > I'm getting some errors like below (2 simultaneous calls). No stress > test. pkmem is ok, shmem is ok. > > CRITICAL:core:timer_ticker: timer handler lasted (5030000 > us) for more than timer tick (1000000 us) -> potential timer shifting. > > Anyone with the same problem? > > Flavio E. Goncalves > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Thu Jan 5 10:59:34 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Thu, 5 Jan 2017 17:59:34 +0200 Subject: [OpenSIPS-Users] ERROR:drouting:populate_dr_bls: Something went wrong in add_rule_to_list In-Reply-To: References: Message-ID: <791c420b-537c-5d1c-ab5a-9d14f3548254@opensips.org> Hi, Flavio? Are you seeing the errors in the logs? Can you send them to us to check? Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/05/2017 02:12 PM, Flavio Goncalves wrote: > Hi, > > I'm getting some errors on drouting and I got some routes sent to > wrong gateways (some gateways being skipped). It seems a fail to > insert in the blacklist, but never saw this message before, opensips > 1.11. I don't know if the problems are correlated. > > Att, > > Flavio E. Goncalves > V.Office Redes e Telecomunicações Ltda. > Fone 48 33328590 > Skype:flaviogoncalves1 > Linkedin: www.linkedin.com/in/flavioegoncalves > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From liviu at opensips.org Thu Jan 5 11:36:07 2017 From: liviu at opensips.org (Liviu Chircu) Date: Thu, 5 Jan 2017 18:36:07 +0200 Subject: [OpenSIPS-Users] OpenSIPS at FOSDEM 2017 In-Reply-To: References: Message-ID: Every year,FOSDEM is a good opportunity to connect with our community and acquaint them with the exciting work going into the newestOpenSIPS versions. And there will be no exception this year! What is this year on the plate? */"OpenSIPS - an event-driven SIP routing engine", by Liviu Chircu, FOSDEM, 4th of Feb 2017 /*When moving from a linear processing architecture to anevent-oriented one ,OpenSIPS becomes able to handle more advanced SIP scenarios, as well as to perform complex integrations with external applications. The newOpenSIPS version follows a Subscribe/Notify model, which allows the SIP routing to be driven by events. These events are triggered from both inside and outsideOpenSIPS , and are internally dispatched byOpenSIPS to the right process/subscriber. The presentation will show how the asynchronous architecture revamp of the upcomingOpenSIPS 2.3 facilitates a series of state-of-the-art integrations (SIP transaction pausing while push notifications are taking effect, custom suspend-resume logic while waiting for an external event, etc.). The discussion will also includeOpenSIPS scripting, and how we tweaked it to incorporate all these changes in a simple, straightforward, and efficient manner. Does it sound interesting? Join us at FOSDEM and find out more - we will be there with our friends fromSIPcapture andCGRates to show how easy the OpenSIPS integration becomes when relying on an event-driven engine! See you soon, -- Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rrobson at greenlightcrm.com Fri Jan 6 04:30:30 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Fri, 6 Jan 2017 09:30:30 +0000 Subject: [OpenSIPS-Users] opensipsp Message-ID: <86d31aca-5635-9683-59d5-1b6412555a57@greenlightcrm.com> Hi, we are getting a crash in opensips. V2.2.2 bt all: #0 0x0000000000425de2 in context_put_int (type=CONTEXT_GLOBAL, ctx=0x0, pos=4, data=1) at context.c:173 No locals. #1 0x00007f1c121642cc in dlg_onreply (t=0x7f1c1d86e938, type=, param=) at dlg_handlers.c:490 rpl = 0x7f1c3be9f3b8 req = 0x7f1c1cf97070 dlg = 0x7f1c20b39040 new_state = 0 old_state = 472847928 unref = 495381272 event = 4 mangled_from = {s = 0x0, len = 0} mangled_to = {s = 0x0, len = 0} req_out_buff = #2 0x00007f1c1b5a4069 in run_trans_callbacks (type=type at entry=64, trans=trans at entry=0x7f1c1d86e938, req=req at entry=0x7f1c1cf97070, rpl=, code=) at t_hooks.c:209 params = {req = 0x7f1c1cf97070, rpl = 0x7f1c3be9f3b8, code = 500, param = 0x7f1c1c6110c0, extra1 = 0x7ffc05c6ebe0, extra2 = 0x7f1c1d86ea50} cbp = 0x7f1c1c6110b0 backup = 0x845628 trans_backup = 0x7f1c1d86e938 __FUNCTION__ = "run_trans_callbacks" #3 0x00007f1c1b5a43c2 in run_trans_callbacks_locked (type=type at entry=64, trans=trans at entry=0x7f1c1d86e938, req=0x7f1c1cf97070, rpl=rpl at entry=0x7f1c3be9f3b8, code=code at entry=500) at t_hooks.c:262 No locals. #4 0x00007f1c1b55bf9c in relay_reply (t=, p_msg=, branch=, msg_status=, cancel_bitmap=) at t_reply.c:1244 relay = save_clone = buf = 0x7f1c3be954b0 "SIP/2.0 500 Service Unavailable-No Bandwidth Available\r\nVia: SIP/2.0/UDP 192.168.36.12:5060;received=192.168.36.12;rport=5060;branch=z9hG4bK32b724a4\r\nTo: ;tag=3692683275"... res_len = 484 relayed_code = 500 relayed_msg = bm = {to_tag_val = {s = 0x1
, len = 8897760}} totag_retr = 0 uas_rb = cb_s = { s = 0x7f1c3be954b0 "SIP/2.0 500 Service Unavailable-No Bandwidth Available\r\nVia: SIP/2.0/UDP 192.168.36.12:5060;received=192.168.36.12;rport=5060;branch=z9hG4bK32b724a4\r\nTo: ;tag=3692683275"..., len = 484} text = {s = 0x1
, len = 1002627336} __FUNCTION__ = "relay_reply" #5 0x00007f1c1b562406 in reply_received (p_msg=0x7f1c3be9f3b8) at t_reply.c:1505 msg_status = 500 last_uac_status = 100 branch = 0 reply_status = timer = 139758694817869 cancel_bitmap = 0 uac = 0x7f1c1d86eb10 t = 0x7f1c1d86e938 backup_list = has_reply_route = __FUNCTION__ = "reply_received" #6 0x0000000000458fed in forward_reply (msg=msg at entry=0x7f1c3be9f3b8) at forward.c:495 new_buf = 0x0 to = 0x0 new_len = 0 mod = 0x7f1c3bbf6e90 proto = id = 0 send_sock = s = len = __FUNCTION__ = "forward_reply" #7 0x0000000000439126 in receive_msg ( buf=0x858c00 "SIP/2.0 503 Service Unavailable-No Bandwidth Available\r\nVia: SIP/2.0/UDP 141.170.9.157:5060;branch=z9hG4bK817f.88c248e3.0\r\nTo: ;tag=3692683275-7994\r\nFrom: , rcv_info=rcv_info at entry=0x7ffc05c6ee60, existing_context=existing_context at entry=0x0) at receive.c:257 ctx = 0x7f1c3be8f3d0 msg = 0x7f1c3be9f3b8 start = {tv_sec = 50509, tv_usec = 139758636819258} rc = 3 in_buff = { s = 0x7f1c3be92b40 "SIP/2.0 500 Service Unavailable-No Bandwidth Available\r\nVia: SIP/2.0/UDP 141.170.9.157:5060;branch=z9hG4bK817f.88c248e3.0\r\nTo: ;tag=3692683275-7994\r\nFrom: , bytes_read=) at net/proto_udp/proto_udp.c:192 ri = {src_ip = {af = 2, len = 4, u = {addrl = {139759486345069, 0}, addr32 = {1250533229, 32540, 0, 0}, addr16 = {40813, 19081, 32540, 0, 0, 0, 0, 0}, addr = "m\237\211J\034\177\000\000\000\000\000\000\000\000\000"}}, dst_ip = { af = 2, len = 4, u = {addrl = {1378134208, 0}, addr32 = {1378134208, 0, 0, 0}, addr16 = {43200, 21028, 0, 0, 0, 0, 0, 0}, addr = "\300\250$R", '\000' }}, src_port = 5060, dst_port = 5060, proto = 1, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 2, sa_data = "\023\304m\237\211J\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 1250533229}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 1250533229, sin6_addr = {__in6_u = {__u6_addr8 = "\000\000\000\000\000\000\000\000\001\000\000\000\000\000\000", __u6_addr16 = {0, 0, 0, 0, 1, 0, 0, 0}, __u6_addr32 = {0, 0, 1, 0}}}, sin6_scope_id = 4851503}}, bind_address = 0x7f1c3bbf6720} len = buf = "SIP/2.0 503 Service Unavailable-No Bandwidth Available\r\nVia: SIP/2.0/UDP 141.170.9.157:5060;branch=z9hG4bK817f.88c248e3.0\r\nTo: ;tag=3692683275-7994\r\nFrom: msg = { s = 0x858c00 "SIP/2.0 503 Service Unavailable-No Bandwidth Available\r\nVia: SIP/2.0/UDP 141.170.9.157:5060;branch=z9hG4bK817f.88c248e3.0\r\nTo: ;tag=3692683275-7994\r\nFrom: , event_type=, fm=) at net/net_udp.c:259 read = 1023068896 fm = #10 io_wait_loop_epoll (h=, t=, repeat=) at net/../io_wait_loop.h:225 ret = e = n = 1 r = 0 #11 udp_rcv_loop (si=si at entry=0x7f1c3bbf6720) at net/net_udp.c:308 __FUNCTION__ = "udp_rcv_loop" #12 0x000000000059b948 in udp_start_processes (chd_rank=chd_rank at entry=0x8457a0 , startup_done=startup_done at entry=0x0) at net/net_udp.c:372 si = 0x7f1c3bbf6720 load_p = 0x7f1c1bee92e8 pid = i = __FUNCTION__ = "udp_start_processes" #13 0x0000000000419f50 in main_loop () at main.c:671 startup_done = 0x0 chd_rank = 3 #14 main (argc=, argv=) at main.c:1261 cfg_stream = c = r = tmp = 0x7ffc05c70f66 "" tmp_len = port = proto = protos_no = options = 0x5df1d0 "f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:" ret = -1 seed = 1763847833 rfd = __FUNCTION__ = "main" From rrobson at greenlightcrm.com Fri Jan 6 07:19:23 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Fri, 6 Jan 2017 12:19:23 +0000 Subject: [OpenSIPS-Users] opensips Crashing v2.2.2 In-Reply-To: <86d31aca-5635-9683-59d5-1b6412555a57@greenlightcrm.com> References: <86d31aca-5635-9683-59d5-1b6412555a57@greenlightcrm.com> Message-ID: <270e22e1-46f3-2f8d-e44c-a4dad2b61711@greenlightcrm.com> I've some more back traces. this could be a resource problem. The back story is we want to check for channel limits and Rate limits for all calls. Channel limit hits should failover to the next gateway and rate limits should delat for up to 2 seconds before failing over to the next gateway. This is all working ok as far as I can tell. We have one provider that has 600 channels and cps of 25. We now have a second provider with 3 nodes of 100 channels and 4 cps. All nodes are being checked for Channels and CPS. I noticed that the failover of GW was not being checked and added new route to do the checking. Also to confuse things more it looks like one of the new carriers nodes may be incorrectly configured asnd we are getting failures (503 Service unavailable). Yesterday we were using all four gateways and no crashes, but after adding in the new route for the failover checking it started to crash this morning. the logs indicate that the failover is working correctly. We are checking the outbound calls twice once for the customer limits and then for the carrier limits. This has been fine for the last few days, since the system was updated ( it was only carrier limits checked before) i've removed the suspect node and the extra route, but I notice the error from the node in the backtraces with an address out of bounds I've more back traces if you require http://pastebin.com/BB9RP6rv http://pastebin.com/QSTbYgNQ http://pastebin.com/vUmQLT0k On 06/01/2017 09:30, Richard Robson wrote: > Hi, > > we are getting a crash in opensips. V2.2.2 > > > bt all: > > > #0 0x0000000000425de2 in context_put_int (type=CONTEXT_GLOBAL, > ctx=0x0, pos=4, data=1) at context.c:173 > No locals. > #1 0x00007f1c121642cc in dlg_onreply (t=0x7f1c1d86e938, > type=, param=) at dlg_handlers.c:490 > rpl = 0x7f1c3be9f3b8 > req = 0x7f1c1cf97070 > dlg = 0x7f1c20b39040 > new_state = 0 > old_state = 472847928 > unref = 495381272 > event = 4 > mangled_from = {s = 0x0, len = 0} > mangled_to = {s = 0x0, len = 0} > req_out_buff = > #2 0x00007f1c1b5a4069 in run_trans_callbacks (type=type at entry=64, > trans=trans at entry=0x7f1c1d86e938, req=req at entry=0x7f1c1cf97070, > rpl=, code=) at t_hooks.c:209 > params = {req = 0x7f1c1cf97070, rpl = 0x7f1c3be9f3b8, code = > 500, param = 0x7f1c1c6110c0, extra1 = 0x7ffc05c6ebe0, extra2 = > 0x7f1c1d86ea50} > cbp = 0x7f1c1c6110b0 > backup = 0x845628 > trans_backup = 0x7f1c1d86e938 > __FUNCTION__ = "run_trans_callbacks" > #3 0x00007f1c1b5a43c2 in run_trans_callbacks_locked > (type=type at entry=64, trans=trans at entry=0x7f1c1d86e938, > req=0x7f1c1cf97070, rpl=rpl at entry=0x7f1c3be9f3b8, code=code at entry=500) > at t_hooks.c:262 > No locals. > #4 0x00007f1c1b55bf9c in relay_reply (t=, > p_msg=, branch=, msg_status= out>, cancel_bitmap=) at t_reply.c:1244 > relay = > save_clone = > buf = 0x7f1c3be954b0 "SIP/2.0 500 Service Unavailable-No > Bandwidth Available\r\nVia: SIP/2.0/UDP > 192.168.36.12:5060;received=192.168.36.12;rport=5060;branch=z9hG4bK32b724a4\r\nTo: > ;tag=3692683275"... > res_len = 484 > relayed_code = 500 > relayed_msg = > bm = {to_tag_val = {s = 0x1
, len = > 8897760}} > totag_retr = 0 > uas_rb = > cb_s = { > s = 0x7f1c3be954b0 "SIP/2.0 500 Service Unavailable-No > Bandwidth Available\r\nVia: SIP/2.0/UDP > 192.168.36.12:5060;received=192.168.36.12;rport=5060;branch=z9hG4bK32b724a4\r\nTo: > ;tag=3692683275"..., len = 484} > text = {s = 0x1
, len = 1002627336} > __FUNCTION__ = "relay_reply" > #5 0x00007f1c1b562406 in reply_received (p_msg=0x7f1c3be9f3b8) at > t_reply.c:1505 > msg_status = 500 > last_uac_status = 100 > branch = 0 > reply_status = > timer = 139758694817869 > cancel_bitmap = 0 > uac = 0x7f1c1d86eb10 > t = 0x7f1c1d86e938 > backup_list = > has_reply_route = > __FUNCTION__ = "reply_received" > #6 0x0000000000458fed in forward_reply (msg=msg at entry=0x7f1c3be9f3b8) > at forward.c:495 > new_buf = 0x0 > to = 0x0 > new_len = 0 > mod = 0x7f1c3bbf6e90 > proto = > id = 0 > send_sock = > s = > len = > __FUNCTION__ = "forward_reply" > #7 0x0000000000439126 in receive_msg ( > buf=0x858c00 "SIP/2.0 503 Service Unavailable-No > Bandwidth Available\r\nVia: SIP/2.0/UDP > 141.170.9.157:5060;branch=z9hG4bK817f.88c248e3.0\r\nTo: > ;tag=3692683275-7994\r\nFrom: > , > rcv_info=rcv_info at entry=0x7ffc05c6ee60, > existing_context=existing_context at entry=0x0) at receive.c:257 > ctx = 0x7f1c3be8f3d0 > msg = 0x7f1c3be9f3b8 > start = {tv_sec = 50509, tv_usec = 139758636819258} > rc = 3 > in_buff = { > s = 0x7f1c3be92b40 "SIP/2.0 500 Service Unavailable-No > Bandwidth Available\r\nVia: SIP/2.0/UDP > 141.170.9.157:5060;branch=z9hG4bK817f.88c248e3.0\r\nTo: > ;tag=3692683275-7994\r\nFrom: > __FUNCTION__ = "receive_msg" > #8 0x00000000005b0b13 in udp_read_req (si=, > bytes_read=) at net/proto_udp/proto_udp.c:192 > ri = {src_ip = {af = 2, len = 4, u = {addrl = > {139759486345069, 0}, addr32 = {1250533229, 32540, 0, 0}, addr16 = > {40813, 19081, 32540, 0, 0, 0, 0, 0}, addr = > "m\237\211J\034\177\000\000\000\000\000\000\000\000\000"}}, dst_ip = { > af = 2, len = 4, u = {addrl = {1378134208, 0}, addr32 = > {1378134208, 0, 0, 0}, addr16 = {43200, 21028, 0, 0, 0, 0, 0, 0}, addr > = "\300\250$R", '\000' }}, src_port = 5060, dst_port > = 5060, proto = 1, > proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = > {sa_family = 2, sa_data = > "\023\304m\237\211J\000\000\000\000\000\000\000"}, sin = {sin_family = > 2, sin_port = 50195, sin_addr = {s_addr = 1250533229}, > sin_zero = "\000\000\000\000\000\000\000"}, sin6 = > {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 1250533229, > sin6_addr = {__in6_u = {__u6_addr8 = > "\000\000\000\000\000\000\000\000\001\000\000\000\000\000\000", > __u6_addr16 = {0, 0, 0, 0, 1, 0, 0, 0}, __u6_addr32 > = {0, 0, 1, 0}}}, sin6_scope_id = 4851503}}, bind_address = > 0x7f1c3bbf6720} > len = > buf = "SIP/2.0 503 Service Unavailable-No Bandwidth > Available\r\nVia: SIP/2.0/UDP > 141.170.9.157:5060;branch=z9hG4bK817f.88c248e3.0\r\nTo: > ;tag=3692683275-7994\r\nFrom: > fromlen = 16 > p = > msg = { > s = 0x858c00 "SIP/2.0 503 Service Unavailable-No > Bandwidth Available\r\nVia: SIP/2.0/UDP > 141.170.9.157:5060;branch=z9hG4bK817f.88c248e3.0\r\nTo: > ;tag=3692683275-7994\r\nFrom: > __FUNCTION__ = "udp_read_req" > #9 0x000000000059a420 in handle_io (idx=, > event_type=, fm=) at net/net_udp.c:259 > read = 1023068896 > fm = > #10 io_wait_loop_epoll (h=, t=, > repeat=) at net/../io_wait_loop.h:225 > ret = > e = > n = 1 > r = 0 > #11 udp_rcv_loop (si=si at entry=0x7f1c3bbf6720) at net/net_udp.c:308 > __FUNCTION__ = "udp_rcv_loop" > #12 0x000000000059b948 in udp_start_processes > (chd_rank=chd_rank at entry=0x8457a0 , > startup_done=startup_done at entry=0x0) at net/net_udp.c:372 > si = 0x7f1c3bbf6720 > load_p = 0x7f1c1bee92e8 > pid = > i = > __FUNCTION__ = "udp_start_processes" > #13 0x0000000000419f50 in main_loop () at main.c:671 > startup_done = 0x0 > chd_rank = 3 > #14 main (argc=, argv=) at main.c:1261 > cfg_stream = > c = > r = > tmp = 0x7ffc05c70f66 "" > tmp_len = > port = > proto = > protos_no = > options = 0x5df1d0 "f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:" > ret = -1 > seed = 1763847833 > rfd = > __FUNCTION__ = "main" > -- Richard Robson Greenlight Support 01382 843843 support at greenlightcrm.com From a.martin at alphalink.fr Fri Jan 6 07:44:32 2017 From: a.martin at alphalink.fr (Adrien Martin) Date: Fri, 6 Jan 2017 13:44:32 +0100 Subject: [OpenSIPS-Users] Topology hiding and Route header Message-ID: <7ea3a62f-0080-3b3c-bf87-3437e711b3cc@alphalink.fr> Hello, I'm using the module topology_hiding with Opensips 2.2 but I'm not sure to understand properly the documentation. Is the header Route supposed to be removed ? (No problem removing and restoring Record-Route) In my tests Route header was not removed unless I added remove_hf("Route") after topology_hiding. Regards, -- Adrien Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From razvan at opensips.org Fri Jan 6 08:01:25 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Fri, 6 Jan 2017 15:01:25 +0200 Subject: [OpenSIPS-Users] Topology hiding and Route header In-Reply-To: <7ea3a62f-0080-3b3c-bf87-3437e711b3cc@alphalink.fr> References: <7ea3a62f-0080-3b3c-bf87-3437e711b3cc@alphalink.fr> Message-ID: Hi, Adrien! If you are talking about a pre-loaded Route header (received from the client) for an initial INVITE, then the topology_hiding() module does not remove it and you have to remove it yourself. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/06/2017 02:44 PM, Adrien Martin wrote: > Hello, > > I'm using the module topology_hiding with Opensips 2.2 but I'm not sure to understand properly the documentation. > > Is the header Route supposed to be removed ? (No problem removing and restoring Record-Route) > In my tests Route header was not removed unless I added remove_hf("Route") after topology_hiding. > > Regards, > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From a.martin at alphalink.fr Fri Jan 6 08:40:39 2017 From: a.martin at alphalink.fr (Adrien Martin) Date: Fri, 6 Jan 2017 14:40:39 +0100 Subject: [OpenSIPS-Users] Topology hiding and Route header In-Reply-To: References: <7ea3a62f-0080-3b3c-bf87-3437e711b3cc@alphalink.fr> Message-ID: <9ca77713-9fc7-181b-98a8-2e07bbf60341@alphalink.fr> Hello, Thank you for the clarification, yes it was about a pre-loaded Route header. Regards, -- Adrien Martin On 06/01/2017 14:01, Răzvan Crainea wrote: > Hi, Adrien! > > If you are talking about a pre-loaded Route header (received from the client) for an initial INVITE, then the topology_hiding() module does not remove it and you have to remove it yourself. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > > On 01/06/2017 02:44 PM, Adrien Martin wrote: >> Hello, >> >> I'm using the module topology_hiding with Opensips 2.2 but I'm not sure to understand properly the documentation. >> >> Is the header Route supposed to be removed ? (No problem removing and restoring Record-Route) >> In my tests Route header was not removed unless I added remove_hf("Route") after topology_hiding. >> >> Regards, >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From rrobson at greenlightcrm.com Fri Jan 6 09:22:35 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Fri, 6 Jan 2017 14:22:35 +0000 Subject: [OpenSIPS-Users] 503 translated to 500 between opensips and homer Message-ID: <736252ef-2076-e207-2119-0129158f163d@greenlightcrm.com> An HTML attachment was scrubbed... URL: From hunterj91 at hotmail.com Fri Jan 6 09:33:44 2017 From: hunterj91 at hotmail.com (Jonathan Hunter) Date: Fri, 6 Jan 2017 14:33:44 +0000 Subject: [OpenSIPS-Users] opensips 2.1 call_center queue position In-Reply-To: References: <96c0390f-2502-2b99-d4a9-a9133ee2b44d@opensips.org> <5d601c3e-ac5b-b6d1-fc0a-7959f1f0e4a0@opensips.org> <698e1be4-ce83-9782-5286-e8154bccd0b8@opensips.org> <63f2329e-066b-ed10-5629-dd8fbe075758@opensips.org> , <2b3b841f-162a-589f-01dc-93b8089a1118@opensips.org>, Message-ID: Hi Bogdan, Happy new year, I hope you are well? Did you see my reply below,? The count works now but its not routing the call. Many thanks Jon ________________________________ From: Jonathan Hunter Sent: 23 December 2016 15:52 To: Bogdan-Andrei Iancu; OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] opensips 2.1 call_center queue position Hi Bogdan, That seems to be better, certainly from the count incrementing, however a couple of issues, I am now seeing this error, and when first call hits opensips it doesnt now route to the Agent who is logged in free and available; : ERROR:b2b_entities:b2b_send_request: Can not send request [INVITE] for entity type [0] for dlg[0x7fe3f348a0f8]->[B2B.273.29] in terminated state Dec 23 15:49:22 HPBXProxy1-beta /usr/local/sbin/opensips[12140]: ERROR:b2b_logic:b2bl_bridge: Failed to send INVITE request Dec 23 15:49:22 HPBXProxy1-beta /usr/local/sbin/opensips[12140]: ERROR:call_center:set_call_leg: bridging failed Dec 23 15:49:22 HPBXProxy1-beta /usr/local/sbin/opensips[12140]: ERROR:call_center:b2bl_callback_customer: failed to set new destination for call Dec 23 15:49:22 HPBXProxy1-beta /usr/local/sbin/opensips[12140]: ERROR:b2b_logic:b2b_logic_notify_request: The callback function was unsuccessful Also the first member in the queue is given value 0, and the second is then given value 1, can it start at 1 or is there a reason behind it? Thanks Jon ________________________________ From: Bogdan-Andrei Iancu Sent: 23 December 2016 14:14 To: Jonathan Hunter; OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] opensips 2.1 call_center queue position Hi Jonathan, A Merry Christmas to you too ! I found a small mistake in the original patch I sent you. Please revert that one and use this new patch (see attachment). Let me know if it does the trick. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com [http://www.opensips-solutions.com/imgs/slideshow/slide3.jpg] Home — OpenSIPS Solutions www.opensips-solutions.com OpenSIPS is a mature Open Source implementation of a SIP server. OpenSIPS is more than a SIP proxy/router as it includes application-level functionalities. On 22.12.2016 13:58, Jonathan Hunter wrote: Hi Bogdan, Merry Christmas to you and the mailing list! I am testing the real queue position, and with one call in progress, and then 2 subsequent calls, both of which hit the hold music loop, I unfortunately dont see the position value increment, it remains at cc_pos=0 for all the calls, this is with just one queue defined to keep things very simple. Please let me know what debug or information you require, here are some outputs; opensipsctl fifo cc_list_calls Call:: 255.0 Ref=2 State=queued Call Time=2 Flow=Cust1 Call:: 884.0 Ref=2 State=queued Call Time=51 Flow=Cust1 Call:: 344.0 Ref=1 State=toagent Call Time=70 Flow=Cust1 Agent=2000 opensipsctl fifo cc_list_agents Agent:: 2000 Ref=1 Loged in=YES State=incall opensipsctl fifo cc_list_flows Flow:: Cust1 Avg Call Duration=199 Processed Calls=3 Logged Agents=1 Ongoing Calls=3 Ref=3 opensipsctl fifo cc_list_queue Call:: 0 Waiting for=114 ETW=0 Flow:: Cust1 Priority=256 Skill=custcare Call:: 1 Waiting for=65 ETW=199 Flow:: Cust1 Priority=256 Skill=custcare Many thanks Jon ________________________________ From: Bogdan-Andrei Iancu Sent: 07 November 2016 20:41 To: Jonathan Hunter; OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] opensips 2.1 call_center queue position Hi Jonathan, I was not able to test it with a real queue, so let me know if it really does the job (in terms of reporting the real position in the queue). Some questions: 1) currently I add that value only when sending to the queue / MOH - do you foresee any need to be added for other announcements like for welcome ? 2) will it be useful to add the ETW (estimate time to wait) ? is it useful ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Fri Jan 6 09:41:28 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Fri, 6 Jan 2017 16:41:28 +0200 Subject: [OpenSIPS-Users] 503 translated to 500 between opensips and homer In-Reply-To: <736252ef-2076-e207-2119-0129158f163d@greenlightcrm.com> References: <736252ef-2076-e207-2119-0129158f163d@greenlightcrm.com> Message-ID: <6aa39dec-1b17-9eeb-40b8-e7b46f9fabe3@opensips.org> Hi Richard, Any incoming 503 reply is converted by OpenSIPS to a 500 reply (as per RFC3261). Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 06.01.2017 16:22, Richard Robson wrote: > > Hi, > > > we are getting 503 messages back but when this is stored on Homer as a > 500. I'm not sure if its Opensips's sipcapture module or Homer doing > the translation > > > This is the packet captured in sngrep in the sip box > > 2017/01/06 14:13:59.210301 141.170.24.20:5060 -> 192.168.36.141:5060 > SIP/2.0 503 Service Unavailable > Via: SIP/2.0/UDP 141.170.9.156:5060;branch=z9hG4bKd116.a30f9976.0 > From: ;tag=as55dfe54a > To: ;tag=gK00d54f0d > Call-ID: > DLGCH_e0lXV2Z/MWR7SFYIMHFjZ3oSAwoyL2YwfkdXX2F5YGsPQVxcfXhma2FDU0BlcWpmf0ZV > CSeq: 103 INVITE > X-ISUPMtype:0c > Reason: Q.850;cause=41;x-source=a > Content-Length: 0 > > this is the same packet viewed in Homer > > 2017-01-06 14:13:59 +0000 : 141.170.24.20:5060 -> 192.168.36.141:5060 > SIP/2.0 *500* Service Unavailable Via: SIP/2.0/UDP > 141.170.9.156:5060;branch=*z9hG4bKd116.a30f9976.0* From: > ;tag=*as55dfe54a* To: > ;tag=gK00d54f0d Call-ID: > *492956a7483fc8345bfdaf6c17212008 at 192.168.36.68:5060* CSeq: 103 INVITE > X-ISUPMtype:0c Reason: Q.850;cause=41;x-source=a Content-Length: 0 > > the sip code and the callid have been changed. the call id is the same > as the original call from the outbound asterisk box > > > Regards, > -- > Richard Robson > Greenlight Support > 01382 843843 > support at greenlightcrm.com > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From rrobson at greenlightcrm.com Fri Jan 6 10:14:35 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Fri, 6 Jan 2017 15:14:35 +0000 Subject: [OpenSIPS-Users] 503 translated to 500 between opensips and homer In-Reply-To: <6aa39dec-1b17-9eeb-40b8-e7b46f9fabe3@opensips.org> References: <736252ef-2076-e207-2119-0129158f163d@greenlightcrm.com> <6aa39dec-1b17-9eeb-40b8-e7b46f9fabe3@opensips.org> Message-ID: <285ee3fa-b1f7-e6ae-8729-6c8e5300cc10@greenlightcrm.com> An HTML attachment was scrubbed... URL: From bogdan at opensips.org Fri Jan 6 10:19:25 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Fri, 6 Jan 2017 17:19:25 +0200 Subject: [OpenSIPS-Users] 503 translated to 500 between opensips and homer In-Reply-To: <285ee3fa-b1f7-e6ae-8729-6c8e5300cc10@greenlightcrm.com> References: <736252ef-2076-e207-2119-0129158f163d@greenlightcrm.com> <6aa39dec-1b17-9eeb-40b8-e7b46f9fabe3@opensips.org> <285ee3fa-b1f7-e6ae-8729-6c8e5300cc10@greenlightcrm.com> Message-ID: <683d7375-1739-bf23-51d9-2aeb97f0d3db@opensips.org> Hi Richard, See rfc3261, chapter 6 "Choosing the best response", Page 111 : A proxy which receives a 503 (Service Unavailable) response SHOULD NOT forward it upstream unless it can determine that any subsequent requests it might proxy will also generate a 503. In other words, forwarding a 503 means that the proxy knows it cannot service any requests, not just the one for the Request- URI in the request which generated the 503. If the only response that was received is a 503, the proxy SHOULD generate a 500 response and forward that upstream. Still, this gives you access (at script level) to the 503 reply (the change is done when sending it out), so you can investigate the Reason hdr (if present). And yes, we got your other email. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 06.01.2017 17:14, Richard Robson wrote: > hmm, > > both our suppliers translate an unavailable number (Q.850;cause=41) as > a 503. > > I Guess Im going to have to live with that. > > Did you see the other email this morning regarding opensips crashing? > I unhelpfully called the email opensipsp > > > > On 06/01/2017 14:41, Bogdan-Andrei Iancu wrote: >> Hi Richard, >> >> Any incoming 503 reply is converted by OpenSIPS to a 500 reply (as >> per RFC3261). >> >> Regards, >> Bogdan-Andrei Iancu >> OpenSIPS Founder and Developer >> http://www.opensips-solutions.com >> On 06.01.2017 16:22, Richard Robson wrote: >>> >>> Hi, >>> >>> >>> we are getting 503 messages back but when this is stored on Homer as >>> a 500. I'm not sure if its Opensips's sipcapture module or Homer >>> doing the translation >>> >>> >>> This is the packet captured in sngrep in the sip box >>> >>> 2017/01/06 14:13:59.210301 141.170.24.20:5060 -> 192.168.36.141:5060 >>> SIP/2.0 503 Service Unavailable >>> Via: SIP/2.0/UDP 141.170.9.156:5060;branch=z9hG4bKd116.a30f9976.0 >>> From: ;tag=as55dfe54a >>> To: ;tag=gK00d54f0d >>> Call-ID: >>> DLGCH_e0lXV2Z/MWR7SFYIMHFjZ3oSAwoyL2YwfkdXX2F5YGsPQVxcfXhma2FDU0BlcWpmf0ZV >>> CSeq: 103 INVITE >>> X-ISUPMtype:0c >>> Reason: Q.850;cause=41;x-source=a >>> Content-Length: 0 >>> >>> this is the same packet viewed in Homer >>> >>> 2017-01-06 14:13:59 +0000 : 141.170.24.20:5060 -> 192.168.36.141:5060 >>> SIP/2.0 *500* Service Unavailable Via: SIP/2.0/UDP >>> 141.170.9.156:5060;branch=*z9hG4bKd116.a30f9976.0* From: >>> ;tag=*as55dfe54a* To: >>> ;tag=gK00d54f0d Call-ID: >>> *492956a7483fc8345bfdaf6c17212008 at 192.168.36.68:5060* CSeq: 103 >>> INVITE X-ISUPMtype:0c Reason: Q.850;cause=41;x-source=a >>> Content-Length: 0 >>> >>> the sip code and the callid have been changed. the call id is the >>> same as the original call from the outbound asterisk box >>> >>> >>> Regards, >>> -- >>> Richard Robson >>> Greenlight Support >>> 01382 843843 >>> support at greenlightcrm.com >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > > > -- > Richard Robson > Greenlight Support > 01382 843843 > support at greenlightcrm.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From xaled at web.de Fri Jan 6 10:44:39 2017 From: xaled at web.de (xaled) Date: Fri, 6 Jan 2017 16:44:39 +0100 Subject: [OpenSIPS-Users] How to parse XML Body? In-Reply-To: <01f101d2674f$dadadee0$90909ca0$@web.de> References: <012c01d266bf$841c7590$8c5560b0$@web.de> <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> <018601d26742$7d877ee0$78967ca0$@web.de> <4936e66b-ae31-a9fa-e260-a87ef6b24b20@opensips.org> <019a01d26746$00669460$0133bd20$@web.de> <01b601d26748$2bebb6e0$83c324a0$@web.de> <01428a9e-5f55-5a7e-154d-59c2f8e96ef0@opensips.org> <01f101d2674f$dadadee0$90909ca0$@web.de> Message-ID: <032b01d26833$cace6370$606b2a50$@web.de> Hi Bogdan, can you give any hints on how to get the Coordinates values and not the whole xml body from the regex subst? Sorry for being not clever enough to figure it out myself. Thanks Hi Bogdan, $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); DBG:core:subst_run:matched shows the needed XML element with value, but not the value alone. The xlog output shows the whole XML body without gml:Coordinates. 2017-01-05T13:23:23.104982+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:tr_eval_re: Trying to apply reg exp [/gml:Coordinates>(.*)<\/gml:Coordinates/\1/] on : [#015#012#015#012 #015#012 #015#012 #015#012 #015#012 #015#012 #015#012 12.32 34.24#015#012 #015#012 #015#012 #015#012 #015#012 no#015#012 #015#012 #01 5#012 #015#012 #015#012 2016-8-02T04:13:23Z#015#012 #015#0 12#015#012#015#012] 2017-01-05T13:23:23.107376+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:tr_eval_re: we must compile the regexp 2017-01-05T13:23:23.107903+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_parser: ok, se is 0x7f39a 5d0a1f0 2017-01-05T13:23:23.108241+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_run: running. r=0 2017-01-05T13:23:23.111918+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_run: matched (404, 45): [ gml:Coordinates>12.32 34.24#015#012#015#0 12 #015#012 #015#012 #015#012 #015#012 #015#012 #015#012 <12.32 34.24>#015#012 #015#012 #015#012 #015#012 #015#012 no#015#012 #015#012 #015# 012 #015#012 #015#012 2016-8-02T04:13:23Z#015#012 #015#012 Thanks From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Donnerstag, 5. Januar 2017 13:12 To: OpenSIPS users mailling list >; xaled > Subject: Re: [OpenSIPS-Users] How to parse XML Body? Try $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; -------------- next part -------------- An HTML attachment was scrubbed... URL: From opensips-list at daork.net Sat Jan 7 04:10:35 2017 From: opensips-list at daork.net (Nathan Ward) Date: Sat, 7 Jan 2017 22:10:35 +1300 Subject: [OpenSIPS-Users] 2.2.2 packaging Message-ID: <0B67E9B3-48DE-4341-AABD-FA16DD38B326@daork.net> Hi, I am running OpenSIPS 2.2.2 from RPMs from the opensips.org yum server. I am trying to find out where the SPEC files to generate the CentOS (/el7) RPMs are. I don’t seem to be able to find these in GitHub. Can someone help with this? I am hoping to submit a PR to move the ‘opensips’ binary to /usr/libexec, rather than a common $PATH location. We have had a problem where this binary was mistakenly run, rather than opensipsctl. Typically, daemon binaries that do not generally get run by users should be in /usr/libexec so that they are only very intentionally executed. This should probably go in to at the very least a minor version change as it may break some people’s custom init scripts etc. On my search, I note change 9e406b2b3acfd61b39ba9679f0a599b95f56f5c2 under the 2.2.2 tag, which appears to be done with something like: sed ’s/2.2.1/2.2.2/‘ Note the matches where . is ‘any’ not a literal period, so there are a lot of dates that get messed up: -* Mon Oct 12.2.19 Bogdan-Andrei Iancu +* Mon Oct 12.2.29 Bogdan-Andrei Iancu -- Nathan Ward From khamlichi.khalil at gmail.com Sun Jan 8 06:11:52 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Sun, 8 Jan 2017 11:11:52 +0000 Subject: [OpenSIPS-Users] do_routing function first argument Message-ID: Hi eveyone, I have been trying to understand the first argument to the d o_routing("1","",,"$var(rule_attrs)") Can anyone please give some explanation of the first argument to this function ? what does the "1" stands for and where does it fit in the logic back in the database setup (in my scenario it's mostly drouting tables) Thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL: From johan at democon.be Sun Jan 8 08:24:37 2017 From: johan at democon.be (Johan De Clercq) Date: Sun, 8 Jan 2017 14:24:37 +0100 Subject: [OpenSIPS-Users] do_routing function first argument In-Reply-To: References: Message-ID: I think that's route set id. On 08 Jan 2017 12:12 PM, "Khalil Khamlichi" wrote: > Hi eveyone, > > I have been trying to understand the first argument to the d > o_routing("1","",,"$var(rule_attrs)") > > Can anyone please give some explanation of the first argument to this > function ? what does the "1" stands for and where does it fit in the logic > back in the database setup (in my scenario it's mostly drouting tables) > > Thanks in advance. > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Sun Jan 8 13:23:23 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Sun, 8 Jan 2017 18:23:23 +0000 Subject: [OpenSIPS-Users] do_routing function first argument In-Reply-To: References: Message-ID: Well you get to my point, shouldn't it be in the database then ? whats the point in having it hard coded inside the config file ? On Sun, Jan 8, 2017 at 1:24 PM, Johan De Clercq wrote: > I think that's route set id. > > On 08 Jan 2017 12:12 PM, "Khalil Khamlichi" > wrote: > >> Hi eveyone, >> >> I have been trying to understand the first argument to the d >> o_routing("1","",,"$var(rule_attrs)") >> >> Can anyone please give some explanation of the first argument to this >> function ? what does the "1" stands for and where does it fit in the logic >> back in the database setup (in my scenario it's mostly drouting tables) >> >> Thanks in advance. >> >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob.dyck at telus.net Sun Jan 8 15:49:46 2017 From: rob.dyck at telus.net (Robert Dyck) Date: Sun, 08 Jan 2017 12:49:46 -0800 Subject: [OpenSIPS-Users] Install opensips to systemd Message-ID: <6871712.CTN75Gpv8W@blacky.mylan> I had a working opensips 1.11 installed by Fedora package manager. I have been trying opensips 2.2.2 and decided to make the jump. Since 2.2.2 is not available as a package from Fedora I cloned the source. I have tried installing using menuconfig and also make but neither installs the necessary files for systemd. I see that the files exist in the source directory "packaging". Is there a way to trigger the installation of the necessary files for systemd or does it need to be done manually. I have thought of re-installing 1.11 from the package manager and then overwriting the opensips binary. The problem I see is that a package upgrade would overwrite 2.2.2 because the package manager sees opensips as an installed package. From razvan at opensips.org Mon Jan 9 03:25:31 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Mon, 9 Jan 2017 10:25:31 +0200 Subject: [OpenSIPS-Users] do_routing function first argument In-Reply-To: References: Message-ID: <98867387-80d0-9bed-bbe4-ac300695c539@opensips.org> Hello, Khalil! If you check the documentation of the do_routing function[1], you will see that the group is not mandatory. If it exists, then it will use the route set within that group. If it does not exist, the group is determined from the dr_group table in the database - this is just a simple mapping between user and group. If you would like to have a more flexible approach, where you determine the route set using a more complex logic than a simple matching, then you will have to implement that logic in the script to find the group, and provide it to the do_routing() function. I hope I answered you question now. [1] http://www.opensips.org/html/docs/modules/2.2.x/drouting.html#id295067 Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/08/2017 08:23 PM, Khalil Khamlichi wrote: > Well you get to my point, shouldn't it be in the database then ? whats > the point in having it hard coded inside the config file ? > > On Sun, Jan 8, 2017 at 1:24 PM, Johan De Clercq > wrote: > > I think that's route set id. > > On 08 Jan 2017 12:12 PM, "Khalil Khamlichi" > > > wrote: > > Hi eveyone, > > I have been trying to understand the first argument to the > do_routing("1","",,"$var(rule_attrs)") > > Can anyone please give some explanation of the first argument > to this function ? what does the "1" stands for and where does > it fit in the logic back in the database setup (in my scenario > it's mostly drouting tables) > > Thanks in advance. > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Mon Jan 9 03:27:01 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Mon, 9 Jan 2017 10:27:01 +0200 Subject: [OpenSIPS-Users] Install opensips to systemd In-Reply-To: <6871712.CTN75Gpv8W@blacky.mylan> References: <6871712.CTN75Gpv8W@blacky.mylan> Message-ID: No, unfortunately there is no way to install the systemd files automatically, you have to do it manually. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/08/2017 10:49 PM, Robert Dyck wrote: > I had a working opensips 1.11 installed by Fedora package manager. I have been > trying opensips 2.2.2 and decided to make the jump. Since 2.2.2 is not > available as a package from Fedora I cloned the source. > > I have tried installing using menuconfig and also make but neither installs the > necessary files for systemd. I see that the files exist in the source directory > "packaging". Is there a way to trigger the installation of the necessary files > for systemd or does it need to be done manually. > > I have thought of re-installing 1.11 from the package manager and then > overwriting the opensips binary. The problem I see is that a package upgrade > would overwrite 2.2.2 because the package manager sees opensips as an > installed package. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From nick.altmann at gmail.com Mon Jan 9 03:35:52 2017 From: nick.altmann at gmail.com (Nick Altmann) Date: Mon, 9 Jan 2017 11:35:52 +0300 Subject: [OpenSIPS-Users] 2.2.2 packaging In-Reply-To: <0B67E9B3-48DE-4341-AABD-FA16DD38B326@daork.net> References: <0B67E9B3-48DE-4341-AABD-FA16DD38B326@daork.net> Message-ID: Hello, You could find packaging specification in packaging/redhat_fedora folder in git tree. However in my opinion there is no need to change opensips binary into libexec folder. There is no general rule to do it, most daemons in rhel are placed in /usr/sbin as opensips. For example sshd. Do you also run it instead of ssh? You may not use /usr/sbin in your PATH. Of course you can generate your own packages to avoid this. 2017-01-07 12:10 GMT+03:00 Nathan Ward : > Hi, > > I am running OpenSIPS 2.2.2 from RPMs from the opensips.org yum server. > > I am trying to find out where the SPEC files to generate the CentOS (/el7) > RPMs are. I don’t seem to be able to find these in GitHub. Can someone help > with this? > > > I am hoping to submit a PR to move the ‘opensips’ binary to /usr/libexec, > rather than a common $PATH location. We have had a problem where this > binary was mistakenly run, rather than opensipsctl. Typically, daemon > binaries that do not generally get run by users should be in /usr/libexec > so that they are only very intentionally executed. This should probably go > in to at the very least a minor version change as it may break some > people’s custom init scripts etc. > > > On my search, I note change 9e406b2b3acfd61b39ba9679f0a599b95f56f5c2 > under the 2.2.2 tag, which appears to be done with something like: > sed ’s/2.2.1/2.2.2/‘ > > Note the matches where . is ‘any’ not a literal period, so there are a lot > of dates that get messed up: > -* Mon Oct 12.2.19 Bogdan-Andrei Iancu > +* Mon Oct 12.2.29 Bogdan-Andrei Iancu > > -- > Nathan Ward > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Mon Jan 9 03:36:30 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Mon, 9 Jan 2017 10:36:30 +0200 Subject: [OpenSIPS-Users] 2.2.2 packaging In-Reply-To: <0B67E9B3-48DE-4341-AABD-FA16DD38B326@daork.net> References: <0B67E9B3-48DE-4341-AABD-FA16DD38B326@daork.net> Message-ID: <6a2d9939-a15e-543c-df48-cc54fb606ba4@opensips.org> Hello, Nathan! You have my answer inline. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/07/2017 11:10 AM, Nathan Ward wrote: > Hi, > > I am running OpenSIPS 2.2.2 from RPMs from the opensips.org yum server. > > I am trying to find out where the SPEC files to generate the CentOS (/el7) RPMs are. I don’t seem to be able to find these in GitHub. Can someone help with this? Nick (CC'ed) is maintaining the SPECS for the CentOS RPMs, but I am not sure all changes are integrated in the RPM files. But AFAIK, they are based on the public specs here: https://github.com/OpenSIPS/opensips/blob/2.2/packaging/rpm/opensips.spec.CentOS > > > I am hoping to submit a PR to move the ‘opensips’ binary to /usr/libexec, rather than a common $PATH location. We have had a problem where this binary was mistakenly run, rather than opensipsctl. Typically, daemon binaries that do not generally get run by users should be in /usr/libexec so that they are only very intentionally executed. This should probably go in to at the very least a minor version change as it may break some people’s custom init scripts etc. I am not sure I fully agree with this. /usr/libexec contain binaries that should never be run as stand-alone. But that is not OpenSIPS' case, where you can easily start it in debug mode or smth like that. For example, a similar daemon is sshd, which is located in /usr/sbin/sshd. However, internally triggered binaries, such as sftp-server are located in /usr/libexec/openssh/sftp-server. This exec should never be executed outside sshd. > > > On my search, I note change 9e406b2b3acfd61b39ba9679f0a599b95f56f5c2 under the 2.2.2 tag, which appears to be done with something like: > sed ’s/2.2.1/2.2.2/‘ > > Note the matches where . is ‘any’ not a literal period, so there are a lot of dates that get messed up: > -* Mon Oct 12.2.19 Bogdan-Andrei Iancu > +* Mon Oct 12.2.29 Bogdan-Andrei Iancu You are right, this is a bug in my changelog update script. I will update it now. Best regards, Răzvan From razvan at opensips.org Mon Jan 9 03:38:55 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Mon, 9 Jan 2017 10:38:55 +0200 Subject: [OpenSIPS-Users] 2.2.2 packaging In-Reply-To: <6a2d9939-a15e-543c-df48-cc54fb606ba4@opensips.org> References: <0B67E9B3-48DE-4341-AABD-FA16DD38B326@daork.net> <6a2d9939-a15e-543c-df48-cc54fb606ba4@opensips.org> Message-ID: <7af11962-3e57-2b66-2c7b-c2057fad38ec@opensips.org> Actually as Nick pointed out, the rpm specs used are here: https://github.com/OpenSIPS/opensips/tree/2.2/packaging/redhat_fedora Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/09/2017 10:36 AM, Răzvan Crainea wrote: > Hello, Nathan! > > You have my answer inline. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > > On 01/07/2017 11:10 AM, Nathan Ward wrote: >> Hi, >> >> I am running OpenSIPS 2.2.2 from RPMs from the opensips.org yum server. >> >> I am trying to find out where the SPEC files to generate the CentOS >> (/el7) RPMs are. I don’t seem to be able to find these in GitHub. Can >> someone help with this? > Nick (CC'ed) is maintaining the SPECS for the CentOS RPMs, but I am > not sure all changes are integrated in the RPM files. But AFAIK, they > are based on the public specs here: > https://github.com/OpenSIPS/opensips/blob/2.2/packaging/rpm/opensips.spec.CentOS > >> >> >> I am hoping to submit a PR to move the ‘opensips’ binary to >> /usr/libexec, rather than a common $PATH location. We have had a >> problem where this binary was mistakenly run, rather than >> opensipsctl. Typically, daemon binaries that do not generally get run >> by users should be in /usr/libexec so that they are only very >> intentionally executed. This should probably go in to at the very >> least a minor version change as it may break some people’s custom >> init scripts etc. > I am not sure I fully agree with this. /usr/libexec contain binaries > that should never be run as stand-alone. But that is not OpenSIPS' > case, where you can easily start it in debug mode or smth like that. > For example, a similar daemon is sshd, which is located in > /usr/sbin/sshd. However, internally triggered binaries, such as > sftp-server are located in /usr/libexec/openssh/sftp-server. This exec > should never be executed outside sshd. >> >> >> On my search, I note change 9e406b2b3acfd61b39ba9679f0a599b95f56f5c2 >> under the 2.2.2 tag, which appears to be done with something like: >> sed ’s/2.2.1/2.2.2/‘ >> >> Note the matches where . is ‘any’ not a literal period, so there are >> a lot of dates that get messed up: >> -* Mon Oct 12.2.19 Bogdan-Andrei Iancu >> +* Mon Oct 12.2.29 Bogdan-Andrei Iancu > You are right, this is a bug in my changelog update script. I will > update it now. > > Best regards, > Răzvan > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From opensips-list at daork.net Mon Jan 9 05:09:26 2017 From: opensips-list at daork.net (Nathan Ward) Date: Mon, 9 Jan 2017 23:09:26 +1300 Subject: [OpenSIPS-Users] 2.2.2 packaging In-Reply-To: <6a2d9939-a15e-543c-df48-cc54fb606ba4@opensips.org> References: <0B67E9B3-48DE-4341-AABD-FA16DD38B326@daork.net> <6a2d9939-a15e-543c-df48-cc54fb606ba4@opensips.org> Message-ID: > On 9/01/2017, at 9:36 PM, Răzvan Crainea wrote: > > Hello, Nathan! Hi! > You have my answer inline. Likewise. > On 01/07/2017 11:10 AM, Nathan Ward wrote: >> Hi, >> >> I am running OpenSIPS 2.2.2 from RPMs from the opensips.org yum server. >> >> I am trying to find out where the SPEC files to generate the CentOS (/el7) RPMs are. I don’t seem to be able to find these in GitHub. Can someone help with this? > Nick (CC'ed) is maintaining the SPECS for the CentOS RPMs, but I am not sure all changes are integrated in the RPM files. But AFAIK, they are based on the public specs here: > https://github.com/OpenSIPS/opensips/blob/2.2/packaging/rpm/opensips.spec.CentOS I don’t believe this to be the case, as the “Version:” line says 2.2.0, while the published RPMs are 2.2.2. >> I am hoping to submit a PR to move the ‘opensips’ binary to /usr/libexec, rather than a common $PATH location. We have had a problem where this binary was mistakenly run, rather than opensipsctl. Typically, daemon binaries that do not generally get run by users should be in /usr/libexec so that they are only very intentionally executed. This should probably go in to at the very least a minor version change as it may break some people’s custom init scripts etc. > I am not sure I fully agree with this. /usr/libexec contain binaries that should never be run as stand-alone. But that is not OpenSIPS' case, where you can easily start it in debug mode or smth like that. For example, a similar daemon is sshd, which is located in /usr/sbin/sshd. However, internally triggered binaries, such as sftp-server are located in /usr/libexec/openssh/sftp-server. This exec should never be executed outside sshd. Hmmm, I’ve seen other applications ship with the daemon binary in libexec.. though I can’t recall what it was off the top of my head. It seemed a sensible thing to do. It would be unusual on a production system to run the daemon binary as a user, stashing it off to the side means it’ll only be run when very clearly intended. I am curious, why did “opensips monitor” allow it to run - I would have expected that to reject “monitor”.. the man page for “opensips” has nothing about accepting an argument like that. Perhaps a partial solution to this would be preventing the binary from running if there are unrecognised arguments? >> On my search, I note change 9e406b2b3acfd61b39ba9679f0a599b95f56f5c2 under the 2.2.2 tag, which appears to be done with something like: >> sed ’s/2.2.1/2.2.2/‘ >> >> Note the matches where . is ‘any’ not a literal period, so there are a lot of dates that get messed up: >> -* Mon Oct 12.2.19 Bogdan-Andrei Iancu >> +* Mon Oct 12.2.29 Bogdan-Andrei Iancu > You are right, this is a bug in my changelog update script. I will update it now. Great :) -- Nathan Ward -------------- next part -------------- An HTML attachment was scrubbed... URL: From opensips-list at daork.net Mon Jan 9 05:14:46 2017 From: opensips-list at daork.net (Nathan Ward) Date: Mon, 9 Jan 2017 23:14:46 +1300 Subject: [OpenSIPS-Users] 2.2.2 packaging In-Reply-To: References: <0B67E9B3-48DE-4341-AABD-FA16DD38B326@daork.net> Message-ID: <63CF076D-5B82-46B4-91D5-551CFC974A56@daork.net> > On 9/01/2017, at 9:35 PM, Nick Altmann wrote: > > For example sshd. Do you also run it instead of ssh? No, as that is longer, so it doesn’t really make sense that someone would run that. In this case, the user typed “opensi monitor”. Running “ssh” instead of “ssh-add” is a better argument, though, running “ssh” instead of “ssh-add” has very limited impact as it doesn’t run a daemon that accepts unexpected arguments and disappears in to the background. Perhaps the convention of “d” on the end of an application primarily intended as a daemon (i.e. ‘opensipsd’) would be an alternative solution (and rejecting unexpected arguments, too). Happy to submit PRs for these, if that’s a better middle ground :) -- Nathan Ward -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Mon Jan 9 05:36:09 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Mon, 9 Jan 2017 12:36:09 +0200 Subject: [OpenSIPS-Users] OpenSips 2.2 Error Message-ID: Hello, Here is my problem: OpenSips 2.2.2 - latest OS - CentOS Linux release 7.3.1611 opensips.cfg ..... loadmodule "aaa_radius.so" ...... aaa_radius.so exists in /usr/local/lib64/opensips/modules Here is list of Eroors Jan 9 12:30:34 dev opensips: ERROR:core:sr_load_module: could not open module : /usr/local/lib64/opensips/modules/aaa_radius.so: undefined symbol: rc_acct_resume Jan 9 12:30:34 dev opensips: ERROR:core:load_module: failed to load module Jan 9 12:30:34 dev opensips: CRITICAL:core:yyerror: parse error in config file /etc/opensips/opensips.cfg, line 53, column 13-14: failed to load module aaa_radius.so Jan 9 12:30:34 dev opensips: ERROR:core:set_mod_param_regex: no module matching aaa_radius found -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Mon Jan 9 05:44:15 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Mon, 9 Jan 2017 10:44:15 +0000 Subject: [OpenSIPS-Users] OpenSips 2.2 Error In-Reply-To: References: Message-ID: you need to set this parameter for the module to load correctly Jan 9 12:30:34 dev opensips: ERROR:core:set_mod_param_regex: no module matching aaa_radius found On Mon, Jan 9, 2017 at 10:36 AM, Dragomir Haralambiev wrote: > Hello, > > Here is my problem: > > OpenSips 2.2.2 - latest > OS - CentOS Linux release 7.3.1611 > > opensips.cfg > ..... > loadmodule "aaa_radius.so" > ...... > > aaa_radius.so exists in /usr/local/lib64/opensips/modules > > Here is list of Eroors > > > Jan 9 12:30:34 dev opensips: ERROR:core:sr_load_module: could not open > module : > /usr/local/lib64/opensips/modules/aaa_radius.so: undefined symbol: > rc_acct_resume > Jan 9 12:30:34 dev opensips: ERROR:core:load_module: failed to load module > Jan 9 12:30:34 dev opensips: CRITICAL:core:yyerror: parse error in config > file /etc/opensips/opensips.cfg, line 53, column 13-14: failed to load > module aaa_radius.so > Jan 9 12:30:34 dev opensips: ERROR:core:set_mod_param_regex: no module > matching aaa_radius found > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Mon Jan 9 05:59:16 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Mon, 9 Jan 2017 12:59:16 +0200 Subject: [OpenSIPS-Users] OpenSips 2.2 Error In-Reply-To: References: Message-ID: I have this line: loadmodule "aaa_radius.so" Where is problem? 2017-01-09 12:44 GMT+02:00 Khalil Khamlichi : > you need to set this parameter for the module to load correctly > > Jan 9 12:30:34 dev opensips: ERROR:core:set_mod_param_regex: no module > matching aaa_radius found > > On Mon, Jan 9, 2017 at 10:36 AM, Dragomir Haralambiev > wrote: > >> Hello, >> >> Here is my problem: >> >> OpenSips 2.2.2 - latest >> OS - CentOS Linux release 7.3.1611 >> >> opensips.cfg >> ..... >> loadmodule "aaa_radius.so" >> ...... >> >> aaa_radius.so exists in /usr/local/lib64/opensips/modules >> >> Here is list of Eroors >> >> >> Jan 9 12:30:34 dev opensips: ERROR:core:sr_load_module: could not open >> module : >> /usr/local/lib64/opensips/modules/aaa_radius.so: undefined symbol: >> rc_acct_resume >> Jan 9 12:30:34 dev opensips: ERROR:core:load_module: failed to load >> module >> Jan 9 12:30:34 dev opensips: CRITICAL:core:yyerror: parse error in >> config file /etc/opensips/opensips.cfg, line 53, column 13-14: failed to >> load module aaa_radius.so >> Jan 9 12:30:34 dev opensips: ERROR:core:set_mod_param_regex: no module >> matching aaa_radius found >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Mon Jan 9 07:09:06 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Mon, 9 Jan 2017 14:09:06 +0200 Subject: [OpenSIPS-Users] AAA RADIUS MODULE - Problem Message-ID: I reed docs for AAA Radius module1.2.2. External Libraries or Applications ..... By default, radiusclient-ng is used. To change at compile time to freeradius, uncomment the USE_FREERADIUS=1 line in main Makefile. In Makefile I not see USE_FREERADIUS=1. Here is only FREERADIUS. If use freeradius-client-1.1.7 what I do? Best regards, Dragomir -------------- next part -------------- An HTML attachment was scrubbed... URL: From ionutionita at opensips.org Mon Jan 9 07:55:33 2017 From: ionutionita at opensips.org (Ionut Ionita) Date: Mon, 9 Jan 2017 14:55:33 +0200 Subject: [OpenSIPS-Users] AAA RADIUS MODULE - Problem In-Reply-To: References: Message-ID: Fixed. Thanks for reporting. "FREERADIUS" has the same behaviour as the old "USE_FREERADIUS". Regards, Ionut Ionita OpenSIPS Developer On 01/09/2017 02:09 PM, Dragomir Haralambiev wrote: > > > I reed docs for AAA Radius module > > > 1.2.2. External Libraries or Applications > ..... > By default, radiusclient-ng is used. To change at compile time > to freeradius, uncomment the USE_FREERADIUS=1 line in main Makefile. > > In Makefile I not see USE_FREERADIUS=1. Here is only FREERADIUS. > > If use freeradius-client-1.1.7 what I do? > > Best regards, > Dragomir > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Mon Jan 9 08:04:40 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Mon, 9 Jan 2017 15:04:40 +0200 Subject: [OpenSIPS-Users] AAA RADIUS MODULE - Problem In-Reply-To: References: Message-ID: Hi, Thanks for your quick replay. When try to start Opensips with aaa_radius support I receive follow Errors: Jan 9 14:57:40 dev opensips: ERROR:core:sr_load_module: could not open module : /usr/local/lib64/opensips/modules/aaa_radius.so: undefined symbol: rc_acct_resume Jan 9 14:57:40 dev opensips: ERROR:core:load_module: failed to load module Jan 9 14:57:40 dev opensips: CRITICAL:core:yyerror: parse error in config file /etc/opensips/opensips.cfg, line 53, column 13-14: failed to load module aaa_radius.so Jan 9 14:57:40 dev opensips: ERROR:core:set_mod_param_regex: no module matching aaa_radius found What I do? 2017-01-09 14:55 GMT+02:00 Ionut Ionita : > > Fixed. Thanks for reporting. "FREERADIUS" has the same behaviour as the > old "USE_FREERADIUS". > > > Regards, > > Ionut Ionita > OpenSIPS Developer > > On 01/09/2017 02:09 PM, Dragomir Haralambiev wrote: > > I reed docs for AAA Radius module 1.2.2. External Libraries or > Applications > ..... > By default, radiusclient-ng is used. To change at compile time to > freeradius, uncomment the USE_FREERADIUS=1 line in main Makefile. > > In Makefile I not see USE_FREERADIUS=1. Here is only FREERADIUS. > > If use freeradius-client-1.1.7 what I do? > > Best regards, > Dragomir > > > > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Mon Jan 9 08:18:36 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Mon, 9 Jan 2017 15:18:36 +0200 Subject: [OpenSIPS-Users] AAA RADIUS MODULE - Problem In-Reply-To: References: Message-ID: I see in /modules/aaa_radius/aaa_radius.c and rad.c follow lines: #ifndef USE_FREERADIUS #include #else #include #endif The last USE_FREERADIUS=1 ot FREERADIUS=1 2017-01-09 14:55 GMT+02:00 Ionut Ionita : > > Fixed. Thanks for reporting. "FREERADIUS" has the same behaviour as the > old "USE_FREERADIUS". > > > Regards, > > Ionut Ionita > OpenSIPS Developer > > On 01/09/2017 02:09 PM, Dragomir Haralambiev wrote: > > I reed docs for AAA Radius module 1.2.2. External Libraries or > Applications > ..... > By default, radiusclient-ng is used. To change at compile time to > freeradius, uncomment the USE_FREERADIUS=1 line in main Makefile. > > In Makefile I not see USE_FREERADIUS=1. Here is only FREERADIUS. > > If use freeradius-client-1.1.7 what I do? > > Best regards, > Dragomir > > > > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From trance_maniak at o2.pl Mon Jan 9 03:58:51 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Mon, 9 Jan 2017 01:58:51 -0700 (MST) Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <586CAAD9.5060906@easycall.pl> References: <1483431205315-7605411.post@n2.nabble.com> <4fa36195-2654-2697-ebb1-e55314b58147@opensips.org> <1483448415681-7605416.post@n2.nabble.com> <586CAAD9.5060906@easycall.pl> Message-ID: <1483952331826-7605485.post@n2.nabble.com> Have You got any clue, why this is happnning? -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605485.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From ionutionita at opensips.org Mon Jan 9 11:13:17 2017 From: ionutionita at opensips.org (Ionut Ionita) Date: Mon, 9 Jan 2017 18:13:17 +0200 Subject: [OpenSIPS-Users] AAA RADIUS MODULE - Problem In-Reply-To: References: Message-ID: <09e59338-24ef-38dd-f6c1-e671e672affb@opensips.org> Did you follow the steps in the docs on how to apply the async patch[0] if you want to use it? [0] http://www.opensips.org/html/docs/modules/2.2.x/aaa_radius#id294296 Ionut Ionita OpenSIPS Developer On 01/09/2017 03:04 PM, Dragomir Haralambiev wrote: > Hi, > > Thanks for your quick replay. > > When try to start Opensips with aaa_radius support I receive follow > Errors: > > Jan 9 14:57:40 dev opensips: ERROR:core:sr_load_module: could not > open module : > /usr/local/lib64/opensips/modules/aaa_radius.so: undefined symbol: > rc_acct_resume > Jan 9 14:57:40 dev opensips: ERROR:core:load_module: failed to load > module > Jan 9 14:57:40 dev opensips: CRITICAL:core:yyerror: parse error in > config file /etc/opensips/opensips.cfg, line 53, column 13-14: failed > to load module aaa_radius.so > Jan 9 14:57:40 dev opensips: ERROR:core:set_mod_param_regex: no > module matching aaa_radius found > > > What I do? > > 2017-01-09 14:55 GMT+02:00 Ionut Ionita >: > > > Fixed. Thanks for reporting. "FREERADIUS" has the same > behaviour as the old "USE_FREERADIUS". > > > Regards, > > Ionut Ionita > OpenSIPS Developer > > On 01/09/2017 02:09 PM, Dragomir Haralambiev wrote: >> >> >> I reed docs for AAA Radius module >> >> >> 1.2.2. External Libraries or Applications >> ..... >> By default, radiusclient-ng is used. To change at compile >> time to freeradius, uncomment the USE_FREERADIUS=1 line in >> main Makefile. >> >> In Makefile I not see USE_FREERADIUS=1. Here is only FREERADIUS. >> >> If use freeradius-client-1.1.7 what I do? >> >> Best regards, >> Dragomir >> >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > _______________________________________________ Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Mon Jan 9 11:52:55 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Mon, 9 Jan 2017 18:52:55 +0200 Subject: [OpenSIPS-Users] AAA RADIUS MODULE - Problem In-Reply-To: <09e59338-24ef-38dd-f6c1-e671e672affb@opensips.org> References: <09e59338-24ef-38dd-f6c1-e671e672affb@opensips.org> Message-ID: Yes I applay patch with follow command: mkdir freeRADIUS-client; cd freeRADIUS-client wget ftp://ftp.freeradius.org/pub/freeradius/freeradius-client-1.1.7.tar.gz tar -xzvf freeradius-client-1.1.7.tar.gz cd freeRADIUS-client/freeradius-client-1.1.7.tar.gz patch -p1 < /root/opensips_2_2/modules/aaa_radius/radius_async_support.patch ./configure make make install cp include/freeradius-client.h /usr/include/freeradius-client.h 2017-01-09 18:13 GMT+02:00 Ionut Ionita : > Did you follow the steps in the docs on how to apply the async patch[0] if > you want to use it? > > [0] http://www.opensips.org/html/docs/modules/2.2.x/aaa_radius#id294296 > > Ionut Ionita > OpenSIPS Developer > > On 01/09/2017 03:04 PM, Dragomir Haralambiev wrote: > > Hi, > > Thanks for your quick replay. > > When try to start Opensips with aaa_radius support I receive follow Errors: > > Jan 9 14:57:40 dev opensips: ERROR:core:sr_load_module: could not open > module : > /usr/local/lib64/opensips/modules/aaa_radius.so: undefined symbol: > rc_acct_resume > Jan 9 14:57:40 dev opensips: ERROR:core:load_module: failed to load module > Jan 9 14:57:40 dev opensips: CRITICAL:core:yyerror: parse error in config > file /etc/opensips/opensips.cfg, line 53, column 13-14: failed to load > module aaa_radius.so > Jan 9 14:57:40 dev opensips: ERROR:core:set_mod_param_regex: no module > matching aaa_radius found > > > What I do? > > > 2017-01-09 14:55 GMT+02:00 Ionut Ionita : > >> >> Fixed. Thanks for reporting. "FREERADIUS" has the same behaviour as >> the old "USE_FREERADIUS". >> >> >> Regards, >> >> Ionut Ionita >> OpenSIPS Developer >> >> On 01/09/2017 02:09 PM, Dragomir Haralambiev wrote: >> >> I reed docs for AAA Radius module 1.2.2. External Libraries or >> Applications >> ..... >> By default, radiusclient-ng is used. To change at compile time to >> freeradius, uncomment the USE_FREERADIUS=1 line in main Makefile. >> >> In Makefile I not see USE_FREERADIUS=1. Here is only FREERADIUS. >> >> If use freeradius-client-1.1.7 what I do? >> >> Best regards, >> Dragomir >> >> >> >> >> _______________________________________________ >> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> _______________________________________________ Users mailing list >> Users at lists.opensips.org http://lists.opensips.org/cgi- >> bin/mailman/listinfo/users > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From trance_maniak at o2.pl Mon Jan 9 10:43:00 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Mon, 9 Jan 2017 08:43:00 -0700 (MST) Subject: [OpenSIPS-Users] How to store variables into file Message-ID: <1483976580415-7605497.post@n2.nabble.com> How can I save any variable into log? I use somethin like this: log("$Ts"); But in log file I always get: Jan 9 16:39:14 OpenSips/sbin/opensips[23670]: $Ts How I can get this variable in log? -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/How-to-store-variables-into-file-tp7605497.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From razvan at opensips.org Tue Jan 10 08:18:37 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Tue, 10 Jan 2017 15:18:37 +0200 Subject: [OpenSIPS-Users] How to store variables into file In-Reply-To: <1483976580415-7605497.post@n2.nabble.com> References: <1483976580415-7605497.post@n2.nabble.com> Message-ID: <1ec554a8-9ba7-9363-4ad7-46dc6c25072a@opensips.org> Hello, PS: Because you are not subscribed to the list, your messages are moderated - therefore they might not reach the list, or might reach the list later. Please subscribe to the users list[1], otherwise the interaction between us and you will be harder. [1] http://lists.opensips.org/cgi-bin/mailman/listinfo/users Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/09/2017 05:43 PM, maatohewetbi wrote: > How can I save any variable into log? I use somethin like this: > > log("$Ts"); > > But in log file I always get: > > Jan 9 16:39:14 OpenSips/sbin/opensips[23670]: $Ts > > How I can get this variable in log? > > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/How-to-store-variables-into-file-tp7605497.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From razvan at opensips.org Tue Jan 10 08:21:00 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Tue, 10 Jan 2017 15:21:00 +0200 Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <1483952331826-7605485.post@n2.nabble.com> References: <1483431205315-7605411.post@n2.nabble.com> <4fa36195-2654-2697-ebb1-e55314b58147@opensips.org> <1483448415681-7605416.post@n2.nabble.com> <586CAAD9.5060906@easycall.pl> <1483952331826-7605485.post@n2.nabble.com> Message-ID: <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> It depends on where you added that block. Also, did you also add the handle_presence route in your script? Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/09/2017 10:58 AM, maatohewetbi wrote: > Have You got any clue, why this is happnning? > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605485.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From trance_maniak at o2.pl Tue Jan 10 08:23:21 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Tue, 10 Jan 2017 06:23:21 -0700 (MST) Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> References: <1483431205315-7605411.post@n2.nabble.com> <4fa36195-2654-2697-ebb1-e55314b58147@opensips.org> <1483448415681-7605416.post@n2.nabble.com> <586CAAD9.5060906@easycall.pl> <1483952331826-7605485.post@n2.nabble.com> <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> Message-ID: <1484054601076-7605502.post@n2.nabble.com> Yes, I added this route. You can check my config, it's in this post. -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605502.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From chandan.pr at webshar.org Wed Jan 11 01:51:58 2017 From: chandan.pr at webshar.org (Chandan PR) Date: Wed, 11 Jan 2017 12:21:58 +0530 Subject: [OpenSIPS-Users] Load Balancer - Checking Node Health Message-ID: Hi, Recently one of our endpoints stopped responding and due to which nearly almost all of the calls ended up in 486. Is there any functions we can use to monitor the response codes per node over a duration so that we can raise an alert to take corrective actions in such cases. *The version of OpenSips we are using is 1.9.x* Regards, Chandan -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Wed Jan 11 03:31:17 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Wed, 11 Jan 2017 10:31:17 +0200 Subject: [OpenSIPS-Users] Load Balancer - Checking Node Health In-Reply-To: References: Message-ID: <3bc5197c-10e0-e62f-cb9e-7ea745683938@opensips.org> Hi, Chandan! Is there any way you could monitor the endpoints? If so, you can use the load balancer pinging, that will automatically disable the end point when it is not responding, and monitor the state over MI. If there is no way you monitor the endoints, you could: 1. Check the tm transactions ended with 4xx status. If you see a spike, send an alert. The comand to do that is: opensipsctl fifo get_statistics 4xx_transactions 2. Create your own statistics in the script based on the endpoint. In the script, do something like this: if (t_check_status("486")) update_stat("$stat(tran_486_$si)", "+1"); Again, monitor these statistics over MI and if you see spikes, send alerts. These are the solutions I am thinking of. Hope they are helpful. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/11/2017 08:51 AM, Chandan PR wrote: > Hi, > > Recently one of our endpoints stopped responding and due to which > nearly almost all of the calls ended up in 486. > > Is there any functions we can use to monitor the response codes per > node over a duration so that we can raise an alert to take corrective > actions in such cases. > > *The version of OpenSips we are using is 1.9.x* > > Regards, > Chandan > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From trance_maniak at o2.pl Wed Jan 11 03:34:27 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Wed, 11 Jan 2017 01:34:27 -0700 (MST) Subject: [OpenSIPS-Users] How to store variables into file In-Reply-To: <1ec554a8-9ba7-9363-4ad7-46dc6c25072a@opensips.org> References: <1483976580415-7605497.post@n2.nabble.com> <1ec554a8-9ba7-9363-4ad7-46dc6c25072a@opensips.org> Message-ID: <1484123667837-7605504.post@n2.nabble.com> Ok, I managed to get variables in log. I used *xlog* instead of *log*. It looks like variables can't be written by log function. -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/How-to-store-variables-into-file-tp7605497p7605504.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From bogdan at opensips.org Wed Jan 11 04:57:29 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 11 Jan 2017 11:57:29 +0200 Subject: [OpenSIPS-Users] opensips 2.1 call_center queue position In-Reply-To: References: <5d601c3e-ac5b-b6d1-fc0a-7959f1f0e4a0@opensips.org> <698e1be4-ce83-9782-5286-e8154bccd0b8@opensips.org> <63f2329e-066b-ed10-5629-dd8fbe075758@opensips.org> <2b3b841f-162a-589f-01dc-93b8089a1118@opensips.org> Message-ID: <9104243a-5ccc-601b-8183-e45c08401bb8@opensips.org> Hi Jonathan, Could you provide me (off list) the pcap holding the 2 calls (taken from OpenSIPS), and the OpenSIPS logs (covering the whole scenario) in log_level 4 ? Thank you, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 12/23/2016 05:52 PM, Jonathan Hunter wrote: > > Hi Bogdan, > > > That seems to be better, certainly from the count incrementing, > however a couple of issues, I am now seeing this error, and when > first call hits opensips it doesnt now route to the Agent who is > logged in free and available; > > > : ERROR:b2b_entities:b2b_send_request: Can not send request [INVITE] > for entity type [0] for dlg[0x7fe3f348a0f8]->[B2B.273.29] in > terminated state > Dec 23 15:49:22 HPBXProxy1-beta /usr/local/sbin/opensips[12140]: > ERROR:b2b_logic:b2bl_bridge: Failed to send INVITE request > Dec 23 15:49:22 HPBXProxy1-beta /usr/local/sbin/opensips[12140]: > ERROR:call_center:set_call_leg: bridging failed > Dec 23 15:49:22 HPBXProxy1-beta /usr/local/sbin/opensips[12140]: > ERROR:call_center:b2bl_callback_customer: failed to set new > destination for call > Dec 23 15:49:22 HPBXProxy1-beta /usr/local/sbin/opensips[12140]: > ERROR:b2b_logic:b2b_logic_notify_request: The callback function was > unsuccessful > > > > Also the first member in the queue is given value 0, and the second is > then given value 1, can it start at 1 or is there a reason behind it? > > > > Thanks > > > Jon > > > > ------------------------------------------------------------------------ > *From:* Bogdan-Andrei Iancu > *Sent:* 23 December 2016 14:14 > *To:* Jonathan Hunter; OpenSIPS users mailling list > *Subject:* Re: [OpenSIPS-Users] opensips 2.1 call_center queue position > Hi Jonathan, > > A Merry Christmas to you too ! > > I found a small mistake in the original patch I sent you. Please > revert that one and use this new patch (see attachment). Let me know > if it does the trick. > > Regards, > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > > Home — OpenSIPS Solutions > www.opensips-solutions.com > OpenSIPS is a mature Open Source implementation of a SIP server. > OpenSIPS is more than a SIP proxy/router as it includes > application-level functionalities. > > > On 22.12.2016 13:58, Jonathan Hunter wrote: >> >> Hi Bogdan, >> >> >> Merry Christmas to you and the mailing list! >> >> >> I am testing the real queue position, and with one call in progress, >> and then 2 subsequent calls, both of which hit the hold music loop, I >> unfortunately dont see the position value increment, it remains at >> cc_pos=0 for all the calls, this is with just one queue defined to >> keep things very simple. >> >> >> Please let me know what debug or information you require, here are >> some outputs; >> >> >> >> >> opensipsctl fifo cc_list_calls >> Call:: 255.0 Ref=2 State=queued Call Time=2 Flow=Cust1 >> Call:: 884.0 Ref=2 State=queued Call Time=51 Flow=Cust1 >> Call:: 344.0 Ref=1 State=toagent Call Time=70 Flow=Cust1 Agent=2000 >> >> opensipsctl fifo cc_list_agents >> Agent:: 2000 Ref=1 Loged in=YES State=incall >> >> opensipsctl fifo cc_list_flows >> Flow:: Cust1 Avg Call Duration=199 Processed Calls=3 Logged Agents=1 >> Ongoing Calls=3 Ref=3 >> >> opensipsctl fifo cc_list_queue >> Call:: 0 Waiting for=114 ETW=0 >> Flow:: Cust1 Priority=256 Skill=custcare >> Call:: 1 Waiting for=65 ETW=199 >> Flow:: Cust1 Priority=256 Skill=custcare >> >> Many thanks >> >> Jon >> >> >> >> >> ------------------------------------------------------------------------ >> *From:* Bogdan-Andrei Iancu >> *Sent:* 07 November 2016 20:41 >> *To:* Jonathan Hunter; OpenSIPS users mailling list >> *Subject:* Re: [OpenSIPS-Users] opensips 2.1 call_center queue position >> Hi Jonathan, >> >> I was not able to test it with a real queue, so let me know if it >> really does the job (in terms of reporting the real position in the >> queue). >> >> Some questions: >> 1) currently I add that value only when sending to the queue / MOH - >> do you foresee any need to be added for other announcements like for >> welcome ? >> >> 2) will it be useful to add the ETW (estimate time to wait) ? is it >> useful ? >> >> Regards, >> Bogdan-Andrei Iancu >> OpenSIPS Founder and Developer >> http://www.opensips-solutions.com >> >>>>>> >>>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Wed Jan 11 05:04:32 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 11 Jan 2017 12:04:32 +0200 Subject: [OpenSIPS-Users] How to parse XML Body? In-Reply-To: <032b01d26833$cace6370$606b2a50$@web.de> References: <012c01d266bf$841c7590$8c5560b0$@web.de> <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> <018601d26742$7d877ee0$78967ca0$@web.de> <4936e66b-ae31-a9fa-e260-a87ef6b24b20@opensips.org> <019a01d26746$00669460$0133bd20$@web.de> <01b601d26748$2bebb6e0$83c324a0$@web.de> <01428a9e-5f55-5a7e-154d-59c2f8e96ef0@opensips.org> <01f101d2674f$dadadee0$90909ca0$@web.de> <032b01d26833$cace6370$606b2a50$@web.de> Message-ID: <6969d0ff-96a6-56da-15f4-54f8cd0c116b@opensips.org> Hi, Please try $var(reg) = "(.*)/gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s"; xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/06/2017 05:44 PM, xaled wrote: > > Hi Bogdan, > > can you give any hints on how to get the Coordinates values and not > the whole xml body from the regex subst? > > Sorry for being not clever enough to figure it out myself. > > Thanks > > Hi Bogdan, > > $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; > > xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); > > DBG:core:subst_run:matched shows the needed XML element with value, > but not the value alone. The xlog output shows the whole XML body > without gml:Coordinates. > > 2017-01-05T13:23:23.104982+01:00 ivr01 /usr/local/sbin/opensips[2227]: > DBG:core:tr_eval_re: Trying to apply reg > > exp [/gml:Coordinates>(.*)<\/gml:Coordinates/\1/] on : [ version="1.0" encoding="UTF-8"?>#015#012 > ns="urn:ietf:params:xml:ns:pidf" > xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" > xmlns:gml="urn:opengis:specificat > > ion:gml:schema-xsd:feature:v3.0" > entity="pres:sip:+1234567 at test.com">#015#012 #015#012 > tatus>#015#012 #015#012 #015#012 > #015#012 > id="point1" srsName="epsg:4346">#015#012 12.32 > 34.24#015#012 > oint>#015#012 #015#012 #015#012 > #015#012 > smission-allowed>no#015#012 > #015#012 #01 > > 5#012 #015#012 #015#012 > 2016-8-02T04:13:23Z#015#012 #015#0 > > 12#015#012#015#012] > > 2017-01-05T13:23:23.107376+01:00 ivr01 /usr/local/sbin/opensips[2227]: > DBG:core:tr_eval_re: we must compile the > > regexp > > 2017-01-05T13:23:23.107903+01:00 ivr01 /usr/local/sbin/opensips[2227]: > DBG:core:subst_parser: ok, se is 0x7f39a > > 5d0a1f0 > > 2017-01-05T13:23:23.108241+01:00 ivr01 /usr/local/sbin/opensips[2227]: > DBG:core:subst_run: running. r=0 > > 2017-01-05T13:23:23.111918+01:00 ivr01 /usr/local/sbin/opensips[2227]: > DBG:core:subst_run: matched (404, 45): [ > > gml:Coordinates>12.32 34.24 > 2017-01-05T13:23:23.112380+01:00 ivr01 /usr/local/sbin/opensips[2227]: > DBG:core:buf_init: initializing... > > 2017-01-05T13:23:23.112730+01:00 ivr01 /usr/local/sbin/opensips[2227]: > Position is > ="UTF-8"?>#015#012 xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xm > > lns:gml="urn:opengis:specification:gml:schema-xsd:feature:v3.0" > entity="pres:sip:+1234567 at test.com">#015#0 > > 12 #015#012 #015#012 #015#012 > #015#012 > n>#015#012 srsName="epsg:4346">#015#012 <12.32 34.24>#015#012 > nt>#015#012 #015#012 #015#012 > #015#012 > ission-allowed>no#015#012 > #015#012 #015# > > 012 #015#012 #015#012 > 2016-8-02T04:13:23Z#015#012 #015#012 > > > > Thanks > > *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] > *Sent:* Donnerstag, 5. Januar 2017 13:12 > *To:* OpenSIPS users mailling list >; xaled > > *Subject:* Re: [OpenSIPS-Users] How to parse XML Body? > > Try $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From trance_maniak at o2.pl Wed Jan 11 05:44:18 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Wed, 11 Jan 2017 03:44:18 -0700 (MST) Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB Message-ID: <1484131458652-7605514.post@n2.nabble.com> Is there any way to make an IP authorization with registrar module? First I want to authenticate peer with IP, and then allow him to register with correct login/pass. Or is there any way to select any variable from DB? -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From razvan at opensips.org Wed Jan 11 06:06:22 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Wed, 11 Jan 2017 13:06:22 +0200 Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB In-Reply-To: <1484131458652-7605514.post@n2.nabble.com> References: <1484131458652-7605514.post@n2.nabble.com> Message-ID: Yes, you can use the check_source() address function[1] just before the auth block. [1] http://www.opensips.org/html/docs/modules/2.2.x/permissions#id295007 Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/11/2017 12:44 PM, maatohewetbi wrote: > Is there any way to make an IP authorization with registrar module? First I > want to authenticate peer with IP, and then allow him to register with > correct login/pass. Or is there any way to select any variable from DB? > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From trance_maniak at o2.pl Wed Jan 11 06:15:56 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Wed, 11 Jan 2017 04:15:56 -0700 (MST) Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB In-Reply-To: References: <1484131458652-7605514.post@n2.nabble.com> Message-ID: <1484133356292-7605516.post@n2.nabble.com> Yes, but I want to check sip login first, not an IP. Here is ny plan, what I want to do: - store IP, login in one table (a new on or existing one) - there will be IP and SIP logins. When a client make a registration, my script should check if this login is in table, if yes - then check IP, if it matches - allow a registration, if not - send 403 and exit. There will be another case, when a SIP login is not in this table - just allow registration without checking an IP. -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514p7605516.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From chandan.pr at webshar.org Wed Jan 11 08:16:36 2017 From: chandan.pr at webshar.org (Chandan PR) Date: Wed, 11 Jan 2017 18:46:36 +0530 Subject: [OpenSIPS-Users] Load Balancer - Checking Node Health In-Reply-To: <3bc5197c-10e0-e62f-cb9e-7ea745683938@opensips.org> References: <3bc5197c-10e0-e62f-cb9e-7ea745683938@opensips.org> Message-ID: Thanks a lot Razvan. Will try them and keep the group posted about the results. On Wed, Jan 11, 2017 at 2:01 PM, Răzvan Crainea wrote: > Hi, Chandan! > > Is there any way you could monitor the endpoints? If so, you can use the > load balancer pinging, that will automatically disable the end point when > it is not responding, and monitor the state over MI. > > If there is no way you monitor the endoints, you could: > 1. Check the tm transactions ended with 4xx status. If you see a spike, > send an alert. The comand to do that is: > opensipsctl fifo get_statistics 4xx_transactions > > 2. Create your own statistics in the script based on the endpoint. In the > script, do something like this: > if (t_check_status("486")) > update_stat("$stat(tran_486_$si)", "+1"); > > Again, monitor these statistics over MI and if you see spikes, send alerts. > > These are the solutions I am thinking of. Hope they are helpful. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutionswww.opensips-solutions.com > > On 01/11/2017 08:51 AM, Chandan PR wrote: > > Hi, > > Recently one of our endpoints stopped responding and due to which nearly > almost all of the calls ended up in 486. > > Is there any functions we can use to monitor the response codes per node > over a duration so that we can raise an alert to take corrective actions in > such cases. > > *The version of OpenSips we are using is 1.9.x* > > Regards, > Chandan > > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahmedmunir007 at gmail.com Wed Jan 11 16:10:36 2017 From: ahmedmunir007 at gmail.com (Ahmed Munir) Date: Wed, 11 Jan 2017 16:10:36 -0500 Subject: [OpenSIPS-Users] OpenSIPs crashed Message-ID: Hi, Our OpenSIPs service crashed with below error; Jan 11 12:16:19 QORBLPSIPROXY05 abrtd: Directory 'ccpp-2017-01-11-12:16:19-2807' creation detected Jan 11 12:16:19 QORBLPSIPROXY05 abrt[65402]: Saved core dump of pid 2807 (/usr/sbin/opensips) to /var/spool/abrt/ccpp-2017-01-11-12:16:19-2807 (70225920 bytes) Jan 11 12:16:19 QORBLPSIPROXY05 abrt[65402]: Can't open 'core.2807': Permission denied Jan 11 12:16:19 QORBLPSIPROXY05 kernel: opensips[2807]: segfault at 29 ip 00000000004bae7a sp 00007fffdb7734d0 error 4 in opensips[400000+13a000] We would like to know, what might be the reason for the crash. Further added, there is another server we are running OpenSIPs, the opensips child processes utilizing 100% of CPU and the system load average reach around 'load average: 20.01, 18.03, 24.00' as normally it is below 1 (load average). After looking into logs, unable to find the info what might causing the CPU to spike. Please advise what useful steps to take for narrowing down this issue. -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Thu Jan 12 03:00:49 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Thu, 12 Jan 2017 10:00:49 +0200 Subject: [OpenSIPS-Users] OpenSIPs crashed In-Reply-To: References: Message-ID: <2b35e2dc-6e11-1787-b87e-33bd29a328f3@opensips.org> Hi, Ahmed! Make sure OpenSIPS is run as root and it is allowed to write in the /var/spool/abrt/ directory, otherwise it is unable to write the core dump, therefore we can't inspect it to say what is happening. If this does not work, make OpenSIPS write the core dump in a writeble directory by changing the /proc/sys/kernel/core_pattern settings. Also, please let us know the version of OpenSIPS you are running. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/11/2017 11:10 PM, Ahmed Munir wrote: > Hi, > > Our OpenSIPs service crashed with below error; > > Jan 11 12:16:19 QORBLPSIPROXY05 abrtd: Directory > 'ccpp-2017-01-11-12:16:19-2807' creation detected > Jan 11 12:16:19 QORBLPSIPROXY05 abrt[65402]: Saved core dump of pid > 2807 (/usr/sbin/opensips) to > /var/spool/abrt/ccpp-2017-01-11-12:16:19-2807 (70225920 bytes) > Jan 11 12:16:19 QORBLPSIPROXY05 abrt[65402]: Can't open 'core.2807': > Permission denied > Jan 11 12:16:19 QORBLPSIPROXY05 kernel: opensips[2807]: segfault at 29 > ip 00000000004bae7a sp 00007fffdb7734d0 error 4 in opensips[400000+13a000] > > > We would like to know, what might be the reason for the crash. > > Further added, there is another server we are running OpenSIPs, the > opensips child processes utilizing 100% of CPU and the system load > average reach around 'load average: 20.01, 18.03, 24.00' as normally > it is below 1 (load average). > > After looking into logs, unable to find the info what might causing > the CPU to spike. > > Please advise what useful steps to take for narrowing down this issue. > > > -- > Regards, > > Ahmed Munir Chohan > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From SOAN at stofa.dk Thu Jan 12 06:13:58 2017 From: SOAN at stofa.dk (=?iso-8859-1?Q?S=F8ren_Andersen?=) Date: Thu, 12 Jan 2017 11:13:58 +0000 Subject: [OpenSIPS-Users] force one AOR Message-ID: Hello, I've some trouble with forceing 1 AOR per contact. I'm using the config: if (!save("location", "fc1")) { sl_reply_error(); } But then I reboot my SIP client opensips allows 2 AOR for the phonenumber? - But if I reboot the sip client again it'll delete all the AORs and insert the new one? opensipsctl fifo ul_show_contact location 88XXXXXX AOR:: 88175263 Contact:: sip: 88XXXXXX at 10.112.130.202 Q= Expires:: 897 Callid:: 25180a4e14bcef242fc01d1d1f5da9af at 10.112.130.202 Cseq:: 103 User-agent:: ICOTERA IGW3000 (2.5.1) State:: CS_SYNC Flags:: 0 Cflags:: Socket:: udp:85.XXX.XXX.120:5060 Methods:: 4294967295 Contact:: sip: 88XXXXXX at 10.112.130.202 Q= Expires:: 9 Callid:: 447b19de71f7ae6e305211c97f4574a9 at 10.112.130.202 Cseq:: 107 User-agent:: ICOTERA IGW3000 (2.5.1) State:: CS_SYNC Flags:: 0 Cflags:: Socket:: udp:85.XXX.XXX.120:5060 Methods:: 4294967295 /Søren -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank21118 at yahoo.com Thu Jan 12 09:40:21 2017 From: frank21118 at yahoo.com (bluerain) Date: Thu, 12 Jan 2017 07:40:21 -0700 (MST) Subject: [OpenSIPS-Users] change T_fr_in_timeout Message-ID: <1484232021878-7605536.post@n2.nabble.com> Ok, so hopefully I get some help in this forum, I'm trying to get a faster PDD by going down the LCR list faster. I'm trying to use the fr_inv_timeout to skip the carrier that has slow PDD. So I did the code below so that if I don't get a 180/183 after invite within 5 second, I will terminate the call and go to the next carrier. But if they do give 180/183 after invite within 5 second, I want to change T_fr_inv to 60 seconds so have enough time for far end user to pick up the call. But I ran into 2 problem: 1. 180/183 seems is NOT picking up inthe onreply_route. I did a log and it seems on 180/183 it never went into the code where I wanted to, so is this is WRONG place to detect 180/183? 2. I also try to display the value of $T_fr_inv_timeout in onreply_route section of the code, but it always show "ZERO"? Anyway, any pointer will be greatly appreciated. Thank you! loadmodule "tm.so" modparam("tm", "fr_timeout", 5) modparam("tm", "fr_inv_timeout", 5) modparam("tm", "restart_fr_on_each_reply", 0) modparam("tm", "onreply_avp_mode", 1) onreply_route { if (t_check_status("(180)|(183)")) { $T_fr_inv_timeout = 60; } } -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/change-T-fr-in-timeout-tp7605536.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From bogdan at opensips.org Thu Jan 12 11:39:39 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Thu, 12 Jan 2017 18:39:39 +0200 Subject: [OpenSIPS-Users] Introducing OpenSIPS 2.3 Message-ID: <99435f67-d572-ce75-531a-a5588935aa1d@opensips.org> A new year has arrived, so it is the time for a new OpenSIPS major release – forOpenSIPS version 2.3 . For this version, the main focus on development is the*/“integration”/*, the integration ofOpenSIPSwith various external entities. Why is integration so important to end up being the main tag of a major release? Well, everybody in the VoIP world is operating VoIP platforms/systems – and these are more than SIP Engines (asOpenSIPSis). Indeed, the SIP Engine is the core and most important part of the platform, but to build something usable and useful, you need additional components into your platform like CDR/billing engines, monitoring and tracing tools, data backends, non-SIP trunking or more specialized SIP engines. Shortly you need your SIP Engine (OpenSIPS, of course) to be able to easily integrate with all these components. OpenSIPS2.3 brings some new and exciting integration capabilities, that will definitely boost the value of your SIP platform: * extendedHomer/SIPCapture integration to allow capturing of non-SIP data (transport level data, Management Interface commands, REST queries and more); * SIP-I support both in terms of passing-through and in terms of converting SIP-I to SIP and vice-versa ; * CGRates integration for powerful rating/billing – everything in a simple and automatic way (via a dedicated module); * FreeSWITCH flavored Load-Balancing for a more realistic and accurate traffic balancing over FreeSWITCH clusters (as the load information is fetched in realtime from FreeSWITCH); * theEvent Engine to provide support for scenarios based on Subscribe/Notify model, where the script execution may subscribe and resume later according to certain events (like a dynamic implementation of the Push Notification mechanism); * extendedRabbitMQ support for custom and flexible data injection directly from OpenSIPS script; * extended Asynchronous support for more complex async scenarios (like launch with no wait); * more end-device integration (special SIP extensions). The timeline for OpenSIPS 2.3 is: * Beta Release – 13-17 March 2017 * Stable Release – 24-28 April 2017 * General Availability – 2nd of May 2017, duringOpenSIPS Summit To talk more about the features of this new release, a publicaudio conference will be available on19th of January 2017, 4 pm GMT , thanks to the kind sponsorship of UberConference . Anyone is welcome to join to find out more details or to ask questions aboutOpenSIPS2.3 . This is a public and open conference, so no registration is needed, but if you want to announce your intention to participate, please let us know via the form on the blog post . Best regards, -- Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahmedmunir007 at gmail.com Thu Jan 12 12:42:03 2017 From: ahmedmunir007 at gmail.com (Ahmed Munir) Date: Thu, 12 Jan 2017 12:42:03 -0500 Subject: [OpenSIPS-Users] OpenSIPs crashed Message-ID: The version currently running is 1.6.3. Will try to enable core dump and share the info if run into the issues again. From: Răzvan Crainea > To: users at lists.opensips.org > Subject: Re: [OpenSIPS-Users] OpenSIPs crashed > Message-ID: <2b35e2dc-6e11-1787-b87e-33bd29a328f3 at opensips.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi, Ahmed! > > Make sure OpenSIPS is run as root and it is allowed to write in the > /var/spool/abrt/ directory, otherwise it is unable to write the core > dump, therefore we can't inspect it to say what is happening. If this > does not work, make OpenSIPS write the core dump in a writeble directory > by changing the /proc/sys/kernel/core_pattern settings. > Also, please let us know the version of OpenSIPS you are running. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > > On 01/11/2017 11:10 PM, Ahmed Munir wrote: > > Hi, > > > > Our OpenSIPs service crashed with below error; > > > > Jan 11 12:16:19 QORBLPSIPROXY05 abrtd: Directory > > 'ccpp-2017-01-11-12:16:19-2807' creation detected > > Jan 11 12:16:19 QORBLPSIPROXY05 abrt[65402]: Saved core dump of pid > > 2807 (/usr/sbin/opensips) to > > /var/spool/abrt/ccpp-2017-01-11-12:16:19-2807 (70225920 bytes) > > Jan 11 12:16:19 QORBLPSIPROXY05 abrt[65402]: Can't open 'core.2807': > > Permission denied > > Jan 11 12:16:19 QORBLPSIPROXY05 kernel: opensips[2807]: segfault at 29 > > ip 00000000004bae7a sp 00007fffdb7734d0 error 4 in > opensips[400000+13a000] > > > > > > We would like to know, what might be the reason for the crash. > > > > Further added, there is another server we are running OpenSIPs, the > > opensips child processes utilizing 100% of CPU and the system load > > average reach around 'load average: 20.01, 18.03, 24.00' as normally > > it is below 1 (load average). > > > > After looking into logs, unable to find the info what might causing > > the CPU to spike. > > > > Please advise what useful steps to take for narrowing down this issue. > > > > > > -- > > Regards, > > > > Ahmed Munir Chohan > > > > -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahmedmunir007 at gmail.com Thu Jan 12 13:28:57 2017 From: ahmedmunir007 at gmail.com (Ahmed Munir) Date: Thu, 12 Jan 2017 13:28:57 -0500 Subject: [OpenSIPS-Users] OpenSIPs crashed Message-ID: The version currently running is 1.6.3. Today again we got the opensips crashed issues i.e. 5 out of 8 were crashed due to below message (common on all 5); Jan 12 10:07:36 QORCLPSIPROXY02 kernel: opensips[2820]: segfault at 0 ip 00000000004a2936 sp 00007fff5cfaa430 error 6 in opensips[400000+13a000] Jan 12 10:07:36 QORCLPSIPROXY02 abrt[39302]: Can't open 'core.2820': Permission denied Jan 12 10:07:36 QORCLPSIPROXY02 abrt[39302]: Saved core dump of pid 2820 (/usr/sbin/opensips) to /var/spool/abrt/ccpp-2017-01-12-10:07:36-2820 (70246400 bytes) Jan 12 10:07:36 QORCLPSIPROXY02 abrtd: Directory 'ccpp-2017-01-12-10:07:36-2820' creation detected Jan 12 10:07:38 QORCLPSIPROXY02 kernel: Bridge firewalling registered Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: Sending an email... Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: /usr/sbin/sendmail: No such file or directory Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: . . . message not sent. Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: Error running '/bin/mailx' Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: 'post-create' on '/var/spool/abrt/ccpp-2017-01-12-10:07:36-2820' exited with 1 Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: Deleting problem directory '/var/spool/abrt/ccpp-2017-01-12-10:07:36-2820' We would like to know why we are getting this segmentation fault? Is there a way to backtrace the issue as don't have the core dump? Further added, did someone faced this similar issue(s) in past and got this fixed without upgrade? Note: we are running opensips for quite a while didn't faced this kind of issue and there is no changes made on opensips routing script. > From: Răzvan Crainea >> To: users at lists.opensips.org >> Subject: Re: [OpenSIPS-Users] OpenSIPs crashed >> Message-ID: <2b35e2dc-6e11-1787-b87e-33bd29a328f3 at opensips.org> >> Content-Type: text/plain; charset="utf-8"; Format="flowed" >> >> Hi, Ahmed! >> >> Make sure OpenSIPS is run as root and it is allowed to write in the >> /var/spool/abrt/ directory, otherwise it is unable to write the core >> dump, therefore we can't inspect it to say what is happening. If this >> does not work, make OpenSIPS write the core dump in a writeble directory >> by changing the /proc/sys/kernel/core_pattern settings. >> Also, please let us know the version of OpenSIPS you are running. >> >> Best regards, >> >> Răzvan Crainea >> OpenSIPS Solutions >> www.opensips-solutions.com >> >> >> On 01/11/2017 11:10 PM, Ahmed Munir wrote: >> > Hi, >> > >> > Our OpenSIPs service crashed with below error; >> > >> > Jan 11 12:16:19 QORBLPSIPROXY05 abrtd: Directory >> > 'ccpp-2017-01-11-12:16:19-2807' creation detected >> > Jan 11 12:16:19 QORBLPSIPROXY05 abrt[65402]: Saved core dump of pid >> > 2807 (/usr/sbin/opensips) to >> > /var/spool/abrt/ccpp-2017-01-11-12:16:19-2807 (70225920 bytes) >> > Jan 11 12:16:19 QORBLPSIPROXY05 abrt[65402]: Can't open 'core.2807': >> > Permission denied >> > Jan 11 12:16:19 QORBLPSIPROXY05 kernel: opensips[2807]: segfault at 29 >> > ip 00000000004bae7a sp 00007fffdb7734d0 error 4 in >> opensips[400000+13a000] >> > >> > >> > We would like to know, what might be the reason for the crash. >> > >> > Further added, there is another server we are running OpenSIPs, the >> > opensips child processes utilizing 100% of CPU and the system load >> > average reach around 'load average: 20.01, 18.03, 24.00' as normally >> > it is below 1 (load average). >> > >> > After looking into logs, unable to find the info what might causing >> > the CPU to spike. >> > >> > Please advise what useful steps to take for narrowing down this issue. >> > >> > >> > -- >> > Regards, >> > >> > Ahmed Munir Chohan >> > >> >> > > > -- > Regards, > > Ahmed Munir Chohan > > -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahmedmunir007 at gmail.com Thu Jan 12 16:55:25 2017 From: ahmedmunir007 at gmail.com (Ahmed Munir) Date: Thu, 12 Jan 2017 16:55:25 -0500 Subject: [OpenSIPS-Users] OpenSIPs crashed Message-ID: Found coredump on one of the server, see some partial message below while taking the back trace; Core was generated by `/usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips'. Program terminated with signal 11, Segmentation fault. #0 0x00007f650687a069 in sip_msg_cloner () from /usr/lib64/opensips/modules/tm.so Missing separate debuginfos, use: debuginfo-install opensips-1.6.3-notls.x86_64 Please advise what might be the reason causing opensips to crash. On Thu, Jan 12, 2017 at 1:28 PM, Ahmed Munir wrote: > > The version currently running is 1.6.3. Today again we got the opensips > crashed issues i.e. 5 out of 8 were crashed due to below message (common on > all 5); > > Jan 12 10:07:36 QORCLPSIPROXY02 kernel: opensips[2820]: segfault at 0 ip > 00000000004a2936 sp 00007fff5cfaa430 error 6 in opensips[400000+13a000] > > Jan 12 10:07:36 QORCLPSIPROXY02 abrt[39302]: Can't open 'core.2820': > Permission denied > > Jan 12 10:07:36 QORCLPSIPROXY02 abrt[39302]: Saved core dump of pid 2820 > (/usr/sbin/opensips) to /var/spool/abrt/ccpp-2017-01-12-10:07:36-2820 > (70246400 bytes) > > Jan 12 10:07:36 QORCLPSIPROXY02 abrtd: Directory 'ccpp-2017-01-12-10:07:36-2820' > creation detected > > Jan 12 10:07:38 QORCLPSIPROXY02 kernel: Bridge firewalling registered > > Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: Sending an email... > > Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: /usr/sbin/sendmail: No such file or > directory > > Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: . . . message not sent. > > Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: Error running '/bin/mailx' > > Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: 'post-create' on > '/var/spool/abrt/ccpp-2017-01-12-10:07:36-2820' exited with 1 > > Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: Deleting problem directory > '/var/spool/abrt/ccpp-2017-01-12-10:07:36-2820' > > > We would like to know why we are getting this segmentation fault? Is there > a way to backtrace the issue as don't have the core dump? Further added, > did someone faced this similar issue(s) in past and got this fixed without > upgrade? > > Note: we are running opensips for quite a while didn't faced this kind of > issue and there is no changes made on opensips routing script. > > >> From: Răzvan Crainea >>> To: users at lists.opensips.org >>> Subject: Re: [OpenSIPS-Users] OpenSIPs crashed >>> Message-ID: <2b35e2dc-6e11-1787-b87e-33bd29a328f3 at opensips.org> >>> Content-Type: text/plain; charset="utf-8"; Format="flowed" >>> >>> Hi, Ahmed! >>> >>> Make sure OpenSIPS is run as root and it is allowed to write in the >>> /var/spool/abrt/ directory, otherwise it is unable to write the core >>> dump, therefore we can't inspect it to say what is happening. If this >>> does not work, make OpenSIPS write the core dump in a writeble directory >>> by changing the /proc/sys/kernel/core_pattern settings. >>> Also, please let us know the version of OpenSIPS you are running. >>> >>> Best regards, >>> >>> Răzvan Crainea >>> OpenSIPS Solutions >>> www.opensips-solutions.com >>> >>> >>> On 01/11/2017 11:10 PM, Ahmed Munir wrote: >>> > Hi, >>> > >>> > Our OpenSIPs service crashed with below error; >>> > >>> > Jan 11 12:16:19 QORBLPSIPROXY05 abrtd: Directory >>> > 'ccpp-2017-01-11-12:16:19-2807' creation detected >>> > Jan 11 12:16:19 QORBLPSIPROXY05 abrt[65402]: Saved core dump of pid >>> > 2807 (/usr/sbin/opensips) to >>> > /var/spool/abrt/ccpp-2017-01-11-12:16:19-2807 (70225920 bytes) >>> > Jan 11 12:16:19 QORBLPSIPROXY05 abrt[65402]: Can't open 'core.2807': >>> > Permission denied >>> > Jan 11 12:16:19 QORBLPSIPROXY05 kernel: opensips[2807]: segfault at 29 >>> > ip 00000000004bae7a sp 00007fffdb7734d0 error 4 in >>> opensips[400000+13a000] >>> > >>> > >>> > We would like to know, what might be the reason for the crash. >>> > >>> > Further added, there is another server we are running OpenSIPs, the >>> > opensips child processes utilizing 100% of CPU and the system load >>> > average reach around 'load average: 20.01, 18.03, 24.00' as normally >>> > it is below 1 (load average). >>> > >>> > After looking into logs, unable to find the info what might causing >>> > the CPU to spike. >>> > >>> > Please advise what useful steps to take for narrowing down this issue. >>> > >>> > >>> > -- >>> > Regards, >>> > >>> > Ahmed Munir Chohan >>> > >>> >>> >> >> >> -- >> Regards, >> >> Ahmed Munir Chohan >> >> > > > -- > Regards, > > Ahmed Munir Chohan > > -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From pat at voxtelesys.com Thu Jan 12 17:48:23 2017 From: pat at voxtelesys.com (Pat Burke) Date: Thu, 12 Jan 2017 16:48:23 -0600 Subject: [OpenSIPS-Users] $rl_count in 2.2.2 Message-ID: Hello, I am trying to get the current rate limit value using $rl_count, but it is giving the following error.        ERROR:ratelimit:pv_get_rl_count: invalid name        WARNING:core:do_assign: no value in right expression at /etc/opensips/opensips_proxy.cfg:598        4024438929 SCRIPT:CCLIMIT:INFO: rl_limit for cps_90761 = 0 Here is the code     $json(call_details/tg_cps) = 0; # Default to 0 ...     if ($avp(maxcps) != NULL && $avp(maxcps) > 0) {         if (!rl_check("cps_$avp(trunk_group)", "$avp(maxcps)")) {             xlog("L_NOTICE", "$rU SCRIPT:CPSLIMIT:DBG: Max $avp(maxcps) cps reached for trunk group $avp(trunk_group) \n");             $avp(error_reason) = $avp(error_reason) + $avp(trunk_group) + " CPS limit reached.";             send_reply("403", "Max CPS limit reached");             exit;         }     }          $json(call_details/tg_cps) = $rl_count("cps_$avp(trunk_group)");     xlog("L_INFO", "$rU SCRIPT:CCLIMIT:INFO: rl_limit for cps_$avp(trunk_group) = $json(call_details/tg_cps) \n"); >From the command  opensipsctl fifo rl_list | grep cps_90761, I get        PIPE::  id=cps_90761 algorithm=TAILDROP limit=2 counter=0 What am I missing? Regards, Pat Burke -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Fri Jan 13 03:44:37 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Fri, 13 Jan 2017 10:44:37 +0200 Subject: [OpenSIPS-Users] $rl_count in 2.2.2 In-Reply-To: References: Message-ID: Hi, Pat! The way you are using $rl_count is wrong, because the $rl_count pseudo variable only accepts strings or other pvars, not formatted strings (such as "cps_$avp(trunk_group)"). To achieve what you are trying to do is to assign the name to a pvar and feed it in the $rl_count's name: $var(rl_name) = "cps_" + $avp(trunk_group); $json(call_details/tg_cps) = $rl_count($var(rl_name)); Let me know how this goes. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/13/2017 12:48 AM, Pat Burke wrote: > Hello, > > I am trying to get the current rate limit value using $rl_count, but > it is giving the following error. > ERROR:ratelimit:pv_get_rl_count: invalid name > WARNING:core:do_assign: no value in right expression at > /etc/opensips/opensips_proxy.cfg:598 > 4024438929 SCRIPT:CCLIMIT:INFO: rl_limit for cps_90761 = 0 > > Here is the code > > $json(call_details/tg_cps) = 0; # Default to 0 > > ... > > if ($avp(maxcps) != NULL && $avp(maxcps) > 0) { > if (!rl_check("cps_$avp(trunk_group)", "$avp(maxcps)")) { > xlog("L_NOTICE", "$rU SCRIPT:CPSLIMIT:DBG: Max > $avp(maxcps) cps reached for trunk group $avp(trunk_group) \n"); > $avp(error_reason) = $avp(error_reason) + > $avp(trunk_group) + " CPS limit reached."; > send_reply("403", "Max CPS limit reached"); > exit; > } > } > $json(call_details/tg_cps) = $rl_count("cps_$avp(trunk_group)"); > xlog("L_INFO", "$rU SCRIPT:CCLIMIT:INFO: rl_limit for > cps_$avp(trunk_group) = $json(call_details/tg_cps) \n"); > > > From the command opensipsctl fifo rl_list | grep cps_90761, I get > PIPE:: id=cps_90761 algorithm=TAILDROP limit=2 counter=0 > > What am I missing? > > Regards, > *Pat Burke* > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Fri Jan 13 03:48:40 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Fri, 13 Jan 2017 10:48:40 +0200 Subject: [OpenSIPS-Users] OpenSIPs crashed In-Reply-To: References: Message-ID: <40f6dada-e121-a2da-b283-69dff891cd11@opensips.org> Hi, Ahmed! OpenSIPS 1.6.3 is no longer supported (since 2013), so there's not much we can do right now. Try upgrading your install to the latest 1.6.4 version and see if your problem is solved. Otherwise, upgrade to a newer, supported version, preferably the latest stable release, 2.2.2. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/12/2017 11:55 PM, Ahmed Munir wrote: > Found coredump on one of the server, see some partial message below > while taking the back trace; > > > > Core was generated by `/usr/sbin/opensips -P /var/run/opensips.pid -m > 64 -u opensips -g opensips'. > > Program terminated with signal 11, Segmentation fault. > > #0 0x00007f650687a069 in sip_msg_cloner () from > /usr/lib64/opensips/modules/tm.so > > Missing separate debuginfos, use: debuginfo-install > opensips-1.6.3-notls.x86_64 > > > > Please advise what might be the reason causing opensips to crash. > > On Thu, Jan 12, 2017 at 1:28 PM, Ahmed Munir > wrote: > > > The version currently running is 1.6.3. Today again we got the > opensips crashed issues i.e. 5 out of 8 were crashed due to below > message (common on all 5); > > Jan 12 10:07:36 QORCLPSIPROXY02 kernel: opensips[2820]: segfault > at 0 ip 00000000004a2936 sp 00007fff5cfaa430 error 6 in > opensips[400000+13a000] > > Jan 12 10:07:36 QORCLPSIPROXY02 abrt[39302]: Can't open > 'core.2820': Permission denied > > Jan 12 10:07:36 QORCLPSIPROXY02 abrt[39302]: Saved core dump of > pid 2820 (/usr/sbin/opensips) to > /var/spool/abrt/ccpp-2017-01-12-10:07:36-2820 (70246400 bytes) > > Jan 12 10:07:36 QORCLPSIPROXY02 abrtd: Directory > 'ccpp-2017-01-12-10:07:36-2820' creation detected > > Jan 12 10:07:38 QORCLPSIPROXY02 kernel: Bridge firewalling registered > > Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: Sending an email... > > Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: /usr/sbin/sendmail: No such > file or directory > > Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: . . . message not sent. > > Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: Error running '/bin/mailx' > > Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: 'post-create' on > '/var/spool/abrt/ccpp-2017-01-12-10:07:36-2820' exited with 1 > > Jan 12 10:08:46 QORCLPSIPROXY02 abrtd: Deleting problem directory > '/var/spool/abrt/ccpp-2017-01-12-10:07:36-2820' > > > > We would like to know why we are getting this segmentation fault? > Is there a way to backtrace the issue as don't have the core dump? > Further added, did someone faced this similar issue(s) in past and > got this fixed without upgrade? > > Note: we are running opensips for quite a while didn't faced this > kind of issue and there is no changes made on opensips routing script. > > > From: Răzvan Crainea > > To: users at lists.opensips.org > Subject: Re: [OpenSIPS-Users] OpenSIPs crashed > Message-ID: > <2b35e2dc-6e11-1787-b87e-33bd29a328f3 at opensips.org > > > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi, Ahmed! > > Make sure OpenSIPS is run as root and it is allowed to > write in the > /var/spool/abrt/ directory, otherwise it is unable to > write the core > dump, therefore we can't inspect it to say what is > happening. If this > does not work, make OpenSIPS write the core dump in a > writeble directory > by changing the /proc/sys/kernel/core_pattern settings. > Also, please let us know the version of OpenSIPS you are > running. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > > > > On 01/11/2017 11:10 PM, Ahmed Munir wrote: > > Hi, > > > > Our OpenSIPs service crashed with below error; > > > > Jan 11 12:16:19 QORBLPSIPROXY05 abrtd: Directory > > 'ccpp-2017-01-11-12 :16:19-2807' > creation detected > > Jan 11 12:16:19 QORBLPSIPROXY05 abrt[65402]: Saved core > dump of pid > > 2807 (/usr/sbin/opensips) to > > /var/spool/abrt/ccpp-2017-01-11-12:16:19-2807 (70225920 > bytes) > > Jan 11 12:16:19 QORBLPSIPROXY05 abrt[65402]: Can't open > 'core.2807': > > Permission denied > > Jan 11 12:16:19 QORBLPSIPROXY05 kernel: opensips[2807]: > segfault at 29 > > ip 00000000004bae7a sp 00007fffdb7734d0 error 4 in > opensips[400000+13a000] > > > > > > We would like to know, what might be the reason for the > crash. > > > > Further added, there is another server we are running > OpenSIPs, the > > opensips child processes utilizing 100% of CPU and the > system load > > average reach around 'load average: 20.01, 18.03, 24.00' > as normally > > it is below 1 (load average). > > > > After looking into logs, unable to find the info what > might causing > > the CPU to spike. > > > > Please advise what useful steps to take for narrowing > down this issue. > > > > > > -- > > Regards, > > > > Ahmed Munir Chohan > > > > > > > -- > Regards, > > Ahmed Munir Chohan > > > > > -- > Regards, > > Ahmed Munir Chohan > > > > > -- > Regards, > > Ahmed Munir Chohan > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Fri Jan 13 03:54:43 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Fri, 13 Jan 2017 10:54:43 +0200 Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB In-Reply-To: <1484133356292-7605516.post@n2.nabble.com> References: <1484131458652-7605514.post@n2.nabble.com> <1484133356292-7605516.post@n2.nabble.com> Message-ID: <9640879b-c012-4529-5e7d-57a8ea817e67@opensips.org> Then simply reverse the IP check logic and do it after the user is authenticated. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/11/2017 01:15 PM, maatohewetbi wrote: > Yes, but I want to check sip login first, not an IP. Here is ny plan, what I > want to do: > > - store IP, login in one table (a new on or existing one) - there will be > IP and SIP logins. > > When a client make a registration, my script should check if this login is > in table, if yes - then check IP, if it matches - allow a registration, if > not - send 403 and exit. There will be another case, when a SIP login is not > in this table - just allow registration without checking an IP. > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514p7605516.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From trance_maniak at o2.pl Fri Jan 13 04:03:04 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Fri, 13 Jan 2017 02:03:04 -0700 (MST) Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB In-Reply-To: <9640879b-c012-4529-5e7d-57a8ea817e67@opensips.org> References: <1484131458652-7605514.post@n2.nabble.com> <1484133356292-7605516.post@n2.nabble.com> <9640879b-c012-4529-5e7d-57a8ea817e67@opensips.org> Message-ID: <1484298184907-7605547.post@n2.nabble.com> Yes, but every IP and login should be in table. How can I read variables from DB? Is it possible to do it? -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514p7605547.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From razvan at opensips.org Fri Jan 13 04:22:47 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Fri, 13 Jan 2017 11:22:47 +0200 Subject: [OpenSIPS-Users] force one AOR In-Reply-To: References: Message-ID: <3607dc46-28aa-e9e4-6f62-ca31445a7755@opensips.org> Hi, Soren! What version of OpenSIPS are you running? Also, can you send over the debug logs for this scenario? Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/12/2017 01:13 PM, Søren Andersen wrote: > > Hello, > > I’ve some trouble with forceing 1 AOR per contact. > > I’m using the config: > > if (!save("location", "fc1")) { > > sl_reply_error(); > > } > > But then I reboot my SIP client opensips allows 2 AOR for the > phonenumber? – But if I reboot the sip client again it’ll delete all > the AORs and insert the new one? > > opensipsctl fifo ul_show_contact location 88XXXXXX > > AOR:: 88175263 > > Contact:: sip: 88XXXXXX at 10.112.130.202 Q= > > Expires:: 897 > > Callid:: 25180a4e14bcef242fc01d1d1f5da9af at 10.112.130.202 > > Cseq:: 103 > > User-agent:: ICOTERA IGW3000 (2.5.1) > > State:: CS_SYNC > > Flags:: 0 > > Cflags:: > > Socket:: udp:85.XXX.XXX.120:5060 > > Methods:: 4294967295 > > Contact:: sip: 88XXXXXX at 10.112.130.202 Q= > > Expires:: 9 > > Callid:: 447b19de71f7ae6e305211c97f4574a9 at 10.112.130.202 > > Cseq:: 107 > > User-agent:: ICOTERA IGW3000 (2.5.1) > > State:: CS_SYNC > > Flags:: 0 > > Cflags:: > > Socket:: udp:85.XXX.XXX.120:5060 > > Methods:: 4294967295 > > /Søren > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Fri Jan 13 04:25:12 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Fri, 13 Jan 2017 11:25:12 +0200 Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB In-Reply-To: <1484298184907-7605547.post@n2.nabble.com> References: <1484131458652-7605514.post@n2.nabble.com> <1484133356292-7605516.post@n2.nabble.com> <9640879b-c012-4529-5e7d-57a8ea817e67@opensips.org> <1484298184907-7605547.post@n2.nabble.com> Message-ID: <40d4cd21-5f93-5372-c09c-04c2a3c131ad@opensips.org> Yes, it is. Provision the address table in the database and use the check_source_address() functionin the script. [1] http://www.opensips.org/html/docs/modules/2.2.x/permissions#id295007 Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/13/2017 11:03 AM, maatohewetbi wrote: > Yes, but every IP and login should be in table. How can I read variables from > DB? Is it possible to do it? > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514p7605547.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From razvan at opensips.org Fri Jan 13 04:38:23 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Fri, 13 Jan 2017 11:38:23 +0200 Subject: [OpenSIPS-Users] change T_fr_in_timeout In-Reply-To: <1484232021878-7605536.post@n2.nabble.com> References: <1484232021878-7605536.post@n2.nabble.com> Message-ID: <46c9630b-1a72-7bc5-a513-f46ce771e033@opensips.org> Hello! The problem is that you are doing your logic in the onreply_route, which is not transaction aware. You should move the logic in a name onreply route that you engage in your main route. Something like: route { ... if (is_method("INVITE")) t_on_reply(handle_timer); ... } onreply_route[handle_timer] { if (t_check_status("(180)|(183)")) $T_fr_inv_timeout = 60; } Hope this is a right pointer to solve your problem. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/12/2017 04:40 PM, bluerain via Users wrote: > Ok, so hopefully I get some help in this forum, I'm trying to get a faster > PDD by going down the LCR list faster. I'm trying to use the fr_inv_timeout > to skip the carrier that has slow PDD. So I did the code below so that if I > don't get a 180/183 after invite within 5 second, I will terminate the call > and go to the next carrier. But if they do give 180/183 after invite within > 5 second, I want to change T_fr_inv to 60 seconds so have enough time for > far end user to pick up the call. But I ran into 2 problem: > > 1. 180/183 seems is NOT picking up inthe onreply_route. I did a log and it > seems on 180/183 it never went into the code where I wanted to, so is this > is WRONG place to detect 180/183? > > 2. I also try to display the value of $T_fr_inv_timeout in onreply_route > section of the code, but it always show "ZERO"? > > Anyway, any pointer will be greatly appreciated. Thank you! > > loadmodule "tm.so" > modparam("tm", "fr_timeout", 5) > modparam("tm", "fr_inv_timeout", 5) > modparam("tm", "restart_fr_on_each_reply", 0) > modparam("tm", "onreply_avp_mode", 1) > > onreply_route { > if (t_check_status("(180)|(183)")) { > $T_fr_inv_timeout = 60; > } > } > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/change-T-fr-in-timeout-tp7605536.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From xaled at web.de Fri Jan 13 05:04:34 2017 From: xaled at web.de (xaled) Date: Fri, 13 Jan 2017 11:04:34 +0100 Subject: [OpenSIPS-Users] How to parse XML Body? In-Reply-To: <6969d0ff-96a6-56da-15f4-54f8cd0c116b@opensips.org> References: <012c01d266bf$841c7590$8c5560b0$@web.de> <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> <018601d26742$7d877ee0$78967ca0$@web.de> <4936e66b-ae31-a9fa-e260-a87ef6b24b20@opensips.org> <019a01d26746$00669460$0133bd20$@web.de> <01b601d26748$2bebb6e0$83c324a0$@web.de> <01428a9e-5f55-5a7e-154d-59c2f8e96ef0@opensips.org> <01f101d2674f$dadadee0$90909ca0$@web.de> <032b01d26833$cace6370$606b2a50$@web.de> <6969d0ff-96a6-56da-15f4-54f8cd0c116b@opensips.org> Message-ID: <009101d26d84$72050d10$560f2730$@web.de> Hi Bogdan, thank you for looking at this issue. This regex does not work. I tried different combinations of the idea but it just not getting there. 2017-01-13T11:02:42.287766+01:00 ivr01 /usr/local/sbin/opensips[24845]: DBG:core:tr_eval_re: we must compile the regexp 2017-01-13T11:02:42.288116+01:00 ivr01 /usr/local/sbin/opensips[24845]: WARNING:core:parse_repl: \/ unknown escape in (.*)<\/gml:Coordinates(.*)/\2/s 2017-01-13T11:02:42.288464+01:00 ivr01 /usr/local/sbin/opensips[24845]: ERROR:core:subst_parser: unknown flag . in (.*)/gml:Coordinates>(.*)<\/gml:Coordin ates(.*)/\2/s 2017-01-13T11:02:42.288787+01:00 ivr01 /usr/local/sbin/opensips[24845]: ERROR:core:tr_eval_re: Can't compile regexp I managed to get it running with perl: use OpenSIPS qw ( log ); use OpenSIPS::Constants; use OpenSIPS::Message; sub parsePIDFLO { my $m = shift; my $body = $m->getBody(); ($coord) = $body =~ /Coordinates>(.*); asd asd Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi, Please try $var(reg) = "(.*)/gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s"; xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/06/2017 05:44 PM, xaled wrote: Hi Bogdan, can you give any hints on how to get the Coordinates values and not the whole xml body from the regex subst? Sorry for being not clever enough to figure it out myself. Thanks Hi Bogdan, $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); DBG:core:subst_run:matched shows the needed XML element with value, but not the value alone. The xlog output shows the whole XML body without gml:Coordinates. 2017-01-05T13:23:23.104982+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:tr_eval_re: Trying to apply reg exp [/gml:Coordinates>(.*)<\/gml:Coordinates/\1/] on : [#015#012 "pres:sip:+1234567 at test.com">#015#012 #015#012 #015#012 #015#012 #015#012 #015#012 #015#012 12.32 34.24#015#012 #015#012 #015#012 #015#012 #015#012 no#015#012 #015#012 #01 5#012 #015#012 #015#012 2016-8-02T04:13:23Z#015#012 #015#0 12#015#012#015#012] 2017-01-05T13:23:23.107376+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:tr_eval_re: we must compile the regexp 2017-01-05T13:23:23.107903+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_parser: ok, se is 0x7f39a 5d0a1f0 2017-01-05T13:23:23.108241+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_run: running. r=0 2017-01-05T13:23:23.111918+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_run: matched (404, 45): [ gml:Coordinates>12.32 34.24#015#012 "pres:sip:+1234567 at test.com">#015#0 12 #015#012 #015#012 #015#012 #015#012 #015#012 #015#012 <12.32 34.24>#015#012 #015#012 #015#012 #015#012 #015#012 no#015#012 #015#012 #015# 012 #015#012 #015#012 2016-8-02T04:13:23Z#015#012 #015#012 Thanks From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Donnerstag, 5. Januar 2017 13:12 To: OpenSIPS users mailling list >; xaled > Subject: Re: [OpenSIPS-Users] How to parse XML Body? Try $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From trance_maniak at o2.pl Fri Jan 13 06:09:24 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Fri, 13 Jan 2017 04:09:24 -0700 (MST) Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB In-Reply-To: <40d4cd21-5f93-5372-c09c-04c2a3c131ad@opensips.org> References: <1484131458652-7605514.post@n2.nabble.com> <1484133356292-7605516.post@n2.nabble.com> <9640879b-c012-4529-5e7d-57a8ea817e67@opensips.org> <1484298184907-7605547.post@n2.nabble.com> <40d4cd21-5f93-5372-c09c-04c2a3c131ad@opensips.org> Message-ID: <1484305764044-7605552.post@n2.nabble.com> I think You don't understand. My Opensips should work in this scenario: 1. When user wants to register, I have to check whether his sip login is in address table (which can be stored in context_info for example). If it is there then check IP, which is in this record, for this sip login. If this IP is the same as real IP of this user (from $si value), the user can be registered. If this IP is not the same - user can't be registered. 2. When user wants to register, but his sip login doesn't exist in address table - this user can be registered without IP checking. So I have to check IP, only for users, whom login is in address table. Others, can registered without checking. If I use one of function in permission module I always have to check IP. I have to check login first, then IP. I hope that now everything is clear. -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514p7605552.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From stefano.pisani at omnianet.it Fri Jan 13 06:20:29 2017 From: stefano.pisani at omnianet.it (Stefano Pisani) Date: Fri, 13 Jan 2017 12:20:29 +0100 Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB In-Reply-To: <1484305764044-7605552.post@n2.nabble.com> References: <1484131458652-7605514.post@n2.nabble.com> <1484133356292-7605516.post@n2.nabble.com> <9640879b-c012-4529-5e7d-57a8ea817e67@opensips.org> <1484298184907-7605547.post@n2.nabble.com> <40d4cd21-5f93-5372-c09c-04c2a3c131ad@opensips.org> <1484305764044-7605552.post@n2.nabble.com> Message-ID: Use 0.0.0.0/0 for those without IP filter. s Il 13/01/2017 12:09, maatohewetbi ha scritto: > I think You don't understand. My Opensips should work in this scenario: > > 1. When user wants to register, I have to check whether his sip login is in > address table (which can be stored in context_info for example). If it is > there then check IP, which is in this record, for this sip login. If this IP > is the same as real IP of this user (from $si value), the user can be > registered. If this IP is not the same - user can't be registered. > 2. When user wants to register, but his sip login doesn't exist in address > table - this user can be registered without IP checking. > > So I have to check IP, only for users, whom login is in address table. > Others, can registered without checking. If I use one of function in > permission module I always have to check IP. I have to check login first, > then IP. I hope that now everything is clear. > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514p7605552.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From trance_maniak at o2.pl Fri Jan 13 06:51:29 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Fri, 13 Jan 2017 04:51:29 -0700 (MST) Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB In-Reply-To: References: <1484131458652-7605514.post@n2.nabble.com> <1484133356292-7605516.post@n2.nabble.com> <9640879b-c012-4529-5e7d-57a8ea817e67@opensips.org> <1484298184907-7605547.post@n2.nabble.com> <40d4cd21-5f93-5372-c09c-04c2a3c131ad@opensips.org> <1484305764044-7605552.post@n2.nabble.com> Message-ID: <1484308289132-7605554.post@n2.nabble.com> Still I have to check login whether it exist in table. Then I have to compare it to IP address. -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514p7605554.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From razvan at opensips.org Fri Jan 13 07:13:36 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Fri, 13 Jan 2017 14:13:36 +0200 Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB In-Reply-To: <1484308289132-7605554.post@n2.nabble.com> References: <1484131458652-7605514.post@n2.nabble.com> <1484133356292-7605516.post@n2.nabble.com> <9640879b-c012-4529-5e7d-57a8ea817e67@opensips.org> <1484298184907-7605547.post@n2.nabble.com> <40d4cd21-5f93-5372-c09c-04c2a3c131ad@opensips.org> <1484305764044-7605552.post@n2.nabble.com> <1484308289132-7605554.post@n2.nabble.com> Message-ID: <62206e87-8dfd-8a30-2e00-702adfb55dbc@opensips.org> You can do something like this: avp_db_query("select ip from address where context_info='$fU'", "$avp(ip)"); if ($rc == -2) { # not found in db } else if ($avp(ip) != $si) { # reject the call } Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/13/2017 01:51 PM, maatohewetbi wrote: > Still I have to check login whether it exist in table. Then I have to compare > it to IP address. > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514p7605554.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From trance_maniak at o2.pl Fri Jan 13 07:18:01 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Fri, 13 Jan 2017 05:18:01 -0700 (MST) Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB In-Reply-To: <62206e87-8dfd-8a30-2e00-702adfb55dbc@opensips.org> References: <1484131458652-7605514.post@n2.nabble.com> <1484133356292-7605516.post@n2.nabble.com> <9640879b-c012-4529-5e7d-57a8ea817e67@opensips.org> <1484298184907-7605547.post@n2.nabble.com> <40d4cd21-5f93-5372-c09c-04c2a3c131ad@opensips.org> <1484305764044-7605552.post@n2.nabble.com> <1484308289132-7605554.post@n2.nabble.com> <62206e87-8dfd-8a30-2e00-702adfb55dbc@opensips.org> Message-ID: <1484309881169-7605556.post@n2.nabble.com> Razvan, that's what I was looking for. I haven't tested it yet but it looks like You made my day! Thanks -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514p7605556.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From pat at voxtelesys.com Fri Jan 13 12:55:33 2017 From: pat at voxtelesys.com (Pat Burke) Date: Fri, 13 Jan 2017 11:55:33 -0600 Subject: [OpenSIPS-Users] $rl_count in 2.2.2 In-Reply-To: References: Message-ID: Hi Răzvan, Thanks. That worked correctly. I figured it was simple. Thanks again, Pat Hi, Pat! The way you are using $rl_count is wrong, because the $rl_count pseudo variable only accepts strings or other pvars, not formatted strings (such as "cps_$avp(trunk_group)"). To achieve what you are trying to do is to assign the name to a pvar and feed it in the $rl_count's name: $var(rl_name) = "cps_" + $avp(trunk_group); $json(call_details/tg_cps) = $rl_count($var(rl_name)); Let me know how this goes. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/13/2017 12:48 AM, Pat Burke wrote: > Hello, >> I am trying to get the current rate limit value using $rl_count, but > it is giving the following error. > ERROR:ratelimit:pv_get_rl_count: invalid name > WARNING:core:do_assign: no value in right expression at > /etc/opensips/opensips_proxy.cfg:598 > 4024438929 SCRIPT:CCLIMIT:INFO: rl_limit for cps_90761 = 0 >> Here is the code >> $json(call_details/tg_cps) = 0; # Default to 0 >> ... >> if ($avp(maxcps) != NULL && $avp(maxcps) > 0) { > if (!rl_check("cps_$avp(trunk_group)", "$avp(maxcps)")) { > xlog("L_NOTICE", "$rU SCRIPT:CPSLIMIT:DBG: Max > $avp(maxcps) cps reached for trunk group $avp(trunk_group) \n"); > $avp(error_reason) = $avp(error_reason) + > $avp(trunk_group) + " CPS limit reached."; > send_reply("403", "Max CPS limit reached"); > exit; > } > } > $json(call_details/tg_cps) = $rl_count("cps_$avp(trunk_group)"); > xlog("L_INFO", "$rU SCRIPT:CCLIMIT:INFO: rl_limit for > cps_$avp(trunk_group) = $json(call_details/tg_cps) \n"); >>> From the command opensipsctl fifo rl_list | grep cps_90761, I get > PIPE:: id=cps_90761 algorithm=TAILDROP limit=2 counter=0 >> What am I missing? >> Regards, > *Pat Burke* >>>> _______________________________________________ > Users mailing list > Users at lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahmedmunir007 at gmail.com Fri Jan 13 17:24:57 2017 From: ahmedmunir007 at gmail.com (Ahmed Munir) Date: Fri, 13 Jan 2017 17:24:57 -0500 Subject: [OpenSIPS-Users] OpenSIPs crashed Message-ID: Hi, I've just installed new version of opensips 2.2.2 on the test box and updated by routing script, the issue currently I'm seeing alot warning messages while starting opensips service below; /usr/sbin/opensips[6902]: WARNING:core:handle_timer_job: utimer job has a 2830000 us delay in execution Number of children running on that server is 8 as it is 8 core processor. I would like to know what steps do I need to take to fix this issue. Btw, warnings only occurred during the time of starting opensips service but not during calls. Further added, a issue I face using avp_db_query () function i.e. when using it as $var(res) = avp_db_query("SELECT Outpulse_number,setid FROM Prefix_data where Program_prefix = $var(pg_prefix)", "$avp(outpluse), $avp(trunkid)"); failed to start opensips service due to errors below; ERROR:avpops:__fixup_db_query_avp: no db url defined to be used by this function ERROR:core:fix_actions: fixing failed (code=-6) at //etc/opensips/opensips.cfg:207 CRITICAL:core:fix_expr: fix_actions error ERROR:core:main: failed to fix configuration with err code -6 If I add this line: avp_db_query("SELECT 1"); above to my $var(res) db query, opensips service starts successfully. Please advise the steps do I need to take to fix above issues. > From: Răzvan Crainea > To: users at lists.opensips.org > Subject: Re: [OpenSIPS-Users] OpenSIPs crashed > Message-ID: <40f6dada-e121-a2da-b283-69dff891cd11 at opensips.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi, Ahmed! > > OpenSIPS 1.6.3 is no longer supported (since 2013), so there's not much > we can do right now. Try upgrading your install to the latest 1.6.4 > version and see if your problem is solved. Otherwise, upgrade to a > newer, supported version, preferably the latest stable release, 2.2.2. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > > On 01/12/2017 11:55 PM, Ahmed Munir wrote: > > Found coredump on one of the server, see some partial message below > > while taking the back trace; > > > > > > > > Core was generated by `/usr/sbin/opensips -P /var/run/opensips.pid -m > > 64 -u opensips -g opensips'. > > > > Program terminated with signal 11, Segmentation fault. > > > > #0 0x00007f650687a069 in sip_msg_cloner () from > > /usr/lib64/opensips/modules/tm.so > > > > Missing separate debuginfos, use: debuginfo-install > > opensips-1.6.3-notls.x86_64 > > > > > > > > Please advise what might be the reason causing opensips to crash. > > > > -- > > Regards, > > > > Ahmed Munir Chohan > > > > > > > > > > -- > > Regards, > > > > Ahmed Munir Chohan > > > -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From rosenberg11219 at gmail.com Sat Jan 14 15:59:18 2017 From: rosenberg11219 at gmail.com (Schneur Rosenberg) Date: Sat, 14 Jan 2017 22:59:18 +0200 Subject: [OpenSIPS-Users] Binary replication errors Message-ID: Hi, I tried to implement binary replication with OpenSIPS ver 2.2.2 and it floods my logs with the following errors on both servers Jan 14 21:12:20 sips /sbin/opensips[4484]: WARNING:dialog:receive_dlg_binary_packet: Invalid dialog binary packet command: 4 (from XXX.XXX.XXX.XXX:45107) Jan 14 21:12:20 sip /sbin/opensips[4484]: ERROR:dialog:receive_dlg_binary_packet: Failed to process a binary packet! when I do a ngrep its flooding with messsage T XXX.XXX.XXX.01:46514 -> XXX.XXX.XXX.02:5799 [AP] P4CK............dialog........ T XXX.XXX.XXX.02:45107 -> XXX.XXX.XXX.01:5799 [AP] P4CK............dialog........ Here are the relevant lines in my config file listen=bin:xxx.xxx.xxx.01:5799 and on server 2 listen=bin:xxx.xxx.xxx.02:5799 loadmodule "proto_bin.so" loadmodule "clusterer.so" modparam("clusterer", "server_id", 1) and the second server is modparam("clusterer", "server_id", 2) modparam("dialog", "accept_replicated_dialogs", 1) modparam("dialog", "replicate_dialogs_to", 1) modparam("dialog", "replicate_profiles_to", 1) modparam("usrloc", "accept_replicated_contacts", 1) modparam("usrloc", "replicate_contacts_to", 1) modparam("usrloc", "skip_replicated_db_ops", 1) I entered both servers in the clusterer table and of course I have the "db_url" set -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Sat Jan 14 17:24:14 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Sat, 14 Jan 2017 22:24:14 +0000 Subject: [OpenSIPS-Users] opensips $Revision: 4448 $ Message-ID: Hi, I am testing opensips 2.2, 2.3 I have tried to configure acc module to save to db failed calls on drouting configuration, I have found that it does save only the first failed call (that is the first gateway) it does not save to database any other failures on second and third gateways that are tried for the call. is this the expected behavioure ? Thanks for your help. regards, kh -------------- next part -------------- An HTML attachment was scrubbed... URL: From rosenberg11219 at gmail.com Sun Jan 15 08:14:16 2017 From: rosenberg11219 at gmail.com (Schneur Rosenberg) Date: Sun, 15 Jan 2017 15:14:16 +0200 Subject: [OpenSIPS-Users] Binary replication errors In-Reply-To: References: Message-ID: I removed the modparam("dialog", "replicate_profiles_to", 1) and the modparam("dialog", "accept_replicated_profiles", 1) (which was in my script but forgot to paste it in previous post) and now it works. Seems like its a old problem, when I had the profile replication I was getting "WARNING:dialog:receive_prof_binary_packet: bad packet type" Liviu was aware of it (https://github.com/OpenSIPS/opensips/issues/938) , but I still have issues in latest build. I wonder why the old replication methods were removed and replaced with a module thats still in Alpha (clusterer) ????? The documentation of clusterer and replication is also outdated, for example opensips does not recognize the parameter persistent_mode which is supposed to work according to the docs. also the binary replication docs for 2.2 still tells you to use bin_listen which has been replaced with listen=bin, it also tells you to use bin_children which was phased out as, see the following link. https://www.opensips.org/Documentation/Interface-Binary-2-2 S. Rosenberg On Sat, Jan 14, 2017 at 10:59 PM, Schneur Rosenberg wrote: > > Hi, I tried to implement binary replication with OpenSIPS ver 2.2.2 and it floods my logs with the following errors on both servers > > Jan 14 21:12:20 sips /sbin/opensips[4484]: WARNING:dialog:receive_dlg_binary_packet: Invalid dialog binary packet command: 4 (from XXX.XXX.XXX.XXX:45107) > Jan 14 21:12:20 sip /sbin/opensips[4484]: ERROR:dialog:receive_dlg_binary_packet: Failed to process a binary packet! > > when I do a ngrep its flooding with messsage > > T XXX.XXX.XXX.01:46514 -> XXX.XXX.XXX.02:5799 [AP] > P4CK............dialog........ > > T XXX.XXX.XXX.02:45107 -> XXX.XXX.XXX.01:5799 [AP] > P4CK............dialog........ > > Here are the relevant lines in my config file > > listen=bin:xxx.xxx.xxx.01:5799 and on server 2 listen=bin:xxx.xxx.xxx.02:5799 > > loadmodule "proto_bin.so" > > loadmodule "clusterer.so" > modparam("clusterer", "server_id", 1) and the second server is modparam("clusterer", "server_id", 2) > > modparam("dialog", "accept_replicated_dialogs", 1) > modparam("dialog", "replicate_dialogs_to", 1) > modparam("dialog", "replicate_profiles_to", 1) > > modparam("usrloc", "accept_replicated_contacts", 1) > modparam("usrloc", "replicate_contacts_to", 1) > modparam("usrloc", "skip_replicated_db_ops", 1) > > I entered both servers in the clusterer table and of course I have the "db_url" set > > From pinghan022 at gmail.com Sun Jan 15 23:33:39 2017 From: pinghan022 at gmail.com (Ping Han) Date: Mon, 16 Jan 2017 15:33:39 +1100 Subject: [OpenSIPS-Users] Question regarding b2b_bridge function In-Reply-To: <578764E9.7010801@opensips.org> References: <574D44F7.9090204@opensips.org> <574E8B1A.7070508@opensips.org> <574FE1C0.9000904@opensips.org> <575145C9.9080406@opensips.org> <575583A1.7050501@opensips.org> <5756A333.1010701@opensips.org> <578764E9.7010801@opensips.org> Message-ID: Hi Bogdan, Sorry for the very late delay. I just came back to this issue and we are still having the problem. It would be great if you can provide a patch for testing that will expose in local route and AVP holding the B2B logic ID. Thanks, Ping On Thu, Jul 14, 2016 at 8:09 PM, Bogdan-Andrei Iancu wrote: > Hello Ping, > > Sorry for the delay - if I provide a small patch for test that will expose > in local route and AVP holding the B2B logic ID, will be fine with you ? > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developerhttp://www.opensips-solutions.com > > On 07.06.2016 16:15, Ping Han wrote: > > Hi Bogdan, > > Yes, that is exactly what I am trying to do. > > Regards, > Ping > > On Tue, Jun 7, 2016 at 8:34 PM, Bogdan-Andrei Iancu < > bogdan at opensips.org> wrote: > >> Hi Ping, >> >> So you need the B2B Logic ID only when you create the B2B session, in >> order to place it in the first outgoing INVITE (as extra hdr), right ? >> >> Regards, >> >> Bogdan-Andrei Iancu >> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com >> >> On 07.06.2016 04:59, Ping Han wrote: >> >> Thanks, Bogdan, >> >> What I am trying to do is to get the b2b logic ID and deliver to the >> next hop via a custom SIP header. >> >> I am using the b2b_init_request("top hiding") and it looks like the only >> place that I can add a custom header is in the local_route. >> >> So in the script I need the b2b logic ID after running b2b_init_request("top >> hiding") but before the new INVITE is sent to the B party as shown >> below. >> >> I am not sure how I can do that. >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Mon Jan 16 03:49:37 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Mon, 16 Jan 2017 10:49:37 +0200 Subject: [OpenSIPS-Users] OpenSIPs crashed In-Reply-To: References: Message-ID: <1584806e-a154-a5ad-a464-4eef609158f4@opensips.org> Hi, Ahmed! Can you tell us exactly what revision of OpenSIPS you are using? Please provide the output of the following commands: opensips -V opensipsctl ps Also, during startup, is there a process who's "eating" a lot of CPU? If so, can you pinpoint the PID to see what type of process is that? Regarding the avp_db_query() issue, did you define a db_url parameter for it? Also I am not sure you can do something like $var(res) = avp_db_query(...). But anyways, this is something completely different, so please open a different topic for it. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/14/2017 12:24 AM, Ahmed Munir wrote: > Hi, > > I've just installed new version of opensips 2.2.2 on the test box and > updated by routing script, the issue currently I'm seeing alot warning > messages while starting opensips service below; > > /usr/sbin/opensips[6902]: WARNING:core:handle_timer_job: utimer job > has a 2830000 us delay in execution > > Number of children running on that server is 8 as it is 8 core processor. > > I would like to know what steps do I need to take to fix this issue. > Btw, warnings only occurred during the time of starting opensips > service but not during calls. > > > Further added, a issue I face using avp_db_query () function i.e. when > using it as > > $var(res) = avp_db_query("SELECT Outpulse_number,setid FROM > Prefix_data where Program_prefix = $var(pg_prefix)", "$avp(outpluse), > $avp(trunkid)"); > > failed to start opensips service due to errors below; > > ERROR:avpops:__fixup_db_query_avp: no db url defined to be used by > this function > ERROR:core:fix_actions: fixing failed (code=-6) at > //etc/opensips/opensips.cfg:207 > CRITICAL:core:fix_expr: fix_actions error > ERROR:core:main: failed to fix configuration with err code -6 > > > If I add this line: avp_db_query("SELECT 1"); above to my $var(res) db > query, opensips service starts successfully. > > Please advise the steps do I need to take to fix above issues. > > > > From: Răzvan Crainea > > To: users at lists.opensips.org > Subject: Re: [OpenSIPS-Users] OpenSIPs crashed > Message-ID: <40f6dada-e121-a2da-b283-69dff891cd11 at opensips.org > > > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi, Ahmed! > > OpenSIPS 1.6.3 is no longer supported (since 2013), so there's not > much > we can do right now. Try upgrading your install to the latest 1.6.4 > version and see if your problem is solved. Otherwise, upgrade to a > newer, supported version, preferably the latest stable release, 2.2.2. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > > On 01/12/2017 11:55 PM, Ahmed Munir wrote: > > Found coredump on one of the server, see some partial message below > > while taking the back trace; > > > > > > > > Core was generated by `/usr/sbin/opensips -P > /var/run/opensips.pid -m > > 64 -u opensips -g opensips'. > > > > Program terminated with signal 11, Segmentation fault. > > > > #0 0x00007f650687a069 in sip_msg_cloner () from > > /usr/lib64/opensips/modules/tm.so > > > > Missing separate debuginfos, use: debuginfo-install > > opensips-1.6.3-notls.x86_64 > > > > > > > > Please advise what might be the reason causing opensips to crash. > > > > -- > > Regards, > > > > Ahmed Munir Chohan > > > > > > > > > > -- > > Regards, > > > > Ahmed Munir Chohan > > > > > > > -- > Regards, > > Ahmed Munir Chohan > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Mon Jan 16 03:51:32 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Mon, 16 Jan 2017 10:51:32 +0200 Subject: [OpenSIPS-Users] opensips $Revision: 4448 $ In-Reply-To: References: Message-ID: <5049c51f-931a-ea24-54ae-a1dfeb6fb7a9@opensips.org> Hi, Khalil! Did you try to call the do_accounting() function for each leg going to the next gateway? Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/15/2017 12:24 AM, Khalil Khamlichi wrote: > Hi, > I am testing opensips 2.2, 2.3 I have tried to configure acc module to > save to db failed calls on drouting configuration, I have found that > it does save only the first failed call (that is the first gateway) it > does not save to database any other failures on second and third > gateways that are tried for the call. > is this the expected behavioure ? > Thanks for your help. > > regards, > kh > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Mon Jan 16 04:07:37 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Mon, 16 Jan 2017 11:07:37 +0200 Subject: [OpenSIPS-Users] mi_json Module Message-ID: Hello, I try to use mi_json modile in Opensips 2.2.2. All is OK when try to read log level: opensips_ip:Opensips_http_port/json/log_level How to use "get_statistics hmem:" ? Follow command not working: opensips_ip:Opensips_http_port/json/get_statistics%20shmem: Regards, Dragomir -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Mon Jan 16 04:47:30 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Mon, 16 Jan 2017 09:47:30 +0000 Subject: [OpenSIPS-Users] opensips $Revision: 4448 $ In-Reply-To: <5049c51f-931a-ea24-54ae-a1dfeb6fb7a9@opensips.org> References: <5049c51f-931a-ea24-54ae-a1dfeb6fb7a9@opensips.org> Message-ID: thanks for your much appreciated help, I am calling do_routing twice. Here is my actual opensips.cfg : route { ... ... ... ... if (has_totag()) { # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { # validate the sequential request against dialog if ( $DLG_status!=NULL && !validate_dialog() ) { xlog("In-Dialog $rm from $si (callid=$ci) is not valid according to dialog\n"); } if (is_method("BYE")) { # do accounting even if the transaction fails do_accounting("db|log","failed|missed",); } else if (is_method("INVITE")) { # even if in most of the cases is useless, do RR for # re-INVITEs alos, as some buggy clients do change route set # during the dialog. record_route(); } ... ... ... ... $acc_extra(gwid)=$avp(gw_id); t_on_failure("GW_FAILOVER"); do_accounting("db|log","cdr|missed",); #NAT if (isbflagset(NAT)) setflag(NAT); #NAT route(RELAY); } # END OF MAIN ROUTE On Mon, Jan 16, 2017 at 8:51 AM, Răzvan Crainea wrote: > Hi, Khalil! > > Did you try to call the do_accounting() function for each leg going to the > next gateway? > > Best regards, > > Răzvan Crainea > OpenSIPS Solutionswww.opensips-solutions.com > > On 01/15/2017 12:24 AM, Khalil Khamlichi wrote: > > Hi, > I am testing opensips 2.2, 2.3 I have tried to configure acc module to > save to db failed calls on drouting configuration, I have found that it > does save only the first failed call (that is the first gateway) it does > not save to database any other failures on second and third gateways that > are tried for the call. > is this the expected behavioure ? > Thanks for your help. > > regards, > kh > > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Mon Jan 16 05:02:29 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Mon, 16 Jan 2017 10:02:29 +0000 Subject: [OpenSIPS-Users] opensips $Revision: 4448 $ In-Reply-To: References: <5049c51f-931a-ea24-54ae-a1dfeb6fb7a9@opensips.org> Message-ID: sorry mistype, I am calling do_accounting() twice. On Mon, Jan 16, 2017 at 9:47 AM, Khalil Khamlichi < khamlichi.khalil at gmail.com> wrote: > thanks for your much appreciated help, > I am calling do_routing twice. > > Here is my actual opensips.cfg : > > route { > ... > ... > > ... > ... > if (has_totag()) { > # sequential request withing a dialog should > # take the path determined by record-routing > if (loose_route()) { > > # validate the sequential request against dialog > if ( $DLG_status!=NULL && !validate_dialog() ) { > xlog("In-Dialog $rm from $si (callid=$ci) > is not valid according to dialog\n"); > } > > if (is_method("BYE")) { > # do accounting even if the transaction > fails > do_accounting("db|log","failed|missed",); > } else if (is_method("INVITE")) { > # even if in most of the cases is useless, > do RR for > # re-INVITEs alos, as some buggy clients > do change route set > # during the dialog. > record_route(); > } > ... > ... > > ... > ... > $acc_extra(gwid)=$avp(gw_id); > > t_on_failure("GW_FAILOVER"); > > do_accounting("db|log","cdr|missed",); > #NAT > if (isbflagset(NAT)) setflag(NAT); > #NAT > route(RELAY); > } > > # END OF MAIN ROUTE > > > On Mon, Jan 16, 2017 at 8:51 AM, Răzvan Crainea > wrote: > >> Hi, Khalil! >> >> Did you try to call the do_accounting() function for each leg going to >> the next gateway? >> >> Best regards, >> >> Răzvan Crainea >> OpenSIPS Solutionswww.opensips-solutions.com >> >> On 01/15/2017 12:24 AM, Khalil Khamlichi wrote: >> >> Hi, >> I am testing opensips 2.2, 2.3 I have tried to configure acc module to >> save to db failed calls on drouting configuration, I have found that it >> does save only the first failed call (that is the first gateway) it does >> not save to database any other failures on second and third gateways that >> are tried for the call. >> is this the expected behavioure ? >> Thanks for your help. >> >> regards, >> kh >> >> >> _______________________________________________ >> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Mon Jan 16 05:24:20 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Mon, 16 Jan 2017 12:24:20 +0200 Subject: [OpenSIPS-Users] Problem with switch .. case Message-ID: Hello, I see problem when using switch .. case. Opensips version 2.2.2. Here is part of my script: radius_send_auth("out","in"); xlog("L_ERR", "Radius return $rc"); switch ($rc) { case -1: xlog("L_ERR", "ERROR during authentication"); sl_reply_error(); exit; case -2: xlog("L_ERR", "Authentication denied"); sl_reply_error(); exit; } # end switch xlog("L_ERR", "Continue ...."); This is results: Jan 16 10:16:55 sbc-01 /usr/sbin/opensips[7820]: Radius return -1 Jan 16 10:16:55 sbc-01 /usr/sbin/opensips[7820]: Continue .... Best regards, Dragomir -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Mon Jan 16 06:06:24 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Mon, 16 Jan 2017 13:06:24 +0200 Subject: [OpenSIPS-Users] mi_json Module In-Reply-To: References: Message-ID: <98cd5d5e-458d-97ea-4eb5-65e22b04638b@opensips.org> Hi, Dragomir! Parameters are sent in the params parameter. Check the example in the documentation: http://www.opensips.org/html/docs/modules/2.2.x/mi_json#id249590 This works for me: # curl -s 'http://127.0.0.1:8080/json/get_statistics?params=shmem:' Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/16/2017 11:07 AM, Dragomir Haralambiev wrote: > Hello, > > I try to use mi_json modile in Opensips 2.2.2. > > All is OK when try to read log level: > > opensips_ip:Opensips_http_port/json/log_level > > How to use "get_statistics hmem:" ? > Follow command not working: > > opensips_ip:Opensips_http_port/json/get_statistics%20shmem: > > Regards, > Dragomir > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Mon Jan 16 06:07:19 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Mon, 16 Jan 2017 13:07:19 +0200 Subject: [OpenSIPS-Users] opensips $Revision: 4448 $ In-Reply-To: References: <5049c51f-931a-ea24-54ae-a1dfeb6fb7a9@opensips.org> Message-ID: <6b622d0c-ec7c-3cc3-56be-8a6425821390@opensips.org> I was asking you to call do_accounting() in failure route, for each leg. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/16/2017 12:02 PM, Khalil Khamlichi wrote: > sorry mistype, I am calling do_accounting() twice. > > On Mon, Jan 16, 2017 at 9:47 AM, Khalil Khamlichi > > wrote: > > thanks for your much appreciated help, > I am calling do_routing twice. > > Here is my actual opensips.cfg : > > route { > ... > ... > > ... > ... > if (has_totag()) { > # sequential request withing a dialog should > # take the path determined by record-routing > if (loose_route()) { > > # validate the sequential request against dialog > if ( $DLG_status!=NULL && > !validate_dialog() ) { > xlog("In-Dialog $rm from $si (callid=$ci) is not valid according > to dialog\n"); > } > > if (is_method("BYE")) { > # do accounting even if the transaction fails > do_accounting("db|log","failed|missed",); > } else if (is_method("INVITE")) { > # even if in most of the cases is useless, do RR for > # re-INVITEs alos, as some buggy clients do change route set > # during the dialog. > record_route(); > } > ... > ... > > ... > ... > $acc_extra(gwid)=$avp(gw_id); > > t_on_failure("GW_FAILOVER"); > > do_accounting("db|log","cdr|missed",); > #NAT > if (isbflagset(NAT)) setflag(NAT); > #NAT > route(RELAY); > } > > # END OF MAIN ROUTE > > > On Mon, Jan 16, 2017 at 8:51 AM, Răzvan Crainea > > wrote: > > Hi, Khalil! > > Did you try to call the do_accounting() function for each leg > going to the next gateway? > > Best regards, > > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > > On 01/15/2017 12:24 AM, Khalil Khamlichi wrote: >> Hi, >> I am testing opensips 2.2, 2.3 I have tried to configure acc >> module to save to db failed calls on drouting configuration, >> I have found that it does save only the first failed call >> (that is the first gateway) it does not save to database any >> other failures on second and third gateways that are tried >> for the call. >> is this the expected behavioure ? >> Thanks for your help. >> >> regards, >> kh >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > _______________________________________________ Users mailing > list Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Mon Jan 16 06:08:51 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Mon, 16 Jan 2017 13:08:51 +0200 Subject: [OpenSIPS-Users] Problem with switch .. case In-Reply-To: References: Message-ID: <21fd7f81-c85a-f19d-a6eb-f289ee393301@opensips.org> The $rc in the switch is the return value of xlog(), which probably is success. Just remove the xlog after the radius_send_auth(), or store the $rc in a variable and test that variable. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/16/2017 12:24 PM, Dragomir Haralambiev wrote: > Hello, > > I see problem when using switch .. case. > Opensips version 2.2.2. > > Here is part of my script: > > radius_send_auth("out","in"); > xlog("L_ERR","Radius return $rc"); > switch ($rc) { > case -1: > xlog("L_ERR", "ERROR during authentication"); > sl_reply_error(); > exit; > case -2: > xlog("L_ERR", "Authentication denied"); > sl_reply_error(); > exit; > } # end switch > xlog("L_ERR","Continue ...."); > > This is results: > Jan 16 10:16:55 sbc-01 /usr/sbin/opensips[7820]: Radius return -1 > Jan 16 10:16:55 sbc-01 /usr/sbin/opensips[7820]: Continue .... > > Best regards, > Dragomir > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Mon Jan 16 06:18:56 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Mon, 16 Jan 2017 11:18:56 +0000 Subject: [OpenSIPS-Users] opensips $Revision: 4448 $ In-Reply-To: <6b622d0c-ec7c-3cc3-56be-8a6425821390@opensips.org> References: <5049c51f-931a-ea24-54ae-a1dfeb6fb7a9@opensips.org> <6b622d0c-ec7c-3cc3-56be-8a6425821390@opensips.org> Message-ID: Oki, I will modify my old failure_route : failure_route[GW_FAILOVER] { if (t_was_cancelled()) { exit; } # detect failure and redirect to next available GW if (t_check_status("(408)|488|([56][0-9][0-9])")) { #xlog("Failed GW $rd detected \n"); if ( use_next_gw() ) { t_on_failure("GW_FAILOVER"); t_relay(); exit; } send_reply("500","All GW are down"); } } to : failure_route[GW_FAILOVER] { if (t_was_cancelled()) { exit; } # detect failure and redirect to next available GW if (t_check_status("(408)|488|([56][0-9][0-9])")) { xlog("Failed GW $rd detected \n"); if ( use_next_gw() ) { t_on_failure("GW_FAILOVER"); *do_accounting("db|log","failed|missed",);* t_relay(); exit; } send_reply("500","All GW are down"); } } right ? On Mon, Jan 16, 2017 at 11:07 AM, Răzvan Crainea wrote: > I was asking you to call do_accounting() in failure route, for each leg. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutionswww.opensips-solutions.com > > On 01/16/2017 12:02 PM, Khalil Khamlichi wrote: > > sorry mistype, I am calling do_accounting() twice. > > On Mon, Jan 16, 2017 at 9:47 AM, Khalil Khamlichi < > khamlichi.khalil at gmail.com> wrote: > >> thanks for your much appreciated help, >> I am calling do_routing twice. >> >> Here is my actual opensips.cfg : >> >> route { >> ... >> ... >> >> ... >> ... >> if (has_totag()) { >> # sequential request withing a dialog should >> # take the path determined by record-routing >> if (loose_route()) { >> >> # validate the sequential request against dialog >> if ( $DLG_status!=NULL && !validate_dialog() ) { >> xlog("In-Dialog $rm from $si (callid=$ci) >> is not valid according to dialog\n"); >> } >> >> if (is_method("BYE")) { >> # do accounting even if the transaction >> fails >> do_accounting("db|log","failed|missed",); >> } else if (is_method("INVITE")) { >> # even if in most of the cases is >> useless, do RR for >> # re-INVITEs alos, as some buggy clients >> do change route set >> # during the dialog. >> record_route(); >> } >> ... >> ... >> >> ... >> ... >> $acc_extra(gwid)=$avp(gw_id); >> >> t_on_failure("GW_FAILOVER"); >> >> do_accounting("db|log","cdr|missed",); >> #NAT >> if (isbflagset(NAT)) setflag(NAT); >> #NAT >> route(RELAY); >> } >> >> # END OF MAIN ROUTE >> >> >> On Mon, Jan 16, 2017 at 8:51 AM, Răzvan Crainea >> wrote: >> >>> Hi, Khalil! >>> >>> Did you try to call the do_accounting() function for each leg going to >>> the next gateway? >>> >>> Best regards, >>> >>> Răzvan Crainea >>> OpenSIPS Solutionswww.opensips-solutions.com >>> >>> On 01/15/2017 12:24 AM, Khalil Khamlichi wrote: >>> >>> Hi, >>> I am testing opensips 2.2, 2.3 I have tried to configure acc module to >>> save to db failed calls on drouting configuration, I have found that it >>> does save only the first failed call (that is the first gateway) it does >>> not save to database any other failures on second and third gateways that >>> are tried for the call. >>> is this the expected behavioure ? >>> Thanks for your help. >>> >>> regards, >>> kh >>> >>> >>> _______________________________________________ >>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> _______________________________________________ Users mailing list >>> Users at lists.opensips.org http://lists.opensips.org/cgi- >>> bin/mailman/listinfo/users >> >> _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Mon Jan 16 06:35:34 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Mon, 16 Jan 2017 13:35:34 +0200 Subject: [OpenSIPS-Users] opensips $Revision: 4448 $ In-Reply-To: References: <5049c51f-931a-ea24-54ae-a1dfeb6fb7a9@opensips.org> <6b622d0c-ec7c-3cc3-56be-8a6425821390@opensips.org> Message-ID: <1478d69f-45f2-9d84-805c-b5bc7f0d547d@opensips.org> Yes, please try that. To be honest, I've never done it using the new accounting module, but this might do the trick. Also, did you take a look at the multi-legging accounting? Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/16/2017 01:18 PM, Khalil Khamlichi wrote: > Oki, I will modify my old failure_route : > > > failure_route[GW_FAILOVER]{ > > if (t_was_cancelled()) { > exit; > } > > # detect failure and redirect to next available GW > if (t_check_status("(408)|488|([56][0-9][0-9])")) { > #xlog("Failed GW $rd detected \n"); > > if ( use_next_gw() ) { > t_on_failure("GW_FAILOVER"); > t_relay(); > exit; > } > > send_reply("500","All GW are down"); > } > } > > > to : > > > failure_route[GW_FAILOVER]{ > > if (t_was_cancelled()) { > exit; > } > > # detect failure and redirect to next available GW > if (t_check_status("(408)|488|([56][0-9][0-9])")) { > xlog("Failed GW $rd detected \n"); > > if ( use_next_gw() ) { > t_on_failure("GW_FAILOVER"); > *do_accounting("db|log","failed|missed",);* > t_relay(); > exit; > } > > send_reply("500","All GW are down"); > } > } > > > right ? > > On Mon, Jan 16, 2017 at 11:07 AM, Răzvan Crainea > wrote: > > I was asking you to call do_accounting() in failure route, for > each leg. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > > On 01/16/2017 12:02 PM, Khalil Khamlichi wrote: >> sorry mistype, I am calling do_accounting() twice. >> >> On Mon, Jan 16, 2017 at 9:47 AM, Khalil Khamlichi >> > >> wrote: >> >> thanks for your much appreciated help, >> I am calling do_routing twice. >> >> Here is my actual opensips.cfg : >> >> route { >> ... >> ... >> >> ... >> ... >> if (has_totag()) { >> # sequential request withing a dialog should >> # take the path determined by record-routing >> if (loose_route()) { >> >> # validate the sequential request against dialog >> if ( $DLG_status!=NULL && >> !validate_dialog() ) { >> xlog("In-Dialog $rm from $si (callid=$ci) is not valid >> according to dialog\n"); >> } >> >> if (is_method("BYE")) { >> # do accounting even if the transaction fails >> do_accounting("db|log","failed|missed",); >> } else if (is_method("INVITE")) { >> # even if in most of the cases is useless, do RR for >> # re-INVITEs alos, as some buggy clients do change route set >> # during the dialog. >> record_route(); >> } >> ... >> ... >> >> ... >> ... >> $acc_extra(gwid)=$avp(gw_id); >> >> t_on_failure("GW_FAILOVER"); >> >> do_accounting("db|log","cdr|missed",); >> #NAT >> if (isbflagset(NAT)) setflag(NAT); >> #NAT >> route(RELAY); >> } >> >> # END OF MAIN ROUTE >> >> >> On Mon, Jan 16, 2017 at 8:51 AM, Răzvan Crainea >> > wrote: >> >> Hi, Khalil! >> >> Did you try to call the do_accounting() function for each >> leg going to the next gateway? >> >> Best regards, >> >> Răzvan Crainea >> OpenSIPS Solutions >> www.opensips-solutions.com >> >> >> On 01/15/2017 12:24 AM, Khalil Khamlichi wrote: >>> Hi, >>> I am testing opensips 2.2, 2.3 I have tried to configure >>> acc module to save to db failed calls on drouting >>> configuration, I have found that it does save only the >>> first failed call (that is the first gateway) it does >>> not save to database any other failures on second and >>> third gateways that are tried for the call. >>> is this the expected behavioure ? >>> Thanks for your help. >>> >>> regards, >>> kh >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >> _______________________________________________ Users >> mailing list Users at lists.opensips.org >> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > _______________________________________________ Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Mon Jan 16 06:46:01 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Mon, 16 Jan 2017 11:46:01 +0000 Subject: [OpenSIPS-Users] opensips $Revision: 4448 $ In-Reply-To: <1478d69f-45f2-9d84-805c-b5bc7f0d547d@opensips.org> References: <5049c51f-931a-ea24-54ae-a1dfeb6fb7a9@opensips.org> <6b622d0c-ec7c-3cc3-56be-8a6425821390@opensips.org> <1478d69f-45f2-9d84-805c-b5bc7f0d547d@opensips.org> Message-ID: multi-legging accounting is the next step in my planning, will let you updated about it. I will be testing this later on today, I just hope $avp(gw_id) gets updated too on the cdr. On Mon, Jan 16, 2017 at 11:35 AM, Răzvan Crainea wrote: > Yes, please try that. To be honest, I've never done it using the new > accounting module, but this might do the trick. > Also, did you take a look at the multi-legging accounting? > > Best regards, > > Răzvan Crainea > OpenSIPS Solutionswww.opensips-solutions.com > > On 01/16/2017 01:18 PM, Khalil Khamlichi wrote: > > Oki, I will modify my old failure_route : > > > failure_route[GW_FAILOVER] { > > if (t_was_cancelled()) { > exit; > } > > # detect failure and redirect to next available GW > if (t_check_status("(408)|488|([56][0-9][0-9])")) { > #xlog("Failed GW $rd detected \n"); > > if ( use_next_gw() ) { > t_on_failure("GW_FAILOVER"); > t_relay(); > exit; > } > > send_reply("500","All GW are down"); > } > } > > > to : > > > failure_route[GW_FAILOVER] { > > if (t_was_cancelled()) { > exit; > } > > # detect failure and redirect to next available GW > if (t_check_status("(408)|488|([56][0-9][0-9])")) { > xlog("Failed GW $rd detected \n"); > > if ( use_next_gw() ) { > t_on_failure("GW_FAILOVER"); > *do_accounting("db|log","failed|missed",);* > t_relay(); > exit; > } > > send_reply("500","All GW are down"); > } > } > > > right ? > > On Mon, Jan 16, 2017 at 11:07 AM, Răzvan Crainea > wrote: > >> I was asking you to call do_accounting() in failure route, for each leg. >> >> Best regards, >> >> Răzvan Crainea >> OpenSIPS Solutionswww.opensips-solutions.com >> >> On 01/16/2017 12:02 PM, Khalil Khamlichi wrote: >> >> sorry mistype, I am calling do_accounting() twice. >> >> On Mon, Jan 16, 2017 at 9:47 AM, Khalil Khamlichi < >> khamlichi.khalil at gmail.com> wrote: >> >>> thanks for your much appreciated help, >>> I am calling do_routing twice. >>> >>> Here is my actual opensips.cfg : >>> >>> route { >>> ... >>> ... >>> >>> ... >>> ... >>> if (has_totag()) { >>> # sequential request withing a dialog should >>> # take the path determined by record-routing >>> if (loose_route()) { >>> >>> # validate the sequential request against dialog >>> if ( $DLG_status!=NULL && !validate_dialog() ) { >>> xlog("In-Dialog $rm from $si (callid=$ci) >>> is not valid according to dialog\n"); >>> } >>> >>> if (is_method("BYE")) { >>> # do accounting even if the transaction >>> fails >>> do_accounting("db|log","failed|missed",); >>> } else if (is_method("INVITE")) { >>> # even if in most of the cases is >>> useless, do RR for >>> # re-INVITEs alos, as some buggy clients >>> do change route set >>> # during the dialog. >>> record_route(); >>> } >>> ... >>> ... >>> >>> ... >>> ... >>> $acc_extra(gwid)=$avp(gw_id); >>> >>> t_on_failure("GW_FAILOVER"); >>> >>> do_accounting("db|log","cdr|missed",); >>> #NAT >>> if (isbflagset(NAT)) setflag(NAT); >>> #NAT >>> route(RELAY); >>> } >>> >>> # END OF MAIN ROUTE >>> >>> >>> On Mon, Jan 16, 2017 at 8:51 AM, Răzvan Crainea >>> wrote: >>> >>>> Hi, Khalil! >>>> >>>> Did you try to call the do_accounting() function for each leg going to >>>> the next gateway? >>>> >>>> Best regards, >>>> >>>> Răzvan Crainea >>>> OpenSIPS Solutionswww.opensips-solutions.com >>>> >>>> On 01/15/2017 12:24 AM, Khalil Khamlichi wrote: >>>> >>>> Hi, >>>> I am testing opensips 2.2, 2.3 I have tried to configure acc module to >>>> save to db failed calls on drouting configuration, I have found that it >>>> does save only the first failed call (that is the first gateway) it does >>>> not save to database any other failures on second and third gateways that >>>> are tried for the call. >>>> is this the expected behavioure ? >>>> Thanks for your help. >>>> >>>> regards, >>>> kh >>>> >>>> >>>> _______________________________________________ >>>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>> >>>> _______________________________________________ Users mailing list >>>> Users at lists.opensips.org http://lists.opensips.org/cgi- >>>> bin/mailman/listinfo/users >>> >>> _______________________________________________ >> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> _______________________________________________ Users mailing list >> Users at lists.opensips.org http://lists.opensips.org/cgi- >> bin/mailman/listinfo/users > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rrobson at greenlightcrm.com Mon Jan 16 07:57:44 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Mon, 16 Jan 2017 12:57:44 +0000 Subject: [OpenSIPS-Users] opensips Crashing v2.2.2 In-Reply-To: <270e22e1-46f3-2f8d-e44c-a4dad2b61711@greenlightcrm.com> References: <86d31aca-5635-9683-59d5-1b6412555a57@greenlightcrm.com> <270e22e1-46f3-2f8d-e44c-a4dad2b61711@greenlightcrm.com> Message-ID: Hi, I've done some more testing and the carrier is now responding with a shorter message, despite them saying nothing was wrong. and the crashing isn't happening. Therefore I'm unable to reproduce the original error on our live system. I've put the node back into service and I'm monitoring the situation. Regards, Richard On 06/01/2017 12:19, Richard Robson wrote: > I've some more back traces. > > this could be a resource problem. The back story is we want to check > for channel limits and Rate limits for all calls. Channel limit hits > should failover to the next gateway and rate limits should delat for > up to 2 seconds before failing over to the next gateway. This is all > working ok as far as I can tell. We have one provider that has 600 > channels and cps of 25. We now have a second provider with 3 nodes of > 100 channels and 4 cps. All nodes are being checked for Channels and > CPS. I noticed that the failover of GW was not being checked and added > new route to do the checking. Also to confuse things more it looks > like one of the new carriers nodes may be incorrectly configured asnd > we are getting failures (503 Service unavailable). > Yesterday we were using all four gateways and no crashes, but after > adding in the new route for the failover checking it started to crash > this morning. the logs indicate that the failover is working correctly. > We are checking the outbound calls twice once for the customer limits > and then for the carrier limits. This has been fine for the last few > days, since the system was updated ( it was only carrier limits > checked before) > > i've removed the suspect node and the extra route, but I notice the > error from the node in the backtraces with an address out of bounds > > I've more back traces if you require > > http://pastebin.com/BB9RP6rv > http://pastebin.com/QSTbYgNQ > http://pastebin.com/vUmQLT0k > > On 06/01/2017 09:30, Richard Robson wrote: >> Hi, >> >> we are getting a crash in opensips. V2.2.2 >> >> >> bt all: >> >> >> #0 0x0000000000425de2 in context_put_int (type=CONTEXT_GLOBAL, >> ctx=0x0, pos=4, data=1) at context.c:173 >> No locals. >> #1 0x00007f1c121642cc in dlg_onreply (t=0x7f1c1d86e938, >> type=, param=) at dlg_handlers.c:490 >> rpl = 0x7f1c3be9f3b8 >> req = 0x7f1c1cf97070 >> dlg = 0x7f1c20b39040 >> new_state = 0 >> old_state = 472847928 >> unref = 495381272 >> event = 4 >> mangled_from = {s = 0x0, len = 0} >> mangled_to = {s = 0x0, len = 0} >> req_out_buff = >> #2 0x00007f1c1b5a4069 in run_trans_callbacks (type=type at entry=64, >> trans=trans at entry=0x7f1c1d86e938, req=req at entry=0x7f1c1cf97070, >> rpl=, code=) at t_hooks.c:209 >> params = {req = 0x7f1c1cf97070, rpl = 0x7f1c3be9f3b8, code = >> 500, param = 0x7f1c1c6110c0, extra1 = 0x7ffc05c6ebe0, extra2 = >> 0x7f1c1d86ea50} >> cbp = 0x7f1c1c6110b0 >> backup = 0x845628 >> trans_backup = 0x7f1c1d86e938 >> __FUNCTION__ = "run_trans_callbacks" >> #3 0x00007f1c1b5a43c2 in run_trans_callbacks_locked >> (type=type at entry=64, trans=trans at entry=0x7f1c1d86e938, >> req=0x7f1c1cf97070, rpl=rpl at entry=0x7f1c3be9f3b8, >> code=code at entry=500) at t_hooks.c:262 >> No locals. >> #4 0x00007f1c1b55bf9c in relay_reply (t=, >> p_msg=, branch=, msg_status=> out>, cancel_bitmap=) at t_reply.c:1244 >> relay = >> save_clone = >> buf = 0x7f1c3be954b0 "SIP/2.0 500 Service Unavailable-No >> Bandwidth Available\r\nVia: SIP/2.0/UDP >> 192.168.36.12:5060;received=192.168.36.12;rport=5060;branch=z9hG4bK32b724a4\r\nTo: >> ;tag=3692683275"... >> res_len = 484 >> relayed_code = 500 >> relayed_msg = >> bm = {to_tag_val = {s = 0x1
, len >> = 8897760}} >> totag_retr = 0 >> uas_rb = >> cb_s = { >> s = 0x7f1c3be954b0 "SIP/2.0 500 Service Unavailable-No >> Bandwidth Available\r\nVia: SIP/2.0/UDP >> 192.168.36.12:5060;received=192.168.36.12;rport=5060;branch=z9hG4bK32b724a4\r\nTo: >> ;tag=3692683275"..., len = 484} >> text = {s = 0x1
, len = 1002627336} >> __FUNCTION__ = "relay_reply" >> #5 0x00007f1c1b562406 in reply_received (p_msg=0x7f1c3be9f3b8) at >> t_reply.c:1505 >> msg_status = 500 >> last_uac_status = 100 >> branch = 0 >> reply_status = >> timer = 139758694817869 >> cancel_bitmap = 0 >> uac = 0x7f1c1d86eb10 >> t = 0x7f1c1d86e938 >> backup_list = >> has_reply_route = >> __FUNCTION__ = "reply_received" >> #6 0x0000000000458fed in forward_reply >> (msg=msg at entry=0x7f1c3be9f3b8) at forward.c:495 >> new_buf = 0x0 >> to = 0x0 >> new_len = 0 >> mod = 0x7f1c3bbf6e90 >> proto = >> id = 0 >> send_sock = >> s = >> len = >> __FUNCTION__ = "forward_reply" >> #7 0x0000000000439126 in receive_msg ( >> buf=0x858c00 "SIP/2.0 503 Service Unavailable-No >> Bandwidth Available\r\nVia: SIP/2.0/UDP >> 141.170.9.157:5060;branch=z9hG4bK817f.88c248e3.0\r\nTo: >> ;tag=3692683275-7994\r\nFrom: >> , >> rcv_info=rcv_info at entry=0x7ffc05c6ee60, >> existing_context=existing_context at entry=0x0) at receive.c:257 >> ctx = 0x7f1c3be8f3d0 >> msg = 0x7f1c3be9f3b8 >> start = {tv_sec = 50509, tv_usec = 139758636819258} >> rc = 3 >> in_buff = { >> s = 0x7f1c3be92b40 "SIP/2.0 500 Service Unavailable-No >> Bandwidth Available\r\nVia: SIP/2.0/UDP >> 141.170.9.157:5060;branch=z9hG4bK817f.88c248e3.0\r\nTo: >> ;tag=3692683275-7994\r\nFrom: >> > __FUNCTION__ = "receive_msg" >> #8 0x00000000005b0b13 in udp_read_req (si=, >> bytes_read=) at net/proto_udp/proto_udp.c:192 >> ri = {src_ip = {af = 2, len = 4, u = {addrl = >> {139759486345069, 0}, addr32 = {1250533229, 32540, 0, 0}, addr16 = >> {40813, 19081, 32540, 0, 0, 0, 0, 0}, addr = >> "m\237\211J\034\177\000\000\000\000\000\000\000\000\000"}}, dst_ip = { >> af = 2, len = 4, u = {addrl = {1378134208, 0}, addr32 = >> {1378134208, 0, 0, 0}, addr16 = {43200, 21028, 0, 0, 0, 0, 0, 0}, >> addr = "\300\250$R", '\000' }}, src_port = 5060, >> dst_port = 5060, proto = 1, >> proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = >> {sa_family = 2, sa_data = >> "\023\304m\237\211J\000\000\000\000\000\000\000"}, sin = {sin_family >> = 2, sin_port = 50195, sin_addr = {s_addr = 1250533229}, >> sin_zero = "\000\000\000\000\000\000\000"}, sin6 = >> {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 1250533229, >> sin6_addr = {__in6_u = {__u6_addr8 = >> "\000\000\000\000\000\000\000\000\001\000\000\000\000\000\000", >> __u6_addr16 = {0, 0, 0, 0, 1, 0, 0, 0}, __u6_addr32 >> = {0, 0, 1, 0}}}, sin6_scope_id = 4851503}}, bind_address = >> 0x7f1c3bbf6720} >> len = >> buf = "SIP/2.0 503 Service Unavailable-No Bandwidth >> Available\r\nVia: SIP/2.0/UDP >> 141.170.9.157:5060;branch=z9hG4bK817f.88c248e3.0\r\nTo: >> ;tag=3692683275-7994\r\nFrom: >> > fromlen = 16 >> p = >> msg = { >> s = 0x858c00 "SIP/2.0 503 Service Unavailable-No >> Bandwidth Available\r\nVia: SIP/2.0/UDP >> 141.170.9.157:5060;branch=z9hG4bK817f.88c248e3.0\r\nTo: >> ;tag=3692683275-7994\r\nFrom: >> > __FUNCTION__ = "udp_read_req" >> #9 0x000000000059a420 in handle_io (idx=, >> event_type=, fm=) at net/net_udp.c:259 >> read = 1023068896 >> fm = >> #10 io_wait_loop_epoll (h=, t=, >> repeat=) at net/../io_wait_loop.h:225 >> ret = >> e = >> n = 1 >> r = 0 >> #11 udp_rcv_loop (si=si at entry=0x7f1c3bbf6720) at net/net_udp.c:308 >> __FUNCTION__ = "udp_rcv_loop" >> #12 0x000000000059b948 in udp_start_processes >> (chd_rank=chd_rank at entry=0x8457a0 , >> startup_done=startup_done at entry=0x0) at net/net_udp.c:372 >> si = 0x7f1c3bbf6720 >> load_p = 0x7f1c1bee92e8 >> pid = >> i = >> __FUNCTION__ = "udp_start_processes" >> #13 0x0000000000419f50 in main_loop () at main.c:671 >> startup_done = 0x0 >> chd_rank = 3 >> #14 main (argc=, argv=) at main.c:1261 >> cfg_stream = >> c = >> r = >> tmp = 0x7ffc05c70f66 "" >> tmp_len = >> port = >> proto = >> protos_no = >> options = 0x5df1d0 "f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:" >> ret = -1 >> seed = 1763847833 >> rfd = >> __FUNCTION__ = "main" >> > > -- Richard Robson Greenlight Support 01382 843843 support at greenlightcrm.com From goup2010 at gmail.com Mon Jan 16 08:41:23 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Mon, 16 Jan 2017 15:41:23 +0200 Subject: [OpenSIPS-Users] Problem with switch .. case In-Reply-To: <21fd7f81-c85a-f19d-a6eb-f289ee393301@opensips.org> References: <21fd7f81-c85a-f19d-a6eb-f289ee393301@opensips.org> Message-ID: When delete xlog after the radius all working fine! Thanks! 2017-01-16 13:08 GMT+02:00 Răzvan Crainea : > The $rc in the switch is the return value of xlog(), which probably is > success. > Just remove the xlog after the radius_send_auth(), or store the $rc in a > variable and test that variable. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutionswww.opensips-solutions.com > > On 01/16/2017 12:24 PM, Dragomir Haralambiev wrote: > > Hello, > > I see problem when using switch .. case. > Opensips version 2.2.2. > > Here is part of my script: > > radius_send_auth("out","in"); > xlog("L_ERR", "Radius return $rc"); > switch ($rc) { > case -1: > xlog("L_ERR", "ERROR during authentication"); > sl_reply_error(); > exit; > case -2: > xlog("L_ERR", "Authentication denied"); > sl_reply_error(); > exit; > } # end switch > xlog("L_ERR", "Continue ...."); > > This is results: > Jan 16 10:16:55 sbc-01 /usr/sbin/opensips[7820]: Radius return -1 > Jan 16 10:16:55 sbc-01 /usr/sbin/opensips[7820]: Continue .... > > Best regards, > Dragomir > > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From miha at softnet.si Mon Jan 16 09:05:07 2017 From: miha at softnet.si (Miha) Date: Mon, 16 Jan 2017 15:05:07 +0100 Subject: [OpenSIPS-Users] radius accounting, Acct-Status-Type = 0 Message-ID: Hello how can i define that for 486/busy opensips will send Acct-Status-Type = 2 to radius server? Acct-Status-Type = 0 it not like standard thing and it should not be send :) I imported dictinary.opensips and .sip. tnx miha -------------- next part -------------- An HTML attachment was scrubbed... URL: From liviu at opensips.org Mon Jan 16 09:50:58 2017 From: liviu at opensips.org (Liviu Chircu) Date: Mon, 16 Jan 2017 16:50:58 +0200 Subject: [OpenSIPS-Users] Binary replication errors In-Reply-To: References: Message-ID: Hi, Schneur! Thanks for the feedback! Answers inline: > I removed the modparam("dialog", "replicate_profiles_to", 1) and the > modparam("dialog", "accept_replicated_profiles", 1) (which was in my > script but forgot to paste it in previous post) and now it works. > > Seems like its a old problem, when I had the profile replication I was > getting "WARNING:dialog:receive_prof_binary_packet: bad packet type" > Liviu was aware of it > (https://github.com/OpenSIPS/opensips/issues/938) , but I still have > issues in latest build. That's exactly the case. 2.3-dev already has this issue fixed, but a backport for 2.2 and below is still pending. > I wonder why the old replication methods were removed and replaced > with a module thats still in Alpha (clusterer) ????? The 2.2 "clusterer" is just a node centralizer, allowing you to provision/group/refer your nodes easier. It's quite safe to use, and bug-free. > The documentation of clusterer and replication is also outdated, for > example opensips does not recognize the parameter persistent_mode > which is supposed to work according to the docs. also the binary > replication docs for 2.2 still tells you to use bin_listen which has > been replaced with listen=bin, it also tells you to use bin_children > which was phased out as, see the following link. > https://www.opensips.org/Documentation/Interface-Binary-2-2 Will get those fixed asap. Regards, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com From ahmedmunir007 at gmail.com Mon Jan 16 09:51:13 2017 From: ahmedmunir007 at gmail.com (Ahmed Munir) Date: Mon, 16 Jan 2017 09:51:13 -0500 Subject: [OpenSIPS-Users] OpenSIPs crashed Message-ID: See details below; [root at qorblpsisprxyd1 ~]# opensips -V version: opensips 2.2.2 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_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_lt, epoll_et, sigio_rt, select. main.c compiled on 11:09:47 Jan 13 2017 with gcc 4.4.7 [root at qorblpsisprxyd1 ~]# opensipsctl ps Process:: ID=0 PID=8269 Type=attendant Process:: ID=1 PID=8271 Type=MI FIFO Process:: ID=2 PID=8272 Type=time_keeper Process:: ID=3 PID=8274 Type=timer Process:: ID=4 PID=8275 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=5 PID=8278 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=6 PID=8279 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=7 PID=8281 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=8 PID=8283 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=9 PID=8285 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=10 PID=8287 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=11 PID=8289 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=12 PID=8291 Type=Timer handler [root at qorblpsisprxyd1 ~]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel CPU family: 6 Model: 44 Stepping: 2 CPU MHz: 1197.000 BogoMIPS: 4266.58 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 8192K NUMA node0 CPU(s): 0-3 NUMA node1 CPU(s): 4-7 In /etc/default/opensips config, declaring shared and pkg memory as server memory is 64 GB; # Amount of shared memory to allocate for the running OpenSIPS server (in Mb) S_MEMORY=256 # Amount of pkg memory to allocate for the running OpenSIPS server (in Mb) P_MEMORY=32 Let me know any other info needed from my end. Date: Mon, 16 Jan 2017 10:49:37 +0200 > From: Răzvan Crainea > To: users at lists.opensips.org > Subject: Re: [OpenSIPS-Users] OpenSIPs crashed > Message-ID: <1584806e-a154-a5ad-a464-4eef609158f4 at opensips.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi, Ahmed! > > Can you tell us exactly what revision of OpenSIPS you are using? Please > provide the output of the following commands: > opensips -V > opensipsctl ps > > Also, during startup, is there a process who's "eating" a lot of CPU? If > so, can you pinpoint the PID to see what type of process is that? > > Regarding the avp_db_query() issue, did you define a db_url parameter > for it? Also I am not sure you can do something like $var(res) = > avp_db_query(...). But anyways, this is something completely different, > so please open a different topic for it. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > > On 01/14/2017 12:24 AM, Ahmed Munir wrote: > > Hi, > > > > I've just installed new version of opensips 2.2.2 on the test box and > > updated by routing script, the issue currently I'm seeing alot warning > > messages while starting opensips service below; > > > > /usr/sbin/opensips[6902]: WARNING:core:handle_timer_job: utimer job > > has a 2830000 us delay in execution > > > > Number of children running on that server is 8 as it is 8 core processor. > > > > I would like to know what steps do I need to take to fix this issue. > > Btw, warnings only occurred during the time of starting opensips > > service but not during calls. > > > > > > Further added, a issue I face using avp_db_query () function i.e. when > > using it as > > > > $var(res) = avp_db_query("SELECT Outpulse_number,setid FROM > > Prefix_data where Program_prefix = $var(pg_prefix)", "$avp(outpluse), > > $avp(trunkid)"); > > > > failed to start opensips service due to errors below; > > > > ERROR:avpops:__fixup_db_query_avp: no db url defined to be used by > > this function > > ERROR:core:fix_actions: fixing failed (code=-6) at > > //etc/opensips/opensips.cfg:207 > > CRITICAL:core:fix_expr: fix_actions error > > ERROR:core:main: failed to fix configuration with err code -6 > > > > > > If I add this line: avp_db_query("SELECT 1"); above to my $var(res) db > > query, opensips service starts successfully. > > > > Please advise the steps do I need to take to fix above issues. > > > > > > > > -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahmedmunir007 at gmail.com Mon Jan 16 10:20:28 2017 From: ahmedmunir007 at gmail.com (Ahmed Munir) Date: Mon, 16 Jan 2017 10:20:28 -0500 Subject: [OpenSIPS-Users] Issues with avp_db_query in opensips 2.2.2 Message-ID: Hi, I've currently upgraded opensips from 1.8.8 to 2.2.2. The issue currently facing after upgrade as getting error messages and failed to start to opensips service when using avp_db_query () function like; $var(res) = avp_db_query("SELECT Outpulse_number,setid FROM Prefix_data where Program_prefix = $var(pg_prefix)", "$avp(outpluse), $avp(trunkid)"); Errors below; ERROR:avpops:__fixup_db_query_avp: no db url defined to be used by this function ERROR:core:fix_actions: fixing failed (code=-6) at //etc/opensips/opensips.cfg:207 CRITICAL:core:fix_expr: fix_actions error ERROR:core:main: failed to fix configuration with err code -6 Whereas, variable $var(res) is storing return code after executing DB query. If I add this line: avp_db_query("SELECT 1"); above to my $var(res) db query, opensips service starts successfully and don't see the errors. Please advise the steps do I need to take to fix above issues. BTW, declared avpops 'db_url' in module parameters. modparam("dispatcher|avpops","db_url","mysql://opensips:opensipsrw at localhost /opensips") -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ionutionita at opensips.org Mon Jan 16 10:45:14 2017 From: ionutionita at opensips.org (Ionut Ionita) Date: Mon, 16 Jan 2017 17:45:14 +0200 Subject: [OpenSIPS-Users] radius accounting, Acct-Status-Type = 0 In-Reply-To: References: Message-ID: Hi Miha, Can you set in your radius dictionary file where the *Acct-Status-Type* values are defined VALUE Acct-Status-Type Start› › › 1 VALUE Acct-Status-Type Stop› › › 2 VALUE Acct-Status-Type Alive› › › 3 VALUE Acct-Status-Type Accounting-On› › 7 VALUE Acct-Status-Type Accounting-Off› › 8 the following line, just below the others: VALUE Acct-Status-Type Failed 4 and then check if you'll see *4 *instead of *0* for *Acct-Status-Type*? It seems that opensips it's using a value that's not in the radius dictionary, *Failed* value. Ionut Ionita OpenSIPS Developer On 01/16/2017 04:05 PM, Miha wrote: > Hello > > how can i define that for 486/busy opensips will send Acct-Status-Type > = 2 to radius server? > Acct-Status-Type = 0 it not like standard thing and it should not be > send :) > > > I imported dictinary.opensips and .sip. > > > tnx > miha > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Mon Jan 16 10:55:12 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Mon, 16 Jan 2017 17:55:12 +0200 Subject: [OpenSIPS-Users] Issues with avp_db_query in opensips 2.2.2 In-Reply-To: References: Message-ID: Hi Ahmed, Instead of modparam("dispatcher|avpops","db_url","mysql://opensips:opensipsrw at localhost/opensips") try: modparam("dispatcher","db_url","mysql://opensips:opensipsrw at localhost/opensips") modparam("avpops","db_url","mysql://opensips:opensipsrw at localhost/opensips") Let me know if this fixed the problem. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/16/2017 05:20 PM, Ahmed Munir wrote: > Hi, > > I've currently upgraded opensips from 1.8.8 to 2.2.2. The issue > currently facing after upgrade as getting error messages and failed to > start to opensips service when using avp_db_query () function like; > > $var(res) = avp_db_query("SELECT Outpulse_number,setid FROM > Prefix_data where Program_prefix = $var(pg_prefix)", "$avp(outpluse), > $avp(trunkid)"); > > Errors below; > > ERROR:avpops:__fixup_db_query_avp: no db url defined to be used by > this function > ERROR:core:fix_actions: fixing failed (code=-6) at > //etc/opensips/opensips.cfg:207 > CRITICAL:core:fix_expr: fix_actions error > ERROR:core:main: failed to fix configuration with err code -6 > > > Whereas, variable $var(res) is storing return code after executing DB > query. > > If I add this line: avp_db_query("SELECT 1"); above to my $var(res) db > query, opensips service starts successfully and don't see the errors. > > Please advise the steps do I need to take to fix above issues. > > BTW, declared avpops 'db_url' in module parameters. > > modparam("dispatcher|avpops","db_url","mysql://opensips:opensipsrw at localhost/opensips") > > -- > Regards, > > Ahmed Munir Chohan > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From liviu at opensips.org Mon Jan 16 11:39:07 2017 From: liviu at opensips.org (Liviu Chircu) Date: Mon, 16 Jan 2017 18:39:07 +0200 Subject: [OpenSIPS-Users] Issues with avp_db_query in opensips 2.2.2 In-Reply-To: References: Message-ID: Hi, Ahmed! You actually found a script syntax bug. Here is a workaround for it, until a fix is available: avp_db_query("SELECT Outpulse_number,setid FROM Prefix_data where Program_prefix = $var(pg_prefix)", "$avp(outpluse),$avp(trunkid)"); $var(res) = $retcode; # or you can just use $retcode! You may track the progress for this issue here [1]. Regards, [1]: https://github.com/OpenSIPS/opensips/issues/1022 Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 16.01.2017 17:20, Ahmed Munir wrote: > Hi, > > I've currently upgraded opensips from 1.8.8 to 2.2.2. The issue > currently facing after upgrade as getting error messages and failed to > start to opensips service when using avp_db_query () function like; > > $var(res) = avp_db_query("SELECT Outpulse_number,setid FROM > Prefix_data where Program_prefix = $var(pg_prefix)", "$avp(outpluse), > $avp(trunkid)"); > > Errors below; > > ERROR:avpops:__fixup_db_query_avp: no db url defined to be used by > this function > ERROR:core:fix_actions: fixing failed (code=-6) at > //etc/opensips/opensips.cfg:207 > CRITICAL:core:fix_expr: fix_actions error > ERROR:core:main: failed to fix configuration with err code -6 > > > Whereas, variable $var(res) is storing return code after executing DB > query. > > If I add this line: avp_db_query("SELECT 1"); above to my $var(res) db > query, opensips service starts successfully and don't see the errors. > > Please advise the steps do I need to take to fix above issues. > > BTW, declared avpops 'db_url' in module parameters. > > modparam("dispatcher|avpops","db_url","mysql://opensips:opensipsrw at localhost/opensips") > > -- > Regards, > > Ahmed Munir Chohan > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at nevian.org Mon Jan 16 16:21:17 2017 From: me at nevian.org (Serge S. Yuriev) Date: Tue, 17 Jan 2017 00:21:17 +0300 Subject: [OpenSIPS-Users] Introducing OpenSIPS 2.3 In-Reply-To: <99435f67-d572-ce75-531a-a5588935aa1d@opensips.org> References: <99435f67-d572-ce75-531a-a5588935aa1d@opensips.org> Message-ID: <619581484601677@web36j.yandex.ru> An HTML attachment was scrubbed... URL: From nabeelshikder at gmail.com Mon Jan 16 16:40:15 2017 From: nabeelshikder at gmail.com (Nabeel) Date: Mon, 16 Jan 2017 21:40:15 +0000 Subject: [OpenSIPS-Users] Introducing OpenSIPS 2.3 In-Reply-To: <99435f67-d572-ce75-531a-a5588935aa1d@opensips.org> References: <99435f67-d572-ce75-531a-a5588935aa1d@opensips.org> Message-ID: Hi, I run an ejabberd server for xmpp as well as OpenSIPS for SIP and was wondering if these two could be integrated in any way in the future. These servers run concurrently but they are completely independent of each other, although for the same user base. Nabeel On 12 Jan 2017 4:48 p.m., "Bogdan-Andrei Iancu" wrote: > A new year has arrived, so it is the time for a new OpenSIPS major > release – for OpenSIPS version 2.3 . > > For this version, the main focus on development is the *“integration”*, > the integration of OpenSIPS with various external entities. Why is > integration so important to end up being the main tag of a major release? > Well, everybody in the VoIP world is operating VoIP platforms/systems – and > these are more than SIP Engines (as OpenSIPS is). Indeed, the SIP Engine > is the core and most important part of the platform, but to build something > usable and useful, you need additional components into your platform like > CDR/billing engines, monitoring and tracing tools, data backends, non-SIP > trunking or more specialized SIP engines. Shortly you need your SIP Engine ( > OpenSIPS, of course) to be able to easily integrate with all these > components. > > OpenSIPS 2.3 brings some new and exciting integration capabilities, that > will definitely boost the value of your SIP platform: > > - extended Homer/SIPCapture integration to > allow capturing of non-SIP data (transport level data, Management Interface > commands, REST queries and more); > - SIP-I support both in terms of passing-through and in terms of > converting SIP-I to SIP and vice-versa ; > - CGRates integration for powerful > rating/billing – everything in a simple and automatic way (via a dedicated > module); > - FreeSWITCH flavored Load-Balancing for a > more realistic and accurate traffic balancing over FreeSWITCH clusters (as > the load information is fetched in realtime from FreeSWITCH); > - the Event Engine > to provide > support for scenarios based on Subscribe/Notify model, where the script > execution may subscribe and resume later according to certain events (like > a dynamic implementation of the Push Notification mechanism); > - extended RabbitMQ support for custom and > flexible data injection directly from OpenSIPS script; > - extended Asynchronous support for more complex async scenarios (like > launch with no wait); > - more end-device integration (special SIP extensions). > > The timeline for OpenSIPS 2.3 is: > > - Beta Release – 13-17 March 2017 > - Stable Release – 24-28 April 2017 > - General Availability – 2nd of May 2017, during OpenSIPS Summit > > > To talk more about the features of this new release, a public audio > conference will be available on 19th > of January 2017, 4 pm GMT > , thanks to > the kind sponsorship of UberConference . > Anyone is welcome to join to find out more details or to ask questions about > OpenSIPS 2.3 . > > This is a public and open conference, so no registration is needed, but if > you want to announce your intention to participate, please let us know via the > form on the blog post > . > > Best regards, > > -- > Bogdan-Andrei Iancu > OpenSIPS Founder and Developerhttp://www.opensips-solutions.com > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Mon Jan 16 17:31:39 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Mon, 16 Jan 2017 22:31:39 +0000 Subject: [OpenSIPS-Users] opensips $Revision: 4448 $ In-Reply-To: <1478d69f-45f2-9d84-805c-b5bc7f0d547d@opensips.org> References: <5049c51f-931a-ea24-54ae-a1dfeb6fb7a9@opensips.org> <6b622d0c-ec7c-3cc3-56be-8a6425821390@opensips.org> <1478d69f-45f2-9d84-805c-b5bc7f0d547d@opensips.org> Message-ID: I confirm, your suggestion works perfect : failure_route[GW_FAILOVER] { if (t_was_cancelled()) { exit; } # detect failure and redirect to next available GW if (t_check_status("(408)|488|([56][0-9][0-9])")) { xlog("Failed GW $rd detected \n"); if ( use_next_gw() ) { t_on_failure("GW_FAILOVER"); *do_accounting("db|log","failed|missed",);* t_relay(); exit; } send_reply("500","All GW are down"); } } On Mon, Jan 16, 2017 at 11:35 AM, Răzvan Crainea wrote: > Yes, please try that. To be honest, I've never done it using the new > accounting module, but this might do the trick. > Also, did you take a look at the multi-legging accounting? > > Best regards, > > Răzvan Crainea > OpenSIPS Solutionswww.opensips-solutions.com > > On 01/16/2017 01:18 PM, Khalil Khamlichi wrote: > > Oki, I will modify my old failure_route : > > > failure_route[GW_FAILOVER] { > > if (t_was_cancelled()) { > exit; > } > > # detect failure and redirect to next available GW > if (t_check_status("(408)|488|([56][0-9][0-9])")) { > #xlog("Failed GW $rd detected \n"); > > if ( use_next_gw() ) { > t_on_failure("GW_FAILOVER"); > t_relay(); > exit; > } > > send_reply("500","All GW are down"); > } > } > > > to : > > > failure_route[GW_FAILOVER] { > > if (t_was_cancelled()) { > exit; > } > > # detect failure and redirect to next available GW > if (t_check_status("(408)|488|([56][0-9][0-9])")) { > xlog("Failed GW $rd detected \n"); > > if ( use_next_gw() ) { > t_on_failure("GW_FAILOVER"); > *do_accounting("db|log","failed|missed",);* > t_relay(); > exit; > } > > send_reply("500","All GW are down"); > } > } > > > right ? > > On Mon, Jan 16, 2017 at 11:07 AM, Răzvan Crainea > wrote: > >> I was asking you to call do_accounting() in failure route, for each leg. >> >> Best regards, >> >> Răzvan Crainea >> OpenSIPS Solutionswww.opensips-solutions.com >> >> On 01/16/2017 12:02 PM, Khalil Khamlichi wrote: >> >> sorry mistype, I am calling do_accounting() twice. >> >> On Mon, Jan 16, 2017 at 9:47 AM, Khalil Khamlichi < >> khamlichi.khalil at gmail.com> wrote: >> >>> thanks for your much appreciated help, >>> I am calling do_routing twice. >>> >>> Here is my actual opensips.cfg : >>> >>> route { >>> ... >>> ... >>> >>> ... >>> ... >>> if (has_totag()) { >>> # sequential request withing a dialog should >>> # take the path determined by record-routing >>> if (loose_route()) { >>> >>> # validate the sequential request against dialog >>> if ( $DLG_status!=NULL && !validate_dialog() ) { >>> xlog("In-Dialog $rm from $si (callid=$ci) >>> is not valid according to dialog\n"); >>> } >>> >>> if (is_method("BYE")) { >>> # do accounting even if the transaction >>> fails >>> do_accounting("db|log","failed|missed",); >>> } else if (is_method("INVITE")) { >>> # even if in most of the cases is >>> useless, do RR for >>> # re-INVITEs alos, as some buggy clients >>> do change route set >>> # during the dialog. >>> record_route(); >>> } >>> ... >>> ... >>> >>> ... >>> ... >>> $acc_extra(gwid)=$avp(gw_id); >>> >>> t_on_failure("GW_FAILOVER"); >>> >>> do_accounting("db|log","cdr|missed",); >>> #NAT >>> if (isbflagset(NAT)) setflag(NAT); >>> #NAT >>> route(RELAY); >>> } >>> >>> # END OF MAIN ROUTE >>> >>> >>> On Mon, Jan 16, 2017 at 8:51 AM, Răzvan Crainea >>> wrote: >>> >>>> Hi, Khalil! >>>> >>>> Did you try to call the do_accounting() function for each leg going to >>>> the next gateway? >>>> >>>> Best regards, >>>> >>>> Răzvan Crainea >>>> OpenSIPS Solutionswww.opensips-solutions.com >>>> >>>> On 01/15/2017 12:24 AM, Khalil Khamlichi wrote: >>>> >>>> Hi, >>>> I am testing opensips 2.2, 2.3 I have tried to configure acc module to >>>> save to db failed calls on drouting configuration, I have found that it >>>> does save only the first failed call (that is the first gateway) it does >>>> not save to database any other failures on second and third gateways that >>>> are tried for the call. >>>> is this the expected behavioure ? >>>> Thanks for your help. >>>> >>>> regards, >>>> kh >>>> >>>> >>>> _______________________________________________ >>>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>> >>>> _______________________________________________ Users mailing list >>>> Users at lists.opensips.org http://lists.opensips.org/cgi- >>>> bin/mailman/listinfo/users >>> >>> _______________________________________________ >> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> _______________________________________________ Users mailing list >> Users at lists.opensips.org http://lists.opensips.org/cgi- >> bin/mailman/listinfo/users > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From miha at softnet.si Tue Jan 17 02:38:21 2017 From: miha at softnet.si (Miha) Date: Tue, 17 Jan 2017 08:38:21 +0100 Subject: [OpenSIPS-Users] radius accounting, Acct-Status-Type = 0 In-Reply-To: References: Message-ID: <06dd350e-51a3-3c71-8a84-9112e0c794d5@softnet.si> Hi Ionut do I need on bouth sides or opensips side? I can see that now i get: Acct-Status-Type = Modem-Start in radius. br miha On 16/01/2017 16:45, Ionut Ionita wrote: > > Hi Miha, > > Can you set in your radius dictionary file where the > *Acct-Status-Type* values are defined > > VALUE Acct-Status-Type Start› › › 1 > VALUE Acct-Status-Type Stop› › › 2 > VALUE Acct-Status-Type Alive› › › 3 > VALUE Acct-Status-Type Accounting-On› › 7 > VALUE Acct-Status-Type Accounting-Off› › 8 > > the following line, just below the others: > > VALUE Acct-Status-Type Failed 4 > > and then check if you'll see *4 *instead of *0* for *Acct-Status-Type*? > > It seems that opensips it's using a value that's not in the radius > dictionary, *Failed* value. > > > Ionut Ionita > OpenSIPS Developer > On 01/16/2017 04:05 PM, Miha wrote: >> Hello >> >> how can i define that for 486/busy opensips will send >> Acct-Status-Type = 2 to radius server? >> Acct-Status-Type = 0 it not like standard thing and it should not be >> send :) >> >> >> I imported dictinary.opensips and .sip. >> >> >> tnx >> miha >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From trance_maniak at o2.pl Tue Jan 17 03:06:12 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Tue, 17 Jan 2017 01:06:12 -0700 (MST) Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB In-Reply-To: <62206e87-8dfd-8a30-2e00-702adfb55dbc@opensips.org> References: <1484131458652-7605514.post@n2.nabble.com> <1484133356292-7605516.post@n2.nabble.com> <9640879b-c012-4529-5e7d-57a8ea817e67@opensips.org> <1484298184907-7605547.post@n2.nabble.com> <40d4cd21-5f93-5372-c09c-04c2a3c131ad@opensips.org> <1484305764044-7605552.post@n2.nabble.com> <1484308289132-7605554.post@n2.nabble.com> <62206e87-8dfd-8a30-2e00-702adfb55dbc@opensips.org> Message-ID: <1484640372992-7605592.post@n2.nabble.com> Razvan, I've found that this conditional doesn't work: if ($rc == -2) It turned out that $rc variable is never -2, although select query(select ip from address where context_info='$fU'", "$avp(ip)"), doesn't contain any values. When I checked $rc variable its value was 1, and once it was something like 1842312...so very long digit, but it was never -2. It it possible that this value changes? -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514p7605592.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From trance_maniak at o2.pl Tue Jan 17 03:07:06 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Tue, 17 Jan 2017 01:07:06 -0700 (MST) Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <1484054601076-7605502.post@n2.nabble.com> References: <1483431205315-7605411.post@n2.nabble.com> <4fa36195-2654-2697-ebb1-e55314b58147@opensips.org> <1483448415681-7605416.post@n2.nabble.com> <586CAAD9.5060906@easycall.pl> <1483952331826-7605485.post@n2.nabble.com> <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> <1484054601076-7605502.post@n2.nabble.com> Message-ID: <1484640426055-7605593.post@n2.nabble.com> Hello, can anybody help? I need blf to work. -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605593.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From ionutionita at opensips.org Tue Jan 17 03:27:55 2017 From: ionutionita at opensips.org (Ionut Ionita) Date: Tue, 17 Jan 2017 10:27:55 +0200 Subject: [OpenSIPS-Users] radius accounting, Acct-Status-Type = 0 In-Reply-To: <06dd350e-51a3-3c71-8a84-9112e0c794d5@softnet.si> References: <06dd350e-51a3-3c71-8a84-9112e0c794d5@softnet.si> Message-ID: <8f907cea-dacd-dfa5-ad67-3613035aa825@opensips.org> No, thank you it's fine now. That value was for testing purposes only, you can remove it now. OpenSIPS it's using *Failed* value for *Acct-Status-Type* which is not defined anywhere (nor in our dictionary, nor in any RFC or somewhere else). Not finding that value results in having *0 *for *Acct-Status-Type*, the value you were seeing before. Will let you know when we'll decide how we should fix this issue. Regards, Ionut Ionita OpenSIPS Developer On 01/17/2017 09:38 AM, Miha wrote: > Hi Ionut > > do I need on bouth sides or opensips side? > > I can see that now i get: Acct-Status-Type = Modem-Start in radius. > > > br > miha > > On 16/01/2017 16:45, Ionut Ionita wrote: >> >> Hi Miha, >> >> Can you set in your radius dictionary file where the >> *Acct-Status-Type* values are defined >> >> VALUE Acct-Status-Type Start› › › 1 >> VALUE Acct-Status-Type Stop› › › 2 >> VALUE Acct-Status-Type Alive› › › 3 >> VALUE Acct-Status-Type Accounting-On› › 7 >> VALUE Acct-Status-Type Accounting-Off› › 8 >> >> the following line, just below the others: >> >> VALUE Acct-Status-Type Failed 4 >> >> and then check if you'll see *4 *instead of *0* for *Acct-Status-Type*? >> >> It seems that opensips it's using a value that's not in the radius >> dictionary, *Failed* value. >> >> >> Ionut Ionita >> OpenSIPS Developer >> On 01/16/2017 04:05 PM, Miha wrote: >>> Hello >>> >>> how can i define that for 486/busy opensips will send >>> Acct-Status-Type = 2 to radius server? >>> Acct-Status-Type = 0 it not like standard thing and it should not be >>> send :) >>> >>> >>> I imported dictinary.opensips and .sip. >>> >>> >>> tnx >>> miha >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Tue Jan 17 03:32:40 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Tue, 17 Jan 2017 10:32:40 +0200 Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB In-Reply-To: <1484640372992-7605592.post@n2.nabble.com> References: <1484131458652-7605514.post@n2.nabble.com> <1484133356292-7605516.post@n2.nabble.com> <9640879b-c012-4529-5e7d-57a8ea817e67@opensips.org> <1484298184907-7605547.post@n2.nabble.com> <40d4cd21-5f93-5372-c09c-04c2a3c131ad@opensips.org> <1484305764044-7605552.post@n2.nabble.com> <1484308289132-7605554.post@n2.nabble.com> <62206e87-8dfd-8a30-2e00-702adfb55dbc@opensips.org> <1484640372992-7605592.post@n2.nabble.com> Message-ID: That's weird. How did you check the value and you got 1842312...? I am asking because that does look like a -2, only converted to an unsigned representation, (unsigned int)-2 = 18446744073709551614). Or was it -1? Can you control the data in the database and make sure you don't have that username when doing the query? Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/17/2017 10:06 AM, maatohewetbi wrote: > Razvan, I've found that this conditional doesn't work: > > if ($rc == -2) > It turned out that $rc variable is never -2, although select query(select ip > from address where context_info='$fU'", "$avp(ip)"), doesn't contain any > values. When I checked $rc variable its value was 1, and once it was > something like 1842312...so very long digit, but it was never -2. It it > possible that this value changes? > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514p7605592.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From miha at softnet.si Tue Jan 17 03:33:28 2017 From: miha at softnet.si (Miha) Date: Tue, 17 Jan 2017 09:33:28 +0100 Subject: [OpenSIPS-Users] radius accounting, Acct-Status-Type = 0 In-Reply-To: <8f907cea-dacd-dfa5-ad67-3613035aa825@opensips.org> References: <06dd350e-51a3-3c71-8a84-9112e0c794d5@softnet.si> <8f907cea-dacd-dfa5-ad67-3613035aa825@opensips.org> Message-ID: <03e5c6b9-5d21-1d55-eb86-2dc47bcae178@softnet.si> ok, then i will use this value and on radius side i will catch it and set to internally to STOP if this is only soluton. The thing is when 486/busy comes, opensips sends this broken radius accouting request and radius server does not replay to it and that is why the opensips waits almost 40s to send back ACK on 486. Or is there any other solution? br miha On 17/01/2017 09:27, Ionut Ionita wrote: > No, thank you it's fine now. That value was for testing purposes only, > you can remove it now. > OpenSIPS it's using *Failed* value for *Acct-Status-Type* which is not > defined anywhere (nor in > our dictionary, nor in any RFC or somewhere else). Not finding that > value results in having *0 > *for *Acct-Status-Type*, the value you were seeing before. Will let > you know when we'll decide > how we should fix this issue. > > Regards, > Ionut Ionita > OpenSIPS Developer > On 01/17/2017 09:38 AM, Miha wrote: >> Hi Ionut >> >> do I need on bouth sides or opensips side? >> >> I can see that now i get: Acct-Status-Type = Modem-Start in radius. >> >> >> br >> miha >> >> On 16/01/2017 16:45, Ionut Ionita wrote: >>> >>> Hi Miha, >>> >>> Can you set in your radius dictionary file where the >>> *Acct-Status-Type* values are defined >>> >>> VALUE Acct-Status-Type Start› › › 1 >>> VALUE Acct-Status-Type Stop› › › 2 >>> VALUE Acct-Status-Type Alive› › › 3 >>> VALUE Acct-Status-Type Accounting-On› › 7 >>> VALUE Acct-Status-Type Accounting-Off› › 8 >>> >>> the following line, just below the others: >>> >>> VALUE Acct-Status-Type Failed 4 >>> >>> and then check if you'll see *4 *instead of *0* for *Acct-Status-Type*? >>> >>> It seems that opensips it's using a value that's not in the radius >>> dictionary, *Failed* value. >>> >>> >>> Ionut Ionita >>> OpenSIPS Developer >>> On 01/16/2017 04:05 PM, Miha wrote: >>>> Hello >>>> >>>> how can i define that for 486/busy opensips will send >>>> Acct-Status-Type = 2 to radius server? >>>> Acct-Status-Type = 0 it not like standard thing and it should not >>>> be send :) >>>> >>>> >>>> I imported dictinary.opensips and .sip. >>>> >>>> >>>> tnx >>>> miha >>>> >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> Users at lists.opensips.org >>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Tue Jan 17 03:36:40 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Tue, 17 Jan 2017 10:36:40 +0200 Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <1484640426055-7605593.post@n2.nabble.com> References: <1483431205315-7605411.post@n2.nabble.com> <4fa36195-2654-2697-ebb1-e55314b58147@opensips.org> <1483448415681-7605416.post@n2.nabble.com> <586CAAD9.5060906@easycall.pl> <1483952331826-7605485.post@n2.nabble.com> <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> <1484054601076-7605502.post@n2.nabble.com> <1484640426055-7605593.post@n2.nabble.com> Message-ID: <247fdfc3-93dc-c097-090e-e6faf103eaac@opensips.org> I checked your script and you are not handling publish/subscribe for sequential requests. You should try to move the route(handle_presence); call for sequential requests too. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/17/2017 10:07 AM, maatohewetbi wrote: > Hello, can anybody help? I need blf to work. > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605593.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From trance_maniak at o2.pl Tue Jan 17 03:38:32 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Tue, 17 Jan 2017 01:38:32 -0700 (MST) Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <247fdfc3-93dc-c097-090e-e6faf103eaac@opensips.org> References: <1483431205315-7605411.post@n2.nabble.com> <4fa36195-2654-2697-ebb1-e55314b58147@opensips.org> <1483448415681-7605416.post@n2.nabble.com> <586CAAD9.5060906@easycall.pl> <1483952331826-7605485.post@n2.nabble.com> <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> <1484054601076-7605502.post@n2.nabble.com> <1484640426055-7605593.post@n2.nabble.com> <247fdfc3-93dc-c097-090e-e6faf103eaac@opensips.org> Message-ID: <1484642312675-7605598.post@n2.nabble.com> Where are the sequential requests? Can You point it in my script? -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605598.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From bogdan at opensips.org Tue Jan 17 03:58:34 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 17 Jan 2017 10:58:34 +0200 Subject: [OpenSIPS-Users] Introducing OpenSIPS 2.3 In-Reply-To: References: <99435f67-d572-ce75-531a-a5588935aa1d@opensips.org> Message-ID: Hi Nabeel, Have you tried the PUA_XMPP module (presence gateway between SIP and XMPP): http://www.opensips.org/html/docs/modules/2.2.x/pua_xmpp.html Or the JABBER module: http://www.opensips.org/html/docs/modules/2.2.x/jabber.html Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/16/2017 11:40 PM, Nabeel wrote: > Hi, > > I run an ejabberd server for xmpp as well as OpenSIPS for SIP and was > wondering if these two could be integrated in any way in the future. > These servers run concurrently but they are completely independent of > each other, although for the same user base. > > Nabeel > > On 12 Jan 2017 4:48 p.m., "Bogdan-Andrei Iancu" > wrote: > > A new year has arrived, so it is the time for a new OpenSIPS major > release – forOpenSIPS version 2.3 . > > For this version, the main focus on development > is the*/“integration”/*, the integration ofOpenSIPSwith various > external entities. Why is integration so important to end up being > the main tag of a major release? Well, everybody in the VoIP world > is operating VoIP platforms/systems – and these are more than SIP > Engines (asOpenSIPSis). Indeed, the SIP Engine is the core and > most important part of the platform, but to build something usable > and useful, you need additional components into your platform like > CDR/billing engines, monitoring and tracing tools, data backends, > non-SIP trunking or more specialized SIP engines. Shortly you need > your SIP Engine (OpenSIPS, of course) to be able to easily > integrate with all these components. > > OpenSIPS2.3 brings some new and exciting integration > capabilities, that will definitely boost the value of your SIP > platform: > > * extendedHomer/SIPCapture integration > to allow capturing of non-SIP data (transport level data, > Management Interface commands, REST queries and more); > * SIP-I support both in terms of passing-through and in terms of > converting SIP-I to SIP and vice-versa ; > * CGRates integration for powerful > rating/billing – everything in a simple and automatic way (via > a dedicated module); > * FreeSWITCH flavored Load-Balancing > for a more realistic and accurate traffic balancing over > FreeSWITCH clusters (as the load information is fetched in > realtime from FreeSWITCH); > * theEvent Engine > to > provide support for scenarios based on Subscribe/Notify model, > where the script execution may subscribe and resume later > according to certain events (like a dynamic implementation of > the Push Notification mechanism); > * extendedRabbitMQ support for > custom and flexible data injection directly from OpenSIPS script; > * extended Asynchronous support for more complex async scenarios > (like launch with no wait); > * more end-device integration (special SIP extensions). > > The timeline for OpenSIPS 2.3 is: > > * Beta Release – 13-17 March 2017 > * Stable Release – 24-28 April 2017 > * General Availability – 2nd of May 2017, duringOpenSIPS Summit > > > To talk more about the features of this new release, a publicaudio > conference will be > available on19th of January 2017, 4 pm GMT > , thanks to > the kind sponsorship of UberConference > . Anyone is welcome to join to > find out more details or to ask questions aboutOpenSIPS2.3 . > > This is a public and open conference, so no registration is > needed, but if you want to announce your intention to participate, > please let us know via the form on the blog post > . > > Best regards, > > -- > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > _______________________________________________ Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From trance_maniak at o2.pl Tue Jan 17 04:03:14 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Tue, 17 Jan 2017 02:03:14 -0700 (MST) Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB In-Reply-To: References: <1484133356292-7605516.post@n2.nabble.com> <9640879b-c012-4529-5e7d-57a8ea817e67@opensips.org> <1484298184907-7605547.post@n2.nabble.com> <40d4cd21-5f93-5372-c09c-04c2a3c131ad@opensips.org> <1484305764044-7605552.post@n2.nabble.com> <1484308289132-7605554.post@n2.nabble.com> <62206e87-8dfd-8a30-2e00-702adfb55dbc@opensips.org> <1484640372992-7605592.post@n2.nabble.com> Message-ID: <1484643794782-7605600.post@n2.nabble.com> I've just did it like this: xlog("$rc"); and on Friday I got 18446744073709551615 so You were right that it was unsigned int. But now if I want to read xlog("$rc") it has 1 value. And my table is empty. Now I've changed script and it looks: if ($avp(s:ip) == null ) { xlog("no results found in DB"); xlog("$rc"); and it is ok, and works like it should, because $avp(s:ip) is NULL when there's no records found. But I'm afraid it's not the best solution. What do You think? -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514p7605600.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From bogdan at opensips.org Tue Jan 17 04:08:27 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 17 Jan 2017 11:08:27 +0200 Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <1484642312675-7605598.post@n2.nabble.com> References: <1483431205315-7605411.post@n2.nabble.com> <4fa36195-2654-2697-ebb1-e55314b58147@opensips.org> <1483448415681-7605416.post@n2.nabble.com> <586CAAD9.5060906@easycall.pl> <1483952331826-7605485.post@n2.nabble.com> <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> <1484054601076-7605502.post@n2.nabble.com> <1484640426055-7605593.post@n2.nabble.com> <247fdfc3-93dc-c097-090e-e6faf103eaac@opensips.org> <1484642312675-7605598.post@n2.nabble.com> Message-ID: Hi, It is a bit difficult to work with OpenSIPS without knowing at least the SIP basics. I suggest to follow there webinars: * Introduction to SIP : http://www.opensips.org/Documentation/Webinars#toc10 * Routing in SIP : http://www.opensips.org/Documentation/Webinars#toc12 A basic OpenSIPS script with Presence support is here: http://www.opensips.org/Documentation/Tutorials-Presence-SimplePresConfig Check the block in the "has_totag" - that is the part handling the sequential requests. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/17/2017 10:38 AM, maatohewetbi wrote: > Where are the sequential requests? Can You point it in my script? > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605598.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From trance_maniak at o2.pl Tue Jan 17 04:19:24 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Tue, 17 Jan 2017 02:19:24 -0700 (MST) Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: References: <1483448415681-7605416.post@n2.nabble.com> <586CAAD9.5060906@easycall.pl> <1483952331826-7605485.post@n2.nabble.com> <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> <1484054601076-7605502.post@n2.nabble.com> <1484640426055-7605593.post@n2.nabble.com> <247fdfc3-93dc-c097-090e-e6faf103eaac@opensips.org> <1484642312675-7605598.post@n2.nabble.com> Message-ID: <1484644764556-7605602.post@n2.nabble.com> You are right Bogdan, I forgot about these requests. Anyway, thanks for help - I will look at webinars. -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605602.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From ionutionita at opensips.org Tue Jan 17 05:06:20 2017 From: ionutionita at opensips.org (Ionut Ionita) Date: Tue, 17 Jan 2017 12:06:20 +0200 Subject: [OpenSIPS-Users] radius accounting, Acct-Status-Type = 0 In-Reply-To: <03e5c6b9-5d21-1d55-eb86-2dc47bcae178@softnet.si> References: <06dd350e-51a3-3c71-8a84-9112e0c794d5@softnet.si> <8f907cea-dacd-dfa5-ad67-3613035aa825@opensips.org> <03e5c6b9-5d21-1d55-eb86-2dc47bcae178@softnet.si> Message-ID: Hello again, Found a fix for your problem. You should use *dictionary.rfc2866* (freeradius has it). This dictionary has value defined for *Failed*. VALUE› Acct-Status-Type› › Start› › › 1 VALUE› Acct-Status-Type› › Stop› › › 2 VALUE› Acct-Status-Type› › Alive› › › 3 # dup VALUE› Acct-Status-Type› › Interim-Update› › 3 VALUE› Acct-Status-Type› › Accounting-On› › 7 VALUE› Acct-Status-Type› › Accounting-Off› › 8 VALUE› Acct-Status-Type› › Failed› › › 15 Regards, Ionut Ionita OpenSIPS Developer On 01/17/2017 10:33 AM, Miha wrote: > ok, then i will use this value and on radius side i will catch it and > set to internally to STOP if this is only soluton. > > The thing is when 486/busy comes, opensips sends this broken radius > accouting request and radius server does not replay to it and that is > why the opensips waits almost 40s to send back ACK on 486. > > > Or is there any other solution? > > > br > miha > > On 17/01/2017 09:27, Ionut Ionita wrote: >> No, thank you it's fine now. That value was for testing purposes >> only, you can remove it now. >> OpenSIPS it's using *Failed* value for *Acct-Status-Type* which is >> not defined anywhere (nor in >> our dictionary, nor in any RFC or somewhere else). Not finding that >> value results in having *0 >> *for *Acct-Status-Type*, the value you were seeing before. Will let >> you know when we'll decide >> how we should fix this issue. >> >> Regards, >> Ionut Ionita >> OpenSIPS Developer >> On 01/17/2017 09:38 AM, Miha wrote: >>> Hi Ionut >>> >>> do I need on bouth sides or opensips side? >>> >>> I can see that now i get: Acct-Status-Type = Modem-Start in radius. >>> >>> >>> br >>> miha >>> >>> On 16/01/2017 16:45, Ionut Ionita wrote: >>>> >>>> Hi Miha, >>>> >>>> Can you set in your radius dictionary file where the >>>> *Acct-Status-Type* values are defined >>>> >>>> VALUE Acct-Status-Type Start› › › 1 >>>> VALUE Acct-Status-Type Stop› › › 2 >>>> VALUE Acct-Status-Type Alive› › › 3 >>>> VALUE Acct-Status-Type Accounting-On› › 7 >>>> VALUE Acct-Status-Type Accounting-Off› › 8 >>>> >>>> the following line, just below the others: >>>> >>>> VALUE Acct-Status-Type Failed 4 >>>> >>>> and then check if you'll see *4 *instead of *0* for *Acct-Status-Type*? >>>> >>>> It seems that opensips it's using a value that's not in the radius >>>> dictionary, *Failed* value. >>>> >>>> >>>> Ionut Ionita >>>> OpenSIPS Developer >>>> On 01/16/2017 04:05 PM, Miha wrote: >>>>> Hello >>>>> >>>>> how can i define that for 486/busy opensips will send >>>>> Acct-Status-Type = 2 to radius server? >>>>> Acct-Status-Type = 0 it not like standard thing and it should not >>>>> be send :) >>>>> >>>>> >>>>> I imported dictinary.opensips and .sip. >>>>> >>>>> >>>>> tnx >>>>> miha >>>>> >>>>> >>>>> _______________________________________________ >>>>> Users mailing list >>>>> Users at lists.opensips.org >>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>> >>>> >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> Users at lists.opensips.org >>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 17 05:10:52 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 17 Jan 2017 12:10:52 +0200 Subject: [OpenSIPS-Users] opensips Crashing v2.2.2 In-Reply-To: References: <86d31aca-5635-9683-59d5-1b6412555a57@greenlightcrm.com> <270e22e1-46f3-2f8d-e44c-a4dad2b61711@greenlightcrm.com> Message-ID: <66693cbd-4204-bb53-803b-15df67bda544@opensips.org> Hi Richard, Sorry for the late reply. The backtraces show a really strange situation - some processing context getting to NULL somewhere along the handling of that 503 reply. What I suspect is that you are using in failure route some functions that are reseting this processing context - could you (off list) send me the failure route which is used for this 503 reply ? Also, when you say the carrier is responding with a shorter message - what you mean ? shorter as length ? or ? Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/16/2017 02:57 PM, Richard Robson wrote: > Hi, > > I've done some more testing and the carrier is now responding with a > shorter message, despite them saying nothing was wrong. and the > crashing isn't happening. > > Therefore I'm unable to reproduce the original error on our live system. > > I've put the node back into service and I'm monitoring the situation. > Regards, > > > Richard > > On 06/01/2017 12:19, Richard Robson wrote: >> I've some more back traces. >> >> this could be a resource problem. The back story is we want to check >> for channel limits and Rate limits for all calls. Channel limit hits >> should failover to the next gateway and rate limits should delat for >> up to 2 seconds before failing over to the next gateway. This is all >> working ok as far as I can tell. We have one provider that has 600 >> channels and cps of 25. We now have a second provider with 3 nodes of >> 100 channels and 4 cps. All nodes are being checked for Channels and >> CPS. I noticed that the failover of GW was not being checked and >> added new route to do the checking. Also to confuse things more it >> looks like one of the new carriers nodes may be incorrectly >> configured asnd we are getting failures (503 Service unavailable). >> Yesterday we were using all four gateways and no crashes, but after >> adding in the new route for the failover checking it started to crash >> this morning. the logs indicate that the failover is working correctly. >> We are checking the outbound calls twice once for the customer limits >> and then for the carrier limits. This has been fine for the last few >> days, since the system was updated ( it was only carrier limits >> checked before) >> >> i've removed the suspect node and the extra route, but I notice the >> error from the node in the backtraces with an address out of bounds >> >> I've more back traces if you require >> >> http://pastebin.com/BB9RP6rv >> http://pastebin.com/QSTbYgNQ >> http://pastebin.com/vUmQLT0k >> >> On 06/01/2017 09:30, Richard Robson wrote: >>> Hi, >>> >>> we are getting a crash in opensips. V2.2.2 >>> >>> >>> bt all: > From bogdan at opensips.org Tue Jan 17 05:28:22 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 17 Jan 2017 12:28:22 +0200 Subject: [OpenSIPS-Users] Introducing OpenSIPS 2.3 In-Reply-To: <619581484601677@web36j.yandex.ru> References: <99435f67-d572-ce75-531a-a5588935aa1d@opensips.org> <619581484601677@web36j.yandex.ru> Message-ID: Hi Serge, During the Thursday call we will present in more details all the listed features. Of course, when the corresponding code will go public (right now all of them are work in progress in different stages), the documentation will be available - all these before the beta release, of course. But once again, during the Thursday call we will present more on these feature and questions are welcome. Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/16/2017 11:21 PM, Serge S. Yuriev wrote: > Hello, > > Can we read details about these features before beta release? > Particularly I'm interested in FS and CGrates integration. > > -- > Wbr, Serge via mobile > > 12.01.2017, 19:41, "Bogdan-Andrei Iancu" : >> >> A new year has arrived, so it is the time for a new OpenSIPS major >> release – forOpenSIPS version 2.3 . >> >> For this version, the main focus on development >> is the*/“integration”/*, the integration ofOpenSIPSwith various >> external entities. Why is integration so important to end up being >> the main tag of a major release? Well, everybody in the VoIP world is >> operating VoIP platforms/systems – and these are more than SIP >> Engines (asOpenSIPSis). Indeed, the SIP Engine is the core and most >> important part of the platform, but to build something usable and >> useful, you need additional components into your platform like >> CDR/billing engines, monitoring and tracing tools, data backends, >> non-SIP trunking or more specialized SIP engines. Shortly you need >> your SIP Engine (OpenSIPS, of course) to be able to easily integrate >> with all these components. >> >> OpenSIPS2.3 brings some new and exciting integration capabilities, >> that will definitely boost the value of your SIP platform: >> >> * extendedHomer/SIPCapture integration to >> allow capturing of non-SIP data (transport level data, Management >> Interface commands, REST queries and more); >> * SIP-I support both in terms of passing-through and in terms of >> converting SIP-I to SIP and vice-versa ; >> * CGRates integration for powerful >> rating/billing – everything in a simple and automatic way (via a >> dedicated module); >> * FreeSWITCH flavored Load-Balancing for >> a more realistic and accurate traffic balancing over FreeSWITCH >> clusters (as the load information is fetched in realtime from >> FreeSWITCH); >> * theEvent Engine >> to >> provide support for scenarios based on Subscribe/Notify model, >> where the script execution may subscribe and resume later >> according to certain events (like a dynamic implementation of the >> Push Notification mechanism); >> * extendedRabbitMQ support for custom >> and flexible data injection directly from OpenSIPS script; >> * extended Asynchronous support for more complex async scenarios >> (like launch with no wait); >> * more end-device integration (special SIP extensions). >> >> The timeline for OpenSIPS 2.3 is: >> >> * Beta Release – 13-17 March 2017 >> * Stable Release – 24-28 April 2017 >> * General Availability – 2nd of May 2017, duringOpenSIPS Summit >> >> >> To talk more about the features of this new release, a publicaudio >> conference will be >> available on19th of January 2017, 4 pm GMT >> , thanks to >> the kind sponsorship of UberConference >> . Anyone is welcome to join to find >> out more details or to ask questions aboutOpenSIPS2.3 . >> >> This is a public and open conference, so no registration is needed, >> but if you want to announce your intention to participate, please let >> us know via the form on the blog post >> . >> >> Best regards, >> >> -- >> Bogdan-Andrei Iancu >> OpenSIPS Founder and Developer >> http://www.opensips-solutions.com >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From ionutionita at opensips.org Tue Jan 17 06:30:59 2017 From: ionutionita at opensips.org (Ionut Ionita) Date: Tue, 17 Jan 2017 13:30:59 +0200 Subject: [OpenSIPS-Users] radius accounting, Acct-Status-Type = 0 In-Reply-To: References: <06dd350e-51a3-3c71-8a84-9112e0c794d5@softnet.si> <8f907cea-dacd-dfa5-ad67-3613035aa825@opensips.org> <03e5c6b9-5d21-1d55-eb86-2dc47bcae178@softnet.si> Message-ID: Also if you'll check latest commit in master[0], modified radius code to throw error and not start if any attribute/ value/vendor is not found in order to not get to similar situations in the future. Backported the commit back to 2.1. [0] https://github.com/OpenSIPS/opensips/commit/75573b41c5453b495a3fa9ad1bdf2df3ee0f4c2f Regards, Ionut Ionita OpenSIPS Developer On 01/17/2017 12:06 PM, Ionut Ionita wrote: > Hello again, > > Found a fix for your problem. You should use *dictionary.rfc2866* > (freeradius has it). This dictionary has value defined > for *Failed*. > > VALUE› Acct-Status-Type› › Start› › › 1 > VALUE› Acct-Status-Type› › Stop› › › 2 > VALUE› Acct-Status-Type› › Alive› › › 3 # dup > VALUE› Acct-Status-Type› › Interim-Update› › 3 > VALUE› Acct-Status-Type› › Accounting-On› › 7 > VALUE› Acct-Status-Type› › Accounting-Off› › 8 > VALUE› Acct-Status-Type› › Failed› › › 15 > > > Regards, > > Ionut Ionita > OpenSIPS Developer > On 01/17/2017 10:33 AM, Miha wrote: >> ok, then i will use this value and on radius side i will catch it and >> set to internally to STOP if this is only soluton. >> >> The thing is when 486/busy comes, opensips sends this broken radius >> accouting request and radius server does not replay to it and that is >> why the opensips waits almost 40s to send back ACK on 486. >> >> >> Or is there any other solution? >> >> >> br >> miha >> >> On 17/01/2017 09:27, Ionut Ionita wrote: >>> No, thank you it's fine now. That value was for testing purposes >>> only, you can remove it now. >>> OpenSIPS it's using *Failed* value for *Acct-Status-Type* which is >>> not defined anywhere (nor in >>> our dictionary, nor in any RFC or somewhere else). Not finding that >>> value results in having *0 >>> *for *Acct-Status-Type*, the value you were seeing before. Will let >>> you know when we'll decide >>> how we should fix this issue. >>> >>> Regards, >>> Ionut Ionita >>> OpenSIPS Developer >>> On 01/17/2017 09:38 AM, Miha wrote: >>>> Hi Ionut >>>> >>>> do I need on bouth sides or opensips side? >>>> >>>> I can see that now i get: Acct-Status-Type = Modem-Start in radius. >>>> >>>> >>>> br >>>> miha >>>> >>>> On 16/01/2017 16:45, Ionut Ionita wrote: >>>>> >>>>> Hi Miha, >>>>> >>>>> Can you set in your radius dictionary file where the >>>>> *Acct-Status-Type* values are defined >>>>> >>>>> VALUE Acct-Status-Type Start› › › 1 >>>>> VALUE Acct-Status-Type Stop› › › 2 >>>>> VALUE Acct-Status-Type Alive› › › 3 >>>>> VALUE Acct-Status-Type Accounting-On› › 7 >>>>> VALUE Acct-Status-Type Accounting-Off› › 8 >>>>> >>>>> the following line, just below the others: >>>>> >>>>> VALUE Acct-Status-Type Failed 4 >>>>> >>>>> and then check if you'll see *4 *instead of *0* for >>>>> *Acct-Status-Type*? >>>>> >>>>> It seems that opensips it's using a value that's not in the radius >>>>> dictionary, *Failed* value. >>>>> >>>>> >>>>> Ionut Ionita >>>>> OpenSIPS Developer >>>>> On 01/16/2017 04:05 PM, Miha wrote: >>>>>> Hello >>>>>> >>>>>> how can i define that for 486/busy opensips will send >>>>>> Acct-Status-Type = 2 to radius server? >>>>>> Acct-Status-Type = 0 it not like standard thing and it should not >>>>>> be send :) >>>>>> >>>>>> >>>>>> I imported dictinary.opensips and .sip. >>>>>> >>>>>> >>>>>> tnx >>>>>> miha >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Users mailing list >>>>>> Users at lists.opensips.org >>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Users mailing list >>>>> Users at lists.opensips.org >>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>> >>>> >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> Users at lists.opensips.org >>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From donguyenha at gmail.com Tue Jan 17 06:47:52 2017 From: donguyenha at gmail.com (Do Nguyen Ha) Date: Tue, 17 Jan 2017 18:47:52 +0700 Subject: [OpenSIPS-Users] Introducing OpenSIPS 2.3 In-Reply-To: References: <99435f67-d572-ce75-531a-a5588935aa1d@opensips.org> <619581484601677@web36j.yandex.ru> Message-ID: is there also present the call center module. I didn't see the call center tutorial on opensips website or opensips blog website On Jan 17, 2017 17:33, "Bogdan-Andrei Iancu" wrote: > Hi Serge, > > During the Thursday call we will present in more details all the listed > features. Of course, when the corresponding code will go public (right now > all of them are work in progress in different stages), the documentation > will be available - all these before the beta release, of course. > > But once again, during the Thursday call we will present more on these > feature and questions are welcome. > > Best regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developerhttp://www.opensips-solutions.com > > On 01/16/2017 11:21 PM, Serge S. Yuriev wrote: > > Hello, > > Can we read details about these features before beta release? > Particularly I'm interested in FS and CGrates integration. > > -- > Wbr, Serge via mobile > > 12.01.2017, 19:41, "Bogdan-Andrei Iancu" > : > > A new year has arrived, so it is the time for a new OpenSIPS major > release – for OpenSIPS version 2.3 . > > For this version, the main focus on development is the *“integration”*, > the integration of OpenSIPS with various external entities. Why is > integration so important to end up being the main tag of a major release? > Well, everybody in the VoIP world is operating VoIP platforms/systems – and > these are more than SIP Engines (as OpenSIPS is). Indeed, the SIP Engine > is the core and most important part of the platform, but to build something > usable and useful, you need additional components into your platform like > CDR/billing engines, monitoring and tracing tools, data backends, non-SIP > trunking or more specialized SIP engines. Shortly you need your SIP Engine ( > OpenSIPS, of course) to be able to easily integrate with all these > components. > > OpenSIPS 2.3 brings some new and exciting integration capabilities, that > will definitely boost the value of your SIP platform: > > - extended Homer/SIPCapture integration to > allow capturing of non-SIP data (transport level data, Management Interface > commands, REST queries and more); > - SIP-I support both in terms of passing-through and in terms of > converting SIP-I to SIP and vice-versa ; > - CGRates integration for powerful > rating/billing – everything in a simple and automatic way (via a dedicated > module); > - FreeSWITCH flavored Load-Balancing for a > more realistic and accurate traffic balancing over FreeSWITCH clusters (as > the load information is fetched in realtime from FreeSWITCH); > - the Event Engine > to provide > support for scenarios based on Subscribe/Notify model, where the script > execution may subscribe and resume later according to certain events (like > a dynamic implementation of the Push Notification mechanism); > - extended RabbitMQ support for custom and > flexible data injection directly from OpenSIPS script; > - extended Asynchronous support for more complex async scenarios (like > launch with no wait); > - more end-device integration (special SIP extensions). > > The timeline for OpenSIPS 2.3 is: > > - Beta Release – 13-17 March 2017 > - Stable Release – 24-28 April 2017 > - General Availability – 2nd of May 2017, during OpenSIPS Summit > > > To talk more about the features of this new release, a public audio > conference will be available on 19th > of January 2017, 4 pm GMT > , thanks to > the kind sponsorship of UberConference . > Anyone is welcome to join to find out more details or to ask questions about > OpenSIPS 2.3 . > > This is a public and open conference, so no registration is needed, but if > you want to announce your intention to participate, please let us know via the > form on the blog post > . > > Best regards, > > -- > Bogdan-Andrei Iancu > OpenSIPS Founder and Developerhttp://www.opensips-solutions.com > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 17 07:19:09 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 17 Jan 2017 14:19:09 +0200 Subject: [OpenSIPS-Users] Introducing OpenSIPS 2.3 In-Reply-To: References: <99435f67-d572-ce75-531a-a5588935aa1d@opensips.org> <619581484601677@web36j.yandex.ru> Message-ID: Hi, The Call Center module was released long time ago, it is not something new in 2.3 . Indeed, there is no tutorial on it, just the README...for the moment. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/17/2017 01:47 PM, Do Nguyen Ha wrote: > is there also present the call center module. I didn't see the call > center tutorial on opensips website or opensips blog website > > On Jan 17, 2017 17:33, "Bogdan-Andrei Iancu" > wrote: > > Hi Serge, > > During the Thursday call we will present in more details all the > listed features. Of course, when the corresponding code will go > public (right now all of them are work in progress in different > stages), the documentation will be available - all these before > the beta release, of course. > > But once again, during the Thursday call we will present more on > these feature and questions are welcome. > > Best regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 01/16/2017 11:21 PM, Serge S. Yuriev wrote: >> Hello, >> Can we read details about these features before beta release? >> Particularly I'm interested in FS and CGrates integration. -- >> Wbr, Serge via mobile 12.01.2017, 19:41, "Bogdan-Andrei Iancu" >> : >>> >>> A new year has arrived, so it is the time for a new OpenSIPS >>> major release – forOpenSIPS version 2.3 . >>> >>> For this version, the main focus on development >>> is the*/“integration”/*, the integration ofOpenSIPSwith various >>> external entities. Why is integration so important to end up >>> being the main tag of a major release? Well, everybody in the >>> VoIP world is operating VoIP platforms/systems – and these are >>> more than SIP Engines (asOpenSIPSis). Indeed, the SIP Engine is >>> the core and most important part of the platform, but to build >>> something usable and useful, you need additional components into >>> your platform like CDR/billing engines, monitoring and tracing >>> tools, data backends, non-SIP trunking or more specialized SIP >>> engines. Shortly you need your SIP Engine (OpenSIPS, of course) >>> to be able to easily integrate with all these components. >>> >>> OpenSIPS2.3 brings some new and exciting integration >>> capabilities, that will definitely boost the value of your SIP >>> platform: >>> >>> * extendedHomer/SIPCapture integration >>> to allow capturing of non-SIP data (transport level data, >>> Management Interface commands, REST queries and more); >>> * SIP-I support both in terms of passing-through and in terms >>> of converting SIP-I to SIP and vice-versa ; >>> * CGRates integration for powerful >>> rating/billing – everything in a simple and automatic way >>> (via a dedicated module); >>> * FreeSWITCH flavored Load-Balancing >>> for a more realistic and accurate traffic balancing over >>> FreeSWITCH clusters (as the load information is fetched in >>> realtime from FreeSWITCH); >>> * theEvent Engine >>> to >>> provide support for scenarios based on Subscribe/Notify >>> model, where the script execution may subscribe and resume >>> later according to certain events (like a dynamic >>> implementation of the Push Notification mechanism); >>> * extendedRabbitMQ support for >>> custom and flexible data injection directly from OpenSIPS >>> script; >>> * extended Asynchronous support for more complex >>> async scenarios (like launch with no wait); >>> * more end-device integration (special SIP extensions). >>> >>> The timeline for OpenSIPS 2.3 is: >>> >>> * Beta Release – 13-17 March 2017 >>> * Stable Release – 24-28 April 2017 >>> * General Availability – 2nd of May 2017, duringOpenSIPS >>> Summit >>> >>> >>> To talk more about the features of this new release, a >>> publicaudio conference >>> will be >>> available on19th of January 2017, 4 pm GMT >>> , thanks to >>> the kind sponsorship of UberConference >>> . Anyone is welcome to join to >>> find out more details or to ask questions aboutOpenSIPS2.3 . >>> >>> This is a public and open conference, so no registration is >>> needed, but if you want to announce your intention to >>> participate, please let us know via the form on the blog post >>> . >>> >>> Best regards, >>> >>> -- >>> Bogdan-Andrei Iancu >>> OpenSIPS Founder and Developer >>> http://www.opensips-solutions.com >>> >>> >>> _______________________________________________ Users mailing >>> list Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > _______________________________________________ Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 17 09:12:26 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 17 Jan 2017 16:12:26 +0200 Subject: [OpenSIPS-Users] How to parse XML Body? In-Reply-To: <009101d26d84$72050d10$560f2730$@web.de> References: <012c01d266bf$841c7590$8c5560b0$@web.de> <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> <018601d26742$7d877ee0$78967ca0$@web.de> <4936e66b-ae31-a9fa-e260-a87ef6b24b20@opensips.org> <019a01d26746$00669460$0133bd20$@web.de> <01b601d26748$2bebb6e0$83c324a0$@web.de> <01428a9e-5f55-5a7e-154d-59c2f8e96ef0@opensips.org> <01f101d2674f$dadadee0$90909ca0$@web.de> <032b01d26833$cace6370$606b2a50$@web.de> <6969d0ff-96a6-56da-15f4-54f8cd0c116b@opensips.org> <009101d26d84$72050d10$560f2730$@web.de> Message-ID: <5e264517-2c83-2808-4e29-f9418125ff7a@opensips.org> Hi, There was a small typo in my regexp. The correct one is: $var(reg) = "/(.*)gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s"; xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); I tried it and it does the job. Regarding the usability of the $rb variable, yes you have a point. I was thinking of something like $rb(mime)[idx] to access also per mime. Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/13/2017 12:04 PM, xaled wrote: > > Hi Bogdan, > > thank you for looking at this issue. This regex does not work. I tried > different combinations of the idea but it just not getting there. > > 2017-01-13T11:02:42.287766+01:00 ivr01 > /usr/local/sbin/opensips[24845]: DBG:core:tr_eval_re: we must compile > the regexp > > 2017-01-13T11:02:42.288116+01:00 ivr01 > /usr/local/sbin/opensips[24845]: WARNING:core:parse_repl: \/ unknown > escape in (.*)<\/gml:Coordinates(.*)/\2/s > > 2017-01-13T11:02:42.288464+01:00 ivr01 > /usr/local/sbin/opensips[24845]: ERROR:core:subst_parser: unknown flag > . in (.*)/gml:Coordinates>(.*)<\/gml:Coordin > > ates(.*)/\2/s > > 2017-01-13T11:02:42.288787+01:00 ivr01 > /usr/local/sbin/opensips[24845]: ERROR:core:tr_eval_re: Can't compile > regexp > > I managed to get it running with perl: > > use OpenSIPS qw ( log ); > > use OpenSIPS::Constants; > > use OpenSIPS::Message; > > sub parsePIDFLO { > > my $m = shift; > > my $body = $m->getBody(); > > ($coord) = $body =~ /Coordinates>(.*) > my ($long, $lat) = split( /\s+/, $coord ); > > Btw it would be great to be able to address the xml body by something > like this: > > rb[application/pidf+xml] or rb["application/pidf+xml"] otherwise if > bodies come in different order rb[1] would not work. > > Thanks > > *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] > *Sent:* Mittwoch, 11. Januar 2017 11:05 > *To:* OpenSIPS users mailling list ; asd asd > > *Subject:* Re: [OpenSIPS-Users] How to parse XML Body? > > Hi, > > Please try > > $var(reg) = "(.*)/gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s"; > xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 01/06/2017 05:44 PM, xaled wrote: > > Hi Bogdan, > > can you give any hints on how to get the Coordinates values and > not the whole xml body from the regex subst? > > Sorry for being not clever enough to figure it out myself. > > Thanks > > Hi Bogdan, > > $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; > > xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); > > DBG:core:subst_run:matched shows the needed XML element with > value, but not the value alone. The xlog output shows the whole > XML body without gml:Coordinates. > > 2017-01-05T13:23:23.104982+01:00 ivr01 > /usr/local/sbin/opensips[2227]: DBG:core:tr_eval_re: Trying to > apply reg > > exp [/gml:Coordinates>(.*)<\/gml:Coordinates/\1/] on : [ version="1.0" encoding="UTF-8"?>#015#012 > ns="urn:ietf:params:xml:ns:pidf" > xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" > xmlns:gml="urn:opengis:specificat > > ion:gml:schema-xsd:feature:v3.0" > entity="pres:sip:+1234567 at test.com" > >#015#012 id="PDT">#015#012 > tatus>#015#012 #015#012 #015#012 > #015#012 > id="point1" srsName="epsg:4346">#015#012 12.32 > 34.24#015#012 > oint>#015#012 #015#012 #015#012 > #015#012 > smission-allowed>no#015#012 > #015#012 #01 > > 5#012 #015#012 #015#012 > 2016-8-02T04:13:23Z#015#012 #015#0 > > 12#015#012#015#012] > > 2017-01-05T13:23:23.107376+01:00 ivr01 > /usr/local/sbin/opensips[2227]: DBG:core:tr_eval_re: we must > compile the > > regexp > > 2017-01-05T13:23:23.107903+01:00 ivr01 > /usr/local/sbin/opensips[2227]: DBG:core:subst_parser: ok, se is > 0x7f39a > > 5d0a1f0 > > 2017-01-05T13:23:23.108241+01:00 ivr01 > /usr/local/sbin/opensips[2227]: DBG:core:subst_run: running. r=0 > > 2017-01-05T13:23:23.111918+01:00 ivr01 > /usr/local/sbin/opensips[2227]: DBG:core:subst_run: matched (404, > 45): [ > > gml:Coordinates>12.32 34.24 > 2017-01-05T13:23:23.112380+01:00 ivr01 > /usr/local/sbin/opensips[2227]: DBG:core:buf_init: initializing... > > 2017-01-05T13:23:23.112730+01:00 ivr01 > /usr/local/sbin/opensips[2227]: Position is encoding > > ="UTF-8"?>#015#012 xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xm > > lns:gml="urn:opengis:specification:gml:schema-xsd:feature:v3.0" > entity="pres:sip:+1234567 at test.com" > >#015#0 > > 12 #015#012 #015#012 #015#012 > #015#012 > n>#015#012 srsName="epsg:4346">#015#012 <12.32 34.24>#015#012 > > nt>#015#012 #015#012 #015#012 > #015#012 > ission-allowed>no#015#012 > #015#012 #015# > > 012 #015#012 #015#012 > 2016-8-02T04:13:23Z#015#012 #015#012 > > > > Thanks > > *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] > *Sent:* Donnerstag, 5. Januar 2017 13:12 > *To:* OpenSIPS users mailling list >; xaled > > *Subject:* Re: [OpenSIPS-Users] How to parse XML Body? > > Try $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; > > > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahmedmunir007 at gmail.com Tue Jan 17 10:43:06 2017 From: ahmedmunir007 at gmail.com (Ahmed Munir) Date: Tue, 17 Jan 2017 10:43:06 -0500 Subject: [OpenSIPS-Users] OpenSIPs crashed Message-ID: Is there updates on this? Date: Mon, 16 Jan 2017 09:51:13 -0500 > From: Ahmed Munir > To: OpenSIPs Users > Subject: Re: [OpenSIPS-Users] OpenSIPs crashed > Message-ID: > gmail.com> > Content-Type: text/plain; charset="utf-8" > > See details below; > > [root at qorblpsisprxyd1 ~]# opensips -V > version: opensips 2.2.2 (x86_64/linux) > flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_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_lt, epoll_et, sigio_rt, select. > main.c compiled on 11:09:47 Jan 13 2017 with gcc 4.4.7 > > [root at qorblpsisprxyd1 ~]# opensipsctl ps > Process:: ID=0 PID=8269 Type=attendant > Process:: ID=1 PID=8271 Type=MI FIFO > Process:: ID=2 PID=8272 Type=time_keeper > Process:: ID=3 PID=8274 Type=timer > Process:: ID=4 PID=8275 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=5 PID=8278 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=6 PID=8279 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=7 PID=8281 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=8 PID=8283 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=9 PID=8285 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=10 PID=8287 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=11 PID=8289 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=12 PID=8291 Type=Timer handler > > > [root at qorblpsisprxyd1 ~]# lscpu > Architecture: x86_64 > CPU op-mode(s): 32-bit, 64-bit > Byte Order: Little Endian > CPU(s): 8 > On-line CPU(s) list: 0-7 > Thread(s) per core: 1 > Core(s) per socket: 4 > Socket(s): 2 > NUMA node(s): 2 > Vendor ID: GenuineIntel > CPU family: 6 > Model: 44 > Stepping: 2 > CPU MHz: 1197.000 > BogoMIPS: 4266.58 > Virtualization: VT-x > L1d cache: 32K > L1i cache: 32K > L2 cache: 256K > L3 cache: 8192K > NUMA node0 CPU(s): 0-3 > NUMA node1 CPU(s): 4-7 > > In /etc/default/opensips config, declaring shared and pkg memory as server > memory is 64 GB; > > # Amount of shared memory to allocate for the running OpenSIPS server (in > Mb) > S_MEMORY=256 > > # Amount of pkg memory to allocate for the running OpenSIPS server (in Mb) > P_MEMORY=32 > > Let me know any other info needed from my end. > > Date: Mon, 16 Jan 2017 10:49:37 +0200 > > From: Răzvan Crainea > > To: users at lists.opensips.org > > Subject: Re: [OpenSIPS-Users] OpenSIPs crashed > > Message-ID: <1584806e-a154-a5ad-a464-4eef609158f4 at opensips.org> > > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > > > Hi, Ahmed! > > > > Can you tell us exactly what revision of OpenSIPS you are using? Please > > provide the output of the following commands: > > opensips -V > > opensipsctl ps > > > > Also, during startup, is there a process who's "eating" a lot of CPU? If > > so, can you pinpoint the PID to see what type of process is that? > > > > Regarding the avp_db_query() issue, did you define a db_url parameter > > for it? Also I am not sure you can do something like $var(res) = > > avp_db_query(...). But anyways, this is something completely different, > > so please open a different topic for it. > > > > Best regards, > > > > Răzvan Crainea > > OpenSIPS Solutions > > www.opensips-solutions.com > > > > On 01/14/2017 12:24 AM, Ahmed Munir wrote: > > > Hi, > > > > > > I've just installed new version of opensips 2.2.2 on the test box and > > > updated by routing script, the issue currently I'm seeing alot warning > > > messages while starting opensips service below; > > > > > > /usr/sbin/opensips[6902]: WARNING:core:handle_timer_job: utimer job > > > has a 2830000 us delay in execution > > > > > > Number of children running on that server is 8 as it is 8 core > processor. > > > > > > I would like to know what steps do I need to take to fix this issue. > > > Btw, warnings only occurred during the time of starting opensips > > > service but not during calls. > > > > > > > > > Further added, a issue I face using avp_db_query () function i.e. when > > > using it as > > > > > > $var(res) = avp_db_query("SELECT Outpulse_number,setid FROM > > > Prefix_data where Program_prefix = $var(pg_prefix)", "$avp(outpluse), > > > $avp(trunkid)"); > > > > > > failed to start opensips service due to errors below; > > > > > > ERROR:avpops:__fixup_db_query_avp: no db url defined to be used by > > > this function > > > ERROR:core:fix_actions: fixing failed (code=-6) at > > > //etc/opensips/opensips.cfg:207 > > > CRITICAL:core:fix_expr: fix_actions error > > > ERROR:core:main: failed to fix configuration with err code -6 > > > > > > > > > If I add this line: avp_db_query("SELECT 1"); above to my $var(res) db > > > query, opensips service starts successfully. > > > > > > Please advise the steps do I need to take to fix above issues. > > > > > > > > > > > > > > > > -- > Regards, > > Ahmed Munir Chohan > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: 20170116/d1f2c3c7/attachment-0001.html> > > -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From frank21118 at yahoo.com Tue Jan 17 12:14:52 2017 From: frank21118 at yahoo.com (bluerain) Date: Tue, 17 Jan 2017 10:14:52 -0700 (MST) Subject: [OpenSIPS-Users] change T_fr_in_timeout In-Reply-To: <46c9630b-1a72-7bc5-a513-f46ce771e033@opensips.org> References: <1484232021878-7605536.post@n2.nabble.com> <46c9630b-1a72-7bc5-a513-f46ce771e033@opensips.org> Message-ID: <1484673292020-7605617.post@n2.nabble.com> thank you! I'll give that a shot! -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/change-T-fr-in-timeout-tp7605536p7605617.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From Agalya_Ramachandran at comcast.com Tue Jan 17 15:03:11 2017 From: Agalya_Ramachandran at comcast.com (Ramachandran, Agalya (Contractor)) Date: Tue, 17 Jan 2017 20:03:11 +0000 Subject: [OpenSIPS-Users] async- issues- 2.2.2 Message-ID: <4afe8b5419b74122ad85d626b5e12872@COPDCEX28.cable.comcast.com> Hi Liviu/team, When I try to do an asynchronous REST_PUT call in OpenSIPS 2.2.2, I see the below observance and issues. All the calls are made from sipp client. No Test Scenario Result/observation 1. Call-Id length < 50 Works perfectly fine 2 Call-Id length >54 and < 56 No crash observed. But error in curl_multiperform 3. Call-Id length > 56 Opensips crashes at liburl. Please find the details for test 2 and test 3. I have tested with REST_POST with case 3, I didn't observe any crashes. Please let me know what could cause this issue and how can I fix this? Test2: Jan 17 18:23:13 /usr/local/sbin/opensips[18554]: ERROR:rest_client:start_async_http_req: curl_multi_perform: Invalid multi handle Jan 17 18:23:13 /usr/local/sbin/opensips[18554]: ERROR:rest_client:start_async_http_req: curl_multi_remove_handle: Invalid multi handle Test 3: (gdb) bt #0 0x00007f370bccb9bb in curl_multi_add_handle () from /lib64/libcurl.so.4 #1 0x00007f370bf05521 in start_async_http_req (msg=msg at entry=0x7f374db14270, method=method at entry=REST_CLIENT_PUT, url=0x7f374dad8178 "http://url", req_body=, req_ctype=, out_handle=out_handle at entry=0x7f374db204e0, body=body at entry=0x7f374db204e8, ctype=0x7f374db204f8) at rest_methods.c:227 #2 0x00007f370bf0e2ca in w_async_rest_put (msg=0x7f374db14270, resume_f=0x7ffc6f551680, resume_param=0x7ffc6f551690, gp_url=, gp_body=, gp_ctype=, body_pv=0x7f374daf5510 "N", ctype_pv=0x7f374daf55a8 "N", code_pv=0x7f374daf5670 "N") at rest_client.c:579 #3 0x00007f370d24920f in t_handle_async (msg=0x7f374db14270, a=0x7f374dad8508, resume_route=) at async.c:240 #4 0x000000000042d724 in do_action (a=a at entry=0x7f374dad8680, msg=msg at entry=0x7f374db14270) at action.c:1863 #5 0x00000000004341cc in run_action_list (a=, msg=0x7f374db14270) at action.c:172 #6 0x0000000000430769 in do_action (a=a at entry=0x7f374dad8760, msg=msg at entry=0x7f374db14270) at action.c:1108 #7 0x000000000043454d in run_action_list (msg=, a=) at action.c:172 #8 run_actions (a=, msg=0x7f374db14270) at action.c:137 #9 0x000000000042f8d7 in do_action (a=a at entry=0x7f374dad6b58, msg=msg at entry=0x7f374db14270) at action.c:745 #10 0x0000000000434393 in run_action_list (msg=, a=) at action.c:172 #11 run_actions (msg=0x7f374db14270, a=) at action.c:137 #12 run_top_route (a=, msg=msg at entry=0x7f374db14270) at action.c:204 #13 0x000000000043bcba in receive_msg ( buf=0x858c20 "INVITE sip:+19084904567 at 10.10.10.05060 SIP/2.0\r\nTo: \r\nFrom: \"test PA\";"..., len=, rcv_info=rcv_info at entry=0x7ffc6f552c70, existing_context=existing_context at entry=0x0) at receive.c:208 #14 0x00000000005b0b03 in udp_read_req (si=, bytes_read=) at net/proto_udp/proto_udp.c:192 #15 0x000000000059b960 in handle_io (idx=, event_type=, fm=) at net/net_udp.c:259 #16 io_wait_loop_epoll (h=, t=, repeat=) at net/../io_wait_loop.h:225 #17 udp_rcv_loop (si=si at entry=0x7f374dacb6c8) at net/net_udp.c:308 #18 0x000000000059ce88 in udp_start_processes (chd_rank=chd_rank at entry=0x845830 , startup_done=startup_done at entry=0x0) at net/net_udp.c:372 #19 0x0000000000419f50 in main_loop () at main.c:671 #20 main (argc=, argv=) at main.c:1261 Regards, Agalya -------------- next part -------------- An HTML attachment was scrubbed... URL: From Agalya_Ramachandran at comcast.com Tue Jan 17 15:57:44 2017 From: Agalya_Ramachandran at comcast.com (Ramachandran, Agalya (Contractor)) Date: Tue, 17 Jan 2017 20:57:44 +0000 Subject: [OpenSIPS-Users] async- issues- 2.2.2 In-Reply-To: <4afe8b5419b74122ad85d626b5e12872@COPDCEX28.cable.comcast.com> References: <4afe8b5419b74122ad85d626b5e12872@COPDCEX28.cable.comcast.com> Message-ID: Hi, Another information may help you to find this issue. Am changing the "req_body" in the rest_methods.c, as per the REST API server is expecting the payload value. If I change this "req_body" in REST_POST as well, and if the Call-Id length is > 56, it crashes in the POST call too. Regards, Agalya From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Ramachandran, Agalya (Contractor) Sent: Tuesday, January 17, 2017 3:03 PM To: OpenSIPS users mailling list ; Liviu Chircu Subject: [OpenSIPS-Users] async- issues- 2.2.2 Hi Liviu/team, When I try to do an asynchronous REST_PUT call in OpenSIPS 2.2.2, I see the below observance and issues. All the calls are made from sipp client. No Test Scenario Result/observation 1. Call-Id length < 50 Works perfectly fine 2 Call-Id length >54 and < 56 No crash observed. But error in curl_multiperform 3. Call-Id length > 56 Opensips crashes at liburl. Please find the details for test 2 and test 3. I have tested with REST_POST with case 3, I didn't observe any crashes. Please let me know what could cause this issue and how can I fix this? Test2: Jan 17 18:23:13 /usr/local/sbin/opensips[18554]: ERROR:rest_client:start_async_http_req: curl_multi_perform: Invalid multi handle Jan 17 18:23:13 /usr/local/sbin/opensips[18554]: ERROR:rest_client:start_async_http_req: curl_multi_remove_handle: Invalid multi handle Test 3: (gdb) bt #0 0x00007f370bccb9bb in curl_multi_add_handle () from /lib64/libcurl.so.4 #1 0x00007f370bf05521 in start_async_http_req (msg=msg at entry=0x7f374db14270, method=method at entry=REST_CLIENT_PUT, url=0x7f374dad8178 "http://url", req_body=, req_ctype=, out_handle=out_handle at entry=0x7f374db204e0, body=body at entry=0x7f374db204e8, ctype=0x7f374db204f8) at rest_methods.c:227 #2 0x00007f370bf0e2ca in w_async_rest_put (msg=0x7f374db14270, resume_f=0x7ffc6f551680, resume_param=0x7ffc6f551690, gp_url=, gp_body=, gp_ctype=, body_pv=0x7f374daf5510 "N", ctype_pv=0x7f374daf55a8 "N", code_pv=0x7f374daf5670 "N") at rest_client.c:579 #3 0x00007f370d24920f in t_handle_async (msg=0x7f374db14270, a=0x7f374dad8508, resume_route=) at async.c:240 #4 0x000000000042d724 in do_action (a=a at entry=0x7f374dad8680, msg=msg at entry=0x7f374db14270) at action.c:1863 #5 0x00000000004341cc in run_action_list (a=, msg=0x7f374db14270) at action.c:172 #6 0x0000000000430769 in do_action (a=a at entry=0x7f374dad8760, msg=msg at entry=0x7f374db14270) at action.c:1108 #7 0x000000000043454d in run_action_list (msg=, a=) at action.c:172 #8 run_actions (a=, msg=0x7f374db14270) at action.c:137 #9 0x000000000042f8d7 in do_action (a=a at entry=0x7f374dad6b58, msg=msg at entry=0x7f374db14270) at action.c:745 #10 0x0000000000434393 in run_action_list (msg=, a=) at action.c:172 #11 run_actions (msg=0x7f374db14270, a=) at action.c:137 #12 run_top_route (a=, msg=msg at entry=0x7f374db14270) at action.c:204 #13 0x000000000043bcba in receive_msg ( buf=0x858c20 "INVITE sip:+19084904567 at 10.10.10.05060 SIP/2.0\r\nTo: \r\nFrom: \"test PA\";"..., len=, rcv_info=rcv_info at entry=0x7ffc6f552c70, existing_context=existing_context at entry=0x0) at receive.c:208 #14 0x00000000005b0b03 in udp_read_req (si=, bytes_read=) at net/proto_udp/proto_udp.c:192 #15 0x000000000059b960 in handle_io (idx=, event_type=, fm=) at net/net_udp.c:259 #16 io_wait_loop_epoll (h=, t=, repeat=) at net/../io_wait_loop.h:225 #17 udp_rcv_loop (si=si at entry=0x7f374dacb6c8) at net/net_udp.c:308 #18 0x000000000059ce88 in udp_start_processes (chd_rank=chd_rank at entry=0x845830 , startup_done=startup_done at entry=0x0) at net/net_udp.c:372 #19 0x0000000000419f50 in main_loop () at main.c:671 #20 main (argc=, argv=) at main.c:1261 Regards, Agalya -------------- next part -------------- An HTML attachment was scrubbed... URL: From Agalya_Ramachandran at comcast.com Tue Jan 17 16:13:42 2017 From: Agalya_Ramachandran at comcast.com (Ramachandran, Agalya (Contractor)) Date: Tue, 17 Jan 2017 21:13:42 +0000 Subject: [OpenSIPS-Users] async- issues- 2.2.2 In-Reply-To: References: <4afe8b5419b74122ad85d626b5e12872@COPDCEX28.cable.comcast.com> Message-ID: Hi Liviu, Found the exact issue what causes the crash. In start_async_http_req, under case PUT/POST, we have the following code blue color by default. But for my project scenario, I need to add call-id header too here, including that code in red color for your reference. if (req_ctype) { sprintf(print_buff, "Content-Type: %s", req_ctype); header_list = curl_slist_append(header_list, print_buff); sprintf(print_buff, "Call-Id: %s", instanceId); header_list = curl_slist_append(header_list, print_buff); w_curl_easy_setopt(handle, CURLOPT_HTTPHEADER, header_list); } If I try by removing the Call-Id header in the curl-slist, then it works perfectly fine in case of POST as well as PUT. How can I overcome this situation? Your guidance would help me a lot. Regards, Agalya From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Ramachandran, Agalya (Contractor) Sent: Tuesday, January 17, 2017 3:58 PM To: OpenSIPS users mailling list ; Liviu Chircu Subject: Re: [OpenSIPS-Users] async- issues- 2.2.2 Hi, Another information may help you to find this issue. Am changing the "req_body" in the rest_methods.c, as per the REST API server is expecting the payload value. If I change this "req_body" in REST_POST as well, and if the Call-Id length is > 56, it crashes in the POST call too. Regards, Agalya From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Ramachandran, Agalya (Contractor) Sent: Tuesday, January 17, 2017 3:03 PM To: OpenSIPS users mailling list >; Liviu Chircu > Subject: [OpenSIPS-Users] async- issues- 2.2.2 Hi Liviu/team, When I try to do an asynchronous REST_PUT call in OpenSIPS 2.2.2, I see the below observance and issues. All the calls are made from sipp client. No Test Scenario Result/observation 1. Call-Id length < 50 Works perfectly fine 2 Call-Id length >54 and < 56 No crash observed. But error in curl_multiperform 3. Call-Id length > 56 Opensips crashes at liburl. Please find the details for test 2 and test 3. I have tested with REST_POST with case 3, I didn't observe any crashes. Please let me know what could cause this issue and how can I fix this? Test2: Jan 17 18:23:13 /usr/local/sbin/opensips[18554]: ERROR:rest_client:start_async_http_req: curl_multi_perform: Invalid multi handle Jan 17 18:23:13 /usr/local/sbin/opensips[18554]: ERROR:rest_client:start_async_http_req: curl_multi_remove_handle: Invalid multi handle Test 3: (gdb) bt #0 0x00007f370bccb9bb in curl_multi_add_handle () from /lib64/libcurl.so.4 #1 0x00007f370bf05521 in start_async_http_req (msg=msg at entry=0x7f374db14270, method=method at entry=REST_CLIENT_PUT, url=0x7f374dad8178 "http://url", req_body=, req_ctype=, out_handle=out_handle at entry=0x7f374db204e0, body=body at entry=0x7f374db204e8, ctype=0x7f374db204f8) at rest_methods.c:227 #2 0x00007f370bf0e2ca in w_async_rest_put (msg=0x7f374db14270, resume_f=0x7ffc6f551680, resume_param=0x7ffc6f551690, gp_url=, gp_body=, gp_ctype=, body_pv=0x7f374daf5510 "N", ctype_pv=0x7f374daf55a8 "N", code_pv=0x7f374daf5670 "N") at rest_client.c:579 #3 0x00007f370d24920f in t_handle_async (msg=0x7f374db14270, a=0x7f374dad8508, resume_route=) at async.c:240 #4 0x000000000042d724 in do_action (a=a at entry=0x7f374dad8680, msg=msg at entry=0x7f374db14270) at action.c:1863 #5 0x00000000004341cc in run_action_list (a=, msg=0x7f374db14270) at action.c:172 #6 0x0000000000430769 in do_action (a=a at entry=0x7f374dad8760, msg=msg at entry=0x7f374db14270) at action.c:1108 #7 0x000000000043454d in run_action_list (msg=, a=) at action.c:172 #8 run_actions (a=, msg=0x7f374db14270) at action.c:137 #9 0x000000000042f8d7 in do_action (a=a at entry=0x7f374dad6b58, msg=msg at entry=0x7f374db14270) at action.c:745 #10 0x0000000000434393 in run_action_list (msg=, a=) at action.c:172 #11 run_actions (msg=0x7f374db14270, a=) at action.c:137 #12 run_top_route (a=, msg=msg at entry=0x7f374db14270) at action.c:204 #13 0x000000000043bcba in receive_msg ( buf=0x858c20 "INVITE sip:+19084904567 at 10.10.10.05060 SIP/2.0\r\nTo: \r\nFrom: \"test PA\";"..., len=, rcv_info=rcv_info at entry=0x7ffc6f552c70, existing_context=existing_context at entry=0x0) at receive.c:208 #14 0x00000000005b0b03 in udp_read_req (si=, bytes_read=) at net/proto_udp/proto_udp.c:192 #15 0x000000000059b960 in handle_io (idx=, event_type=, fm=) at net/net_udp.c:259 #16 io_wait_loop_epoll (h=, t=, repeat=) at net/../io_wait_loop.h:225 #17 udp_rcv_loop (si=si at entry=0x7f374dacb6c8) at net/net_udp.c:308 #18 0x000000000059ce88 in udp_start_processes (chd_rank=chd_rank at entry=0x845830 , startup_done=startup_done at entry=0x0) at net/net_udp.c:372 #19 0x0000000000419f50 in main_loop () at main.c:671 #20 main (argc=, argv=) at main.c:1261 Regards, Agalya -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcunningham at voisonics.com Tue Jan 17 19:43:00 2017 From: dcunningham at voisonics.com (David Cunningham) Date: Wed, 18 Jan 2017 11:43:00 +1100 Subject: [OpenSIPS-Users] Return body/string from Perl library Message-ID: Hello, We are using Kamailio's perl module and want our custom library to set the body on a SIP message. Is it possible to set a SIP message body from within Perl, or can we return a string to the Kamailio configuration to then use with set_body()? Thanks for any advice. -- David Cunningham, Voisonics http://voisonics.com/ USA: +1 213 221 1092 Australia: +61 (0) 2 8063 9019 -------------- next part -------------- An HTML attachment was scrubbed... URL: From miha at softnet.si Wed Jan 18 02:27:29 2017 From: miha at softnet.si (Miha) Date: Wed, 18 Jan 2017 08:27:29 +0100 Subject: [OpenSIPS-Users] radius accounting, Acct-Status-Type = 0 In-Reply-To: References: <06dd350e-51a3-3c71-8a84-9112e0c794d5@softnet.si> <8f907cea-dacd-dfa5-ad67-3613035aa825@opensips.org> <03e5c6b9-5d21-1d55-eb86-2dc47bcae178@softnet.si> Message-ID: <407eb9d3-d674-236e-c17e-2bf0a7d1c9a4@softnet.si> Tnx:) working! br miha On 17/01/2017 12:30, Ionut Ionita wrote: > Also if you'll check latest commit in master[0], modified radius > code to throw error and not start if any attribute/ > value/vendor is not found in order to not get to similar situations in > the future. Backported the commit back to 2.1. > > [0] > https://github.com/OpenSIPS/opensips/commit/75573b41c5453b495a3fa9ad1bdf2df3ee0f4c2f > > Regards, > > Ionut Ionita > OpenSIPS Developer > On 01/17/2017 12:06 PM, Ionut Ionita wrote: >> Hello again, >> >> Found a fix for your problem. You should use *dictionary.rfc2866* >> (freeradius has it). This dictionary has value defined >> for *Failed*. >> >> VALUE› Acct-Status-Type› › Start› › › 1 >> VALUE› Acct-Status-Type› › Stop› › › 2 >> VALUE› Acct-Status-Type› › Alive› › › 3 # dup >> VALUE› Acct-Status-Type› › Interim-Update› › 3 >> VALUE› Acct-Status-Type› › Accounting-On› › 7 >> VALUE› Acct-Status-Type› › Accounting-Off› › 8 >> VALUE› Acct-Status-Type› › Failed› › › 15 >> >> >> Regards, >> >> Ionut Ionita >> OpenSIPS Developer >> On 01/17/2017 10:33 AM, Miha wrote: >>> ok, then i will use this value and on radius side i will catch it >>> and set to internally to STOP if this is only soluton. >>> >>> The thing is when 486/busy comes, opensips sends this broken radius >>> accouting request and radius server does not replay to it and that >>> is why the opensips waits almost 40s to send back ACK on 486. >>> >>> >>> Or is there any other solution? >>> >>> >>> br >>> miha >>> >>> On 17/01/2017 09:27, Ionut Ionita wrote: >>>> No, thank you it's fine now. That value was for testing purposes >>>> only, you can remove it now. >>>> OpenSIPS it's using *Failed* value for *Acct-Status-Type* which is >>>> not defined anywhere (nor in >>>> our dictionary, nor in any RFC or somewhere else). Not finding that >>>> value results in having *0 >>>> *for *Acct-Status-Type*, the value you were seeing before. Will let >>>> you know when we'll decide >>>> how we should fix this issue. >>>> >>>> Regards, >>>> Ionut Ionita >>>> OpenSIPS Developer >>>> On 01/17/2017 09:38 AM, Miha wrote: >>>>> Hi Ionut >>>>> >>>>> do I need on bouth sides or opensips side? >>>>> >>>>> I can see that now i get: Acct-Status-Type = Modem-Start in radius. >>>>> >>>>> >>>>> br >>>>> miha >>>>> >>>>> On 16/01/2017 16:45, Ionut Ionita wrote: >>>>>> >>>>>> Hi Miha, >>>>>> >>>>>> Can you set in your radius dictionary file where the >>>>>> *Acct-Status-Type* values are defined >>>>>> >>>>>> VALUE Acct-Status-Type Start› › › 1 >>>>>> VALUE Acct-Status-Type Stop› › › 2 >>>>>> VALUE Acct-Status-Type Alive› › › 3 >>>>>> VALUE Acct-Status-Type Accounting-On› › 7 >>>>>> VALUE Acct-Status-Type Accounting-Off› › 8 >>>>>> >>>>>> the following line, just below the others: >>>>>> >>>>>> VALUE Acct-Status-Type Failed 4 >>>>>> >>>>>> and then check if you'll see *4 *instead of *0* for >>>>>> *Acct-Status-Type*? >>>>>> >>>>>> It seems that opensips it's using a value that's not in the >>>>>> radius dictionary, *Failed* value. >>>>>> >>>>>> >>>>>> Ionut Ionita >>>>>> OpenSIPS Developer >>>>>> On 01/16/2017 04:05 PM, Miha wrote: >>>>>>> Hello >>>>>>> >>>>>>> how can i define that for 486/busy opensips will send >>>>>>> Acct-Status-Type = 2 to radius server? >>>>>>> Acct-Status-Type = 0 it not like standard thing and it should >>>>>>> not be send :) >>>>>>> >>>>>>> >>>>>>> I imported dictinary.opensips and .sip. >>>>>>> >>>>>>> >>>>>>> tnx >>>>>>> miha >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Users mailing list >>>>>>> Users at lists.opensips.org >>>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Users mailing list >>>>>> Users at lists.opensips.org >>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Users mailing list >>>>> Users at lists.opensips.org >>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>> >>>> >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> Users at lists.opensips.org >>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Wed Jan 18 03:33:06 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Wed, 18 Jan 2017 10:33:06 +0200 Subject: [OpenSIPS-Users] Registrar with IP authentication - selecting variables from DB In-Reply-To: <1484643794782-7605600.post@n2.nabble.com> References: <1484133356292-7605516.post@n2.nabble.com> <9640879b-c012-4529-5e7d-57a8ea817e67@opensips.org> <1484298184907-7605547.post@n2.nabble.com> <40d4cd21-5f93-5372-c09c-04c2a3c131ad@opensips.org> <1484305764044-7605552.post@n2.nabble.com> <1484308289132-7605554.post@n2.nabble.com> <62206e87-8dfd-8a30-2e00-702adfb55dbc@opensips.org> <1484640372992-7605592.post@n2.nabble.com> <1484643794782-7605600.post@n2.nabble.com> Message-ID: <96f8e55f-41f4-c4df-78d8-92c9dce24fb4@opensips.org> You are probably using an old version of OpenSIPS, that's why you are not seeing negative return values. Checking if the IP might still be ok, if your database is consistent and has an IP for every user. So for now I would go with this solution. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/17/2017 11:03 AM, maatohewetbi wrote: > I've just did it like this: > > xlog("$rc"); > and on Friday I got > 18446744073709551615 > so You were right that it was unsigned int. But now if I want to read > xlog("$rc") it has 1 value. And my table is empty. > Now I've changed script and it looks: > > if ($avp(s:ip) == null ) { > xlog("no results found in DB"); > xlog("$rc"); > > and it is ok, and works like it should, because $avp(s:ip) is NULL when > there's no records found. But I'm afraid it's not the best solution. What do > You think? > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Registrar-with-IP-authentication-selecting-variables-from-DB-tp7605514p7605600.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From rfmundkowsky at yahoo.com Tue Jan 17 14:15:20 2017 From: rfmundkowsky at yahoo.com (robert mundkowsky) Date: Tue, 17 Jan 2017 19:15:20 +0000 (UTC) Subject: [OpenSIPS-Users] does OpenSIPS Control Panel work? References: <338031073.4799866.1484680520944.ref@mail.yahoo.com> Message-ID: <338031073.4799866.1484680520944@mail.yahoo.com> I installed https://github.com/OpenSIPS/opensips-cp/archive/6.2.zip And I am getting a parse errors for list_admins.main.php which I assume means there is an error in the php code. Below is the error log, but note the line number might be a little different from source code because I tried adding error log messages, but forgot these will nto work, because the code will not even parse. PHP Parse error:  syntax error, unexpected '}' in /var/www/opensips-cp/web/tools/admin/list_admins/template/list_admins.main.php on line 152 -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1795868916 at qq.com Tue Jan 17 21:47:15 2017 From: 1795868916 at qq.com (=?gb18030?B?zrA=?=) Date: Wed, 18 Jan 2017 10:47:15 +0800 Subject: [OpenSIPS-Users] How to transplant OpenSIPS to the Android platform Message-ID: hello, I want to transplant OpenSIPS to my Android device.How to compile the OpenSIPS source code for Android? Thankyou very much. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Wed Jan 18 03:43:43 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 18 Jan 2017 10:43:43 +0200 Subject: [OpenSIPS-Users] Return body/string from Perl library In-Reply-To: References: Message-ID: Hi David, You are on the wrong mailing list :) Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/18/2017 02:43 AM, David Cunningham wrote: > Hello, > > We are using Kamailio's perl module and want our custom library to set > the body on a SIP message. > > Is it possible to set a SIP message body from within Perl, or can we > return a string to the Kamailio configuration to then use with set_body()? > > Thanks for any advice. > > -- > David Cunningham, Voisonics > http://voisonics.com/ > USA: +1 213 221 1092 > Australia: +61 (0) 2 8063 9019 > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Wed Jan 18 03:44:43 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Wed, 18 Jan 2017 10:44:43 +0200 Subject: [OpenSIPS-Users] does OpenSIPS Control Panel work? In-Reply-To: <338031073.4799866.1484680520944@mail.yahoo.com> References: <338031073.4799866.1484680520944.ref@mail.yahoo.com> <338031073.4799866.1484680520944@mail.yahoo.com> Message-ID: <64a8f218-7ec6-945a-50ae-20da950aa221@opensips.org> Hi, Robert! Yes, OpenSIPS Control Panel should work without problems. I double checked the line you get that error[1], but it doesn't seem anything wrong over there. Can you post your file on pastebin so I can check your version? [1] https://github.com/OpenSIPS/opensips-cp/blob/6.2/web/tools/admin/list_admins/template/list_admins.main.php#L152 Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/17/2017 09:15 PM, robert mundkowsky via Users wrote: > > I installed https://github.com/OpenSIPS/opensips-cp/archive/6.2.zip > > And I am getting a parse errors for list_admins.main.php which I > assume means there is an error in the php code. > > Below is the error log, but note the line number might be a little > different from source code because I tried adding error log messages, > but forgot these will nto work, because the code will not even parse. > > PHP Parse error: syntax error, unexpected '}' in > /var/www/opensips-cp/web/tools/admin/list_admins/template/list_admins.main.php > on line 152 > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Wed Jan 18 04:28:30 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Wed, 18 Jan 2017 11:28:30 +0200 Subject: [OpenSIPS-Users] async- issues- 2.2.2 In-Reply-To: References: <4afe8b5419b74122ad85d626b5e12872@COPDCEX28.cable.comcast.com> Message-ID: <518a4bb0-f469-ce49-318f-108e09d8dd00@opensips.org> Hi, Ramachandran! The print_buff buffer is declared with length MAX_CONTENT_TYPE_LEN -> 64. Writing more than 64 bytes will lead to a buffer overflow, probably followed by a crash. If you want to suppor longer CallIDs, just increase the size of the buffer, or allocate the buffer with a size large enought to fit your callid length. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/17/2017 11:13 PM, Ramachandran, Agalya (Contractor) wrote: > > Hi Liviu, > > Found the exact issue what causes the crash. > > In start_async_http_req, under case PUT/POST, we have the following > code blue color by default. > > But for my project scenario, I need to add call-id header too here, > including that code in red color for your reference. > > if (req_ctype) { > > sprintf(print_buff, "Content-Type: %s", req_ctype); > > header_list = curl_slist_append(header_list, print_buff); > > sprintf(print_buff, "Call-Id: %s", instanceId); > > header_list = curl_slist_append(header_list, print_buff); > > w_curl_easy_setopt(handle, CURLOPT_HTTPHEADER, header_list); > > } > > If I try by removing the Call-Id header in the curl-slist, then it > works perfectly fine in case of POST as well as PUT. > > How can I overcome this situation? Your guidance would help me a lot. > > Regards, > Agalya > > *From:* Users [mailto:users-bounces at lists.opensips.org] *On Behalf Of > *Ramachandran, Agalya (Contractor) > *Sent:* Tuesday, January 17, 2017 3:58 PM > *To:* OpenSIPS users mailling list ; Liviu > Chircu > *Subject:* Re: [OpenSIPS-Users] async- issues- 2.2.2 > > Hi, > > Another information may help you to find this issue. > > Am changing the “req_body” in the rest_methods.c, as per the REST API > server is expecting the payload value. > > If I change this “req_body” in *REST_POST* as well, and if the > *Call-Id length is > 56*, it crashes in *the POST call too*. > > Regards, > Agalya > > *From:* Users [mailto:users-bounces at lists.opensips.org] *On Behalf Of > *Ramachandran, Agalya (Contractor) > *Sent:* Tuesday, January 17, 2017 3:03 PM > *To:* OpenSIPS users mailling list >; Liviu Chircu > > *Subject:* [OpenSIPS-Users] async- issues- 2.2.2 > > Hi Liviu/team, > > When I try to do an asynchronous REST_PUT call in OpenSIPS 2.2.2, I > see the below observance and issues. > > All the calls are made from sipp client. > > *No* > > > > *Test Scenario * > > > > *Result/observation* > > 1. > > > > Call-Id length < 50 > > > > Works perfectly fine > > 2 > > > > Call-Id length >54 and < 56 > > > > No crash observed. But error in curl_multiperform > > 3. > > > > Call-Id length > 56 > > > > Opensips crashes at liburl. > > Please find the details for test 2 and test 3. > > I have tested with REST_POST with case 3, I didn’t observe any crashes. > > Please let me know what could cause this issue and how can I fix this? > > *Test2:* > > ** > > Jan 17 18:23:13 /usr/local/sbin/opensips[18554]: > ERROR:rest_client:start_async_http_req: curl_multi_perform: Invalid > multi handle > > Jan 17 18:23:13 /usr/local/sbin/opensips[18554]: > ERROR:rest_client:start_async_http_req: curl_multi_remove_handle: > Invalid multi handle > > *Test 3:* > > (gdb) bt > > #0 0x00007f370bccb9bb in curl_multi_add_handle () from /lib64/libcurl.so.4 > > #1 0x00007f370bf05521 in start_async_http_req > (msg=msg at entry=0x7f374db14270, method=method at entry=REST_CLIENT_PUT, > > url=0x7f374dad8178 "http://url", req_body=, > > req_ctype=, out_handle=out_handle at entry=0x7f374db204e0, > body=body at entry=0x7f374db204e8, ctype=0x7f374db204f8) > > at rest_methods.c:227 > > #2 0x00007f370bf0e2ca in w_async_rest_put (msg=0x7f374db14270, > resume_f=0x7ffc6f551680, resume_param=0x7ffc6f551690, > > gp_url=, gp_body=, gp_ctype= out>, body_pv=0x7f374daf5510 "N", > > ctype_pv=0x7f374daf55a8 "N", code_pv=0x7f374daf5670 "N") at > rest_client.c:579 > > #3 0x00007f370d24920f in t_handle_async (msg=0x7f374db14270, > a=0x7f374dad8508, resume_route=) at async.c:240 > > #4 0x000000000042d724 in do_action (a=a at entry=0x7f374dad8680, > msg=msg at entry=0x7f374db14270) at action.c:1863 > > #5 0x00000000004341cc in run_action_list (a=, > msg=0x7f374db14270) at action.c:172 > > #6 0x0000000000430769 in do_action (a=a at entry=0x7f374dad8760, > msg=msg at entry=0x7f374db14270) at action.c:1108 > > #7 0x000000000043454d in run_action_list (msg=, > a=) at action.c:172 > > #8 run_actions (a=, msg=0x7f374db14270) at action.c:137 > > #9 0x000000000042f8d7 in do_action (a=a at entry=0x7f374dad6b58, > msg=msg at entry=0x7f374db14270) at action.c:745 > > #10 0x0000000000434393 in run_action_list (msg=, > a=) at action.c:172 > > #11 run_actions (msg=0x7f374db14270, a=) at action.c:137 > > #12 run_top_route (a=, msg=msg at entry=0x7f374db14270) at > action.c:204 > > #13 0x000000000043bcba in receive_msg ( > > buf=0x858c20 "INVITE sip:+19084904567 at 10.10.10.05060 > SIP/2.0\r\nTo: \r\nFrom: > \"test > PA\";"..., > len=, > > rcv_info=rcv_info at entry=0x7ffc6f552c70, > existing_context=existing_context at entry=0x0) at receive.c:208 > > #14 0x00000000005b0b03 in udp_read_req (si=, > bytes_read=) at net/proto_udp/proto_udp.c:192 > > #15 0x000000000059b960 in handle_io (idx=, > event_type=, fm=) at net/net_udp.c:259 > > #16 io_wait_loop_epoll (h=, t=, > repeat=) at net/../io_wait_loop.h:225 > > #17 udp_rcv_loop (si=si at entry=0x7f374dacb6c8) at net/net_udp.c:308 > > #18 0x000000000059ce88 in udp_start_processes > (chd_rank=chd_rank at entry=0x845830 , > startup_done=startup_done at entry=0x0) > > at net/net_udp.c:372 > > #19 0x0000000000419f50 in main_loop () at main.c:671 > > #20 main (argc=, argv=) at main.c:1261 > > Regards, > Agalya > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From rrobson at greenlightcrm.com Wed Jan 18 08:28:18 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Wed, 18 Jan 2017 13:28:18 +0000 Subject: [OpenSIPS-Users] different data from MI and fifo Message-ID: <58abbcc9-42c2-eb49-831c-056b63d1f828@greenlightcrm.com> Hi, I'm using ruby to pull profile counts from opensips datagrams to push into influxdb (adapted from Rik Broers presentation at the sumit) If I run the fifo command at the command line I get different data than running the ruby script via the datagram interface influxdb = InfluxDB::Client.new udp: {host: '192.168.36.152', port: 8125} cprofiles = opensips.profile_get_values ('customer') FIFO value:: 0069 count=2 value:: 0079 count=41 value:: 0018 count=25 value:: 0016 count=8 value:: 0026 count=13 value:: 0066 count=8 value:: 0076 count=1 value:: 0017 count=4 value:: count=13 value:: 0064 count=6 value:: 0065 count=9 value:: 0012 count=63 value:: 0072 count=1 value:: 0063 count=2 value:: 0060 count=15 value:: 0021 count=3 value:: 0061 count=38 value:: 0080 count=1 value:: 2099 count=10 value:: 4199 count=1 MI "value:: 0069 count=2", "value:: 0079 count=36", "value:: 0018 count=32", "value:: 0016 count=9", "value:: 0026 count=15", "value:: 0066 count=8", "value:: 0076 count=1", "value:: 0017 count=4", "value:: count=14", "value:: 0064 count=6", "value:: 0065 count=9", "value:: 0012 count=69", "value:: 0063 count=2", "value:: 0060 count=20", "value:: 0021 count=3", "value:: 0061 count=37", "value:: 0080 count=1", "value:: 2099 count=11" apparet from the counts being different, which you would expect on live data the MI is missing the 4199 ( a call was in progress for this profile) and the 0072 value. Now this is either a bug in the MI or in the Ruby gem. I just don't know which. Would there be a simple script I can run to test the MI interface against the fifo interface? If this is OK then I'll bug report the ruby gem. Regards, -- Richard Robson Greenlight Support 01382 843843 support at greenlightcrm.com From spanda at 3clogic.com Wed Jan 18 08:36:52 2017 From: spanda at 3clogic.com (Sasmita Panda) Date: Wed, 18 Jan 2017 19:06:52 +0530 Subject: [OpenSIPS-Users] tcp with opensips . Message-ID: HI All, Earlier there is problem with running tcp with saving data in database at the same time . Is the problem get solved . If yes then in which version of opensips . I think , there was problem with openisps -1.6 . In heavy load it was not recomended to run tcp in same instance which is saving data in database too . Can anybody inform me whcih version i should use for this . *Thanks & Regards* *Sasmita Panda* *Network Testing and Software Engineer* *3CLogic , ph:07827611765* -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Wed Jan 18 08:45:18 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 18 Jan 2017 15:45:18 +0200 Subject: [OpenSIPS-Users] Introducing OpenSIPS 2.3 In-Reply-To: <99435f67-d572-ce75-531a-a5588935aa1d@opensips.org> References: <99435f67-d572-ce75-531a-a5588935aa1d@opensips.org> Message-ID: Reminder : one day left to the audio conference - 19th of January, 4pm GMT, https://www.uberconference.com/opensips Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/12/2017 06:39 PM, Bogdan-Andrei Iancu wrote: > > A new year has arrived, so it is the time for a new OpenSIPS major > release – forOpenSIPS version 2.3 . > > For this version, the main focus on development > is the*/“integration”/*, the integration ofOpenSIPSwith various > external entities. Why is integration so important to end up being the > main tag of a major release? Well, everybody in the VoIP world is > operating VoIP platforms/systems – and these are more than SIP Engines > (asOpenSIPSis). Indeed, the SIP Engine is the core and most important > part of the platform, but to build something usable and useful, you > need additional components into your platform like CDR/billing > engines, monitoring and tracing tools, data backends, non-SIP trunking > or more specialized SIP engines. Shortly you need your SIP Engine > (OpenSIPS, of course) to be able to easily integrate with all these > components. > > OpenSIPS2.3 brings some new and exciting integration capabilities, > that will definitely boost the value of your SIP platform: > > * extendedHomer/SIPCapture integration to > allow capturing of non-SIP data (transport level data, Management > Interface commands, REST queries and more); > * SIP-I support both in terms of passing-through and in terms of > converting SIP-I to SIP and vice-versa ; > * CGRates integration for powerful > rating/billing – everything in a simple and automatic way (via a > dedicated module); > * FreeSWITCH flavored Load-Balancing for a > more realistic and accurate traffic balancing over FreeSWITCH > clusters (as the load information is fetched in realtime from > FreeSWITCH); > * theEvent Engine > to provide > support for scenarios based on Subscribe/Notify model, where the > script execution may subscribe and resume later according to > certain events (like a dynamic implementation of the Push > Notification mechanism); > * extendedRabbitMQ support for custom > and flexible data injection directly from OpenSIPS script; > * extended Asynchronous support for more complex async scenarios > (like launch with no wait); > * more end-device integration (special SIP extensions). > > The timeline for OpenSIPS 2.3 is: > > * Beta Release – 13-17 March 2017 > * Stable Release – 24-28 April 2017 > * General Availability – 2nd of May 2017, duringOpenSIPS Summit > > > To talk more about the features of this new release, a publicaudio > conference will be > available on19th of January 2017, 4 pm GMT > , thanks to > the kind sponsorship of UberConference > . Anyone is welcome to join to find > out more details or to ask questions aboutOpenSIPS2.3 . > > This is a public and open conference, so no registration is needed, > but if you want to announce your intention to participate, please let > us know via the form on the blog post > . > > Best regards, > > -- > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Wed Jan 18 08:45:36 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Wed, 18 Jan 2017 15:45:36 +0200 Subject: [OpenSIPS-Users] async radius problem Message-ID: Hello, I have problem with async radius implementation. OS - CEntOs 7 Opensips 2.2.2 - git hub from 15.01.2017 Here pasrt of srcipt: onreply_route[outgoing] { ..... if (t_check_status("200")) { async( radius_send_auth("prepayout","prepayin"), return_prepay ); } } route[return_prepay] { xlog("L_ERR", "Radius return $rc"); } # end route return_prepay Here is part of Opensips log level 6: /usr/sbin/opensips[21026]: DBG:tm:update_totag_set: new totag /usr/sbin/opensips[21026]: DBG:tm:insert_timer_unsafe: [2]: 0x7fee75f19bd0 (36) /usr/sbin/opensips[21026]: DBG:tm:run_trans_callbacks: trans=0x7fee75f19b50, callback type 64, id 0 entered /usr/sbin/opensips[21005]: DBG:core:handle_sigs: status = 11 /usr/sbin/opensips[21005]: INFO:core:handle_sigs: child process 21026 exited by a signal 11 /usr/sbin/opensips[21005]: INFO:core:handle_sigs: core was not generated /usr/sbin/opensips[21005]: INFO:core:handle_sigs: terminating due to SIGCHLD /usr/sbin/opensips[21024]: INFO:core:sig_usr: signal 15 received /usr/sbin/opensips[21011]: INFO:core:sig_usr: signal 15 received /usr/sbin/opensips[21018]: INFO:core:sig_usr: signal 15 received Where is problem? Best regards, Dragomir -------------- next part -------------- An HTML attachment was scrubbed... URL: From xaled at web.de Wed Jan 18 09:09:09 2017 From: xaled at web.de (xaled) Date: Wed, 18 Jan 2017 15:09:09 +0100 Subject: [OpenSIPS-Users] How to parse XML Body? In-Reply-To: <5e264517-2c83-2808-4e29-f9418125ff7a@opensips.org> References: <012c01d266bf$841c7590$8c5560b0$@web.de> <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> <018601d26742$7d877ee0$78967ca0$@web.de> <4936e66b-ae31-a9fa-e260-a87ef6b24b20@opensips.org> <019a01d26746$00669460$0133bd20$@web.de> <01b601d26748$2bebb6e0$83c324a0$@web.de> <01428a9e-5f55-5a7e-154d-59c2f8e96ef0@opensips.org> <01f101d2674f$dadadee0$90909ca0$@web.de> <032b01d26833$cace6370$606b2a50$@web.de> <6969d0ff-96a6-56da-15f4-54f8cd0c116b@opensips.org> <009101d26d84$72050d10$560f2730$@web.de> <5e264517-2c83-2808-4e29-f9418125ff7a@opensips.org> Message-ID: <016e01d27194$712ba570$5382f050$@web.de> Hi Bogdan, works like a charm, thanks! As an additional bonus now I know how to work with the perl module ;) $rb(mime)[idx] is even more flexible. From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Dienstag, 17. Januar 2017 15:12 To: xaled ; 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi, There was a small typo in my regexp. The correct one is: $var(reg) = "/(.*)gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s"; xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); I tried it and it does the job. Regarding the usability of the $rb variable, yes you have a point. I was thinking of something like $rb(mime)[idx] to access also per mime. Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/13/2017 12:04 PM, xaled wrote: Hi Bogdan, thank you for looking at this issue. This regex does not work. I tried different combinations of the idea but it just not getting there. 2017-01-13T11:02:42.287766+01:00 ivr01 /usr/local/sbin/opensips[24845]: DBG:core:tr_eval_re: we must compile the regexp 2017-01-13T11:02:42.288116+01:00 ivr01 /usr/local/sbin/opensips[24845]: WARNING:core:parse_repl: \/ unknown escape in (.*)<\/gml:Coordinates(.*)/\2/s 2017-01-13T11:02:42.288464+01:00 ivr01 /usr/local/sbin/opensips[24845]: ERROR:core:subst_parser: unknown flag . in (.*)/gml:Coordinates>(.*)<\/gml:Coordin ates(.*)/\2/s 2017-01-13T11:02:42.288787+01:00 ivr01 /usr/local/sbin/opensips[24845]: ERROR:core:tr_eval_re: Can't compile regexp I managed to get it running with perl: use OpenSIPS qw ( log ); use OpenSIPS::Constants; use OpenSIPS::Message; sub parsePIDFLO { my $m = shift; my $body = $m->getBody(); ($coord) = $body =~ /Coordinates>(.*) ; asd asd Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi, Please try $var(reg) = "(.*)/gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s"; xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/06/2017 05:44 PM, xaled wrote: Hi Bogdan, can you give any hints on how to get the Coordinates values and not the whole xml body from the regex subst? Sorry for being not clever enough to figure it out myself. Thanks Hi Bogdan, $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); DBG:core:subst_run:matched shows the needed XML element with value, but not the value alone. The xlog output shows the whole XML body without gml:Coordinates. 2017-01-05T13:23:23.104982+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:tr_eval_re: Trying to apply reg exp [/gml:Coordinates>(.*)<\/gml:Coordinates/\1/] on : [#015#012 "pres:sip:+1234567 at test.com">#015#012 #015#012 #015#012 #015#012 #015#012 #015#012 #015#012 12.32 34.24#015#012 #015#012 #015#012 #015#012 #015#012 no#015#012 #015#012 #01 5#012 #015#012 #015#012 2016-8-02T04:13:23Z#015#012 #015#0 12#015#012#015#012] 2017-01-05T13:23:23.107376+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:tr_eval_re: we must compile the regexp 2017-01-05T13:23:23.107903+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_parser: ok, se is 0x7f39a 5d0a1f0 2017-01-05T13:23:23.108241+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_run: running. r=0 2017-01-05T13:23:23.111918+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_run: matched (404, 45): [ gml:Coordinates>12.32 34.24#015#012 "pres:sip:+1234567 at test.com">#015#0 12 #015#012 #015#012 #015#012 #015#012 #015#012 #015#012 <12.32 34.24>#015#012 #015#012 #015#012 #015#012 #015#012 no#015#012 #015#012 #015# 012 #015#012 #015#012 2016-8-02T04:13:23Z#015#012 #015#012 Thanks From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Donnerstag, 5. Januar 2017 13:12 To: OpenSIPS users mailling list >; xaled > Subject: Re: [OpenSIPS-Users] How to parse XML Body? Try $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From rrobson at greenlightcrm.com Wed Jan 18 12:47:05 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Wed, 18 Jan 2017 17:47:05 +0000 Subject: [OpenSIPS-Users] different data from MI and fifo [Solved Kinda] In-Reply-To: <58abbcc9-42c2-eb49-831c-056b63d1f828@greenlightcrm.com> References: <58abbcc9-42c2-eb49-831c-056b63d1f828@greenlightcrm.com> Message-ID: <70dceac7-2b5b-cd45-f782-ae82c2f91334@greenlightcrm.com> It looks like the Ruby is not parsing the returned data array correctly. I found out how to access MI datagrams directly from the command line and this is showing the correct information. R On 18/01/2017 13:28, Richard Robson wrote: > Hi, > > > I'm using ruby to pull profile counts from opensips datagrams to push > into influxdb (adapted from Rik Broers presentation at the sumit) > > If I run the fifo command at the command line I get different data > than running the ruby script via the datagram interface > > influxdb = InfluxDB::Client.new udp: {host: '192.168.36.152', port: 8125} > > cprofiles = opensips.profile_get_values ('customer') > > FIFO > > value:: 0069 count=2 > value:: 0079 count=41 > value:: 0018 count=25 > value:: 0016 count=8 > value:: 0026 count=13 > value:: 0066 count=8 > value:: 0076 count=1 > value:: 0017 count=4 > value:: count=13 > value:: 0064 count=6 > value:: 0065 count=9 > value:: 0012 count=63 > value:: 0072 count=1 > value:: 0063 count=2 > value:: 0060 count=15 > value:: 0021 count=3 > value:: 0061 count=38 > value:: 0080 count=1 > value:: 2099 count=10 > value:: 4199 count=1 > > > MI > > > "value:: 0069 count=2", > "value:: 0079 count=36", > "value:: 0018 count=32", > "value:: 0016 count=9", > "value:: 0026 count=15", > "value:: 0066 count=8", > "value:: 0076 count=1", > "value:: 0017 count=4", > "value:: count=14", > "value:: 0064 count=6", > "value:: 0065 count=9", > "value:: 0012 count=69", > "value:: 0063 count=2", > "value:: 0060 count=20", > "value:: 0021 count=3", > "value:: 0061 count=37", > "value:: 0080 count=1", > "value:: 2099 count=11" > > apparet from the counts being different, which you would expect on > live data the MI is missing the 4199 ( a call was in progress for this > profile) and the 0072 value. > > Now this is either a bug in the MI or in the Ruby gem. I just don't > know which. > Would there be a simple script I can run to test the MI interface > against the fifo interface? > If this is OK then I'll bug report the ruby gem. > > Regards, > -- Richard Robson Greenlight Support 01382 843843 support at greenlightcrm.com From Agalya_Ramachandran at comcast.com Wed Jan 18 13:17:17 2017 From: Agalya_Ramachandran at comcast.com (Ramachandran, Agalya (Contractor)) Date: Wed, 18 Jan 2017 18:17:17 +0000 Subject: [OpenSIPS-Users] async- issues- 2.2.2 In-Reply-To: <518a4bb0-f469-ce49-318f-108e09d8dd00@opensips.org> References: <4afe8b5419b74122ad85d626b5e12872@COPDCEX28.cable.comcast.com> <518a4bb0-f469-ce49-318f-108e09d8dd00@opensips.org> Message-ID: <9db8366c20274e289a11c722eac65189@COPDCEX28.cable.comcast.com> Hi Razvan, Got your point. I tried to increase the MAX_CONTENT_TYPE_LEN and tested async call and it is working fine without crash. But one more question. The same piece of code am using for sync REST_API query too in rest_put() method. There also print_buff is only being used. It is working absolutely fine in the case of sync call even if the MAX_CONTENT_TYPE_LEN – is 64. Wondering what would be the reason in sync call, it is working and in async it is not? Regards, Agalya From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Razvan Crainea Sent: Wednesday, January 18, 2017 4:29 AM To: users at lists.opensips.org Subject: Re: [OpenSIPS-Users] async- issues- 2.2.2 Hi, Ramachandran! The print_buff buffer is declared with length MAX_CONTENT_TYPE_LEN -> 64. Writing more than 64 bytes will lead to a buffer overflow, probably followed by a crash. If you want to suppor longer CallIDs, just increase the size of the buffer, or allocate the buffer with a size large enought to fit your callid length. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/17/2017 11:13 PM, Ramachandran, Agalya (Contractor) wrote: Hi Liviu, Found the exact issue what causes the crash. In start_async_http_req, under case PUT/POST, we have the following code blue color by default. But for my project scenario, I need to add call-id header too here, including that code in red color for your reference. if (req_ctype) { sprintf(print_buff, "Content-Type: %s", req_ctype); header_list = curl_slist_append(header_list, print_buff); sprintf(print_buff, "Call-Id: %s", instanceId); header_list = curl_slist_append(header_list, print_buff); w_curl_easy_setopt(handle, CURLOPT_HTTPHEADER, header_list); } If I try by removing the Call-Id header in the curl-slist, then it works perfectly fine in case of POST as well as PUT. How can I overcome this situation? Your guidance would help me a lot. Regards, Agalya From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Ramachandran, Agalya (Contractor) Sent: Tuesday, January 17, 2017 3:58 PM To: OpenSIPS users mailling list ; Liviu Chircu Subject: Re: [OpenSIPS-Users] async- issues- 2.2.2 Hi, Another information may help you to find this issue. Am changing the “req_body” in the rest_methods.c, as per the REST API server is expecting the payload value. If I change this “req_body” in REST_POST as well, and if the Call-Id length is > 56, it crashes in the POST call too. Regards, Agalya From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Ramachandran, Agalya (Contractor) Sent: Tuesday, January 17, 2017 3:03 PM To: OpenSIPS users mailling list >; Liviu Chircu > Subject: [OpenSIPS-Users] async- issues- 2.2.2 Hi Liviu/team, When I try to do an asynchronous REST_PUT call in OpenSIPS 2.2.2, I see the below observance and issues. All the calls are made from sipp client. No Test Scenario Result/observation 1. Call-Id length < 50 Works perfectly fine 2 Call-Id length >54 and < 56 No crash observed. But error in curl_multiperform 3. Call-Id length > 56 Opensips crashes at liburl. Please find the details for test 2 and test 3. I have tested with REST_POST with case 3, I didn’t observe any crashes. Please let me know what could cause this issue and how can I fix this? Test2: Jan 17 18:23:13 /usr/local/sbin/opensips[18554]: ERROR:rest_client:start_async_http_req: curl_multi_perform: Invalid multi handle Jan 17 18:23:13 /usr/local/sbin/opensips[18554]: ERROR:rest_client:start_async_http_req: curl_multi_remove_handle: Invalid multi handle Test 3: (gdb) bt #0 0x00007f370bccb9bb in curl_multi_add_handle () from /lib64/libcurl.so.4 #1 0x00007f370bf05521 in start_async_http_req (msg=msg at entry=0x7f374db14270, method=method at entry=REST_CLIENT_PUT, url=0x7f374dad8178 "http://url", req_body=, req_ctype=, out_handle=out_handle at entry=0x7f374db204e0, body=body at entry=0x7f374db204e8, ctype=0x7f374db204f8) at rest_methods.c:227 #2 0x00007f370bf0e2ca in w_async_rest_put (msg=0x7f374db14270, resume_f=0x7ffc6f551680, resume_param=0x7ffc6f551690, gp_url=, gp_body=, gp_ctype=, body_pv=0x7f374daf5510 "N", ctype_pv=0x7f374daf55a8 "N", code_pv=0x7f374daf5670 "N") at rest_client.c:579 #3 0x00007f370d24920f in t_handle_async (msg=0x7f374db14270, a=0x7f374dad8508, resume_route=) at async.c:240 #4 0x000000000042d724 in do_action (a=a at entry=0x7f374dad8680, msg=msg at entry=0x7f374db14270) at action.c:1863 #5 0x00000000004341cc in run_action_list (a=, msg=0x7f374db14270) at action.c:172 #6 0x0000000000430769 in do_action (a=a at entry=0x7f374dad8760, msg=msg at entry=0x7f374db14270) at action.c:1108 #7 0x000000000043454d in run_action_list (msg=, a=) at action.c:172 #8 run_actions (a=, msg=0x7f374db14270) at action.c:137 #9 0x000000000042f8d7 in do_action (a=a at entry=0x7f374dad6b58, msg=msg at entry=0x7f374db14270) at action.c:745 #10 0x0000000000434393 in run_action_list (msg=, a=) at action.c:172 #11 run_actions (msg=0x7f374db14270, a=) at action.c:137 #12 run_top_route (a=, msg=msg at entry=0x7f374db14270) at action.c:204 #13 0x000000000043bcba in receive_msg ( buf=0x858c20 "INVITE sip:+19084904567 at 10.10.10.05060 SIP/2.0\r\nTo: \r\nFrom: \"test PA\";"..., len=, rcv_info=rcv_info at entry=0x7ffc6f552c70, existing_context=existing_context at entry=0x0) at receive.c:208 #14 0x00000000005b0b03 in udp_read_req (si=, bytes_read=) at net/proto_udp/proto_udp.c:192 #15 0x000000000059b960 in handle_io (idx=, event_type=, fm=) at net/net_udp.c:259 #16 io_wait_loop_epoll (h=, t=, repeat=) at net/../io_wait_loop.h:225 #17 udp_rcv_loop (si=si at entry=0x7f374dacb6c8) at net/net_udp.c:308 #18 0x000000000059ce88 in udp_start_processes (chd_rank=chd_rank at entry=0x845830 , startup_done=startup_done at entry=0x0) at net/net_udp.c:372 #19 0x0000000000419f50 in main_loop () at main.c:671 #20 main (argc=, argv=) at main.c:1261 Regards, Agalya _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahmedmunir007 at gmail.com Wed Jan 18 13:30:49 2017 From: ahmedmunir007 at gmail.com (Ahmed Munir) Date: Wed, 18 Jan 2017 13:30:49 -0500 Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service Message-ID: Hi, I'm currently seeing the warnings when I start opensips service; Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: timer job has a 1500000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: timer job has a 1500000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: timer job has a 1500000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: utimer job has a 2290000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: INFO:core:do_action: max while loops are encountered Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 2470 ms), it may over lap.. I've tried to update the source code for timer.c (line#: 190) ref: https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split, but didn't work at all. Currently running 8 child processors, see below; [root at qorblpsisprxyd1 ]# opensips -V version: opensips 2.2.2 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_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_lt, epoll_et, sigio_rt, select. main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7 [root at qorblpsisprxyd1 ]# opensipsctl fifo ps Process:: ID=0 PID=3083 Type=attendant Process:: ID=1 PID=3085 Type=MI FIFO Process:: ID=2 PID=3086 Type=time_keeper Process:: ID=3 PID=3088 Type=timer Process:: ID=4 PID=3089 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=5 PID=3091 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=6 PID=3092 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=7 PID=3094 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=8 PID=3096 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=9 PID=3098 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=10 PID=3100 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=11 PID=3102 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=12 PID=3104 Type=Timer handler I would like to know what changes required to fix this change? Please advise. -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Agalya_Ramachandran at comcast.com Wed Jan 18 16:55:58 2017 From: Agalya_Ramachandran at comcast.com (Ramachandran, Agalya (Contractor)) Date: Wed, 18 Jan 2017 21:55:58 +0000 Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service In-Reply-To: References: Message-ID: <92c380d81d5c45a9a2bce09fe344188e@COPDCEX28.cable.comcast.com> Same with my case too. Regards, Agalya From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Ahmed Munir Sent: Wednesday, January 18, 2017 1:31 PM To: OpenSIPs Users Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service Hi, I'm currently seeing the warnings when I start opensips service; Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: timer job has a 1500000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: timer job has a 1500000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: timer job has a 1500000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: utimer job has a 2290000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: INFO:core:do_action: max while loops are encountered Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 2470 ms), it may over lap.. I've tried to update the source code for timer.c (line#: 190) ref: https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split, but didn't work at all. Currently running 8 child processors, see below; [root at qorblpsisprxyd1 ]# opensips -V version: opensips 2.2.2 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_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_lt, epoll_et, sigio_rt, select. main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7 [root at qorblpsisprxyd1 ]# opensipsctl fifo ps Process:: ID=0 PID=3083 Type=attendant Process:: ID=1 PID=3085 Type=MI FIFO Process:: ID=2 PID=3086 Type=time_keeper Process:: ID=3 PID=3088 Type=timer Process:: ID=4 PID=3089 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=5 PID=3091 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=6 PID=3092 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=7 PID=3094 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=8 PID=3096 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=9 PID=3098 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=10 PID=3100 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=11 PID=3102 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=12 PID=3104 Type=Timer handler I would like to know what changes required to fix this change? Please advise. -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcunningham at voisonics.com Wed Jan 18 18:01:54 2017 From: dcunningham at voisonics.com (David Cunningham) Date: Thu, 19 Jan 2017 10:01:54 +1100 Subject: [OpenSIPS-Users] Return body/string from Perl library In-Reply-To: References: Message-ID: Ah, thank you. On 18 January 2017 at 19:43, Bogdan-Andrei Iancu wrote: > Hi David, > > You are on the wrong mailing list :) > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developerhttp://www.opensips-solutions.com > > On 01/18/2017 02:43 AM, David Cunningham wrote: > > Hello, > > We are using Kamailio's perl module and want our custom library to set the > body on a SIP message. > > Is it possible to set a SIP message body from within Perl, or can we > return a string to the Kamailio configuration to then use with set_body()? > > Thanks for any advice. > > -- > David Cunningham, Voisonics > http://voisonics.com/ > USA: +1 213 221 1092 <(213)%20221-1092> > Australia: +61 (0) 2 8063 9019 <+61%202%208063%209019> > > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > -- David Cunningham, Voisonics http://voisonics.com/ USA: +1 213 221 1092 Australia: +61 (0) 2 8063 9019 -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Thu Jan 19 03:25:43 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Thu, 19 Jan 2017 10:25:43 +0200 Subject: [OpenSIPS-Users] async radius problem In-Reply-To: References: Message-ID: <4fca4555-64a8-c3cd-d9cf-0856e722ee6b@opensips.org> Hi, Dragomir! Currently async operations are only available for requests, not for replies. In the onreply_route you can only use synchronous operations for now. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/18/2017 03:45 PM, Dragomir Haralambiev wrote: > Hello, > > I have problem with async radius implementation. > OS - CEntOs 7 > Opensips 2.2.2 - git hub from 15.01.2017 > > Here pasrt of srcipt: > > onreply_route[outgoing] { > ..... > if (t_check_status("200")) { > async( radius_send_auth("prepayout","prepayin"), return_prepay ); > } > } > > > route[return_prepay] { > xlog("L_ERR", "Radius return $rc"); > } # end route return_prepay > > Here is part of Opensips log level 6: > > /usr/sbin/opensips[21026]: DBG:tm:update_totag_set: new totag > /usr/sbin/opensips[21026]: DBG:tm:insert_timer_unsafe: [2]: > 0x7fee75f19bd0 (36) > /usr/sbin/opensips[21026]: DBG:tm:run_trans_callbacks: > trans=0x7fee75f19b50, callback type 64, id 0 entered > /usr/sbin/opensips[21005]: DBG:core:handle_sigs: status = 11 > /usr/sbin/opensips[21005]: INFO:core:handle_sigs: child process 21026 > exited by a signal 11 > /usr/sbin/opensips[21005]: INFO:core:handle_sigs: core was not generated > /usr/sbin/opensips[21005]: INFO:core:handle_sigs: terminating due to > SIGCHLD > /usr/sbin/opensips[21024]: INFO:core:sig_usr: signal 15 received > /usr/sbin/opensips[21011]: INFO:core:sig_usr: signal 15 received > /usr/sbin/opensips[21018]: INFO:core:sig_usr: signal 15 received > > > Where is problem? > > Best regards, > Dragomir > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Thu Jan 19 03:30:19 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Thu, 19 Jan 2017 10:30:19 +0200 Subject: [OpenSIPS-Users] async- issues- 2.2.2 In-Reply-To: <9db8366c20274e289a11c722eac65189@COPDCEX28.cable.comcast.com> References: <4afe8b5419b74122ad85d626b5e12872@COPDCEX28.cable.comcast.com> <518a4bb0-f469-ce49-318f-108e09d8dd00@opensips.org> <9db8366c20274e289a11c722eac65189@COPDCEX28.cable.comcast.com> Message-ID: You have my answer inline. Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/18/2017 08:17 PM, Ramachandran, Agalya (Contractor) wrote: > > Hi Razvan, > > Got your point.I tried to increase the MAX_CONTENT_TYPE_LEN and > tested async call and it is working fine without crash. > > But one more question. > > The same piece of code am using for *sync REST_API* query too in > rest_put() method. There also print_buff is only being used. > > It is working absolutely fine in the case of sync call even if the > MAX_CONTENT_TYPE_LEN – is 64. > > Wondering what would be the reason in sync call, it is working and in > async it is not? > Pure luck. You are doing a buffer overflow, overwriting the data section. Probably when doing sync calls, nobody is using the data you are overwriting. But if it doesn't crash it doesn't mean it is ok :). > > Regards, > > Agalya > > *From:*Users [mailto:users-bounces at lists.opensips.org] *On Behalf Of > *Razvan Crainea > *Sent:* Wednesday, January 18, 2017 4:29 AM > *To:* users at lists.opensips.org > *Subject:* Re: [OpenSIPS-Users] async- issues- 2.2.2 > > Hi, Ramachandran! > > The print_buff buffer is declared with length MAX_CONTENT_TYPE_LEN -> > 64. Writing more than 64 bytes will lead to a buffer overflow, > probably followed by a crash. > If you want to suppor longer CallIDs, just increase the size of the > buffer, or allocate the buffer with a size large enought to fit your > callid length. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > > On 01/17/2017 11:13 PM, Ramachandran, Agalya (Contractor) wrote: > > Hi Liviu, > > Found the exact issue what causes the crash. > > In start_async_http_req, under case PUT/POST, we have the > following code blue color by default. > > But for my project scenario, I need to add call-id header too > here, including that code in red color for your reference. > > if (req_ctype) { > > sprintf(print_buff, "Content-Type: %s", req_ctype); > > header_list = curl_slist_append(header_list, print_buff); > > sprintf(print_buff, "Call-Id: %s", instanceId); > > header_list = curl_slist_append(header_list, print_buff); > > w_curl_easy_setopt(handle, CURLOPT_HTTPHEADER, header_list); > > } > > If I try by removing the Call-Id header in the curl-slist, then it > works perfectly fine in case of POST as well as PUT. > > How can I overcome this situation? Your guidance would help me a lot. > > Regards, > Agalya > > *From:* Users [mailto:users-bounces at lists.opensips.org] *On Behalf > Of *Ramachandran, Agalya (Contractor) > *Sent:* Tuesday, January 17, 2017 3:58 PM > *To:* OpenSIPS users mailling list > ; Liviu Chircu > > *Subject:* Re: [OpenSIPS-Users] async- issues- 2.2.2 > > Hi, > > Another information may help you to find this issue. > > Am changing the “req_body” in the rest_methods.c, as per the REST > API server is expecting the payload value. > > If I change this “req_body” in *REST_POST* as well, and if the > *Call-Id length is > 56*, it crashes in *the POST call too*. > > Regards, > Agalya > > *From:* Users [mailto:users-bounces at lists.opensips.org] *On Behalf > Of *Ramachandran, Agalya (Contractor) > *Sent:* Tuesday, January 17, 2017 3:03 PM > *To:* OpenSIPS users mailling list >; Liviu Chircu > > > *Subject:* [OpenSIPS-Users] async- issues- 2.2.2 > > Hi Liviu/team, > > When I try to do an asynchronous REST_PUT call in OpenSIPS 2.2.2, > I see the below observance and issues. > > All the calls are made from sipp client. > > *No* > > > > *Test Scenario * > > > > *Result/observation* > > 1. > > > > Call-Id length < 50 > > > > Works perfectly fine > > 2 > > > > Call-Id length >54 and < 56 > > > > No crash observed. But error in curl_multiperform > > 3. > > > > Call-Id length > 56 > > > > Opensips crashes at liburl. > > Please find the details for test 2 and test 3. > > I have tested with REST_POST with case 3, I didn’t observe any > crashes. > > Please let me know what could cause this issue and how can I fix this? > > *Test2:* > > ** > > Jan 17 18:23:13 /usr/local/sbin/opensips[18554]: > ERROR:rest_client:start_async_http_req: curl_multi_perform: > Invalid multi handle > > Jan 17 18:23:13 /usr/local/sbin/opensips[18554]: > ERROR:rest_client:start_async_http_req: curl_multi_remove_handle: > Invalid multi handle > > *Test 3:* > > (gdb) bt > > #0 0x00007f370bccb9bb in curl_multi_add_handle () from > /lib64/libcurl.so.4 > > #1 0x00007f370bf05521 in start_async_http_req > (msg=msg at entry=0x7f374db14270, method=method at entry=REST_CLIENT_PUT, > > url=0x7f374dad8178 "http://url", req_body=, > > req_ctype=, > out_handle=out_handle at entry=0x7f374db204e0, > body=body at entry=0x7f374db204e8, ctype=0x7f374db204f8) > > at rest_methods.c:227 > > #2 0x00007f370bf0e2ca in w_async_rest_put (msg=0x7f374db14270, > resume_f=0x7ffc6f551680, resume_param=0x7ffc6f551690, > > gp_url=, gp_body=, > gp_ctype=, body_pv=0x7f374daf5510 "N", > > ctype_pv=0x7f374daf55a8 "N", code_pv=0x7f374daf5670 "N") at > rest_client.c:579 > > #3 0x00007f370d24920f in t_handle_async (msg=0x7f374db14270, > a=0x7f374dad8508, resume_route=) at async.c:240 > > #4 0x000000000042d724 in do_action (a=a at entry=0x7f374dad8680, > msg=msg at entry=0x7f374db14270) at action.c:1863 > > #5 0x00000000004341cc in run_action_list (a=, > msg=0x7f374db14270) at action.c:172 > > #6 0x0000000000430769 in do_action (a=a at entry=0x7f374dad8760, > msg=msg at entry=0x7f374db14270) at action.c:1108 > > #7 0x000000000043454d in run_action_list (msg=, > a=) at action.c:172 > > #8 run_actions (a=, msg=0x7f374db14270) at > action.c:137 > > #9 0x000000000042f8d7 in do_action (a=a at entry=0x7f374dad6b58, > msg=msg at entry=0x7f374db14270) at action.c:745 > > #10 0x0000000000434393 in run_action_list (msg=, > a=) at action.c:172 > > #11 run_actions (msg=0x7f374db14270, a=) at > action.c:137 > > #12 run_top_route (a=, > msg=msg at entry=0x7f374db14270) at action.c:204 > > #13 0x000000000043bcba in receive_msg ( > > buf=0x858c20 "INVITE sip:+19084904567 at 10.10.10.05060 > SIP/2.0\r\nTo: > \r\nFrom: \"test > PA\";"..., > len=, > > rcv_info=rcv_info at entry=0x7ffc6f552c70, > existing_context=existing_context at entry=0x0) at receive.c:208 > > #14 0x00000000005b0b03 in udp_read_req (si=, > bytes_read=) at net/proto_udp/proto_udp.c:192 > > #15 0x000000000059b960 in handle_io (idx=, > event_type=, fm=) at net/net_udp.c:259 > > #16 io_wait_loop_epoll (h=, t=, > repeat=) at net/../io_wait_loop.h:225 > > #17 udp_rcv_loop (si=si at entry=0x7f374dacb6c8) at net/net_udp.c:308 > > #18 0x000000000059ce88 in udp_start_processes > (chd_rank=chd_rank at entry=0x845830 , > startup_done=startup_done at entry=0x0) > > at net/net_udp.c:372 > > #19 0x0000000000419f50 in main_loop () at main.c:671 > > #20 main (argc=, argv=) at main.c:1261 > > Regards, > Agalya > > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Thu Jan 19 03:32:35 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Thu, 19 Jan 2017 10:32:35 +0200 Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service In-Reply-To: <92c380d81d5c45a9a2bce09fe344188e@COPDCEX28.cable.comcast.com> References: <92c380d81d5c45a9a2bce09fe344188e@COPDCEX28.cable.comcast.com> Message-ID: <2d785128-affa-c955-e779-1d4305ec1119@opensips.org> When starting opensips, is there any opensips process that is using more than 80% of a core? If so, can you pinpoint the PID in the opensipsctl ps command? Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/18/2017 11:55 PM, Ramachandran, Agalya (Contractor) wrote: > > Same with my case too. > > Regards, > Agalya > > *From:*Users [mailto:users-bounces at lists.opensips.org] *On Behalf Of > *Ahmed Munir > *Sent:* Wednesday, January 18, 2017 1:31 PM > *To:* OpenSIPs Users > *Subject:* [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service > > Hi, > > I'm currently seeing the warnings when I start opensips service; > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a 1500000 > us delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a 1500000 us > delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a 1500000 us > delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: utimer job has a 2290000 us > delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > INFO:core:do_action: max while loops are encountered > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: > WARNING:core:utimer_ticker: utimer task already scheduled > for 190 ms (now 2470 ms), it may over > lap.. > > I've tried to update the source code for timer.c (line#: 190) ref: > https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split, > but didn't work at all. > > Currently running 8 child processors, see below; > > [root at qorblpsisprxyd1 ]# opensips -V > version: opensips 2.2.2 (x86_64/linux) > flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, > F_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_lt, epoll_et, sigio_rt, select. > main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7 > > > [root at qorblpsisprxyd1 ]# opensipsctl fifo ps > Process:: ID=0 PID=3083 Type=attendant > Process:: ID=1 PID=3085 Type=MI FIFO > Process:: ID=2 PID=3086 Type=time_keeper > Process:: ID=3 PID=3088 Type=timer > Process:: ID=4 PID=3089 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=5 PID=3091 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=6 PID=3092 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=7 PID=3094 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=8 PID=3096 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=9 PID=3098 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=10 PID=3100 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=11 PID=3102 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=12 PID=3104 Type=Timer handler > > I would like to know what changes required to fix this change? Please > advise. > > > -- > > Regards, > > Ahmed Munir Chohan > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Thu Jan 19 03:40:14 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Thu, 19 Jan 2017 10:40:14 +0200 Subject: [OpenSIPS-Users] async radius problem In-Reply-To: <4fca4555-64a8-c3cd-d9cf-0856e722ee6b@opensips.org> References: <4fca4555-64a8-c3cd-d9cf-0856e722ee6b@opensips.org> Message-ID: Hi, Thanks for your quick replay. Please add this information in AAA_Radius module. Best regards, Dragomir 2017-01-19 10:25 GMT+02:00 Răzvan Crainea : > Hi, Dragomir! > > Currently async operations are only available for requests, not for > replies. In the onreply_route you can only use synchronous operations for > now. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutionswww.opensips-solutions.com > > On 01/18/2017 03:45 PM, Dragomir Haralambiev wrote: > > Hello, > > I have problem with async radius implementation. > OS - CEntOs 7 > Opensips 2.2.2 - git hub from 15.01.2017 > > Here pasrt of srcipt: > > onreply_route[outgoing] { > ..... > if (t_check_status("200")) { > async( radius_send_auth("prepayout","prepayin"), return_prepay ); > } > } > > > route[return_prepay] { > xlog("L_ERR", "Radius return $rc"); > } # end route return_prepay > > Here is part of Opensips log level 6: > > /usr/sbin/opensips[21026]: DBG:tm:update_totag_set: new totag > /usr/sbin/opensips[21026]: DBG:tm:insert_timer_unsafe: [2]: > 0x7fee75f19bd0 (36) > /usr/sbin/opensips[21026]: DBG:tm:run_trans_callbacks: > trans=0x7fee75f19b50, callback type 64, id 0 entered > /usr/sbin/opensips[21005]: DBG:core:handle_sigs: status = 11 > /usr/sbin/opensips[21005]: INFO:core:handle_sigs: child process 21026 > exited by a signal 11 > /usr/sbin/opensips[21005]: INFO:core:handle_sigs: core was not generated > /usr/sbin/opensips[21005]: INFO:core:handle_sigs: terminating due to > SIGCHLD > /usr/sbin/opensips[21024]: INFO:core:sig_usr: signal 15 received > /usr/sbin/opensips[21011]: INFO:core:sig_usr: signal 15 received > /usr/sbin/opensips[21018]: INFO:core:sig_usr: signal 15 received > > > Where is problem? > > Best regards, > Dragomir > > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Thu Jan 19 04:03:26 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Thu, 19 Jan 2017 11:03:26 +0200 Subject: [OpenSIPS-Users] async radius problem In-Reply-To: References: <4fca4555-64a8-c3cd-d9cf-0856e722ee6b@opensips.org> Message-ID: <56e53b2b-e194-7406-3311-818111833bc1@opensips.org> Actually this is a characteristic of the async engine, not only the AAA_Radius module. I check to see where is the best place to specify this info. Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/19/2017 10:40 AM, Dragomir Haralambiev wrote: > Hi, > > Thanks for your quick replay. > > Please add this information in AAA_Radius module. > > Best regards, > Dragomir > > 2017-01-19 10:25 GMT+02:00 Răzvan Crainea >: > > Hi, Dragomir! > > Currently async operations are only available for requests, not > for replies. In the onreply_route you can only use synchronous > operations for now. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > > On 01/18/2017 03:45 PM, Dragomir Haralambiev wrote: >> Hello, >> >> I have problem with async radius implementation. >> OS - CEntOs 7 >> Opensips 2.2.2 - git hub from 15.01.2017 >> >> Here pasrt of srcipt: >> >> onreply_route[outgoing] { >> ..... >> if (t_check_status("200")) { >> async( radius_send_auth("prepayout","prepayin"), return_prepay ); >> } >> } >> >> >> route[return_prepay] { >> xlog("L_ERR", "Radius return $rc"); >> } # end route return_prepay >> >> Here is part of Opensips log level 6: >> >> /usr/sbin/opensips[21026]: DBG:tm:update_totag_set: new totag >> /usr/sbin/opensips[21026]: DBG:tm:insert_timer_unsafe: [2]: >> 0x7fee75f19bd0 (36) >> /usr/sbin/opensips[21026]: DBG:tm:run_trans_callbacks: >> trans=0x7fee75f19b50, callback type 64, id 0 entered >> /usr/sbin/opensips[21005]: DBG:core:handle_sigs: status = 11 >> /usr/sbin/opensips[21005]: INFO:core:handle_sigs: child process >> 21026 exited by a signal 11 >> /usr/sbin/opensips[21005]: INFO:core:handle_sigs: core was not >> generated >> /usr/sbin/opensips[21005]: INFO:core:handle_sigs: terminating >> due to SIGCHLD >> /usr/sbin/opensips[21024]: INFO:core:sig_usr: signal 15 received >> /usr/sbin/opensips[21011]: INFO:core:sig_usr: signal 15 received >> /usr/sbin/opensips[21018]: INFO:core:sig_usr: signal 15 received >> >> >> Where is problem? >> >> Best regards, >> Dragomir >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > _______________________________________________ Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Thu Jan 19 04:14:28 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Thu, 19 Jan 2017 11:14:28 +0200 Subject: [OpenSIPS-Users] async radius problem In-Reply-To: <56e53b2b-e194-7406-3311-818111833bc1@opensips.org> References: <4fca4555-64a8-c3cd-d9cf-0856e722ee6b@opensips.org> <56e53b2b-e194-7406-3311-818111833bc1@opensips.org> Message-ID: Thanks !!!! 2017-01-19 11:03 GMT+02:00 Răzvan Crainea : > Actually this is a characteristic of the async engine, not only the > AAA_Radius module. I check to see where is the best place to specify this > info. > > Best regards, > > Răzvan Crainea > OpenSIPS Solutionswww.opensips-solutions.com > > On 01/19/2017 10:40 AM, Dragomir Haralambiev wrote: > > Hi, > > Thanks for your quick replay. > > Please add this information in AAA_Radius module. > > Best regards, > Dragomir > > 2017-01-19 10:25 GMT+02:00 Răzvan Crainea : > >> Hi, Dragomir! >> >> Currently async operations are only available for requests, not for >> replies. In the onreply_route you can only use synchronous operations for >> now. >> >> Best regards, >> >> Răzvan Crainea >> OpenSIPS Solutionswww.opensips-solutions.com >> >> On 01/18/2017 03:45 PM, Dragomir Haralambiev wrote: >> >> Hello, >> >> I have problem with async radius implementation. >> OS - CEntOs 7 >> Opensips 2.2.2 - git hub from 15.01.2017 >> >> Here pasrt of srcipt: >> >> onreply_route[outgoing] { >> ..... >> if (t_check_status("200")) { >> async( radius_send_auth("prepayout","prepayin"), return_prepay ); >> } >> } >> >> >> route[return_prepay] { >> xlog("L_ERR", "Radius return $rc"); >> } # end route return_prepay >> >> Here is part of Opensips log level 6: >> >> /usr/sbin/opensips[21026]: DBG:tm:update_totag_set: new totag >> /usr/sbin/opensips[21026]: DBG:tm:insert_timer_unsafe: [2]: >> 0x7fee75f19bd0 (36) >> /usr/sbin/opensips[21026]: DBG:tm:run_trans_callbacks: >> trans=0x7fee75f19b50, callback type 64, id 0 entered >> /usr/sbin/opensips[21005]: DBG:core:handle_sigs: status = 11 >> /usr/sbin/opensips[21005]: INFO:core:handle_sigs: child process 21026 >> exited by a signal 11 >> /usr/sbin/opensips[21005]: INFO:core:handle_sigs: core was not generated >> /usr/sbin/opensips[21005]: INFO:core:handle_sigs: terminating due to >> SIGCHLD >> /usr/sbin/opensips[21024]: INFO:core:sig_usr: signal 15 received >> /usr/sbin/opensips[21011]: INFO:core:sig_usr: signal 15 received >> /usr/sbin/opensips[21018]: INFO:core:sig_usr: signal 15 received >> >> >> Where is problem? >> >> Best regards, >> Dragomir >> >> >> _______________________________________________ >> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> _______________________________________________ Users mailing list >> Users at lists.opensips.org http://lists.opensips.org/cgi- >> bin/mailman/listinfo/users > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Thu Jan 19 05:53:41 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Thu, 19 Jan 2017 12:53:41 +0200 Subject: [OpenSIPS-Users] How to parse XML Body? In-Reply-To: <016e01d27194$712ba570$5382f050$@web.de> References: <012c01d266bf$841c7590$8c5560b0$@web.de> <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> <018601d26742$7d877ee0$78967ca0$@web.de> <4936e66b-ae31-a9fa-e260-a87ef6b24b20@opensips.org> <019a01d26746$00669460$0133bd20$@web.de> <01b601d26748$2bebb6e0$83c324a0$@web.de> <01428a9e-5f55-5a7e-154d-59c2f8e96ef0@opensips.org> <01f101d2674f$dadadee0$90909ca0$@web.de> <032b01d26833$cace6370$606b2a50$@web.de> <6969d0ff-96a6-56da-15f4-54f8cd0c116b@opensips.org> <009101d26d84$72050d10$560f2730$@web.de> <5e264517-2c83-2808-4e29-f9418125ff7a@opensips.org> <016e01d27194$712ba570$5382f050$@web.de> Message-ID: <603ad545-bf7e-4adf-a4d1-7fd8be0f01f1@opensips.org> Hi, To be honest I'm not good on perl, but if you can do it directly at script level, it it cleaner and more efficient. Also, check this https://github.com/OpenSIPS/opensips/commit/d509aa63698bc26fde390a4b707dbf2be31f5de5 Thanks and Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/18/2017 04:09 PM, xaled wrote: > > Hi Bogdan, > > works like a charm, thanks! > > As an additional bonus now I know how to work with the perl module ;) > > $rb(mime)[idx] is even more flexible. > > *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] > *Sent:* Dienstag, 17. Januar 2017 15:12 > *To:* xaled ; 'OpenSIPS users mailling list' > > *Subject:* Re: [OpenSIPS-Users] How to parse XML Body? > > Hi, > > There was a small typo in my regexp. The correct one is: > > $var(reg) = "/(.*)gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s"; > xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); > > I tried it and it does the job. > > Regarding the usability of the $rb variable, yes you have a point. I > was thinking of something like $rb(mime)[idx] to access also per mime. > > Best regards, > > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 01/13/2017 12:04 PM, xaled wrote: > > Hi Bogdan, > > thank you for looking at this issue. This regex does not work. I > tried different combinations of the idea but it just not getting > there. > > 2017-01-13T11:02:42.287766+01:00 ivr01 > /usr/local/sbin/opensips[24845]: DBG:core:tr_eval_re: we must > compile the regexp > > 2017-01-13T11:02:42.288116+01:00 ivr01 > /usr/local/sbin/opensips[24845]: WARNING:core:parse_repl: \/ > unknown escape in (.*)<\/gml:Coordinates(.*)/\2/s > > 2017-01-13T11:02:42.288464+01:00 ivr01 > /usr/local/sbin/opensips[24845]: ERROR:core:subst_parser: unknown > flag . in (.*)/gml:Coordinates>(.*)<\/gml:Coordin > > ates(.*)/\2/s > > 2017-01-13T11:02:42.288787+01:00 ivr01 > /usr/local/sbin/opensips[24845]: ERROR:core:tr_eval_re: Can't > compile regexp > > I managed to get it running with perl: > > use OpenSIPS qw ( log ); > > use OpenSIPS::Constants; > > use OpenSIPS::Message; > > sub parsePIDFLO { > > my $m = shift; > > my $body = $m->getBody(); > > ($coord) = $body =~ /Coordinates>(.*) > my ($long, $lat) = split( /\s+/, $coord ); > > Btw it would be great to be able to address the xml body by > something like this: > > rb[application/pidf+xml] or rb["application/pidf+xml"] otherwise > if bodies come in different order rb[1] would not work. > > Thanks > > *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] > *Sent:* Mittwoch, 11. Januar 2017 11:05 > *To:* OpenSIPS users mailling list > ; asd asd > > *Subject:* Re: [OpenSIPS-Users] How to parse XML Body? > > Hi, > > Please try > > $var(reg) = "(.*)/gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s"; > xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); > > Regards, > > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > > http://www.opensips-solutions.com > > On 01/06/2017 05:44 PM, xaled wrote: > > Hi Bogdan, > > can you give any hints on how to get the Coordinates values > and not the whole xml body from the regex subst? > > Sorry for being not clever enough to figure it out myself. > > Thanks > > Hi Bogdan, > > $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; > > xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); > > DBG:core:subst_run:matched shows the needed XML element with > value, but not the value alone. The xlog output shows the > whole XML body without gml:Coordinates. > > 2017-01-05T13:23:23.104982+01:00 ivr01 > /usr/local/sbin/opensips[2227]: DBG:core:tr_eval_re: Trying to > apply reg > > exp [/gml:Coordinates>(.*)<\/gml:Coordinates/\1/] on : [ version="1.0" encoding="UTF-8"?>#015#012 > ns="urn:ietf:params:xml:ns:pidf" > xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" > xmlns:gml="urn:opengis:specificat > > ion:gml:schema-xsd:feature:v3.0" > entity="pres:sip:+1234567 at test.com" > >#015#012 id="PDT">#015#012 > tatus>#015#012 #015#012 #015#012 > #015#012 > id="point1" srsName="epsg:4346">#015#012 > 12.32 34.24#015#012 > > oint>#015#012 #015#012 > #015#012 #015#012 > > smission-allowed>no#015#012 > #015#012 #01 > > 5#012 #015#012 #015#012 > 2016-8-02T04:13:23Z#015#012 #015#0 > > 12#015#012#015#012] > > 2017-01-05T13:23:23.107376+01:00 ivr01 > /usr/local/sbin/opensips[2227]: DBG:core:tr_eval_re: we must > compile the > > regexp > > 2017-01-05T13:23:23.107903+01:00 ivr01 > /usr/local/sbin/opensips[2227]: DBG:core:subst_parser: ok, se > is 0x7f39a > > 5d0a1f0 > > 2017-01-05T13:23:23.108241+01:00 ivr01 > /usr/local/sbin/opensips[2227]: DBG:core:subst_run: running. r=0 > > 2017-01-05T13:23:23.111918+01:00 ivr01 > /usr/local/sbin/opensips[2227]: DBG:core:subst_run: matched > (404, 45): [ > > gml:Coordinates>12.32 34.24 > 2017-01-05T13:23:23.112380+01:00 ivr01 > /usr/local/sbin/opensips[2227]: DBG:core:buf_init: initializing... > > 2017-01-05T13:23:23.112730+01:00 ivr01 > /usr/local/sbin/opensips[2227]: Position is version="1.0" encoding > > ="UTF-8"?>#015#012 xmlns="urn:ietf:params:xml:ns:pidf" > xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xm > > lns:gml="urn:opengis:specification:gml:schema-xsd:feature:v3.0" > entity="pres:sip:+1234567 at test.com" > >#015#0 > > 12 #015#012 #015#012 > #015#012 #015#012 > n>#015#012 srsName="epsg:4346">#015#012 <12.32 34.24>#015#012 > nt>#015#012 #015#012 > #015#012 #015#012 > > ission-allowed>no#015#012 > #015#012 #015# > > 012 #015#012 #015#012 > 2016-8-02T04:13:23Z#015#012 > #015#012 > > > > Thanks > > *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] > *Sent:* Donnerstag, 5. Januar 2017 13:12 > *To:* OpenSIPS users mailling list >; xaled > > *Subject:* Re: [OpenSIPS-Users] How to parse XML Body? > > Try $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; > > > > > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From trance_maniak at o2.pl Thu Jan 19 06:03:28 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Thu, 19 Jan 2017 04:03:28 -0700 (MST) Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <1484644764556-7605602.post@n2.nabble.com> References: <586CAAD9.5060906@easycall.pl> <1483952331826-7605485.post@n2.nabble.com> <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> <1484054601076-7605502.post@n2.nabble.com> <1484640426055-7605593.post@n2.nabble.com> <247fdfc3-93dc-c097-090e-e6faf103eaac@opensips.org> <1484642312675-7605598.post@n2.nabble.com> <1484644764556-7605602.post@n2.nabble.com> Message-ID: <1484823808329-7605662.post@n2.nabble.com> I want to ask what bolded values mean: # -- core presence params -- modparam("presence","server_address","sip:*sa*@10.10.10.10:5060") # -- pua and pua_dialoginfo parameters -- modparam("pua_dialoginfo", "presence_server", "sip:*sa*@10.10.10.10:5060") I don't really know what to write there. -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605662.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From trance_maniak at o2.pl Thu Jan 19 06:33:45 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Thu, 19 Jan 2017 04:33:45 -0700 (MST) Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <1484823808329-7605662.post@n2.nabble.com> References: <586CAAD9.5060906@easycall.pl> <1483952331826-7605485.post@n2.nabble.com> <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> <1484054601076-7605502.post@n2.nabble.com> <1484640426055-7605593.post@n2.nabble.com> <247fdfc3-93dc-c097-090e-e6faf103eaac@opensips.org> <1484642312675-7605598.post@n2.nabble.com> <1484644764556-7605602.post@n2.nabble.com> <1484823808329-7605662.post@n2.nabble.com> Message-ID: <1484825625209-7605664.post@n2.nabble.com> I think I found the reason BLF doesn't work. I made a test. I've erased presenity table. Then: 1. I called other user, led is blinking, and presentity table shows record with xml bodies with *early* state. 2. Then I pickup a call, the same record changes with *confirmed* state. 3. Then I end this call, the same record changes to *terminated* state. So first call was ok. But after it I made second call, but it turned out that presentity table wasn't erased, and previous records exist. So when I make this second call, xml body contains previous xml, and this right one! I think presentity table should be erased after a call. Do You know the reason? -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605664.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From Agalya_Ramachandran at comcast.com Thu Jan 19 09:55:01 2017 From: Agalya_Ramachandran at comcast.com (Ramachandran, Agalya (Contractor)) Date: Thu, 19 Jan 2017 14:55:01 +0000 Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service In-Reply-To: <2d785128-affa-c955-e779-1d4305ec1119@opensips.org> References: <92c380d81d5c45a9a2bce09fe344188e@COPDCEX28.cable.comcast.com> <2d785128-affa-c955-e779-1d4305ec1119@opensips.org> Message-ID: <21840442533f445397309d17eec6bcbe@COPDCEX28.cable.comcast.com> Hi Razvan, I didn’t see any process that is using more than 80% of a core. OpenSIPS is simply being idle and these warnings come periodically. Like once in couple of hours. I didn’t track the exact time line, how frequent am getting this warnings. Ahmed, Do you notice these warnings only when you start OpenSIPS or could see it in regular intervals? Regards, Agalya From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Razvan Crainea Sent: Thursday, January 19, 2017 3:33 AM To: users at lists.opensips.org Subject: Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service When starting opensips, is there any opensips process that is using more than 80% of a core? If so, can you pinpoint the PID in the opensipsctl ps command? Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/18/2017 11:55 PM, Ramachandran, Agalya (Contractor) wrote: Same with my case too. Regards, Agalya From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Ahmed Munir Sent: Wednesday, January 18, 2017 1:31 PM To: OpenSIPs Users Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service Hi, I'm currently seeing the warnings when I start opensips service; Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: timer job has a 1500000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: timer job has a 1500000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: timer job has a 1500000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: utimer job has a 2290000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: INFO:core:do_action: max while loops are encountered Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 2470 ms), it may over lap.. I've tried to update the source code for timer.c (line#: 190) ref: https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split, but didn't work at all. Currently running 8 child processors, see below; [root at qorblpsisprxyd1 ]# opensips -V version: opensips 2.2.2 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_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_lt, epoll_et, sigio_rt, select. main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7 [root at qorblpsisprxyd1 ]# opensipsctl fifo ps Process:: ID=0 PID=3083 Type=attendant Process:: ID=1 PID=3085 Type=MI FIFO Process:: ID=2 PID=3086 Type=time_keeper Process:: ID=3 PID=3088 Type=timer Process:: ID=4 PID=3089 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=5 PID=3091 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=6 PID=3092 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=7 PID=3094 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=8 PID=3096 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=9 PID=3098 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=10 PID=3100 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=11 PID=3102 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=12 PID=3104 Type=Timer handler I would like to know what changes required to fix this change? Please advise. -- Regards, Ahmed Munir Chohan _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From Agalya_Ramachandran at comcast.com Thu Jan 19 10:00:07 2017 From: Agalya_Ramachandran at comcast.com (Ramachandran, Agalya (Contractor)) Date: Thu, 19 Jan 2017 15:00:07 +0000 Subject: [OpenSIPS-Users] async- issues- 2.2.2 In-Reply-To: References: <4afe8b5419b74122ad85d626b5e12872@COPDCEX28.cable.comcast.com> <518a4bb0-f469-ce49-318f-108e09d8dd00@opensips.org> <9db8366c20274e289a11c722eac65189@COPDCEX28.cable.comcast.com> Message-ID: <13e06d602aec411fb24c4690da61b7c1@COPDCEX28.cable.comcast.com> Got it. Thank you. From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Razvan Crainea Sent: Thursday, January 19, 2017 3:30 AM To: users at lists.opensips.org Subject: Re: [OpenSIPS-Users] async- issues- 2.2.2 You have my answer inline. Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/18/2017 08:17 PM, Ramachandran, Agalya (Contractor) wrote: Hi Razvan, Got your point. I tried to increase the MAX_CONTENT_TYPE_LEN and tested async call and it is working fine without crash. But one more question. The same piece of code am using for sync REST_API query too in rest_put() method. There also print_buff is only being used. It is working absolutely fine in the case of sync call even if the MAX_CONTENT_TYPE_LEN – is 64. Wondering what would be the reason in sync call, it is working and in async it is not? Pure luck. You are doing a buffer overflow, overwriting the data section. Probably when doing sync calls, nobody is using the data you are overwriting. But if it doesn't crash it doesn't mean it is ok :). Regards, Agalya -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahmedmunir007 at gmail.com Thu Jan 19 11:01:31 2017 From: ahmedmunir007 at gmail.com (Ahmed Munir) Date: Thu, 19 Jan 2017 11:01:31 -0500 Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service Message-ID: Hi Razvan, During starting up the opensips service, I see the first opensips child process (pid"11172) consumes CPU process to 70-80% and later drop downs to 0.3 - 0.0 % CPU per core. See below; [root at qorblpsisprxyd1 ~]# top -c -u opensips top - 10:49:54 up 76 days, 23:31, 5 users, load average: 0.00, 0.00, 0.00 Tasks: 229 total, 1 running, 228 sleeping, 0 stopped, 0 zombie Cpu(s): 0.0%us, 0.1%sy, 0.0%ni, 99.9%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 65964364k total, 2568124k used, 63396240k free, 180220k buffers Swap: 1023996k total, 0k used, 1023996k free, 1226104k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 11177 opensips 20 0 165m 5696 4528 S 0.3 0.0 0:00.23 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11187 opensips 20 0 165m 5628 4460 S 0.3 0.0 0:00.41 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11166 opensips 20 0 165m 6892 5752 S 0.0 0.0 0:00.23 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11168 opensips 20 0 165m 1980 840 S 0.0 0.0 0:00.00 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11169 opensips 20 0 165m 1464 328 S 0.0 0.0 0:00.53 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11171 opensips 20 0 165m 1640 504 S 0.0 0.0 0:00.15 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11172 opensips 20 0 166m 40m 38m S 0.0 0.1 0:02.61 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11174 opensips 20 0 165m 6304 5136 S 0.0 0.0 0:00.24 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11175 opensips 20 0 165m 5884 4716 S 0.0 0.0 0:00.22 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11179 opensips 20 0 165m 7660 6492 S 0.0 0.0 0:00.27 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11181 opensips 20 0 165m 7756 6588 S 0.0 0.0 0:00.33 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11183 opensips 20 0 165m 5520 4352 S 0.0 0.0 0:00.34 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11185 opensips 20 0 165m 7336 6168 S 0.0 0.0 0:00.36 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11189 opensips 20 0 165m 7320 6152 S 0.0 0.0 0:00.36 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips 11190 opensips 20 0 165m 4688 3528 S 0.0 0.0 0:00.30 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips [root at qorblpsisprxyd1 ~]# opensipsctl fifo ps Process:: ID=0 PID=11166 Type=attendant Process:: ID=1 PID=11168 Type=MI FIFO Process:: ID=2 PID=11169 Type=time_keeper Process:: ID=3 PID=11171 Type=timer Process:: ID=4 PID=11172 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=5 PID=11174 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=6 PID=11175 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=7 PID=11177 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=8 PID=11179 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=9 PID=11181 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=10 PID=11183 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=11 PID=11185 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=12 PID=11187 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=13 PID=11189 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=14 PID=11190 Type=Timer handler OpenSIPs used by each CPU processor; [root at qorblpsisprxyd1 ~]# ps -o pid,psr,comm -C opensips PID PSR COMMAND 11166 0 opensips 11168 2 opensips 11169 6 opensips 11171 5 opensips 11172 5 opensips 11174 5 opensips 11175 5 opensips 11177 5 opensips 11179 7 opensips 11181 1 opensips 11183 0 opensips 11185 2 opensips 11187 5 opensips 11189 5 opensips 11190 4 opensips [root at qorblpsisprxyd1 ~]# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel CPU family: 6 Model: 44 Stepping: 2 CPU MHz: 1197.000 BogoMIPS: 4266.58 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 8192K NUMA node0 CPU(s): 0-3 NUMA node1 CPU(s): 4-7 Please advise for the fix as currently setting child processes to 10 in opensips config. Date: Thu, 19 Jan 2017 10:32:35 +0200 > From: Răzvan Crainea > To: users at lists.opensips.org > Subject: Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start > service > Message-ID: <2d785128-affa-c955-e779-1d4305ec1119 at opensips.org> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > When starting opensips, is there any opensips process that is using more > than 80% of a core? If so, can you pinpoint the PID in the opensipsctl > ps command? > > Best regards, > > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > > On 01/18/2017 11:55 PM, Ramachandran, Agalya (Contractor) wrote: > > > > Same with my case too. > > > > Regards, > > Agalya > > > > *From:*Users [mailto:users-bounces at lists.opensips.org] *On Behalf Of > > *Ahmed Munir > > *Sent:* Wednesday, January 18, 2017 1:31 PM > > *To:* OpenSIPs Users > > *Subject:* [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service > > > > Hi, > > > > I'm currently seeing the warnings when I start opensips service; > > > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > > WARNING:core:handle_timer_job: timer job has a 1500000 > > us delay in execution > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > > WARNING:core:handle_timer_job: timer job has a 1500000 us > > delay in execution > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > > WARNING:core:handle_timer_job: timer job has a 1500000 us > > delay in execution > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > > WARNING:core:handle_timer_job: utimer job has a 2290000 us > > delay in execution > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > > INFO:core:do_action: max while loops are encountered > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: > > WARNING:core:utimer_ticker: utimer task already scheduled > > for 190 ms (now 2470 ms), it may over > > lap.. > > > > I've tried to update the source code for timer.c (line#: 190) ref: > > https://github.com/OpenSIPS/opensips/commit/ > fd8f6ec442b4365da9d274af6939954246ece865?diff=split, > > but didn't work at all. > > > > Currently running 8 child processors, see below; > > > > [root at qorblpsisprxyd1 ]# opensips -V > > version: opensips 2.2.2 (x86_64/linux) > > flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, > > F_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_lt, epoll_et, sigio_rt, select. > > main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7 > > > > > > [root at qorblpsisprxyd1 ]# opensipsctl fifo ps > > Process:: ID=0 PID=3083 Type=attendant > > Process:: ID=1 PID=3085 Type=MI FIFO > > Process:: ID=2 PID=3086 Type=time_keeper > > Process:: ID=3 PID=3088 Type=timer > > Process:: ID=4 PID=3089 Type=SIP receiver udp:10.3.120.94:5060 > > > > Process:: ID=5 PID=3091 Type=SIP receiver udp:10.3.120.94:5060 > > > > Process:: ID=6 PID=3092 Type=SIP receiver udp:10.3.120.94:5060 > > > > Process:: ID=7 PID=3094 Type=SIP receiver udp:10.3.120.94:5060 > > > > Process:: ID=8 PID=3096 Type=SIP receiver udp:10.3.120.94:5060 > > > > Process:: ID=9 PID=3098 Type=SIP receiver udp:10.3.120.94:5060 > > > > Process:: ID=10 PID=3100 Type=SIP receiver udp:10.3.120.94:5060 > > > > Process:: ID=11 PID=3102 Type=SIP receiver udp:10.3.120.94:5060 > > > > Process:: ID=12 PID=3104 Type=Timer handler > > > > I would like to know what changes required to fix this change? Please > > advise. > > > > > > -- > > > > Regards, > > > > Ahmed Munir Chohan > > > > > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: 20170119/81b8d547/attachment-0001.html> > > > -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahmedmunir007 at gmail.com Thu Jan 19 11:05:15 2017 From: ahmedmunir007 at gmail.com (Ahmed Munir) Date: Thu, 19 Jan 2017 11:05:15 -0500 Subject: [OpenSIPS-Users] Users Digest, Vol 102, Issue 62 Message-ID: These warnings appears during opensips startup service. Date: Thu, 19 Jan 2017 14:55:01 +0000 > From: "Ramachandran, Agalya (Contractor)" > > To: OpenSIPS users mailling list > Subject: Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start > service > Message-ID: > <21840442533f445397309d17eec6bcbe at COPDCEX28.cable.comcast.com> > Content-Type: text/plain; charset="utf-8" > > Hi Razvan, > > I didn’t see any process that is using more than 80% of a core. OpenSIPS > is simply being idle and these warnings come periodically. > > Like once in couple of hours. I didn’t track the exact time line, how > frequent am getting this warnings. > > Ahmed, > Do you notice these warnings only when you start OpenSIPS or could see it > in regular intervals? > > Regards, > Agalya > > From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Razvan > Crainea > Sent: Thursday, January 19, 2017 3:33 AM > To: users at lists.opensips.org > Subject: Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service > > When starting opensips, is there any opensips process that is using more > than 80% of a core? If so, can you pinpoint the PID in the opensipsctl ps > command? > > Best regards, > > > Răzvan Crainea > > OpenSIPS Solutions > > www.opensips-solutions.com > On 01/18/2017 11:55 PM, Ramachandran, Agalya (Contractor) wrote: > Same with my case too. > > Regards, > Agalya > > From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Ahmed > Munir > Sent: Wednesday, January 18, 2017 1:31 PM > To: OpenSIPs Users org> > Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service > > Hi, > I'm currently seeing the warnings when I start opensips service; > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a 1500000 us > delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a 1500000 us delay > in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a 1500000 us delay > in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: utimer job has a 2290000 us > delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > INFO:core:do_action: max while loops are encountered > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: > WARNING:core:utimer_ticker: utimer task already scheduled for > 190 ms (now 2470 ms), it may over > lap.. > > > I've tried to update the source code for timer.c (line#: 190) ref: > https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af693995 > 4246ece865?diff=split, but didn't work at all. > Currently running 8 child processors, see below; > > [root at qorblpsisprxyd1 ]# opensips -V > version: opensips 2.2.2 (x86_64/linux) > flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, > F_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_lt, epoll_et, sigio_rt, select. > main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7 > > > [root at qorblpsisprxyd1 ]# opensipsctl fifo ps > Process:: ID=0 PID=3083 Type=attendant > Process:: ID=1 PID=3085 Type=MI FIFO > Process:: ID=2 PID=3086 Type=time_keeper > Process:: ID=3 PID=3088 Type=timer > Process:: ID=4 PID=3089 Type=SIP receiver udp:10.3.120.94:5060 10.3.120.94:5060> > Process:: ID=5 PID=3091 Type=SIP receiver udp:10.3.120.94:5060 10.3.120.94:5060> > Process:: ID=6 PID=3092 Type=SIP receiver udp:10.3.120.94:5060 10.3.120.94:5060> > Process:: ID=7 PID=3094 Type=SIP receiver udp:10.3.120.94:5060 10.3.120.94:5060> > Process:: ID=8 PID=3096 Type=SIP receiver udp:10.3.120.94:5060 10.3.120.94:5060> > Process:: ID=9 PID=3098 Type=SIP receiver udp:10.3.120.94:5060 10.3.120.94:5060> > Process:: ID=10 PID=3100 Type=SIP receiver udp:10.3.120.94:5060 10.3.120.94:5060> > Process:: ID=11 PID=3102 Type=SIP receiver udp:10.3.120.94:5060 10.3.120.94:5060> > Process:: ID=12 PID=3104 Type=Timer handler > I would like to know what changes required to fix this change? Please > advise. > > -- > Regards, > > Ahmed Munir Chohan > > -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From xaled at web.de Thu Jan 19 12:44:56 2017 From: xaled at web.de (xaled) Date: Thu, 19 Jan 2017 18:44:56 +0100 Subject: [OpenSIPS-Users] How to parse XML Body? In-Reply-To: <603ad545-bf7e-4adf-a4d1-7fd8be0f01f1@opensips.org> References: <012c01d266bf$841c7590$8c5560b0$@web.de> <7ff31d5b-ad90-44d5-dcdf-86edaf84cf76@opensips.org> <018601d26742$7d877ee0$78967ca0$@web.de> <4936e66b-ae31-a9fa-e260-a87ef6b24b20@opensips.org> <019a01d26746$00669460$0133bd20$@web.de> <01b601d26748$2bebb6e0$83c324a0$@web.de> <01428a9e-5f55-5a7e-154d-59c2f8e96ef0@opensips.org> <01f101d2674f$dadadee0$90909ca0$@web.de> <032b01d26833$cace6370$606b2a50$@web.de> <6969d0ff-96a6-56da-15f4-54f8cd0c116b@opensips.org> <009101d26d84$72050d10$560f2730$@web.de> <5e264517-2c83-2808-4e29-f9418125ff7a@opensips.org> <016e01d27194$712ba570$5382f050$@web.de> <603ad545-bf7e-4adf-a4d1-7fd8be0f01f1@opensips.org> Message-ID: <002101d2727b$c116da90$43448fb0$@web.de> Hi Bogdan, I know, that script level is better and I use the script regex now it is working. Perl was used out of frustration of not being able to get the right regex with script. I’m neither good at perl, but the first regex example I found on the web worked right away with minor changes. Honestly I do not quite understand why the workable script regex should be the way it is. Especially compared with the regex I used in perl. But I’m not a regex expert either. Anyway I’m happy as long as it does what I need. The patch looks good. I will try it and let you know how it will work out. Thanks a lot for your support! From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Donnerstag, 19. Januar 2017 11:54 To: xaled ; 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi, To be honest I'm not good on perl, but if you can do it directly at script level, it it cleaner and more efficient. Also, check this https://github.com/OpenSIPS/opensips/commit/d509aa63698bc26fde390a4b707dbf2be31f5de5 Thanks and Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/18/2017 04:09 PM, xaled wrote: Hi Bogdan, works like a charm, thanks! As an additional bonus now I know how to work with the perl module ;) $rb(mime)[idx] is even more flexible. From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Dienstag, 17. Januar 2017 15:12 To: xaled ; 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi, There was a small typo in my regexp. The correct one is: $var(reg) = "/(.*)gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s"; xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); I tried it and it does the job. Regarding the usability of the $rb variable, yes you have a point. I was thinking of something like $rb(mime)[idx] to access also per mime. Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/13/2017 12:04 PM, xaled wrote: Hi Bogdan, thank you for looking at this issue. This regex does not work. I tried different combinations of the idea but it just not getting there. 2017-01-13T11:02:42.287766+01:00 ivr01 /usr/local/sbin/opensips[24845]: DBG:core:tr_eval_re: we must compile the regexp 2017-01-13T11:02:42.288116+01:00 ivr01 /usr/local/sbin/opensips[24845]: WARNING:core:parse_repl: \/ unknown escape in (.*)<\/gml:Coordinates(.*)/\2/s 2017-01-13T11:02:42.288464+01:00 ivr01 /usr/local/sbin/opensips[24845]: ERROR:core:subst_parser: unknown flag . in (.*)/gml:Coordinates>(.*)<\/gml:Coordin ates(.*)/\2/s 2017-01-13T11:02:42.288787+01:00 ivr01 /usr/local/sbin/opensips[24845]: ERROR:core:tr_eval_re: Can't compile regexp I managed to get it running with perl: use OpenSIPS qw ( log ); use OpenSIPS::Constants; use OpenSIPS::Message; sub parsePIDFLO { my $m = shift; my $body = $m->getBody(); ($coord) = $body =~ /Coordinates>(.*) ; asd asd Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi, Please try $var(reg) = "(.*)/gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s"; xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/06/2017 05:44 PM, xaled wrote: Hi Bogdan, can you give any hints on how to get the Coordinates values and not the whole xml body from the regex subst? Sorry for being not clever enough to figure it out myself. Thanks Hi Bogdan, $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; xlog("Position is $(rb[1]{re.subst,$var(reg)})\n"); DBG:core:subst_run:matched shows the needed XML element with value, but not the value alone. The xlog output shows the whole XML body without gml:Coordinates. 2017-01-05T13:23:23.104982+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:tr_eval_re: Trying to apply reg exp [/gml:Coordinates>(.*)<\/gml:Coordinates/\1/] on : [#015#012 "pres:sip:+1234567 at test.com">#015#012 #015#012 #015#012 #015#012 #015#012 #015#012 #015#012 12.32 34.24#015#012 #015#012 #015#012 #015#012 #015#012 no#015#012 #015#012 #01 5#012 #015#012 #015#012 2016-8-02T04:13:23Z#015#012 #015#0 12#015#012#015#012] 2017-01-05T13:23:23.107376+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:tr_eval_re: we must compile the regexp 2017-01-05T13:23:23.107903+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_parser: ok, se is 0x7f39a 5d0a1f0 2017-01-05T13:23:23.108241+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_run: running. r=0 2017-01-05T13:23:23.111918+01:00 ivr01 /usr/local/sbin/opensips[2227]: DBG:core:subst_run: matched (404, 45): [ gml:Coordinates>12.32 34.24#015#012 "pres:sip:+1234567 at test.com">#015#0 12 #015#012 #015#012 #015#012 #015#012 #015#012 #015#012 <12.32 34.24>#015#012 #015#012 #015#012 #015#012 #015#012 no#015#012 #015#012 #015# 012 #015#012 #015#012 2016-8-02T04:13:23Z#015#012 #015#012 Thanks From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Donnerstag, 5. Januar 2017 13:12 To: OpenSIPS users mailling list >; xaled > Subject: Re: [OpenSIPS-Users] How to parse XML Body? Try $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/"; _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Thu Jan 19 14:25:34 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Thu, 19 Jan 2017 21:25:34 +0200 Subject: [OpenSIPS-Users] Call per second limit Message-ID: Hello, How to made Call Per Second limitation using Opensips 2.2.2 ? Regards, Dragomir -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahmedmunir007 at gmail.com Thu Jan 19 18:31:45 2017 From: ahmedmunir007 at gmail.com (Ahmed Munir) Date: Thu, 19 Jan 2017 18:31:45 -0500 Subject: [OpenSIPS-Users] Async DB statement Message-ID: Hi, Currently I'm trying to use async fucntion for avp_db_query. The issue I'm facing while using it as not retrieving or returning correct return code and not execute later part of the routing script. See old & new DB queries; Without Async: ---------------------- route[1]{ ... if($var(Outpluseflag) == 0) { avp_db_query("SELECT Outpulse_number,setid FROM Prefix_data where Program_prefix = '$var(pg_prefix)'", "$avp(outpluse), $avp(trunkid)"); $var(res) = $retcode; # or you can just use $retcode! xlog("--------- OB Route 1-1 DB fetched value outpluse -> $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code: $rc | Var Res: $var(res)-------"); if ($var(res) > 0) { cache_store("local", "DID_$tU", "$avp(outpluse)", 60); cache_store("local", "Trunk_$tU", "$avp(trunkid)", 60); } #xlog("DB fetched value outpluse -> $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code -> $var(res)"); xlog("--------- OB Route 1-2 DB fetched value outpluse -> $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code: $rc | Var Res: $var(res)-------"); } } With Async: ------------------- route[1]{ ... if($var(Outpluseflag) == 0) { async(avp_db_query("SELECT Outpulse_number,setid FROM Prefix_data where Program_prefix = '$var(pg_prefix)'", "$avp(outpluse), $avp(trunkid)"),ob_route_1); } } route[ob_route_1]{ xlog("--------- OB Route 1-1 DB fetched value outpluse -> $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code: $rc-------"); if ($rc > 0) { cache_store("local", "DID_$tU", "$avp(outpluse)", 60); cache_store("local", "Trunk_$tU", "$avp(trunkid)", 60); } xlog("--------- OB Route 1-2 DB fetched value outpluse -> $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code: $rc-------"); } The records in xlog I'm getting without using async; Jan 19 18:05:39 qorblpsisprxyd1 /usr/sbin/opensips[14040]: --------- OB Route 1-1 DB fetched value outpluse -> 6099020000 | trunkid -> 117 | Return Code: 1 | Var Res: 1------- Jan 19 18:05:39 qorblpsisprxyd1 /usr/sbin/opensips[14040]: --------- OB Route 1-2 DB fetched value outpluse -> 6099020000 | trunkid -> 117 | Return Code: 1 | Var Res: 1------- Whereas, records in xlog I'm getting using async; Jan 19 18:10:07 qorblpsisprxyd1 /usr/sbin/opensips[14109]: --------- OB Route 1-1 DB fetched value outpluse -> 6099020000 | trunkid -> 117 | Return Code: 1------- Jan 19 18:10:07 qorblpsisprxyd1 /usr/sbin/opensips[14109]: --------- OB Route 1-2 DB fetched value outpluse -> 6099020000 | trunkid -> 117 | Return Code: 0------- Is there is way to properly retain the $retcode/$rc in version 2.2.2? Seems like using async return code(s) are not properly set or the avp variables are not setting up correct using async statement. Please advise, if the above async db statement is correct as shared in sample above. -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From trance_maniak at o2.pl Fri Jan 20 02:58:17 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Fri, 20 Jan 2017 00:58:17 -0700 (MST) Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <1484823808329-7605662.post@n2.nabble.com> References: <586CAAD9.5060906@easycall.pl> <1483952331826-7605485.post@n2.nabble.com> <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> <1484054601076-7605502.post@n2.nabble.com> <1484640426055-7605593.post@n2.nabble.com> <247fdfc3-93dc-c097-090e-e6faf103eaac@opensips.org> <1484642312675-7605598.post@n2.nabble.com> <1484644764556-7605602.post@n2.nabble.com> <1484823808329-7605662.post@n2.nabble.com> Message-ID: <1484899097544-7605672.post@n2.nabble.com> I think I found the reason BLF doesn't work. I made a test. I've erased presenity table. Then: 1. I called other user, led is blinking, and presentity table shows record with xml bodies with early state. 2. Then I pickup a call, the same record changes with confirmed state. 3. Then I end this call, the same record changes to terminated state. So first call was ok. But after it I made second call, but it turned out that presentity table wasn't erased, and previous records exist. So when I make this second call, xml body contains previous xml, and this right one! I think presentity table should be erased after a call. Do You know the reason? -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605672.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From carlos.oliva at numintec.com Fri Jan 20 03:39:24 2017 From: carlos.oliva at numintec.com (Carlos Oliva) Date: Fri, 20 Jan 2017 09:39:24 +0100 Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <1484899097544-7605672.post@n2.nabble.com> References: <586CAAD9.5060906@easycall.pl> <1483952331826-7605485.post@n2.nabble.com> <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> <1484054601076-7605502.post@n2.nabble.com> <1484640426055-7605593.post@n2.nabble.com> <247fdfc3-93dc-c097-090e-e6faf103eaac@opensips.org> <1484642312675-7605598.post@n2.nabble.com> <1484644764556-7605602.post@n2.nabble.com> <1484823808329-7605662.post@n2.nabble.com> <1484899097544-7605672.post@n2.nabble.com> Message-ID: Hi Marcin: I had the same problem years ago with 1.6 version. In the first call BLF works but the second call fails. I solved it using dialog module to check the mumber of calls and not doing pua_set_publish if the mubers of calls are > 1 I think this problem was solved on 1.11 version, wich is suported until 7th of May 2017, 1.6 version has reached end of life on 2010 regards, * _________________________________________________ Carlos OlivaDepartamento de Sistemas C/ Pujades, 77-79, 8a Planta 9B | 08005 Barcelona www.numintec.com | carlos.oliva at numintec.com | T: 902 02 02 97 _________________________________________________ Talking Numintec: Dialogando con empresarios de éxito Las soluciones en la nube de Numintec - Casos de éxito Solicita una demo _________________________________________________ Medio Ambiente: Antes de imprimir este mensaje, asegúrese de que es necesario. Nota Legal: La información contenida en la presente transmisión es confidencial y su uso únicamente está permitido a su(s) destinatario(s). Le informamos que los datos personales que facilite/ha facilitado pasarán/han pasado a formar parte de un fichero responsabilidad de NUMINTEC COMUNICACIONES S.L.. y que tiene por finalidad gestionar las relaciones. Tiene la posibilidad de ejercitar los derechos de acceso, rectificación, cancelación y oposición respecto a sus datos ante la empresa, en el e-mail comunicacion at numintec.com o bien en el domicilio sito en C/ Pujades, 77-79 8ª Planta 9-B 08005 de Barcelona.* 2017-01-20 8:58 GMT+01:00 maatohewetbi : > I think I found the reason BLF doesn't work. I made a test. I've erased > presenity table. Then: > 1. I called other user, led is blinking, and presentity table shows record > with xml bodies with early state. > 2. Then I pickup a call, the same record changes with confirmed state. > 3. Then I end this call, the same record changes to terminated state. > > So first call was ok. But after it I made second call, but it turned out > that presentity table wasn't erased, and previous records exist. So when I > make this second call, xml body contains previous xml, and this right one! > I > think presentity table should be erased after a call. Do You know the > reason? > > > > > -- > View this message in context: http://opensips-open-sip- > server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server- > tp7605411p7605672.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From albertosgonzale at gmail.com Fri Jan 20 04:56:37 2017 From: albertosgonzale at gmail.com (Alberto Gonzales) Date: Fri, 20 Jan 2017 09:56:37 +0000 Subject: [OpenSIPS-Users] topology hiding in opensips Message-ID: Hello grupo, We have configured topology hiding in opensips 2.2 this way : please confirm to us this is the only thing we need to do or is there anything else that needs to be added. route { .... .... if (has_totag()) { # sequential request withing a dialog should # take the path determined by record-routing #### remplazar : if (loose_route()) { if (topology_hiding_match()) { ... ... *## esconder topologia antes de pasar la llamada* topology_hiding("UC"); route(RELAY); } also what could be a quick test to see if this hiding is working or not. thanks in advance. Alberto -------------- next part -------------- An HTML attachment was scrubbed... URL: From albertosgonzale at gmail.com Fri Jan 20 05:14:18 2017 From: albertosgonzale at gmail.com (Alberto Gonzales) Date: Fri, 20 Jan 2017 10:14:18 +0000 Subject: [OpenSIPS-Users] topology hiding in opensips In-Reply-To: References: Message-ID: I forgot to mention that doing this resulted in opensips crashing after 20 minutes :) On Fri, Jan 20, 2017 at 9:56 AM, Alberto Gonzales wrote: > Hello grupo, > > We have configured topology hiding in opensips 2.2 this way : > > please confirm to us this is the only thing we need to do or is there > anything else that needs to be added. > > route { > .... > .... > if (has_totag()) { > # sequential request withing a dialog should > # take the path determined by record-routing > #### remplazar : if (loose_route()) { > if (topology_hiding_match()) { > > ... > ... > *## esconder topologia antes de pasar la llamada* > topology_hiding("UC"); > route(RELAY); > } > > > also what could be a quick test to see if this hiding is working or not. > > thanks in advance. > > Alberto > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From trance_maniak at o2.pl Fri Jan 20 05:15:36 2017 From: trance_maniak at o2.pl (maatohewetbi) Date: Fri, 20 Jan 2017 03:15:36 -0700 (MST) Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: References: <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> <1484054601076-7605502.post@n2.nabble.com> <1484640426055-7605593.post@n2.nabble.com> <247fdfc3-93dc-c097-090e-e6faf103eaac@opensips.org> <1484642312675-7605598.post@n2.nabble.com> <1484644764556-7605602.post@n2.nabble.com> <1484823808329-7605662.post@n2.nabble.com> <1484899097544-7605672.post@n2.nabble.com> Message-ID: <1484907336450-7605677.post@n2.nabble.com> How did You check it? You checked calls from this sip login? -- View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605677.html Sent from the OpenSIPS - Users mailing list archive at Nabble.com. From albertosgonzale at gmail.com Fri Jan 20 05:42:35 2017 From: albertosgonzale at gmail.com (Alberto Gonzales) Date: Fri, 20 Jan 2017 10:42:35 +0000 Subject: [OpenSIPS-Users] topology hiding in opensips In-Reply-To: References: Message-ID: We used instruction in the book, which states at the end of the paragraph this : Topology hiding limitations You cannot easily combine topology hiding with NAT traversal because both the processes mangle the Contact header. Topology hiding will not hide the address and other information contained in other headers such as the display in the >From header. To change the From header, you can use the uac_replace_from() function. I think our problem comes from the fact that we are using nathelper and also an rtpproxy in our script. can anyone provide help about activating topology hiding along with nathelper ? thanks in advance. On Fri, Jan 20, 2017 at 10:14 AM, Alberto Gonzales < albertosgonzale at gmail.com> wrote: > I forgot to mention that doing this resulted in opensips crashing after 20 > minutes :) > > On Fri, Jan 20, 2017 at 9:56 AM, Alberto Gonzales < > albertosgonzale at gmail.com> wrote: > >> Hello grupo, >> >> We have configured topology hiding in opensips 2.2 this way : >> >> please confirm to us this is the only thing we need to do or is there >> anything else that needs to be added. >> >> route { >> .... >> .... >> if (has_totag()) { >> # sequential request withing a dialog should >> # take the path determined by record-routing >> #### remplazar : if (loose_route()) { >> if (topology_hiding_match()) { >> >> ... >> ... >> *## esconder topologia antes de pasar la llamada* >> topology_hiding("UC"); >> route(RELAY); >> } >> >> >> also what could be a quick test to see if this hiding is working or not. >> >> thanks in advance. >> >> Alberto >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at 42com.com Fri Jan 20 06:21:25 2017 From: mm at 42com.com (=?UTF-8?Q?Max_M=c3=bchlbronner?=) Date: Fri, 20 Jan 2017 12:21:25 +0100 Subject: [OpenSIPS-Users] Gateway failover special setup (t_check_status question) Message-ID: <5f8b7143-61ee-6ccd-98b4-bdc646a67b2f@42com.com> Hi, my scenario is a special setup where we are checking for the reply code (t_check_status) and only do a failover to the next gateway when there is a 444 reply or gateway type is not "1". ... if (use_next_gw()) { if( t_check_status("444") || !goes_to_gw("1") ) { t_on_failure("2"); t_relay(); exit; } The problem is, there are multiple gateways in a carrier/gatewaylist (gateway type 1) which are not responding (t1 timer hits and invite is re-transmitted) and there is no failover after the first gateway anymore. Is there anything i am missing, is it even possible to do failover only for the 444 reply while at the same time still doing a failover in case of Timeout-based failover ? (t1/t2 timers) I didn't try yet, but is something like !t_check_status("\d") feasible? E.g. doing a failover if there is no t_check_status (checking regular expression for !digits?) but i guess it does not work that way? if (use_next_gw()) { if( t_check_status("444") || !goes_to_gw("1") ) { t_on_failure("2"); t_relay(); exit; } if(!t_check_status("\d")) { t_on_failure("2"); t_relay(); exit; } ... BR -- Max Mühlbronner 42com Telecommunication GmbH Straße der Pariser Kommune 12-16 10243 Berlin E-Mail: mm at 42com.com Web: www.42com.com Firmenangaben/Company information: Handelsregister/Commercial register: Amtsgericht Berlin HRB 99071 B Umsatzsteuer-ID/VAT-ID: DE223812306 Geschäftsführer/CEO: Thomas Reinig, Alexander Reinig Diese E-Mail enthält Informationen von 42com Telecommunication GmbH. Diese sind möglicherweise vertraulich und ausschließlich für den Adressaten bestimmt. Sollten Sie diese elektronische Nachricht irrtümlicherweise erhalten haben, so informieren Sie uns bitte unverzüglich telefonisch oder per E-Mail. This message is intended only for the use of the individual or entity to which it is addressed. If you have received this message by mistake, please notify us immediately. From alain.bieuzent at free.fr Fri Jan 20 06:24:27 2017 From: alain.bieuzent at free.fr (Alain Bieuzent) Date: Fri, 20 Jan 2017 12:24:27 +0100 Subject: [OpenSIPS-Users] Call per second limit In-Reply-To: References: Message-ID: Hi, You case use ratelimit module : http://www.opensips.org/html/docs/modules/devel/ratelimit.html, with rl_check function. Regards De : Users au nom de Dragomir Haralambiev Répondre à : OpenSIPS users mailling list Date : jeudi 19 janvier 2017 à 20:25 À : OpenSIPS users mailling list Objet : [OpenSIPS-Users] Call per second limit Hello, How to made Call Per Second limitation using Opensips 2.2.2 ? Regards, Dragomir _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlos.oliva at numintec.com Fri Jan 20 06:27:24 2017 From: carlos.oliva at numintec.com (Carlos Oliva) Date: Fri, 20 Jan 2017 12:27:24 +0100 Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <1484907336450-7605677.post@n2.nabble.com> References: <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> <1484054601076-7605502.post@n2.nabble.com> <1484640426055-7605593.post@n2.nabble.com> <247fdfc3-93dc-c097-090e-e6faf103eaac@opensips.org> <1484642312675-7605598.post@n2.nabble.com> <1484644764556-7605602.post@n2.nabble.com> <1484823808329-7605662.post@n2.nabble.com> <1484899097544-7605672.post@n2.nabble.com> <1484907336450-7605677.post@n2.nabble.com> Message-ID: you can count calls from/to a sip user using dialog profiling You can read about it in opensips book ( https://books.google.es/books?id=y2wdDAAAQBAJ&pg=PA202&lpg=PA202&dq=opensips+dialog+count+calls&source=bl&ots=LFFoLxC9Gf&sig=fe_67u5d7xSNXm2gXUqbSOmTznM&hl=es&sa=X&ved=0ahUKEwiD6s3dy9DRAhXEUhQKHRoCAtUQ6AEIOzAD#v=onepage&q=opensips%20dialog%20count%20calls&f=false ) To do it you create a profile with value and add the current dialog with the sip username as value. After it you get the profile size, if it is >1 you do not do pua_setpublish because there is another ongoing call. But as I said this problem is solved in 1.11 version, 1.6 is very old. * _________________________________________________ Carlos OlivaDepartamento de Sistemas C/ Pujades, 77-79, 8a Planta 9B | 08005 Barcelona www.numintec.com | carlos.oliva at numintec.com | T: 902 02 02 97 _________________________________________________ Talking Numintec: Dialogando con empresarios de éxito Las soluciones en la nube de Numintec - Casos de éxito Solicita una demo _________________________________________________ Medio Ambiente: Antes de imprimir este mensaje, asegúrese de que es necesario. Nota Legal: La información contenida en la presente transmisión es confidencial y su uso únicamente está permitido a su(s) destinatario(s). Le informamos que los datos personales que facilite/ha facilitado pasarán/han pasado a formar parte de un fichero responsabilidad de NUMINTEC COMUNICACIONES S.L.. y que tiene por finalidad gestionar las relaciones. Tiene la posibilidad de ejercitar los derechos de acceso, rectificación, cancelación y oposición respecto a sus datos ante la empresa, en el e-mail comunicacion at numintec.com o bien en el domicilio sito en C/ Pujades, 77-79 8ª Planta 9-B 08005 de Barcelona.* 2017-01-20 11:15 GMT+01:00 maatohewetbi : > How did You check it? You checked calls from this sip login? > > > > -- > View this message in context: http://opensips-open-sip- > server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server- > tp7605411p7605677.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ionutionita at opensips.org Fri Jan 20 07:30:50 2017 From: ionutionita at opensips.org (Ionut Ionita) Date: Fri, 20 Jan 2017 14:30:50 +0200 Subject: [OpenSIPS-Users] [BLOG] Migrating registrations to OpenSIPS 2.2 In-Reply-To: References: Message-ID: <7de1c572-f36e-3b69-9457-ce43b2f41788@opensips.org> Hello guys, We just uploaded a new article on our blog about migrating your contacts from older versions of OpenSIPS to 2.2[0]. Starting withOpenSIPS2.2 the registered SIP contacts (stored the location table) have a new unique ID named *contact ID*. This new ID is contact specific (computed based on various contact elements) and it replaces the old opaque ID which was a simple DB auto-increment key. This creates a series of problems when you need to migrate from older versions and not only. You can find how to detect and solve this problems by reading the blog post. [0] https://blog.opensips.org/2017/01/19/migrating-contacts-in-opensips-2-2/ -- Regards, Ionut Ionita OpenSIPS Developer -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Fri Jan 20 07:57:57 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Fri, 20 Jan 2017 14:57:57 +0200 Subject: [OpenSIPS-Users] Gateway failover special setup (t_check_status question) In-Reply-To: <5f8b7143-61ee-6ccd-98b4-bdc646a67b2f@42com.com> References: <5f8b7143-61ee-6ccd-98b4-bdc646a67b2f@42com.com> Message-ID: Hi Max, Something like: if( (t_check_status("444") || (t_check_status("408") && t_local_replied("all")) ) || !goes_to_gw("1") ) { Do failover if 444 reply or if 408 without any reply received (internal 408). Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/20/2017 01:21 PM, Max Mühlbronner wrote: > Hi, > > > my scenario is a special setup where we are checking for the reply > code (t_check_status) and only do a failover to the next gateway when > there is a 444 reply or gateway type is not "1". > > ... > > if (use_next_gw()) { > if( t_check_status("444") || !goes_to_gw("1") ) { > t_on_failure("2"); > t_relay(); > exit; > } > > > The problem is, there are multiple gateways in a carrier/gatewaylist > (gateway type 1) which are not responding (t1 timer hits and invite is > re-transmitted) and there is no failover after the first gateway > anymore. Is there anything i am missing, is it even possible to do > failover only for the 444 reply while at the same time still doing a > failover in case of Timeout-based failover ? (t1/t2 timers) > > > I didn't try yet, but is something like !t_check_status("\d") > feasible? E.g. doing a failover if there is no t_check_status > (checking regular expression for !digits?) but i guess it does not > work that way? > > > if (use_next_gw()) { > if( t_check_status("444") || !goes_to_gw("1") ) { > t_on_failure("2"); > t_relay(); > exit; > } > > if(!t_check_status("\d")) { > > t_on_failure("2"); > t_relay(); > exit; > > } > > ... > > > > BR > From bogdan at opensips.org Fri Jan 20 08:13:14 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Fri, 20 Jan 2017 15:13:14 +0200 Subject: [OpenSIPS-Users] [BLOG] Migrating registrations to OpenSIPS 2.2 In-Reply-To: <7de1c572-f36e-3b69-9457-ce43b2f41788@opensips.org> References: <7de1c572-f36e-3b69-9457-ce43b2f41788@opensips.org> Message-ID: <845081d8-beab-88ba-d2cc-eb6519f65c15@opensips.org> This issue (not being able to preserve contacts when migrating to 2.2 version) was reported and the fix sponsored by Chris Maciejewski from https://voipstudio.com/ . Thank you Chris !! Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/20/2017 02:30 PM, Ionut Ionita wrote: > > Hello guys, > We just uploaded a new article on our blog about migrating your > contacts from older versions of OpenSIPS to 2.2[0]. > Starting withOpenSIPS2.2 the registered SIP contacts (stored the > location table) have a new unique ID named *contact ID*. This new > ID is contact specific (computed based on various contact elements) > and it replaces the old opaque ID which was a simple DB auto-increment > key. This creates a series of problems when you need to migrate from > older versions and not only. You can find how to detect and solve this > problems by reading the blog post. > > > [0] > https://blog.opensips.org/2017/01/19/migrating-contacts-in-opensips-2-2/ > -- > Regards, > Ionut Ionita > OpenSIPS Developer > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at 42com.com Fri Jan 20 08:38:41 2017 From: mm at 42com.com (=?UTF-8?Q?Max_M=c3=bchlbronner?=) Date: Fri, 20 Jan 2017 14:38:41 +0100 Subject: [OpenSIPS-Users] Gateway failover special setup (t_check_status question) In-Reply-To: References: <5f8b7143-61ee-6ccd-98b4-bdc646a67b2f@42com.com> Message-ID: <839d1619-d2ff-9d33-b2d2-b99f4a506c52@42com.com> Hi, Actually this is very similar to what i tried before. But i just assumed that it is not being executed (no 408 in the trace, and no log entries at that moment). Now i checked again and i can see several xlog entries. (408 gateway timeout...) , just wasn't patient enough. if (use_next_gw()) { if( t_check_status("444") || !goes_to_gw("1") ) { t_on_failure("2"); t_relay("0x08"); exit; } #Timeout fix #3814 if (t_check_status("408") && t_local_replied("all")) { xlog("L_ERR", "408 gateway timeout fix test - rU: $rU ci: $ci"); } ... # end of gw list / failover t_reply("503", "Service Unavailable"); exit; Thanks very much, i will try but this now. BR Max M. On 20.01.2017 13:57, Bogdan-Andrei Iancu wrote: > Hi Max, > > Something like: > > if( (t_check_status("444") || (t_check_status("408") && > t_local_replied("all")) ) || !goes_to_gw("1") ) { > > Do failover if 444 reply or if 408 without any reply received > (internal 408). > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 01/20/2017 01:21 PM, Max Mühlbronner wrote: >> Hi, >> >> >> my scenario is a special setup where we are checking for the reply >> code (t_check_status) and only do a failover to the next gateway when >> there is a 444 reply or gateway type is not "1". >> >> ... >> >> if (use_next_gw()) { >> if( t_check_status("444") || !goes_to_gw("1") ) { >> t_on_failure("2"); >> t_relay(); >> exit; >> } >> >> >> The problem is, there are multiple gateways in a carrier/gatewaylist >> (gateway type 1) which are not responding (t1 timer hits and invite >> is re-transmitted) and there is no failover after the first gateway >> anymore. Is there anything i am missing, is it even possible to do >> failover only for the 444 reply while at the same time still doing a >> failover in case of Timeout-based failover ? (t1/t2 timers) >> >> >> I didn't try yet, but is something like !t_check_status("\d") >> feasible? E.g. doing a failover if there is no t_check_status >> (checking regular expression for !digits?) but i guess it does not >> work that way? >> >> >> if (use_next_gw()) { >> if( t_check_status("444") || !goes_to_gw("1") ) { >> t_on_failure("2"); >> t_relay(); >> exit; >> } >> >> if(!t_check_status("\d")) { >> >> t_on_failure("2"); >> t_relay(); >> exit; >> >> } >> >> ... >> >> >> >> BR >> > -- Max Mühlbronner 42com Telecommunication GmbH Straße der Pariser Kommune 12-16 10243 Berlin E-Mail: mm at 42com.com Web: www.42com.com Firmenangaben/Company information: Handelsregister/Commercial register: Amtsgericht Berlin HRB 99071 B Umsatzsteuer-ID/VAT-ID: DE223812306 Geschäftsführer/CEO: Thomas Reinig, Alexander Reinig Diese E-Mail enthält Informationen von 42com Telecommunication GmbH. Diese sind möglicherweise vertraulich und ausschließlich für den Adressaten bestimmt. Sollten Sie diese elektronische Nachricht irrtümlicherweise erhalten haben, so informieren Sie uns bitte unverzüglich telefonisch oder per E-Mail. This message is intended only for the use of the individual or entity to which it is addressed. If you have received this message by mistake, please notify us immediately. From bogdan at opensips.org Fri Jan 20 08:58:23 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Fri, 20 Jan 2017 15:58:23 +0200 Subject: [OpenSIPS-Users] Introducing OpenSIPS 2.3 In-Reply-To: <99435f67-d572-ce75-531a-a5588935aa1d@opensips.org> References: <99435f67-d572-ce75-531a-a5588935aa1d@opensips.org> Message-ID: <13a5ecd5-57ce-a423-9f8b-84137e524573@opensips.org> Have you missed the "Introducing OpenSIPS 2.3" conference ? It was awesome, so we had it recorded for you: https://www.youtube.com/watch?v=4xy2vZl72Tg Enjoy, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/12/2017 06:39 PM, Bogdan-Andrei Iancu wrote: > > A new year has arrived, so it is the time for a new OpenSIPS major > release – forOpenSIPS version 2.3 . > > For this version, the main focus on development > is the*/“integration”/*, the integration ofOpenSIPSwith various > external entities. Why is integration so important to end up being the > main tag of a major release? Well, everybody in the VoIP world is > operating VoIP platforms/systems – and these are more than SIP Engines > (asOpenSIPSis). Indeed, the SIP Engine is the core and most important > part of the platform, but to build something usable and useful, you > need additional components into your platform like CDR/billing > engines, monitoring and tracing tools, data backends, non-SIP trunking > or more specialized SIP engines. Shortly you need your SIP Engine > (OpenSIPS, of course) to be able to easily integrate with all these > components. > > OpenSIPS2.3 brings some new and exciting integration capabilities, > that will definitely boost the value of your SIP platform: > > * extendedHomer/SIPCapture integration to > allow capturing of non-SIP data (transport level data, Management > Interface commands, REST queries and more); > * SIP-I support both in terms of passing-through and in terms of > converting SIP-I to SIP and vice-versa ; > * CGRates integration for powerful > rating/billing – everything in a simple and automatic way (via a > dedicated module); > * FreeSWITCH flavored Load-Balancing for a > more realistic and accurate traffic balancing over FreeSWITCH > clusters (as the load information is fetched in realtime from > FreeSWITCH); > * theEvent Engine > to provide > support for scenarios based on Subscribe/Notify model, where the > script execution may subscribe and resume later according to > certain events (like a dynamic implementation of the Push > Notification mechanism); > * extendedRabbitMQ support for custom > and flexible data injection directly from OpenSIPS script; > * extended Asynchronous support for more complex async scenarios > (like launch with no wait); > * more end-device integration (special SIP extensions). > > The timeline for OpenSIPS 2.3 is: > > * Beta Release – 13-17 March 2017 > * Stable Release – 24-28 April 2017 > * General Availability – 2nd of May 2017, duringOpenSIPS Summit > > > To talk more about the features of this new release, a publicaudio > conference will be > available on19th of January 2017, 4 pm GMT > , thanks to > the kind sponsorship of UberConference > . Anyone is welcome to join to find > out more details or to ask questions aboutOpenSIPS2.3 . > > This is a public and open conference, so no registration is needed, > but if you want to announce your intention to participate, please let > us know via the form on the blog post > . > > Best regards, > > -- > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From haus.voip at gmail.com Sat Jan 21 13:42:58 2017 From: haus.voip at gmail.com (abc1) Date: Sat, 21 Jan 2017 18:42:58 +0000 Subject: [OpenSIPS-Users] freeradius-xs / cdrtool / ag-projects Message-ID: Hi There I'm trying to install the freeradius-xs on Debian 8 - there are unmet dependencies... The following packages have unmet dependencies: freeradius-xs : Depends: libperl5.10 (>= 5.10.1) but it is not installable Depends: libpython2.6 (>= 2.6) but it is not installable Depends: libssl0.9.8 (>= 0.9.8m-1) but it is not installable I downloaded the source and I'm having issues there too.. //usr/src/freeradius-2.1.10/src/lib/.libs/libfreeradius-radius-2.1.10.so: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status Makefile:33: recipe for target 'radeapclient' failed Couple of questions - is this still necessary? Do the official freeradius not have the stored procedure support yet? I can see there is ubuntu xenial repo so would it be better to use this OS now? What OS are you guys aiming for these days with packages, it used always be debian - is this no longer the case? Thanks Alex. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tijmen at ag-projects.com Mon Jan 23 06:57:38 2017 From: tijmen at ag-projects.com (Tijmen de Mes) Date: Mon, 23 Jan 2017 12:57:38 +0100 Subject: [OpenSIPS-Users] freeradius-xs / cdrtool / ag-projects In-Reply-To: References: Message-ID: Hi Alex, Currently Debian 8 is not tested/supported for Freeradius-XS / CDRTool. Soon (I can't give you an ETA) we will build some new packages which should be compatible Debian >= 8. BTW the Freeradius-XS is not for the stored procedure, it contains patches to allow for FAILED type radius packets. I’ve to check if this is present in upstream, but I don’t think so. Best regards, Tijmen de Mes — AG Projects > On 21 jan. 2017, at 19:42, abc1 wrote: > > Hi There > > I'm trying to install the freeradius-xs on Debian 8 - there are unmet dependencies... > > The following packages have unmet dependencies: > freeradius-xs : Depends: libperl5.10 (>= 5.10.1) but it is not installable > Depends: libpython2.6 (>= 2.6) but it is not installable > Depends: libssl0.9.8 (>= 0.9.8m-1) but it is not installable > > I downloaded the source and I'm having issues there too.. > > //usr/src/freeradius-2.1.10/src/lib/.libs/libfreeradius-radius-2.1.10.so : error adding symbols: DSO missing from command line > collect2: error: ld returned 1 exit status > Makefile:33: recipe for target 'radeapclient' failed > > > Couple of questions - is this still necessary? Do the official freeradius not have the stored procedure support yet? > I can see there is ubuntu xenial repo so would it be better to use this OS now? > > What OS are you guys aiming for these days with packages, it used always be debian - is this no longer the case? > > Thanks > Alex. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: Message signed with OpenPGP using GPGMail URL: From khamlichi.khalil at gmail.com Mon Jan 23 17:39:31 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Mon, 23 Jan 2017 22:39:31 +0000 Subject: [OpenSIPS-Users] scheduled concurrent call reporting Message-ID: Hi, I am trying to get call load information out of opensips at regular intervals to get some sort of realtime view of the load on the server. After applying profiles on the the INVITEs, I have tried to call get_profile_size from a timer_route. I am getting error : CRITICAL:core:yyerror: parse error in config file /usr/local//etc/opensips/opensips.cfg, line 483, column 38-39: Command cannot be used in the block Any alternative solutions ? Thanks in advance. kkh -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Mon Jan 23 18:05:50 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Mon, 23 Jan 2017 23:05:50 +0000 Subject: [OpenSIPS-Users] scheduled concurrent call reporting In-Reply-To: References: Message-ID: the idea is that I don't need to get the number of calls 30 times per second which would happens if I save to redis on each invite. scheduling the saving to redis every 10 seconds serves well my purpose but the timer_route doesn't seem to accept get_profile_size() any hints would be appreciated. On Mon, Jan 23, 2017 at 10:39 PM, Khalil Khamlichi < khamlichi.khalil at gmail.com> wrote: > Hi, > > I am trying to get call load information out of opensips at regular > intervals to get some sort of realtime view of the load on the server. > > After applying profiles on the the INVITEs, I have tried to call > get_profile_size from a timer_route. > I am getting error : > > CRITICAL:core:yyerror: parse error in config file /usr/local//etc/opensips/opensips.cfg, > line 483, column 38-39: Command cannot be used in the block > > Any alternative solutions ? > > Thanks in advance. > > kkh > -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Tue Jan 24 03:38:52 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Tue, 24 Jan 2017 10:38:52 +0200 Subject: [OpenSIPS-Users] scheduled concurrent call reporting In-Reply-To: References: Message-ID: <93a0287e-1c78-849c-a11e-31f62a17737b@opensips.org> Hello, Khalil! You could check the $stat(active_dialogs) pvar, which will return the number of ongoing dialogs. Best regards, Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 01/24/2017 01:05 AM, Khalil Khamlichi wrote: > the idea is that I don't need to get the number of calls 30 times per > second which would happens if I save to redis on each invite. scheduling > the saving to redis every 10 seconds serves well my purpose but the > timer_route doesn't seem to accept get_profile_size() > > any hints would be appreciated. > > On Mon, Jan 23, 2017 at 10:39 PM, Khalil Khamlichi > > wrote: > > Hi, > > I am trying to get call load information out of opensips at regular > intervals to get some sort of realtime view of the load on the server. > > After applying profiles on the the INVITEs, I have tried to call > get_profile_size from a timer_route. > I am getting error : > > CRITICAL:core:yyerror: parse error in config file > /usr/local//etc/opensips/opensips.cfg, line 483, column 38-39: > Command cannot be used in the block > > Any alternative solutions ? > > Thanks in advance. > > kkh > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > From khamlichi.khalil at gmail.com Tue Jan 24 03:49:31 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Tue, 24 Jan 2017 08:49:31 +0000 Subject: [OpenSIPS-Users] scheduled concurrent call reporting In-Reply-To: <93a0287e-1c78-849c-a11e-31f62a17737b@opensips.org> References: <93a0287e-1c78-849c-a11e-31f62a17737b@opensips.org> Message-ID: Hi Răzvan, would $stat(active_dialogs) give detailed stats ? I mean for each label I put on the calls ? example if I am labeling by IP would I get from $stat(active_dialogs) stats by label ? On Tue, Jan 24, 2017 at 8:38 AM, Răzvan Crainea wrote: > Hello, Khalil! > > You could check the $stat(active_dialogs) pvar, which will return the > number of ongoing dialogs. > > Best regards, > > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > > On 01/24/2017 01:05 AM, Khalil Khamlichi wrote: > >> the idea is that I don't need to get the number of calls 30 times per >> second which would happens if I save to redis on each invite. scheduling >> the saving to redis every 10 seconds serves well my purpose but the >> timer_route doesn't seem to accept get_profile_size() >> >> any hints would be appreciated. >> >> On Mon, Jan 23, 2017 at 10:39 PM, Khalil Khamlichi >> > wrote: >> >> Hi, >> >> I am trying to get call load information out of opensips at regular >> intervals to get some sort of realtime view of the load on the server. >> >> After applying profiles on the the INVITEs, I have tried to call >> get_profile_size from a timer_route. >> I am getting error : >> >> CRITICAL:core:yyerror: parse error in config file >> /usr/local//etc/opensips/opensips.cfg, line 483, column 38-39: >> Command cannot be used in the block >> >> Any alternative solutions ? >> >> Thanks in advance. >> >> kkh >> >> >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Tue Jan 24 04:48:55 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Tue, 24 Jan 2017 09:48:55 +0000 Subject: [OpenSIPS-Users] scheduled concurrent call reporting In-Reply-To: References: <93a0287e-1c78-849c-a11e-31f62a17737b@opensips.org> Message-ID: I looked up at the docs, $stat(active_dialogs) is for the whole system, If there is no way to call get_profile_size() automatically from whithin opensips I will need to fall back to MI fifo from an external script. On Tue, Jan 24, 2017 at 8:49 AM, Khalil Khamlichi < khamlichi.khalil at gmail.com> wrote: > Hi Răzvan, would $stat(active_dialogs) give detailed stats ? I mean for > each label I put on the calls ? example if I am labeling by IP would I get > from $stat(active_dialogs) stats by label ? > > On Tue, Jan 24, 2017 at 8:38 AM, Răzvan Crainea > wrote: > >> Hello, Khalil! >> >> You could check the $stat(active_dialogs) pvar, which will return the >> number of ongoing dialogs. >> >> Best regards, >> >> Răzvan Crainea >> OpenSIPS Core Developer >> http://www.opensips-solutions.com >> >> On 01/24/2017 01:05 AM, Khalil Khamlichi wrote: >> >>> the idea is that I don't need to get the number of calls 30 times per >>> second which would happens if I save to redis on each invite. scheduling >>> the saving to redis every 10 seconds serves well my purpose but the >>> timer_route doesn't seem to accept get_profile_size() >>> >>> any hints would be appreciated. >>> >>> On Mon, Jan 23, 2017 at 10:39 PM, Khalil Khamlichi >>> > wrote: >>> >>> Hi, >>> >>> I am trying to get call load information out of opensips at regular >>> intervals to get some sort of realtime view of the load on the >>> server. >>> >>> After applying profiles on the the INVITEs, I have tried to call >>> get_profile_size from a timer_route. >>> I am getting error : >>> >>> CRITICAL:core:yyerror: parse error in config file >>> /usr/local//etc/opensips/opensips.cfg, line 483, column 38-39: >>> Command cannot be used in the block >>> >>> Any alternative solutions ? >>> >>> Thanks in advance. >>> >>> kkh >>> >>> >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 24 06:06:56 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 13:06:56 +0200 Subject: [OpenSIPS-Users] tcp with opensips . In-Reply-To: References: Message-ID: <2fc516a1-3976-484a-aa9c-bf6c7548c40d@opensips.org> Hi Sasmita, 1.6 is a real old version. The oldest still maintained version is 1.11, so you should consider it. The newer version have support for async (none blocking) TCP support (connect, read, write) so it should not be a problem at all. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/18/2017 03:36 PM, Sasmita Panda wrote: > HI All, > > Earlier there is problem with running tcp with saving data in > database at the same time . Is the problem get solved . If yes then in > which version of opensips . > > I think , there was problem with openisps -1.6 . In heavy load > it was not recomended to run tcp in same instance which is saving data > in database too . > > Can anybody inform me whcih version i should use for this . > > > */Thanks & Regards/* > /Sasmita Panda/ > /Network Testing and Software Engineer/ > /3CLogic , ph:07827611765/ > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 24 06:33:31 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 13:33:31 +0200 Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service In-Reply-To: References: Message-ID: <0c37477f-1cb2-3482-e1e8-7b9efe7e7e1a@opensips.org> Hi, Does this happen ONLY at startup ? without any other warnings during runtime ? There is something interesting in your logs: First is this log, saying you do an infinite loop in a "while" in the script: Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: INFO:core:do_action: max while loops are encountered And secondly all the warning are from the same process (3089) which is the the first SIP UDP listener. Do you use any startup route ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/18/2017 08:30 PM, Ahmed Munir wrote: > Hi, > > I'm currently seeing the warnings when I start opensips service; > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a 1500000 > us delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a 1500000 us > delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a 1500000 us > delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: utimer job has a 2290000 us > delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > INFO:core:do_action: max while loops are encountered > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: > WARNING:core:utimer_ticker: utimer task already scheduled > for 190 ms (now 2470 ms), it may over > lap.. > > > I've tried to update the source code for timer.c (line#: 190) ref: > https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split, > but didn't work at all. > > Currently running 8 child processors, see below; > > [root at qorblpsisprxyd1 ]# opensips -V > version: opensips 2.2.2 (x86_64/linux) > flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, > F_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_lt, epoll_et, sigio_rt, select. > main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7 > > > [root at qorblpsisprxyd1 ]# opensipsctl fifo ps > Process:: ID=0 PID=3083 Type=attendant > Process:: ID=1 PID=3085 Type=MI FIFO > Process:: ID=2 PID=3086 Type=time_keeper > Process:: ID=3 PID=3088 Type=timer > Process:: ID=4 PID=3089 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=5 PID=3091 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=6 PID=3092 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=7 PID=3094 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=8 PID=3096 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=9 PID=3098 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=10 PID=3100 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=11 PID=3102 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=12 PID=3104 Type=Timer handler > > I would like to know what changes required to fix this change? Please > advise. > > -- > Regards, > > Ahmed Munir Chohan > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 24 06:34:27 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 13:34:27 +0200 Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service In-Reply-To: <21840442533f445397309d17eec6bcbe@COPDCEX28.cable.comcast.com> References: <92c380d81d5c45a9a2bce09fe344188e@COPDCEX28.cable.comcast.com> <2d785128-affa-c955-e779-1d4305ec1119@opensips.org> <21840442533f445397309d17eec6bcbe@COPDCEX28.cable.comcast.com> Message-ID: <02f2179c-d838-cd83-d8ef-b0a67870c339@opensips.org> Hi Agalya, Please provide the output of "opensipsctl fifo ps" Best regards. Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/19/2017 04:55 PM, Ramachandran, Agalya (Contractor) wrote: > > Hi Razvan, > > I didn’t see any process that is using more than 80% of a core. > OpenSIPS is simply being idle and these warnings come periodically. > > Like once in couple of hours. I didn’t track the exact time line, how > frequent am getting this warnings. > > Ahmed, > > Do you notice these warnings only when you start OpenSIPS or could see > it in regular intervals? > > Regards, > Agalya > > *From:*Users [mailto:users-bounces at lists.opensips.org] *On Behalf Of > *Razvan Crainea > *Sent:* Thursday, January 19, 2017 3:33 AM > *To:* users at lists.opensips.org > *Subject:* Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start > service > > When starting opensips, is there any opensips process that is using > more than 80% of a core? If so, can you pinpoint the PID in the > opensipsctl ps command? > > Best regards, > > Răzvan Crainea > OpenSIPS Solutions > www.opensips-solutions.com > > On 01/18/2017 11:55 PM, Ramachandran, Agalya (Contractor) wrote: > > Same with my case too. > > Regards, > Agalya > > *From:*Users [mailto:users-bounces at lists.opensips.org] *On Behalf > Of *Ahmed Munir > *Sent:* Wednesday, January 18, 2017 1:31 PM > *To:* OpenSIPs Users > > *Subject:* [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start > service > > Hi, > > I'm currently seeing the warnings when I start opensips service; > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a > 1500000 us delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a 1500000 > us delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a 1500000 > us delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: utimer job has a > 2290000 us delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > INFO:core:do_action : max while loops are > encountered > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: > WARNING:core:utimer_ticker: utimer task already > scheduled for 190 ms (now 2470 ms), it may over > lap.. > > > I've tried to update the source code for timer.c (line#: 190) ref: > https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split, > but didn't work at all. > > Currently running 8 child processors, see below; > > [root at qorblpsisprxyd1 ]# opensips -V > version: opensips 2.2.2 (x86_64/linux) > flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, > F_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_lt, epoll_et, sigio_rt, select. > main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7 > > > [root at qorblpsisprxyd1 ]# opensipsctl fifo ps > Process:: ID=0 PID=3083 Type=attendant > Process:: ID=1 PID=3085 Type=MI FIFO > Process:: ID=2 PID=3086 Type=time_keeper > Process:: ID=3 PID=3088 Type=timer > Process:: ID=4 PID=3089 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=5 PID=3091 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=6 PID=3092 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=7 PID=3094 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=8 PID=3096 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=9 PID=3098 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=10 PID=3100 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=11 PID=3102 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=12 PID=3104 Type=Timer handler > > I would like to know what changes required to fix this change? > Please advise. > > > -- > > Regards, > > Ahmed Munir Chohan > > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 24 06:38:34 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 13:38:34 +0200 Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service In-Reply-To: References: Message-ID: <23db254e-202c-c01c-0ac9-15ccf39f447b@opensips.org> Hi Ahmed, So, the warnings pop up ONLY during startup sequence. Do you use startup route or any module performing mem caching of some DB table (drouting, permission, etc) ? Usually, the first UDP child is doing some heavy lifting during startup. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/19/2017 06:01 PM, Ahmed Munir wrote: > Hi Razvan, > > During starting up the opensips service, I see the first opensips > child process (pid"11172) consumes CPU process to 70-80% and later > drop downs to 0.3 - 0.0 % CPU per core. See below; > > [root at qorblpsisprxyd1 ~]# top -c -u opensips > top - 10:49:54 up 76 days, 23:31, 5 users, load average: 0.00, 0.00, > 0.00 > Tasks: 229 total, 1 running, 228 sleeping, 0 stopped, 0 zombie > Cpu(s): 0.0%us, 0.1%sy, 0.0%ni, 99.9%id, 0.0%wa, 0.0%hi, 0.0%si, > 0.0%st > Mem: 65964364k total, 2568124k used, 63396240k free, 180220k buffers > Swap: 1023996k total, 0k used, 1023996k free, 1226104k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 11177 opensips 20 0 165m 5696 4528 S 0.3 0.0 0:00.23 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11187 opensips 20 0 165m 5628 4460 S 0.3 0.0 0:00.41 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11166 opensips 20 0 165m 6892 5752 S 0.0 0.0 0:00.23 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11168 opensips 20 0 165m 1980 840 S 0.0 0.0 0:00.00 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11169 opensips 20 0 165m 1464 328 S 0.0 0.0 0:00.53 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11171 opensips 20 0 165m 1640 504 S 0.0 0.0 0:00.15 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11172 opensips 20 0 166m 40m 38m S 0.0 0.1 0:02.61 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11174 opensips 20 0 165m 6304 5136 S 0.0 0.0 0:00.24 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11175 opensips 20 0 165m 5884 4716 S 0.0 0.0 0:00.22 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11179 opensips 20 0 165m 7660 6492 S 0.0 0.0 0:00.27 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11181 opensips 20 0 165m 7756 6588 S 0.0 0.0 0:00.33 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11183 opensips 20 0 165m 5520 4352 S 0.0 0.0 0:00.34 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11185 opensips 20 0 165m 7336 6168 S 0.0 0.0 0:00.36 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11189 opensips 20 0 165m 7320 6152 S 0.0 0.0 0:00.36 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11190 opensips 20 0 165m 4688 3528 S 0.0 0.0 0:00.30 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > > [root at qorblpsisprxyd1 ~]# opensipsctl fifo ps > Process:: ID=0 PID=11166 Type=attendant > Process:: ID=1 PID=11168 Type=MI FIFO > Process:: ID=2 PID=11169 Type=time_keeper > Process:: ID=3 PID=11171 Type=timer > Process:: ID=4 PID=11172 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=5 PID=11174 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=6 PID=11175 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=7 PID=11177 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=8 PID=11179 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=9 PID=11181 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=10 PID=11183 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=11 PID=11185 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=12 PID=11187 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=13 PID=11189 Type=SIP receiver udp:10.3.120.94:5060 > > Process:: ID=14 PID=11190 Type=Timer handler > > OpenSIPs used by each CPU processor; > > [root at qorblpsisprxyd1 ~]# ps -o pid,psr,comm -C opensips > PID PSR COMMAND > 11166 0 opensips > 11168 2 opensips > 11169 6 opensips > 11171 5 opensips > 11172 5 opensips > 11174 5 opensips > 11175 5 opensips > 11177 5 opensips > 11179 7 opensips > 11181 1 opensips > 11183 0 opensips > 11185 2 opensips > 11187 5 opensips > 11189 5 opensips > 11190 4 opensips > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 24 06:45:13 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 13:45:13 +0200 Subject: [OpenSIPS-Users] Async DB statement In-Reply-To: References: Message-ID: <119780fe-3b78-8ba5-d73e-ad75b87951e4@opensips.org> Hi Ahmed, Note the $rc holds the return code of the LAST executed statement/instruction/function in the script. In the first case you do it right by saving the ret code of the avp_db_query into a separate variable, so you can use it even later. In the sync script, the $rc, when entering the resume route, it will hold the return code of the avp_db_query() function. But the $rc will be changed when doing the xlog(), the if(), etc...So when you do the last xlog(), the $rc will have nothing to do with the avp_db_query(). If you need it later in the script, better save it, as you do in the first example. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/20/2017 01:31 AM, Ahmed Munir wrote: > Hi, > > Currently I'm trying to use async fucntion for avp_db_query. The issue > I'm facing while using it as not retrieving or returning correct > return code and not execute later part of the routing script. See old > & new DB queries; > > Without Async: > ---------------------- > route[1]{ > ... > > if($var(Outpluseflag) == 0) { > avp_db_query("SELECT Outpulse_number,setid FROM > Prefix_data where Program_prefix = '$var(pg_prefix)'", > "$avp(outpluse), $avp(trunkid)"); > $var(res) = $retcode; # or you can just use $retcode! > xlog("--------- OB Route 1-1 DB fetched value outpluse > -> $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code: $rc | Var > Res: $var(res)-------"); > if ($var(res) > 0) { > cache_store("local", "DID_$tU", > "$avp(outpluse)", 60); > cache_store("local", "Trunk_$tU", > "$avp(trunkid)", 60); > } > #xlog("DB fetched value outpluse -> $avp(outpluse) | > trunkid -> $avp(trunkid) | Return Code -> $var(res)"); > xlog("--------- OB Route 1-2 DB fetched value outpluse > -> $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code: $rc | Var > Res: $var(res)-------"); > } > } > > With Async: > ------------------- > route[1]{ > > ... > > if($var(Outpluseflag) == 0) { > async(avp_db_query("SELECT Outpulse_number,setid FROM Prefix_data > where Program_prefix = '$var(pg_prefix)'", "$avp(outpluse), > $avp(trunkid)"),ob_route_1); > } > } > > route[ob_route_1]{ > xlog("--------- OB Route 1-1 DB fetched value outpluse -> > $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code: $rc-------"); > > if ($rc > 0) { > cache_store("local", "DID_$tU", "$avp(outpluse)", 60); > cache_store("local", "Trunk_$tU", "$avp(trunkid)", 60); > } > xlog("--------- OB Route 1-2 DB fetched value outpluse -> > $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code: $rc-------"); > > } > > > The records in xlog I'm getting without using async; > > Jan 19 18:05:39 qorblpsisprxyd1 /usr/sbin/opensips[14040]: --------- > OB Route 1-1 DB fetched value outpluse -> 6099020000 | trunkid -> 117 > | Return Code: 1 | Var Res: 1------- > Jan 19 18:05:39 qorblpsisprxyd1 /usr/sbin/opensips[14040]: --------- > OB Route 1-2 DB fetched value outpluse -> 6099020000 | trunkid -> 117 > | Return Code: 1 | Var Res: 1------- > > Whereas, records in xlog I'm getting using async; > > Jan 19 18:10:07 qorblpsisprxyd1 /usr/sbin/opensips[14109]: --------- > OB Route 1-1 DB fetched value outpluse -> 6099020000 | trunkid -> 117 > | Return Code: 1------- > Jan 19 18:10:07 qorblpsisprxyd1 /usr/sbin/opensips[14109]: --------- > OB Route 1-2 DB fetched value outpluse -> 6099020000 | trunkid -> 117 > | Return Code: 0------- > > Is there is way to properly retain the $retcode/$rc in version 2.2.2? > Seems like using async return code(s) are not properly set or the avp > variables are not setting up correct using async statement. > > Please advise, if the above async db statement is correct as shared in > sample above. > > > -- > Regards, > > Ahmed Munir Chohan > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 24 06:50:41 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 13:50:41 +0200 Subject: [OpenSIPS-Users] topology hiding in opensips In-Reply-To: References: Message-ID: <33dab71b-8865-b4cf-0054-4ec1f4f3908f@opensips.org> Hi Alberto, Do you have any logs to show the crash ? also, do you get a corefile (see http://www.opensips.org/Documentation/TroubleShooting-Crash). Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/20/2017 12:14 PM, Alberto Gonzales wrote: > I forgot to mention that doing this resulted in opensips crashing > after 20 minutes :) > > On Fri, Jan 20, 2017 at 9:56 AM, Alberto Gonzales > > wrote: > > Hello grupo, > > We have configured topology hiding in opensips 2.2 this way : > > please confirm to us this is the only thing we need to do or is > there anything else that needs to be added. > > route { > .... > .... > if (has_totag()) { > # sequential request withing a dialog should > # take the path determined by record-routing > #### remplazar : if (loose_route()) { > if (topology_hiding_match()) { > > ... > ... > *## esconder topologia antes de pasar la llamada* > topology_hiding("UC"); > route(RELAY); > } > > > also what could be a quick test to see if this hiding is working > or not. > > thanks in advance. > > Alberto > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 24 06:52:30 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 13:52:30 +0200 Subject: [OpenSIPS-Users] topology hiding in opensips In-Reply-To: References: Message-ID: <5def493a-55c6-e6cd-2ffd-0e96a5eb57b9@opensips.org> Hi, You can do TH with nathelper, BUT be sure to create the dialog + TH AFTER doing the fix_nated_contact(). Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/20/2017 12:42 PM, Alberto Gonzales wrote: > We used instruction in the book, which states at the end of the > paragraph this : > > Topology hiding limitations > You cannot easily combine topology hiding with NAT traversal because > both the > processes mangle the Contact header. Topology hiding will not hide the > address and > other information contained in other headers such as the display in > the From header. > To change the From header, you can use the uac_replace_from() function. > > I think our problem comes from the fact that we are using nathelper > and also an rtpproxy in our script. > > can anyone provide help about activating topology hiding along with > nathelper ? > > thanks in advance. > > > On Fri, Jan 20, 2017 at 10:14 AM, Alberto Gonzales > > wrote: > > I forgot to mention that doing this resulted in opensips crashing > after 20 minutes :) > > On Fri, Jan 20, 2017 at 9:56 AM, Alberto Gonzales > > wrote: > > Hello grupo, > > We have configured topology hiding in opensips 2.2 this way : > > please confirm to us this is the only thing we need to do or > is there anything else that needs to be added. > > route { > .... > .... > if (has_totag()) { > # sequential request withing a dialog should > # take the path determined by record-routing > #### remplazar : if (loose_route()) { > if (topology_hiding_match()) { > > ... > ... > *## esconder topologia antes de pasar la llamada* > topology_hiding("UC"); > route(RELAY); > } > > > also what could be a quick test to see if this hiding is > working or not. > > thanks in advance. > > Alberto > > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 24 06:54:34 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 13:54:34 +0200 Subject: [OpenSIPS-Users] Opensips 1.6 as a Proxy and Presence Server In-Reply-To: <1484823808329-7605662.post@n2.nabble.com> References: <586CAAD9.5060906@easycall.pl> <1483952331826-7605485.post@n2.nabble.com> <5d1de454-7688-43ed-e966-bd5eb20d1678@opensips.org> <1484054601076-7605502.post@n2.nabble.com> <1484640426055-7605593.post@n2.nabble.com> <247fdfc3-93dc-c097-090e-e6faf103eaac@opensips.org> <1484642312675-7605598.post@n2.nabble.com> <1484644764556-7605602.post@n2.nabble.com> <1484823808329-7605662.post@n2.nabble.com> Message-ID: <2669f396-991d-7574-9a75-37ace6208c99@opensips.org> Hi, Those are SIP URIs to be used as contacts by the presence server (a SIP URI pointing back - as address- to the presence server); in a Contact URI, the username part is no relevant (as the contact is a reference to the IP location of the device), so you can put whatever you want as username. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/19/2017 01:03 PM, maatohewetbi wrote: > I want to ask what bolded values mean: > > # -- core presence params -- > modparam("presence","server_address","sip:*sa*@10.10.10.10:5060") > > > # -- pua and pua_dialoginfo parameters -- > modparam("pua_dialoginfo", "presence_server", "sip:*sa*@10.10.10.10:5060") > > I don't really know what to write there. > > > > -- > View this message in context: http://opensips-open-sip-server.1449251.n2.nabble.com/Opensips-1-6-as-a-Proxy-and-Presence-Server-tp7605411p7605662.html > Sent from the OpenSIPS - Users mailing list archive at Nabble.com. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From bogdan at opensips.org Tue Jan 24 07:09:44 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 14:09:44 +0200 Subject: [OpenSIPS-Users] topology hiding in opensips In-Reply-To: References: <5def493a-55c6-e6cd-2ffd-0e96a5eb57b9@opensips.org> Message-ID: <09a1b85d-b7c9-1a29-4188-6f6a4faa763a@opensips.org> Hi, It should be ok, but in your case the TH will not benefit from the dialog module (you do not use it) - all the info to he hidden will be appended to the Contact hdr (as extra param), while when using the dialog support, this info is stored into the dialog. To be honest, I never tried the combination of nathelper and TH _without_ dialog support. But give it a try...if you get a trace, I can check if ok. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/24/2017 02:03 PM, Alberto Gonzales wrote: > Thanks Bogdan, Well, I have fix_nated_contact() at the very top of my > script : > > route{ > > force_rport(); > if (nat_uac_test("23")) { > fix_nated_contact(); > setflag(NAT); > } > > > if (!mf_process_maxfwd_header("10")) { > sl_send_reply("483","Too Many Hops"); > exit; > } > > .... > .... > if (has_totag()) { > # sequential request withing a dialog should > # take the path determined by record-routing > #### remplazar : if (loose_route()) { > if (topology_hiding_match()) { > > ... > ... > *## esconder topologia antes de pasar la llamada* > topology_hiding("UC"); > route(RELAY); > } > > so is my script correct ? > I just want to make sure I have a correct script before I do any > further work on this. > > Thanks. > > On Tue, Jan 24, 2017 at 11:52 AM, Bogdan-Andrei Iancu > > wrote: > > Hi, > > You can do TH with nathelper, BUT be sure to create the dialog + > TH AFTER doing the fix_nated_contact(). > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 01/20/2017 12:42 PM, Alberto Gonzales wrote: >> We used instruction in the book, which states at the end of the >> paragraph this : >> Topology hiding limitations >> You cannot easily combine topology hiding with NAT traversal >> because both the >> processes mangle the Contact header. Topology hiding will not >> hide the address and >> other information contained in other headers such as the display >> in the From header. >> To change the From header, you can use the uac_replace_from() >> function. >> I think our problem comes from the fact that we are using >> nathelper and also an rtpproxy in our script. >> can anyone provide help about activating topology hiding along >> with nathelper ? >> thanks in advance. >> On Fri, Jan 20, 2017 at 10:14 AM, Alberto Gonzales >> > >> wrote: >> >> I forgot to mention that doing this resulted in opensips >> crashing after 20 minutes :) >> On Fri, Jan 20, 2017 at 9:56 AM, Alberto Gonzales >> > > wrote: >> >> Hello grupo, >> We have configured topology hiding in opensips 2.2 this >> way : >> please confirm to us this is the only thing we need to do >> or is there anything else that needs to be added. >> route { >> .... >> .... >> if (has_totag()) { # sequential request withing a >> dialog should # take the path determined by >> record-routing #### remplazar : if (loose_route()) { if >> (topology_hiding_match()) { ... >> ... >> *## esconder topologia antes de pasar la llamada* >> topology_hiding("UC"); route(RELAY);} >> also what could be a quick test to see if this hiding is >> working or not. >> thanks in advance. >> Alberto >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From albertosgonzale at gmail.com Tue Jan 24 07:20:07 2017 From: albertosgonzale at gmail.com (Alberto Gonzales) Date: Tue, 24 Jan 2017 12:20:07 +0000 Subject: [OpenSIPS-Users] topology hiding in opensips In-Reply-To: <09a1b85d-b7c9-1a29-4188-6f6a4faa763a@opensips.org> References: <5def493a-55c6-e6cd-2ffd-0e96a5eb57b9@opensips.org> <09a1b85d-b7c9-1a29-4188-6f6a4faa763a@opensips.org> Message-ID: I am using dialog in my script, here is the part of main function # apply transformations from dialplan table dp_translate("0","$rU/$rU"); # route calls based on prefix if ( !do_routing("1","W",,"$var(rule_attrs)","$var(gw_attrs)") ) { send_reply("404","No Route found"); exit; } $acc_extra(gwid)=$avp(gw_id); t_on_failure("GW_FAILOVER"); do_accounting("db|log","cdr|missed",); #NAT if (isbflagset(NAT)) setflag(NAT); #NAT #TOPOHIDE toopology_hiding("UC"); #TOPOHIDE route(RELAY); } On Tue, Jan 24, 2017 at 12:09 PM, Bogdan-Andrei Iancu wrote: > Hi, > > It should be ok, but in your case the TH will not benefit from the dialog > module (you do not use it) - all the info to he hidden will be appended to > the Contact hdr (as extra param), while when using the dialog support, this > info is stored into the dialog. > > To be honest, I never tried the combination of nathelper and TH _without_ > dialog support. But give it a try...if you get a trace, I can check if ok. > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developerhttp://www.opensips-solutions.com > > On 01/24/2017 02:03 PM, Alberto Gonzales wrote: > > Thanks Bogdan, Well, I have fix_nated_contact() at the very top of my > script : > > route{ > > force_rport(); > if (nat_uac_test("23")) { > fix_nated_contact(); > setflag(NAT); > } > > > if (!mf_process_maxfwd_header("10")) { > sl_send_reply("483","Too Many Hops"); > exit; > } > > .... > .... > if (has_totag()) { > # sequential request withing a dialog should > # take the path determined by record-routing > #### remplazar : if (loose_route()) { > if (topology_hiding_match()) { > > ... > ... > *## esconder topologia antes de pasar la llamada* > topology_hiding("UC"); > route(RELAY); > } > > so is my script correct ? > I just want to make sure I have a correct script before I do any further > work on this. > > Thanks. > > On Tue, Jan 24, 2017 at 11:52 AM, Bogdan-Andrei Iancu < > bogdan at opensips.org> wrote: > >> Hi, >> >> You can do TH with nathelper, BUT be sure to create the dialog + TH AFTER >> doing the fix_nated_contact(). >> >> Regards, >> >> Bogdan-Andrei Iancu >> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com >> >> On 01/20/2017 12:42 PM, Alberto Gonzales wrote: >> >> We used instruction in the book, which states at the end of the paragraph >> this : >> Topology hiding limitations >> You cannot easily combine topology hiding with NAT traversal because both >> the >> processes mangle the Contact header. Topology hiding will not hide the >> address and >> other information contained in other headers such as the display in the >> From header. >> To change the From header, you can use the uac_replace_from() function. >> I think our problem comes from the fact that we are using nathelper and >> also an rtpproxy in our script. >> can anyone provide help about activating topology hiding along with >> nathelper ? >> thanks in advance. >> On Fri, Jan 20, 2017 at 10:14 AM, Alberto Gonzales < >> albertosgonzale at gmail.com> wrote: >>> >>> I forgot to mention that doing this resulted in opensips crashing after >>> 20 minutes :) >>> On Fri, Jan 20, 2017 at 9:56 AM, Alberto Gonzales < >>> albertosgonzale at gmail.com> wrote: >>>> >>>> Hello grupo, >>>> We have configured topology hiding in opensips 2.2 this way : >>>> please confirm to us this is the only thing we need to do or is there >>>> anything else that needs to be added. >>>> route { >>>> .... >>>> .... >>>> if (has_totag()) { # sequential request withing >>>> a dialog should # take the path determined by >>>> record-routing #### remplazar : if (loose_route()) { >>>> if (topology_hiding_match()) { ... >>>> ... >>>> *## esconder topologia antes de pasar la llamada* >>>> topology_hiding("UC"); route(RELAY); } >>>> also what could be a quick test to see if this hiding is working or not. >>>> thanks in advance. >>>> Alberto >>>> >>> _______________________________________________ >> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 24 07:53:45 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 14:53:45 +0200 Subject: [OpenSIPS-Users] topology hiding in opensips In-Reply-To: References: <5def493a-55c6-e6cd-2ffd-0e96a5eb57b9@opensips.org> <09a1b85d-b7c9-1a29-4188-6f6a4faa763a@opensips.org> Message-ID: I see no indication of creating a dialog in your script sample :(...Are you sure about this ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/24/2017 02:20 PM, Alberto Gonzales wrote: > I am using dialog in my script, > here is the part of main function > > # apply transformations from dialplan table > dp_translate("0","$rU/$rU"); > > # route calls based on prefix > if ( !do_routing("1","W",,"$var(rule_attrs)","$var(gw_attrs)") ) { > send_reply("404","No Route found"); > exit; > } > > $acc_extra(gwid)=$avp(gw_id); > > t_on_failure("GW_FAILOVER"); > > do_accounting("db|log","cdr|missed",); > #NAT > if (isbflagset(NAT)) setflag(NAT); > #NAT > #TOPOHIDE > toopology_hiding("UC"); > #TOPOHIDE > route(RELAY); > > } > > > > On Tue, Jan 24, 2017 at 12:09 PM, Bogdan-Andrei Iancu > > wrote: > > Hi, > > It should be ok, but in your case the TH will not benefit from the > dialog module (you do not use it) - all the info to he hidden will > be appended to the Contact hdr (as extra param), while when using > the dialog support, this info is stored into the dialog. > > To be honest, I never tried the combination of nathelper and TH > _without_ dialog support. But give it a try...if you get a trace, > I can check if ok. > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 01/24/2017 02:03 PM, Alberto Gonzales wrote: >> Thanks Bogdan, Well, I have fix_nated_contact() at the very top >> of my script : >> route{ force_rport(); if (nat_uac_test("23")) { >> fix_nated_contact(); setflag(NAT); } >> if (!mf_process_maxfwd_header("10")) { >> sl_send_reply("483","Too Many >> Hops"); exit; } >> .... >> .... >> if (has_totag()) { # sequential request withing a dialog >> should # take the path determined by record-routing #### >> remplazar : if (loose_route()) { if (topology_hiding_match()) { ... >> ... >> *## esconder topologia antes de pasar la llamada* >> topology_hiding("UC"); route(RELAY);} >> so is my script correct ? >> I just want to make sure I have a correct script before I do any >> further work on this. >> Thanks. >> On Tue, Jan 24, 2017 at 11:52 AM, Bogdan-Andrei Iancu >> > wrote: >> >> Hi, You can do TH with nathelper, BUT be sure to create the >> dialog + TH AFTER doing the fix_nated_contact(). Regards, >> >> Bogdan-Andrei Iancu >> OpenSIPS Founder and Developer >> http://www.opensips-solutions.com >> >> >> On 01/20/2017 12:42 PM, Alberto Gonzales wrote: >>> We used instruction in the book, which states at the end of >>> the paragraph this : >>> Topology hiding limitations >>> You cannot easily combine topology hiding with NAT traversal >>> because both the >>> processes mangle the Contact header. Topology hiding will >>> not hide the address and >>> other information contained in other headers such as the >>> display in the From header. >>> To change the From header, you can use the >>> uac_replace_from() function. >>> I think our problem comes from the fact that we are using >>> nathelper and also an rtpproxy in our script. >>> can anyone provide help about activating topology hiding >>> along with nathelper ? >>> thanks in advance. >>> On Fri, Jan 20, 2017 at 10:14 AM, Alberto Gonzales >>> >> > wrote: >>> >>> I forgot to mention that doing this resulted in opensips >>> crashing after 20 minutes :) >>> On Fri, Jan 20, 2017 at 9:56 AM, Alberto Gonzales >>> >> > wrote: >>> >>> Hello grupo, >>> We have configured topology hiding in opensips 2.2 >>> this way : >>> please confirm to us this is the only thing we need >>> to do or is there anything else that needs to be added. >>> route { >>> .... >>> .... >>> if (has_totag()) { # sequential request >>> withing a dialog should # take the path determined >>> by record-routing #### remplazar : if >>> (loose_route()) { if (topology_hiding_match()) { ... >>> ... >>> *## esconder topologia antes de pasar la llamada* >>> topology_hiding("UC"); route(RELAY);} >>> also what could be a quick test to see if this >>> hiding is working or not. >>> thanks in advance. >>> Alberto >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Tue Jan 24 08:02:48 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Tue, 24 Jan 2017 13:02:48 +0000 Subject: [OpenSIPS-Users] topology hiding in opensips In-Reply-To: References: <5def493a-55c6-e6cd-2ffd-0e96a5eb57b9@opensips.org> <09a1b85d-b7c9-1a29-4188-6f6a4faa763a@opensips.org> Message-ID: sorry : # record routing record_route(); # create dialog with timeout if ( !create_dialog("B") ) { send_reply("500","Internal Server Error"); exit; } # apply transformations from dialplan table dp_translate("0","$rU/$rU"); # route calls based on prefix if ( !do_routing("1","W",,"$var(rule_attrs)","$var(gw_attrs)") ) { send_reply("404","No Route found"); exit; } $acc_extra(gwid)=$avp(gw_id); t_on_failure("GW_FAILOVER"); do_accounting("db|log","cdr|missed",); #NAT if (isbflagset(NAT)) setflag(NAT); #NAT #TOPOHIDE toopology_hiding("UC"); #TOPOHIDE route(RELAY); } -------------- next part -------------- An HTML attachment was scrubbed... URL: From albertosgonzale at gmail.com Tue Jan 24 08:11:53 2017 From: albertosgonzale at gmail.com (Alberto Gonzales) Date: Tue, 24 Jan 2017 13:11:53 +0000 Subject: [OpenSIPS-Users] topology hiding in opensips In-Reply-To: References: <5def493a-55c6-e6cd-2ffd-0e96a5eb57b9@opensips.org> <09a1b85d-b7c9-1a29-4188-6f6a4faa763a@opensips.org> Message-ID: lunch time here, gracias khalil. On Tue, Jan 24, 2017 at 1:02 PM, Khalil Khamlichi < khamlichi.khalil at gmail.com> wrote: > sorry : > > # record routing > record_route(); > > # create dialog with timeout > if ( !create_dialog("B") ) { > send_reply("500","Internal Server Error"); > exit; > } > > # apply transformations from dialplan table > dp_translate("0","$rU/$rU"); > > # route calls based on prefix > if ( !do_routing("1","W",,"$var(rule_attrs)","$var(gw_attrs)") ) { > send_reply("404","No Route found"); > exit; > } > > $acc_extra(gwid)=$avp(gw_id); > > t_on_failure("GW_FAILOVER"); > > do_accounting("db|log","cdr|missed",); > #NAT > if (isbflagset(NAT)) setflag(NAT); > #NAT > #TOPOHIDE > toopology_hiding("UC"); > #TOPOHIDE > route(RELAY); > > } > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahmedmunir007 at gmail.com Tue Jan 24 08:44:35 2017 From: ahmedmunir007 at gmail.com (Ahmed Munir) Date: Tue, 24 Jan 2017 08:44:35 -0500 Subject: [OpenSIPS-Users] Async DB statement Message-ID: Thanks, have been working on this and it is working. Btw, I would like to know, is there a way to resume route while using async avp_db_query? As currently setting/declaring another async route for DB query, looking for resume route in main routing script. On Tue, Jan 24, 2017 at 6:45 AM, Bogdan-Andrei Iancu wrote: > Hi Ahmed, > > Note the $rc holds the return code of the LAST executed > statement/instruction/function in the script. In the first case you do it > right by saving the ret code of the avp_db_query into a separate variable, > so you can use it even later. > > In the sync script, the $rc, when entering the resume route, it will hold > the return code of the avp_db_query() function. But the $rc will be changed > when doing the xlog(), the if(), etc...So when you do the last xlog(), the > $rc will have nothing to do with the avp_db_query(). If you need it later > in the script, better save it, as you do in the first example. > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developerhttp://www.opensips-solutions.com > > On 01/20/2017 01:31 AM, Ahmed Munir wrote: > > Hi, > > Currently I'm trying to use async fucntion for avp_db_query. The issue I'm > facing while using it as not retrieving or returning correct return code > and not execute later part of the routing script. See old & new DB queries; > > Without Async: > ---------------------- > route[1]{ > ... > > if($var(Outpluseflag) == 0) { > avp_db_query("SELECT Outpulse_number,setid FROM Prefix_data > where Program_prefix = '$var(pg_prefix)'", "$avp(outpluse), $avp(trunkid)"); > $var(res) = $retcode; # or you can just use $retcode! > xlog("--------- OB Route 1-1 DB fetched value outpluse -> > $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code: $rc | Var Res: > $var(res)-------"); > if ($var(res) > 0) { > cache_store("local", "DID_$tU", > "$avp(outpluse)", 60); > cache_store("local", "Trunk_$tU", > "$avp(trunkid)", 60); > } > #xlog("DB fetched value outpluse -> $avp(outpluse) | > trunkid -> $avp(trunkid) | Return Code -> $var(res)"); > xlog("--------- OB Route 1-2 DB fetched value outpluse -> > $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code: $rc | Var Res: > $var(res)-------"); > } > } > > With Async: > ------------------- > route[1]{ > > ... > > if($var(Outpluseflag) == 0) { > async(avp_db_query("SELECT Outpulse_number,setid FROM Prefix_data > where Program_prefix = '$var(pg_prefix)'", "$avp(outpluse), > $avp(trunkid)"),ob_route_1); > } > } > > route[ob_route_1]{ > xlog("--------- OB Route 1-1 DB fetched value outpluse -> > $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code: $rc-------"); > > if ($rc > 0) { > cache_store("local", "DID_$tU", "$avp(outpluse)", 60); > cache_store("local", "Trunk_$tU", "$avp(trunkid)", 60); > } > xlog("--------- OB Route 1-2 DB fetched value outpluse -> > $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code: $rc-------"); > > } > > > The records in xlog I'm getting without using async; > > Jan 19 18:05:39 qorblpsisprxyd1 /usr/sbin/opensips[14040]: --------- OB > Route 1-1 DB fetched value outpluse -> 6099020000 <(609)%20902-0000> | > trunkid -> 117 | Return Code: 1 | Var Res: 1------- > Jan 19 18:05:39 qorblpsisprxyd1 /usr/sbin/opensips[14040]: --------- OB > Route 1-2 DB fetched value outpluse -> 6099020000 <(609)%20902-0000> | > trunkid -> 117 | Return Code: 1 | Var Res: 1------- > > Whereas, records in xlog I'm getting using async; > > Jan 19 18:10:07 qorblpsisprxyd1 /usr/sbin/opensips[14109]: --------- OB > Route 1-1 DB fetched value outpluse -> 6099020000 <(609)%20902-0000> | > trunkid -> 117 | Return Code: 1------- > Jan 19 18:10:07 qorblpsisprxyd1 /usr/sbin/opensips[14109]: --------- OB > Route 1-2 DB fetched value outpluse -> 6099020000 <(609)%20902-0000> | > trunkid -> 117 | Return Code: 0------- > > Is there is way to properly retain the $retcode/$rc in version 2.2.2? > Seems like using async return code(s) are not properly set or the avp > variables are not setting up correct using async statement. > > Please advise, if the above async db statement is correct as shared in > sample above. > > > -- > Regards, > > Ahmed Munir Chohan > > > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From ahmedmunir007 at gmail.com Tue Jan 24 08:49:38 2017 From: ahmedmunir007 at gmail.com (Ahmed Munir) Date: Tue, 24 Jan 2017 08:49:38 -0500 Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service In-Reply-To: <23db254e-202c-c01c-0ac9-15ccf39f447b@opensips.org> References: <23db254e-202c-c01c-0ac9-15ccf39f447b@opensips.org> Message-ID: Yes, using startup route in my routing script and running DB query. This kind of warning I didn't face using 1.6 and 1.8 opensips versions but 2.2.2. Will you recommend async statement for my current routing (see below) for the startup? startup_route { $var(res) = 1; $avp(tmp) = "1"; # $var(x) = 0; while($var(res) > 0) { $var(res) = avp_db_query("SELECT Distinct One800, dnis FROM DNIS_Mapping where One800 > $avp(tmp) order by One800;", "$avp(One800), $avp(dnis)"); if($var(res) >= 0) { $var(i) = 0; while($(avp(One800)[$var(i)]) != "NULL") { cache_store("local", "DNIS_$(avp(dnis)[$var(i)])", "$(avp(One800)[$var(i)])"); $avp(tmp) = $(avp(One800)[$var(i)]); # $var(x) = $var(x) + 1; $(avp(One800)[$var(i)]) = "NULL"; $var(i) = $var(i) + 1; # xlog("$var(x) : $(avp(s:dnis)[$var(i)])"); } } } } On Tue, Jan 24, 2017 at 6:38 AM, Bogdan-Andrei Iancu wrote: > Hi Ahmed, > > So, the warnings pop up ONLY during startup sequence. Do you use startup > route or any module performing mem caching of some DB table (drouting, > permission, etc) ? Usually, the first UDP child is doing some heavy lifting > during startup. > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developerhttp://www.opensips-solutions.com > > On 01/19/2017 06:01 PM, Ahmed Munir wrote: > > Hi Razvan, > > During starting up the opensips service, I see the first opensips child > process (pid"11172) consumes CPU process to 70-80% and later drop downs to > 0.3 - 0.0 % CPU per core. See below; > > [root at qorblpsisprxyd1 ~]# top -c -u opensips > top - 10:49:54 up 76 days, 23:31, 5 users, load average: 0.00, 0.00, 0.00 > Tasks: 229 total, 1 running, 228 sleeping, 0 stopped, 0 zombie > Cpu(s): 0.0%us, 0.1%sy, 0.0%ni, 99.9%id, 0.0%wa, 0.0%hi, 0.0%si, > 0.0%st > Mem: 65964364k total, 2568124k used, 63396240k free, 180220k buffers > Swap: 1023996k total, 0k used, 1023996k free, 1226104k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 11177 opensips 20 0 165m 5696 4528 S 0.3 0.0 0:00.23 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11187 opensips 20 0 165m 5628 4460 S 0.3 0.0 0:00.41 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11166 opensips 20 0 165m 6892 5752 S 0.0 0.0 0:00.23 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11168 opensips 20 0 165m 1980 840 S 0.0 0.0 0:00.00 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11169 opensips 20 0 165m 1464 328 S 0.0 0.0 0:00.53 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11171 opensips 20 0 165m 1640 504 S 0.0 0.0 0:00.15 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11172 opensips 20 0 166m 40m 38m S 0.0 0.1 0:02.61 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11174 opensips 20 0 165m 6304 5136 S 0.0 0.0 0:00.24 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11175 opensips 20 0 165m 5884 4716 S 0.0 0.0 0:00.22 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11179 opensips 20 0 165m 7660 6492 S 0.0 0.0 0:00.27 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11181 opensips 20 0 165m 7756 6588 S 0.0 0.0 0:00.33 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11183 opensips 20 0 165m 5520 4352 S 0.0 0.0 0:00.34 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11185 opensips 20 0 165m 7336 6168 S 0.0 0.0 0:00.36 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11189 opensips 20 0 165m 7320 6152 S 0.0 0.0 0:00.36 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > 11190 opensips 20 0 165m 4688 3528 S 0.0 0.0 0:00.30 > /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g opensips > > [root at qorblpsisprxyd1 ~]# opensipsctl fifo ps > Process:: ID=0 PID=11166 Type=attendant > Process:: ID=1 PID=11168 Type=MI FIFO > Process:: ID=2 PID=11169 Type=time_keeper > Process:: ID=3 PID=11171 Type=timer > Process:: ID=4 PID=11172 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=5 PID=11174 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=6 PID=11175 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=7 PID=11177 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=8 PID=11179 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=9 PID=11181 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=10 PID=11183 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=11 PID=11185 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=12 PID=11187 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=13 PID=11189 Type=SIP receiver udp:10.3.120.94:5060 > Process:: ID=14 PID=11190 Type=Timer handler > > OpenSIPs used by each CPU processor; > > [root at qorblpsisprxyd1 ~]# ps -o pid,psr,comm -C opensips > PID PSR COMMAND > 11166 0 opensips > 11168 2 opensips > 11169 6 opensips > 11171 5 opensips > 11172 5 opensips > 11174 5 opensips > 11175 5 opensips > 11177 5 opensips > 11179 7 opensips > 11181 1 opensips > 11183 0 opensips > 11185 2 opensips > 11187 5 opensips > 11189 5 opensips > 11190 4 opensips > > > -- Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 24 09:09:52 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 16:09:52 +0200 Subject: [OpenSIPS-Users] Async DB statement In-Reply-To: References: Message-ID: Could you please rephrase / detail your question, as I do not understand what you are asking. Thanks, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/24/2017 03:44 PM, Ahmed Munir wrote: > Thanks, have been working on this and it is working. > > Btw, I would like to know, is there a way to resume route while using > async avp_db_query? As currently setting/declaring another async route > for DB query, looking for resume route in main routing script. > > On Tue, Jan 24, 2017 at 6:45 AM, Bogdan-Andrei Iancu > > wrote: > > Hi Ahmed, > > Note the $rc holds the return code of the LAST executed > statement/instruction/function in the script. In the first case > you do it right by saving the ret code of the avp_db_query into a > separate variable, so you can use it even later. > > In the sync script, the $rc, when entering the resume route, it > will hold the return code of the avp_db_query() function. But the > $rc will be changed when doing the xlog(), the if(), etc...So when > you do the last xlog(), the $rc will have nothing to do with the > avp_db_query(). If you need it later in the script, better save > it, as you do in the first example. > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 01/20/2017 01:31 AM, Ahmed Munir wrote: >> Hi, >> Currently I'm trying to use async fucntion for avp_db_query. The >> issue I'm facing while using it as not retrieving or returning >> correct return code and not execute later part of the routing >> script. See old & new DB queries; >> Without Async: ---------------------- route[1]{ ... >> if($var(Outpluseflag) == 0) { avp_db_query("SELECT >> Outpulse_number,setid FROM Prefix_data where Program_prefix = >> '$var(pg_prefix)'", "$avp(outpluse), $avp(trunkid)"); >> $var(res) = $retcode; # or you can just use >> $retcode! xlog("--------- OB Route 1-1 DB fetched >> value outpluse -> $avp(outpluse) | trunkid -> $avp(trunkid) | >> Return Code: $rc | Var Res: $var(res)-------"); >> if ($var(res) > 0) { >> cache_store("local", "DID_$tU", "$avp(outpluse)", 60); >> cache_store("local", "Trunk_$tU", >> "$avp(trunkid)", 60); } #xlog("DB >> fetched value outpluse -> $avp(outpluse) | trunkid -> >> $avp(trunkid) | Return Code -> $var(res)"); >> xlog("--------- OB Route 1-2 DB fetched value outpluse -> >> $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code: $rc | >> Var Res: $var(res)-------"); } >> } With Async: ------------------- >> route[1]{ >> ... >> if($var(Outpluseflag) == 0) { async(avp_db_query("SELECT >> Outpulse_number,setid FROM Prefix_data where Program_prefix = >> '$var(pg_prefix)'", "$avp(outpluse), $avp(trunkid)"),ob_route_1); >> } } >> route[ob_route_1]{ xlog("--------- OB Route 1-1 DB >> fetched value outpluse -> $avp(outpluse) | trunkid -> >> $avp(trunkid) | Return Code: $rc-------"); if ($rc > 0) { >> cache_store("local", "DID_$tU", "$avp(outpluse)", >> 60); cache_store("local", "Trunk_$tU", >> "$avp(trunkid)", 60); } xlog("--------- OB Route >> 1-2 DB fetched value outpluse -> $avp(outpluse) | trunkid -> >> $avp(trunkid) | Return Code: $rc-------"); } >> The records in xlog I'm getting without using async; Jan 19 >> 18:05:39 qorblpsisprxyd1 /usr/sbin/opensips[14040]: --------- OB >> Route 1-1 DB fetched value outpluse -> 6099020000 >> | trunkid -> 117 | Return Code: 1 | >> Var Res: 1------- Jan 19 18:05:39 qorblpsisprxyd1 >> /usr/sbin/opensips[14040]: --------- OB Route 1-2 DB fetched >> value outpluse -> 6099020000 | trunkid >> -> 117 | Return Code: 1 | Var Res: 1------- >> Whereas, records in xlog I'm getting using async; Jan 19 18:10:07 >> qorblpsisprxyd1 /usr/sbin/opensips[14109]: --------- OB Route 1-1 >> DB fetched value outpluse -> 6099020000 >> | trunkid -> 117 | Return Code: >> 1------- Jan 19 18:10:07 qorblpsisprxyd1 >> /usr/sbin/opensips[14109]: --------- OB Route 1-2 DB fetched >> value outpluse -> 6099020000 | trunkid >> -> 117 | Return Code: 0------- >> Is there is way to properly retain the $retcode/$rc in version >> 2.2.2? Seems like using async return code(s) are not properly set >> or the avp variables are not setting up correct using async >> statement. >> Please advise, if the above async db statement is correct as >> shared in sample above. >> -- >> Regards, Ahmed Munir Chohan >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > > -- > Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 24 09:12:24 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 16:12:24 +0200 Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service In-Reply-To: References: <23db254e-202c-c01c-0ac9-15ccf39f447b@opensips.org> Message-ID: <5ad0aa83-0f9e-8b19-ffcd-e90996bd5c85@opensips.org> The versions before 2.1 had a completely different approach on hoe the timer jobs were handled - different code, so no such warnings. The 2.1 introduces the a more flexible and scalable processing for the timer jobs. Could you confirm that removing the DB op from the startup route eliminates the warnings ? Thanks, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/24/2017 03:49 PM, Ahmed Munir wrote: > Yes, using startup route in my routing script and running DB query. > This kind of warning I didn't face using 1.6 and 1.8 opensips versions > but 2.2.2. > > Will you recommend async statement for my current routing (see below) > for the startup? > > startup_route > { > $var(res) = 1; > $avp(tmp) = "1"; > # $var(x) = 0; > while($var(res) > 0) > { > $var(res) = avp_db_query("SELECT Distinct One800, dnis FROM > DNIS_Mapping where One800 > $avp(tmp) order by One800;", > "$avp(One800), $avp(dnis)"); > if($var(res) >= 0) > { > $var(i) = 0; > while($(avp(One800)[$var(i)]) != "NULL") > { > cache_store("local", > "DNIS_$(avp(dnis)[$var(i)])", "$(avp(One800)[$var(i)])"); > $avp(tmp) = $(avp(One800)[$var(i)]); > # $var(x) = $var(x) + 1; > $(avp(One800)[$var(i)]) = "NULL"; > $var(i) = $var(i) + 1; > # xlog("$var(x) : $(avp(s:dnis)[$var(i)])"); > } > } > } > } > > > On Tue, Jan 24, 2017 at 6:38 AM, Bogdan-Andrei Iancu > > wrote: > > Hi Ahmed, > > So, the warnings pop up ONLY during startup sequence. Do you use > startup route or any module performing mem caching of some DB > table (drouting, permission, etc) ? Usually, the first UDP child > is doing some heavy lifting during startup. > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 01/19/2017 06:01 PM, Ahmed Munir wrote: >> Hi Razvan, >> During starting up the opensips service, I see the first opensips >> child process (pid"11172) consumes CPU process to 70-80% and >> later drop downs to 0.3 - 0.0 % CPU per core. See below; >> [root at qorblpsisprxyd1 ~]# top -c -u opensips top - 10:49:54 up 76 >> days, 23:31, 5 users, load average: 0.00, 0.00, 0.00 Tasks: 229 >> total, 1 running, 228 sleeping, 0 stopped, 0 zombie >> Cpu(s): 0.0%us, 0.1%sy, 0.0%ni, 99.9%id, 0.0%wa, 0.0%hi, >> 0.0%si, 0.0%st Mem: 65964364k total, 2568124k used, 63396240k >> free, 180220k buffers Swap: 1023996k total, 0k used, >> 1023996k free, 1226104k cached PID USER PR NI VIRT >> RES SHR S %CPU %MEM TIME+ COMMAND 11177 opensips 20 0 >> 165m 5696 4528 S 0.3 0.0 0:00.23 /usr/sbin/opensips -P >> /var/run/opensips.pid -m 64 -u opensips -g opensips 11187 >> opensips 20 0 165m 5628 4460 S 0.3 0.0 0:00.41 >> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g >> opensips 11166 opensips 20 0 165m 6892 5752 S 0.0 0.0 >> 0:00.23 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u >> opensips -g opensips 11168 opensips 20 0 165m 1980 840 S >> 0.0 0.0 0:00.00 /usr/sbin/opensips -P /var/run/opensips.pid -m >> 64 -u opensips -g opensips 11169 opensips 20 0 165m 1464 328 >> S 0.0 0.0 0:00.53 /usr/sbin/opensips -P /var/run/opensips.pid >> -m 64 -u opensips -g opensips 11171 opensips 20 0 165m 1640 >> 504 S 0.0 0.0 0:00.15 /usr/sbin/opensips -P >> /var/run/opensips.pid -m 64 -u opensips -g opensips 11172 >> opensips 20 0 166m 40m 38m S 0.0 0.1 0:02.61 >> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g >> opensips 11174 opensips 20 0 165m 6304 5136 S 0.0 0.0 >> 0:00.24 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u >> opensips -g opensips 11175 opensips 20 0 165m 5884 4716 S >> 0.0 0.0 0:00.22 /usr/sbin/opensips -P /var/run/opensips.pid -m >> 64 -u opensips -g opensips 11179 opensips 20 0 165m 7660 6492 >> S 0.0 0.0 0:00.27 /usr/sbin/opensips -P /var/run/opensips.pid >> -m 64 -u opensips -g opensips 11181 opensips 20 0 165m 7756 >> 6588 S 0.0 0.0 0:00.33 /usr/sbin/opensips -P >> /var/run/opensips.pid -m 64 -u opensips -g opensips 11183 >> opensips 20 0 165m 5520 4352 S 0.0 0.0 0:00.34 >> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u opensips -g >> opensips 11185 opensips 20 0 165m 7336 6168 S 0.0 0.0 >> 0:00.36 /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u >> opensips -g opensips 11189 opensips 20 0 165m 7320 6152 S >> 0.0 0.0 0:00.36 /usr/sbin/opensips -P /var/run/opensips.pid -m >> 64 -u opensips -g opensips 11190 opensips 20 0 165m 4688 3528 >> S 0.0 0.0 0:00.30 /usr/sbin/opensips -P /var/run/opensips.pid >> -m 64 -u opensips -g opensips >> [root at qorblpsisprxyd1 ~]# opensipsctl fifo ps Process:: ID=0 >> PID=11166 Type=attendant Process:: ID=1 PID=11168 Type=MI FIFO >> Process:: ID=2 PID=11169 Type=time_keeper Process:: ID=3 >> PID=11171 Type=timer Process:: ID=4 PID=11172 Type=SIP receiver >> udp:10.3.120.94:5060 Process:: ID=5 >> PID=11174 Type=SIP receiver udp:10.3.120.94:5060 >> Process:: ID=6 PID=11175 Type=SIP >> receiver udp:10.3.120.94:5060 >> Process:: ID=7 PID=11177 Type=SIP receiver udp:10.3.120.94:5060 >> Process:: ID=8 PID=11179 Type=SIP >> receiver udp:10.3.120.94:5060 >> Process:: ID=9 PID=11181 Type=SIP receiver udp:10.3.120.94:5060 >> Process:: ID=10 PID=11183 Type=SIP >> receiver udp:10.3.120.94:5060 >> Process:: ID=11 PID=11185 Type=SIP receiver udp:10.3.120.94:5060 >> Process:: ID=12 PID=11187 Type=SIP >> receiver udp:10.3.120.94:5060 >> Process:: ID=13 PID=11189 Type=SIP receiver udp:10.3.120.94:5060 >> Process:: ID=14 PID=11190 Type=Timer >> handler OpenSIPs used by each CPU processor; >> [root at qorblpsisprxyd1 ~]# ps -o pid,psr,comm -C opensips PID >> PSR COMMAND 11166 0 opensips 11168 2 opensips 11169 6 >> opensips 11171 5 opensips 11172 5 opensips 11174 5 opensips >> 11175 5 opensips 11177 5 opensips 11179 7 opensips 11181 >> 1 opensips 11183 0 opensips 11185 2 opensips 11187 5 >> opensips 11189 5 opensips 11190 4 opensips > > -- > Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 24 09:25:11 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 16:25:11 +0200 Subject: [OpenSIPS-Users] topology hiding in opensips In-Reply-To: References: <5def493a-55c6-e6cd-2ffd-0e96a5eb57b9@opensips.org> <09a1b85d-b7c9-1a29-4188-6f6a4faa763a@opensips.org> Message-ID: <77bd54d2-abf5-01dd-bb53-372f3691f6cc@opensips.org> OK, that should work for sure. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/24/2017 03:02 PM, Khalil Khamlichi wrote: > sorry : > > # record routing > record_route(); > > # create dialog with timeout > if ( !create_dialog("B") ) { > send_reply("500","Internal Server Error"); > exit; > } > > # apply transformations from dialplan table > dp_translate("0","$rU/$rU"); > > # route calls based on prefix > if ( !do_routing("1","W",,"$var(rule_attrs)","$var(gw_attrs)") ) { > send_reply("404","No Route found"); > exit; > } > > $acc_extra(gwid)=$avp(gw_id); > > t_on_failure("GW_FAILOVER"); > > do_accounting("db|log","cdr|missed",); > #NAT > if (isbflagset(NAT)) setflag(NAT); > #NAT > #TOPOHIDE > toopology_hiding("UC"); > #TOPOHIDE > route(RELAY); > > } > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 24 10:41:39 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 17:41:39 +0200 Subject: [OpenSIPS-Users] Async DB statement In-Reply-To: References: Message-ID: <4fb08999-7ff7-14f2-4ac9-77f76ad0b355@opensips.org> Ahmed, after an async() call, the execution never returns, but it continues exclusively via the resume route. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/24/2017 05:06 PM, Ahmed Munir wrote: > I mean to say, after calling async statement, somehow it is not > routing back the call to the main routing script after post DB query, > see e.g. below for the current routing using async; > > route [1]{ > .... > > if($avp(Outpluseflag) == 0) { > async(avp_db_query("SELECT Outpulse_number,setid FROM Prefix_data > where Program_prefix = '$avp(pg_prefix)'", "$avp(outpluse); > $avp(trunkid)"),ob_route_1); > } > .. > } > > route[ob_route_1]{ > $avp(res)=$rc; > > if ($avp(res) > 0) { > cache_store("local", "DID_$tU", "$avp(outpluse)", 60); > cache_store("local", "Trunk_$tU", "$avp(trunkid)", 60); > > } > > $avp(ru)=$(avp(ru){s.substr,1,0}); > > #Look for exten and trunk id for the FROM cache Internal > number table > if(cache_fetch("local", "$tU", $avp(iexten))) { > if(cache_fetch("local", "GroupID_$tU", $avp(igroupid))) { > #$var(flag) = 1; > $avp(flag) = 1; > } > } > > > } > > At first in route[1], I was setting up > '$avp(ru)=$(avp(ru){s.substr,1,0});' and post routing script after > async DB statement, but it is not resuming the route from there. As a > work around, instead of setting up $avp(ru) and storing variable in > cache in route[1], added them in route[ob_route_1] (as example above), > it works. > > I would like to know, is there way after executing async DB statement > (in route[ob_route_1]), we can resume back the route in route[1] or not? > > On Tue, Jan 24, 2017 at 9:09 AM, Bogdan-Andrei Iancu > > wrote: > > Could you please rephrase / detail your question, as I do not > understand what you are asking. > > Thanks, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 01/24/2017 03:44 PM, Ahmed Munir wrote: >> Thanks, have been working on this and it is working. >> Btw, I would like to know, is there a way to resume route while >> using async avp_db_query? As currently setting/declaring another >> async route for DB query, looking for resume route in main >> routing script. >> On Tue, Jan 24, 2017 at 6:45 AM, Bogdan-Andrei Iancu >> > wrote: >> >> Hi Ahmed, Note the $rc holds the return code of the LAST >> executed statement/instruction/function in the script. In the >> first case you do it right by saving the ret code of the >> avp_db_query into a separate variable, so you can use it even >> later. In the sync script, the $rc, when entering the resume >> route, it will hold the return code of the avp_db_query() >> function. But the $rc will be changed when doing the xlog(), >> the if(), etc...So when you do the last xlog(), the $rc will >> have nothing to do with the avp_db_query(). If you need it >> later in the script, better save it, as you do in the first >> example. Regards, >> >> Bogdan-Andrei Iancu >> OpenSIPS Founder and Developer >> http://www.opensips-solutions.com >> >> >> On 01/20/2017 01:31 AM, Ahmed Munir wrote: >>> Hi, >>> Currently I'm trying to use async fucntion for avp_db_query. >>> The issue I'm facing while using it as not retrieving or >>> returning correct return code and not execute later part of >>> the routing script. See old & new DB queries; >>> Without Async: ---------------------- route[1]{ ... >>> if($var(Outpluseflag) == 0) { >>> avp_db_query("SELECT Outpulse_number,setid FROM Prefix_data >>> where Program_prefix = '$var(pg_prefix)'", "$avp(outpluse), >>> $avp(trunkid)"); $var(res) = $retcode; # or >>> you can just use $retcode! xlog("--------- >>> OB Route 1-1 DB fetched value outpluse -> $avp(outpluse) | >>> trunkid -> $avp(trunkid) | Return Code: $rc | Var Res: >>> $var(res)-------"); if ($var(res) > 0) { >>> cache_store("local", "DID_$tU", >>> "$avp(outpluse)", 60); >>> cache_store("local", "Trunk_$tU", "$avp(trunkid)", 60); >>> } #xlog("DB fetched value >>> outpluse -> $avp(outpluse) | trunkid -> $avp(trunkid) | >>> Return Code -> $var(res)"); xlog("--------- >>> OB Route 1-2 DB fetched value outpluse -> $avp(outpluse) | >>> trunkid -> $avp(trunkid) | Return Code: $rc | Var Res: >>> $var(res)-------"); } >>> } With Async: ------------------- >>> route[1]{ >>> ... >>> if($var(Outpluseflag) == 0) { >>> async(avp_db_query("SELECT Outpulse_number,setid FROM >>> Prefix_data where Program_prefix = '$var(pg_prefix)'", >>> "$avp(outpluse), $avp(trunkid)"),ob_route_1); } } >>> route[ob_route_1]{ xlog("--------- OB Route 1-1 DB >>> fetched value outpluse -> $avp(outpluse) | trunkid -> >>> $avp(trunkid) | Return Code: $rc-------"); if ($rc > >>> 0) { cache_store("local", "DID_$tU", >>> "$avp(outpluse)", 60); cache_store("local", >>> "Trunk_$tU", "$avp(trunkid)", 60); } >>> xlog("--------- OB Route 1-2 DB fetched value outpluse -> >>> $avp(outpluse) | trunkid -> $avp(trunkid) | Return Code: >>> $rc-------"); } >>> The records in xlog I'm getting without using async; Jan 19 >>> 18:05:39 qorblpsisprxyd1 /usr/sbin/opensips[14040]: >>> --------- OB Route 1-1 DB fetched value outpluse -> >>> 6099020000 | trunkid -> 117 | >>> Return Code: 1 | Var Res: 1------- Jan 19 18:05:39 >>> qorblpsisprxyd1 /usr/sbin/opensips[14040]: --------- OB >>> Route 1-2 DB fetched value outpluse -> 6099020000 >>> | trunkid -> 117 | Return Code: 1 >>> | Var Res: 1------- >>> Whereas, records in xlog I'm getting using async; Jan 19 >>> 18:10:07 qorblpsisprxyd1 /usr/sbin/opensips[14109]: >>> --------- OB Route 1-1 DB fetched value outpluse -> >>> 6099020000 | trunkid -> 117 | >>> Return Code: 1------- Jan 19 18:10:07 qorblpsisprxyd1 >>> /usr/sbin/opensips[14109]: --------- OB Route 1-2 DB fetched >>> value outpluse -> 6099020000 | >>> trunkid -> 117 | Return Code: 0------- >>> Is there is way to properly retain the $retcode/$rc in >>> version 2.2.2? Seems like using async return code(s) are not >>> properly set or the avp variables are not setting up correct >>> using async statement. >>> Please advise, if the above async db statement is correct as >>> shared in sample above. >>> -- >>> Regards, Ahmed Munir Chohan >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >> >> -- >> Regards, Ahmed Munir Chohan > > -- > Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Agalya_Ramachandran at comcast.com Tue Jan 24 11:00:43 2017 From: Agalya_Ramachandran at comcast.com (Ramachandran, Agalya (Contractor)) Date: Tue, 24 Jan 2017 16:00:43 +0000 Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service In-Reply-To: <02f2179c-d838-cd83-d8ef-b0a67870c339@opensips.org> References: <92c380d81d5c45a9a2bce09fe344188e@COPDCEX28.cable.comcast.com> <2d785128-affa-c955-e779-1d4305ec1119@opensips.org> <21840442533f445397309d17eec6bcbe@COPDCEX28.cable.comcast.com> <02f2179c-d838-cd83-d8ef-b0a67870c339@opensips.org> Message-ID: <9066a330ccf04484964a0c9e70ad7e2a@COPDCEX28.cable.comcast.com> Hi Bogdan, Please find the result of “opensipsctl fifo ps” and the warnings am seeing in logs. Process:: ID=0 PID=3497 Type=attendant Process:: ID=1 PID=3498 Type=MI FIFO Process:: ID=2 PID=3499 Type=time_keeper Process:: ID=3 PID=3500 Type=timer Process:: ID=4 PID=3501 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=5 PID=3502 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=6 PID=3503 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=7 PID=3504 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=8 PID=3505 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=9 PID=3506 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=10 PID=3507 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=11 PID=3508 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=12 PID=3509 Type=Timer handler Warnings: Jan 24 15:03:00 /usr/local/sbin/opensips[27867]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 24 15:04:15 /usr/local/sbin/opensips[27866]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 24 15:10:02 /usr/local/sbin/opensips[27866]: WARNING:core:handle_timer_job: utimer job has a 80000 us delay in execution Jan 24 15:19:35 /usr/local/sbin/opensips[27866]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 24 15:23:42 /usr/local/sbin/opensips[27866]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 24 15:25:55 /usr/local/sbin/opensips[27872]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 24 15:42:04 /usr/local/sbin/opensips[27860]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Regards, Agalya From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Tuesday, January 24, 2017 6:34 AM To: OpenSIPS users mailling list ; Ramachandran, Agalya (Contractor) Subject: Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service Hi Agalya, Please provide the output of "opensipsctl fifo ps" Best regards. Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/19/2017 04:55 PM, Ramachandran, Agalya (Contractor) wrote: Hi Razvan, I didn’t see any process that is using more than 80% of a core. OpenSIPS is simply being idle and these warnings come periodically. Like once in couple of hours. I didn’t track the exact time line, how frequent am getting this warnings. Ahmed, Do you notice these warnings only when you start OpenSIPS or could see it in regular intervals? Regards, Agalya From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Razvan Crainea Sent: Thursday, January 19, 2017 3:33 AM To: users at lists.opensips.org Subject: Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service When starting opensips, is there any opensips process that is using more than 80% of a core? If so, can you pinpoint the PID in the opensipsctl ps command? Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/18/2017 11:55 PM, Ramachandran, Agalya (Contractor) wrote: Same with my case too. Regards, Agalya From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of Ahmed Munir Sent: Wednesday, January 18, 2017 1:31 PM To: OpenSIPs Users Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service Hi, I'm currently seeing the warnings when I start opensips service; Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: timer job has a 1500000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: timer job has a 1500000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: timer job has a 1500000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: WARNING:core:handle_timer_job: utimer job has a 2290000 us delay in execution Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: INFO:core:do_action: max while loops are encountered Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 2470 ms), it may over lap.. I've tried to update the source code for timer.c (line#: 190) ref: https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split, but didn't work at all. Currently running 8 child processors, see below; [root at qorblpsisprxyd1 ]# opensips -V version: opensips 2.2.2 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_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_lt, epoll_et, sigio_rt, select. main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7 [root at qorblpsisprxyd1 ]# opensipsctl fifo ps Process:: ID=0 PID=3083 Type=attendant Process:: ID=1 PID=3085 Type=MI FIFO Process:: ID=2 PID=3086 Type=time_keeper Process:: ID=3 PID=3088 Type=timer Process:: ID=4 PID=3089 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=5 PID=3091 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=6 PID=3092 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=7 PID=3094 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=8 PID=3096 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=9 PID=3098 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=10 PID=3100 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=11 PID=3102 Type=SIP receiver udp:10.3.120.94:5060 Process:: ID=12 PID=3104 Type=Timer handler I would like to know what changes required to fix this change? Please advise. -- Regards, Ahmed Munir Chohan _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jan 24 11:08:34 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 24 Jan 2017 18:08:34 +0200 Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service In-Reply-To: <9066a330ccf04484964a0c9e70ad7e2a@COPDCEX28.cable.comcast.com> References: <92c380d81d5c45a9a2bce09fe344188e@COPDCEX28.cable.comcast.com> <2d785128-affa-c955-e779-1d4305ec1119@opensips.org> <21840442533f445397309d17eec6bcbe@COPDCEX28.cable.comcast.com> <02f2179c-d838-cd83-d8ef-b0a67870c339@opensips.org> <9066a330ccf04484964a0c9e70ad7e2a@COPDCEX28.cable.comcast.com> Message-ID: <905e5006-a86e-9588-9f3f-4db33f9d864d@opensips.org> Hi Agalya, 1)do you get warning only for the tm-utimer job ? or do you see other too ? 2) do you have some load on the server (in terms of traffic) ? or is it idle/almost-idle ? 3) the "ps" and the logs are not from the same run (the pid's do not match) - can you get thedata from same run please ? Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/24/2017 06:00 PM, Ramachandran, Agalya (Contractor) wrote: > > Hi Bogdan, > > Please find the result of “opensipsctl fifo ps” and the warnings am > seeing in logs. > > Process:: ID=0 PID=3497 Type=attendant > > Process:: ID=1 PID=3498 Type=MI FIFO > > Process:: ID=2 PID=3499 Type=time_keeper > > Process:: ID=3 PID=3500 Type=timer > > Process:: ID=4 PID=3501 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=5 PID=3502 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=6 PID=3503 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=7 PID=3504 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=8 PID=3505 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=9 PID=3506 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=10 PID=3507 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=11 PID=3508 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=12 PID=3509 Type=Timer handler > > Warnings: > > Jan 24 15:03:00 /usr/local/sbin/opensips[27867]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Jan 24 15:04:15 /usr/local/sbin/opensips[27866]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Jan 24 15:10:02 /usr/local/sbin/opensips[27866]: > WARNING:core:handle_timer_job: utimer job has a 80000 us > delay in execution > > Jan 24 15:19:35 /usr/local/sbin/opensips[27866]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Jan 24 15:23:42 /usr/local/sbin/opensips[27866]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Jan 24 15:25:55 /usr/local/sbin/opensips[27872]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Jan 24 15:42:04 /usr/local/sbin/opensips[27860]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Regards, > Agalya > > *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] > *Sent:* Tuesday, January 24, 2017 6:34 AM > *To:* OpenSIPS users mailling list ; > Ramachandran, Agalya (Contractor) > *Subject:* Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start > service > > Hi Agalya, > > Please provide the output of "opensipsctl fifo ps" > > Best regards. > > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 01/19/2017 04:55 PM, Ramachandran, Agalya (Contractor) wrote: > > Hi Razvan, > > I didn’t see any process that is using more than 80% of a core. > OpenSIPS is simply being idle and these warnings come periodically. > > Like once in couple of hours. I didn’t track the exact time line, > how frequent am getting this warnings. > > Ahmed, > > Do you notice these warnings only when you start OpenSIPS or could > see it in regular intervals? > > Regards, > Agalya > > *From:*Users [mailto:users-bounces at lists.opensips.org] *On Behalf > Of *Razvan Crainea > *Sent:* Thursday, January 19, 2017 3:33 AM > *To:* users at lists.opensips.org > *Subject:* Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during > start service > > When starting opensips, is there any opensips process that is > using more than 80% of a core? If so, can you pinpoint the PID in > the opensipsctl ps command? > > Best regards, > > > Răzvan Crainea > > OpenSIPS Solutions > > www.opensips-solutions.com > > On 01/18/2017 11:55 PM, Ramachandran, Agalya (Contractor) wrote: > > Same with my case too. > > Regards, > Agalya > > *From:*Users [mailto:users-bounces at lists.opensips.org] *On > Behalf Of *Ahmed Munir > *Sent:* Wednesday, January 18, 2017 1:31 PM > *To:* OpenSIPs Users > > *Subject:* [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during > start service > > Hi, > > I'm currently seeing the warnings when I start opensips service; > > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a > 1500000 us delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a > 1500000 us delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: timer job has a > 1500000 us delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > WARNING:core:handle_timer_job: utimer job has a > 2290000 us delay in execution > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3089]: > INFO:core:do_action : max while loops are > encountered > Jan 18 13:04:35 qorblpsisprxyd1 /usr/sbin/opensips[3088]: > WARNING:core:utimer_ticker: utimer task already > scheduled for 190 ms (now 2470 ms), it may over > lap.. > > > > I've tried to update the source code for timer.c (line#: 190) > ref: > https://github.com/OpenSIPS/opensips/commit/fd8f6ec442b4365da9d274af6939954246ece865?diff=split, > but didn't work at all. > > Currently running 8 child processors, see below; > > [root at qorblpsisprxyd1 ]# opensips -V > version: opensips 2.2.2 (x86_64/linux) > flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, > PKG_MALLOC, F_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_lt, epoll_et, sigio_rt, select. > main.c compiled on 12:39:45 Jan 18 2017 with gcc 4.4.7 > > > [root at qorblpsisprxyd1 ]# opensipsctl fifo ps > Process:: ID=0 PID=3083 Type=attendant > Process:: ID=1 PID=3085 Type=MI FIFO > Process:: ID=2 PID=3086 Type=time_keeper > Process:: ID=3 PID=3088 Type=timer > Process:: ID=4 PID=3089 Type=SIP receiver > udp:10.3.120.94:5060 > Process:: ID=5 PID=3091 Type=SIP receiver > udp:10.3.120.94:5060 > Process:: ID=6 PID=3092 Type=SIP receiver > udp:10.3.120.94:5060 > Process:: ID=7 PID=3094 Type=SIP receiver > udp:10.3.120.94:5060 > Process:: ID=8 PID=3096 Type=SIP receiver > udp:10.3.120.94:5060 > Process:: ID=9 PID=3098 Type=SIP receiver > udp:10.3.120.94:5060 > Process:: ID=10 PID=3100 Type=SIP receiver > udp:10.3.120.94:5060 > Process:: ID=11 PID=3102 Type=SIP receiver > udp:10.3.120.94:5060 > Process:: ID=12 PID=3104 Type=Timer handler > > I would like to know what changes required to fix this change? > Please advise. > > > -- > > Regards, > > Ahmed Munir Chohan > > > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Agalya_Ramachandran at comcast.com Tue Jan 24 11:42:53 2017 From: Agalya_Ramachandran at comcast.com (Ramachandran, Agalya (Contractor)) Date: Tue, 24 Jan 2017 16:42:53 +0000 Subject: [OpenSIPS-Users] FW: OpenSIPs 2.2.2 warnings during start service References: <92c380d81d5c45a9a2bce09fe344188e@COPDCEX28.cable.comcast.com> <2d785128-affa-c955-e779-1d4305ec1119@opensips.org> <21840442533f445397309d17eec6bcbe@COPDCEX28.cable.comcast.com> <02f2179c-d838-cd83-d8ef-b0a67870c339@opensips.org> <9066a330ccf04484964a0c9e70ad7e2a@COPDCEX28.cable.comcast.com> <905e5006-a86e-9588-9f3f-4db33f9d864d@opensips.org> Message-ID: From: Ramachandran, Agalya (Contractor) Sent: Tuesday, January 24, 2017 11:42 AM To: 'Bogdan-Andrei Iancu' Subject: RE: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service Hi Bogdan, 1) do you get warning only for the tm-utimer job ? or do you see other too ? I rarely see from blcore-expire job too. 2) do you have some load on the server (in terms of traffic) ? or is it idle/almost-idle ? Mostly its idle, May be it will process 5 to 10 calls in an hour. That is the load it is been handling right now. Giving the Process id and its same logs. Process:: ID=0 PID=11744 Type=attendant Process:: ID=1 PID=11745 Type=MI FIFO Process:: ID=2 PID=11746 Type=time_keeper Process:: ID=3 PID=11747 Type=timer Process:: ID=4 PID=11748 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=5 PID=11749 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=6 PID=11750 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=7 PID=11751 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=8 PID=11752 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=9 PID=11753 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=10 PID=11754 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=11 PID=11755 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=12 PID=11756 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=13 PID=11757 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=14 PID=11758 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=15 PID=11759 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=16 PID=11760 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=17 PID=11761 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=18 PID=11762 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=19 PID=11763 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=20 PID=11764 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=21 PID=11765 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=22 PID=11766 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=23 PID=11767 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=24 PID=11768 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=25 PID=11769 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=26 PID=11770 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=27 PID=11771 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=28 PID=11772 Type=Timer handler Jan 23 22:36:29 /usr/local/sbin/opensips[11771]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 22:49:42 /usr/local/sbin/opensips[11767]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 22:53:15 /usr/local/sbin/opensips[11771]: WARNING:core:handle_timer_job: timer job has a 80000 us delay in execution Jan 23 22:53:15 /usr/local/sbin/opensips[11753]: WARNING:core:handle_timer_job: timer job has a 80000 us delay in execution Jan 23 22:55:06 /usr/local/sbin/opensips[11771]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 22:59:37 /usr/local/sbin/opensips[11767]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 23:07:20 /usr/local/sbin/opensips[11771]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 23:29:51 /usr/local/sbin/opensips[11771]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 23:30:11 /usr/local/sbin/opensips[11771]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 23:30:26 /usr/local/sbin/opensips[11772]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 23:35:55 /usr/local/sbin/opensips[11758]: WARNING:core:handle_timer_job: utimer job has a 30000 us delay in execution Jan 23 23:35:55 /usr/local/sbin/opensips[11771]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Regards, Agalya From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Tuesday, January 24, 2017 11:09 AM To: Ramachandran, Agalya (Contractor) >; OpenSIPS users mailling list > Subject: Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service Hi Agalya, 1) do you get warning only for the tm-utimer job ? or do you see other too ? 2) do you have some load on the server (in terms of traffic) ? or is it idle/almost-idle ? 3) the "ps" and the logs are not from the same run (the pid's do not match) - can you get the data from same run please ? Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rmundkowsky at ets.org Tue Jan 24 19:16:44 2017 From: rmundkowsky at ets.org (Mundkowsky, Robert) Date: Wed, 25 Jan 2017 00:16:44 +0000 Subject: [OpenSIPS-Users] Load-Balancer Module - status destinations in database? Message-ID: Is there a way to get the status (enabled or disabled) of load balancer destinations in database? Or is lb_list MI only way? ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________ From johan at democon.be Wed Jan 25 02:16:29 2017 From: johan at democon.be (Johan De Clercq) Date: Wed, 25 Jan 2017 08:16:29 +0100 Subject: [OpenSIPS-Users] Load-Balancer Module - status destinations in database? In-Reply-To: References: Message-ID: as far as I know, you can only do this with mi. As the status depends on probing, in my opinion, it doesn't make sense to store this in a db. BR, Johan. 2017-01-25 1:16 GMT+01:00 Mundkowsky, Robert : > Is there a way to get the status (enabled or disabled) of load balancer > destinations in database? > > Or is lb_list MI only way? > > > > ________________________________ > > This e-mail and any files transmitted with it may contain privileged or > confidential information. It is solely for use by the individual for whom > it is intended, even if addressed incorrectly. If you received this e-mail > in error, please notify the sender; do not disclose, copy, distribute, or > take any action in reliance on the contents of this information; and delete > it from your system. Any other use of this e-mail is prohibited. > > > Thank you for your compliance. > > ________________________________ > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Wed Jan 25 04:23:29 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 25 Jan 2017 11:23:29 +0200 Subject: [OpenSIPS-Users] FW: OpenSIPs 2.2.2 warnings during start service In-Reply-To: References: <92c380d81d5c45a9a2bce09fe344188e@COPDCEX28.cable.comcast.com> <2d785128-affa-c955-e779-1d4305ec1119@opensips.org> <21840442533f445397309d17eec6bcbe@COPDCEX28.cable.comcast.com> <02f2179c-d838-cd83-d8ef-b0a67870c339@opensips.org> <9066a330ccf04484964a0c9e70ad7e2a@COPDCEX28.cable.comcast.com> <905e5006-a86e-9588-9f3f-4db33f9d864d@opensips.org> Message-ID: <8a6a2556-c10b-b97f-1dfa-de3d71c31a55@opensips.org> Hi Agalya, That is really weird - I suppose you are using the latest 2.2, right ? Are you using a VM or container to run OpenSIPS ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/24/2017 06:42 PM, Ramachandran, Agalya (Contractor) wrote: > > *From:*Ramachandran, Agalya (Contractor) > *Sent:* Tuesday, January 24, 2017 11:42 AM > *To:* 'Bogdan-Andrei Iancu' > *Subject:* RE: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start > service > > Hi Bogdan, > > 1)do you get warning only for the tm-utimer job ? or do you see other > too ? > > I rarely see from blcore-expire job too. > > 2) do you have some load on the server (in terms of traffic) > ? or is it idle/almost-idle ? > > Mostly its idle, May be it will process 5 to 10 calls in an hour. That > is the load it is been handling right now. > > Giving the Process id and its same logs. > > Process:: ID=0 PID=11744 Type=attendant > > Process:: ID=1 PID=11745 Type=MI FIFO > > Process:: ID=2 PID=11746 Type=time_keeper > > Process:: ID=3 PID=11747 Type=timer > > Process:: ID=4 PID=11748 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=5 PID=11749 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=6 PID=11750 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=7 PID=11751 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=8 PID=11752 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=9 PID=11753 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=10 PID=11754 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=11 PID=11755 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=12 PID=11756 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=13 PID=11757 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=14 PID=11758 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=15 PID=11759 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=16 PID=11760 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=17 PID=11761 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=18 PID=11762 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=19 PID=11763 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=20 PID=11764 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=21 PID=11765 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=22 PID=11766 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=23 PID=11767 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=24 PID=11768 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=25 PID=11769 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=26 PID=11770 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=27 PID=11771 Type=SIP receiver udp:10.0.0.1:5060 > > Process:: ID=28 PID=11772 Type=Timer handler > > Jan 23 22:36:29 /usr/local/sbin/opensips[11771]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Jan 23 22:49:42 /usr/local/sbin/opensips[11767]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Jan 23 22:53:15 /usr/local/sbin/opensips[11771]: > WARNING:core:handle_timer_job: timer job has a 80000 us > delay in execution > > Jan 23 22:53:15 /usr/local/sbin/opensips[11753]: > WARNING:core:handle_timer_job: timer job has a 80000 > us delay in execution > > Jan 23 22:55:06 /usr/local/sbin/opensips[11771]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Jan 23 22:59:37 /usr/local/sbin/opensips[11767]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Jan 23 23:07:20 /usr/local/sbin/opensips[11771]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Jan 23 23:29:51 /usr/local/sbin/opensips[11771]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Jan 23 23:30:11 /usr/local/sbin/opensips[11771]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Jan 23 23:30:26 /usr/local/sbin/opensips[11772]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Jan 23 23:35:55 /usr/local/sbin/opensips[11758]: > WARNING:core:handle_timer_job: utimer job has a 30000 us > delay in execution > > Jan 23 23:35:55 /usr/local/sbin/opensips[11771]: > WARNING:core:handle_timer_job: utimer job has a 20000 us > delay in execution > > Regards, > Agalya > > *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] > *Sent:* Tuesday, January 24, 2017 11:09 AM > *To:* Ramachandran, Agalya (Contractor) > >; OpenSIPS users mailling > list > > *Subject:* Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start > service > > Hi Agalya, > > 1) do you get warning only for the tm-utimer job ? or do you see other > too ? > > 2) do you have some load on the server (in terms of traffic) ? or is > it idle/almost-idle ? > > 3) the "ps" and the logs are not from the same run (the pid's do not > match) - can you get the data from same run please ? > > Best regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From liviu at opensips.org Wed Jan 25 06:45:40 2017 From: liviu at opensips.org (Liviu Chircu) Date: Wed, 25 Jan 2017 13:45:40 +0200 Subject: [OpenSIPS-Users] scheduled concurrent call reporting In-Reply-To: References: Message-ID: I do not see any problems with calling "get_profile_size()" from timer routes, event routes, etc. As such, you can safely bypass the block restriction using the following example: route [get_prof_sz_inboundCalls] { get_profile_size("inboundCalls",,"$var(size)"); } route [get_prof_sz_outboundCalls] { get_profile_size("outboundCalls",,"$var(size)"); } timer_route [mytimer, 1] { route(get_prof_sz_inboundCalls); xlog("inboundCalls: $var(size)\n"); route(get_prof_sz_outboundCalls); xlog("outboundCalls: $var(size)\n"); } Regards, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 24.01.2017 01:05, Khalil Khamlichi wrote: > the idea is that I don't need to get the number of calls 30 times per > second which would happens if I save to redis on each invite. > scheduling the saving to redis every 10 seconds serves well my > purpose but the timer_route doesn't seem to accept get_profile_size() > > any hints would be appreciated. > > On Mon, Jan 23, 2017 at 10:39 PM, Khalil Khamlichi > > wrote: > > Hi, > > I am trying to get call load information out of opensips at > regular intervals to get some sort of realtime view of the load on > the server. > > After applying profiles on the the INVITEs, I have tried to call > get_profile_size from a timer_route. > I am getting error : > > CRITICAL:core:yyerror: parse error in config file > /usr/local//etc/opensips/opensips.cfg, line 483, column 38-39: > Command cannot be used in the block > > Any alternative solutions ? > > Thanks in advance. > > kkh > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Wed Jan 25 07:04:52 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Wed, 25 Jan 2017 12:04:52 +0000 Subject: [OpenSIPS-Users] scheduled concurrent call reporting In-Reply-To: References: Message-ID: Liviu, you just saved my day. my plan is to push information to redis every 10s maybe 5s if need there is, when dashboard is complete I might consider saving the stream of data for plotting and further analysis. On Wed, Jan 25, 2017 at 11:45 AM, Liviu Chircu wrote: > I do not see any problems with calling "get_profile_size()" from timer > routes, event routes, etc. As such, you can safely bypass the block > restriction using the following example: > > route [get_prof_sz_inboundCalls] { > get_profile_size("inboundCalls",,"$var(size)"); > } > > route [get_prof_sz_outboundCalls] { > get_profile_size("outboundCalls",,"$var(size)"); > } > > timer_route [mytimer, 1] > { > route(get_prof_sz_inboundCalls); > xlog("inboundCalls: $var(size)\n"); > > route(get_prof_sz_outboundCalls); > xlog("outboundCalls: $var(size)\n"); > } > > Regards, > > Liviu Chircu > OpenSIPS Developerhttp://www.opensips-solutions.com > > On 24.01.2017 01:05, Khalil Khamlichi wrote: > > the idea is that I don't need to get the number of calls 30 times per > second which would happens if I save to redis on each invite. scheduling > the saving to redis every 10 seconds serves well my purpose but the > timer_route doesn't seem to accept get_profile_size() > > any hints would be appreciated. > > On Mon, Jan 23, 2017 at 10:39 PM, Khalil Khamlichi < > khamlichi.khalil at gmail.com> wrote: > >> Hi, >> >> I am trying to get call load information out of opensips at regular >> intervals to get some sort of realtime view of the load on the server. >> >> After applying profiles on the the INVITEs, I have tried to call >> get_profile_size from a timer_route. >> I am getting error : >> >> CRITICAL:core:yyerror: parse error in config file >> /usr/local//etc/opensips/opensips.cfg, line 483, column 38-39: Command >> cannot be used in the block >> >> Any alternative solutions ? >> >> Thanks in advance. >> >> kkh >> > > > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Wed Jan 25 07:24:57 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Wed, 25 Jan 2017 12:24:57 +0000 Subject: [OpenSIPS-Users] how to catch hangup event inside opensips Message-ID: there is one more question we still struggling with, how to run a route at each hangup, we never found any way to do it inside opensips. right now we catching the event upon cdr insert in db. -------------- next part -------------- An HTML attachment was scrubbed... URL: From stefano.pisani at omnianet.it Wed Jan 25 07:32:28 2017 From: stefano.pisani at omnianet.it (Stefano Pisani) Date: Wed, 25 Jan 2017 13:32:28 +0100 Subject: [OpenSIPS-Users] how to catch hangup event inside opensips In-Reply-To: References: Message-ID: <9ADC7AB3-F488-4CA8-8A29-FB528F01753E@omnianet.it> please explain better Il 25 Gennaio 2017 13:24:57 CET, Khalil Khamlichi ha scritto: >there is one more question we still struggling with, how to run a route >at >each hangup, we never found any way to do it inside opensips. right now >we >catching the event upon cdr insert in db. -- Inviato dal mio cellulare Android con K-9 Mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Wed Jan 25 07:52:54 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Wed, 25 Jan 2017 12:52:54 +0000 Subject: [OpenSIPS-Users] how to catch hangup event inside opensips In-Reply-To: <9ADC7AB3-F488-4CA8-8A29-FB528F01753E@omnianet.it> References: <9ADC7AB3-F488-4CA8-8A29-FB528F01753E@omnianet.it> Message-ID: sorry the expression "run a route" was misleading, actually we are working on a dashboard, we need to catch events happening inside opensips to feed our counters, we hope to be able to catch hangup event and probably the sip_code so that we can have counters for every sip code specific to every gateway. the other way around this is to catch the cdr insert and feed counters. On Wed, Jan 25, 2017 at 12:32 PM, Stefano Pisani wrote: > please explain better > > Il 25 Gennaio 2017 13:24:57 CET, Khalil Khamlichi < > khamlichi.khalil at gmail.com> ha scritto: >> >> there is one more question we still struggling with, how to run a route >> at each hangup, we never found any way to do it inside opensips. right now >> we catching the event upon cdr insert in db. >> > > -- Inviato dal mio cellulare Android con K-9 Mail. > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From liviu at opensips.org Wed Jan 25 08:08:40 2017 From: liviu at opensips.org (Liviu Chircu) Date: Wed, 25 Jan 2017 15:08:40 +0200 Subject: [OpenSIPS-Users] how to catch hangup event inside opensips In-Reply-To: References: <9ADC7AB3-F488-4CA8-8A29-FB528F01753E@omnianet.it> Message-ID: <51d34193-b5d9-81fb-1423-0208968b1c23@opensips.org> There are several ways of doing this, to name a few: - catch CDR events (E_ACC_CDR) [1] in the event_route, and go from there. This is the most straight-forward solution, giving you lots of information to work with. However, you must be using the "acc" module in order for it to work. - catch dialog state change events (E_DLG_STATE_CHANGED) [2] in the event_route, go from there. The idea is to detect when a dialog goes from state 4 (confirmed) -> 5 (deleted). A problem with this approach might be the limited amount of information available in the event route. - simply catch all BYE requests in your OpenSIPS script, and go from there. The tricky part with this approach is to not forget about the auto-generated BYEs (calls cut by OpenSIPS), by also doing some handling inside the "local route". [1]: http://www.opensips.org/html/docs/modules/2.3.x/acc#id295391 [2]: http://www.opensips.org/html/docs/modules/2.3.x/dialog.html#id297615 Regards, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 25.01.2017 14:52, Khalil Khamlichi wrote: > sorry the expression "run a route" was misleading, actually we are > working on a dashboard, we need to catch events happening inside > opensips to feed our counters, we hope to be able to catch hangup > event and probably the sip_code so that we can have counters for every > sip code specific to every gateway. the other way around this is to > catch the cdr insert and feed counters. > > On Wed, Jan 25, 2017 at 12:32 PM, Stefano Pisani > > wrote: > > please explain better > > Il 25 Gennaio 2017 13:24:57 CET, Khalil Khamlichi > > > ha scritto: > > there is one more question we still struggling with, how to > run a route at each hangup, we never found any way to do it > inside opensips. right now we catching the event upon cdr > insert in db. > > > -- Inviato dal mio cellulare Android con K-9 Mail. > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Wed Jan 25 09:22:47 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 25 Jan 2017 16:22:47 +0200 Subject: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service In-Reply-To: References: <23db254e-202c-c01c-0ac9-15ccf39f447b@opensips.org> <5ad0aa83-0f9e-8b19-ffcd-e90996bd5c85@opensips.org> Message-ID: Hi, That explains - during the execution of the startup route the rest of worker-like processes are not yet created (we wait to have the startup route finished), while the timer is already fires. So it triggers some timer jobs but there is no proc available to handle them. This is a corner case, still I'm thinking of a solution on how to go around it. Still, at the end, there is nothing wrong (the timer jobs will still be handled, but later, after startup route is done), but you get those warnings. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/24/2017 11:28 PM, Ahmed Munir wrote: > Yes, this works not to do DB op during route startup script and > eliminate the warnings. > > > I would like to know, what method will you recommend for route startup > DB op in opensips 2.2? > > On Tue, Jan 24, 2017 at 9:12 AM, Bogdan-Andrei Iancu > > wrote: > > The versions before 2.1 had a completely different approach on hoe > the timer jobs were handled - different code, so no such warnings. > The 2.1 introduces the a more flexible and scalable processing for > the timer jobs. > > Could you confirm that removing the DB op from the startup route > eliminates the warnings ? > > Thanks, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 01/24/2017 03:49 PM, Ahmed Munir wrote: >> Yes, using startup route in my routing script and running DB >> query. This kind of warning I didn't face using 1.6 and 1.8 >> opensips versions but 2.2.2. >> Will you recommend async statement for my current routing (see >> below) for the startup? startup_route { $var(res) = 1; >> $avp(tmp) = "1"; # $var(x) = 0; while($var(res) > 0) { >> $var(res) = avp_db_query("SELECT Distinct One800, dnis >> FROM DNIS_Mapping where One800 > $avp(tmp) order by One800;", >> "$avp(One800), $avp(dnis)"); if($var(res) >= 0) { >> $var(i) = 0; >> while($(avp(One800)[$var(i)]) != "NULL") { >> cache_store("local", >> "DNIS_$(avp(dnis)[$var(i)])", "$(avp(One800)[$var(i)])"); >> $avp(tmp) = $(avp(One800)[$var(i)]); >> # $var(x) = $var(x) + 1; >> $(avp(One800)[$var(i)]) = "NULL"; >> $var(i) = $var(i) + 1; >> # xlog("$var(x) : $(avp(s:dnis)[$var(i)])"); >> } } } } >> On Tue, Jan 24, 2017 at 6:38 AM, Bogdan-Andrei Iancu >> > wrote: >> >> Hi Ahmed, So, the warnings pop up ONLY during startup >> sequence. Do you use startup route or any module performing >> mem caching of some DB table (drouting, permission, etc) ? >> Usually, the first UDP child is doing some heavy lifting >> during startup.Regards, >> >> Bogdan-Andrei Iancu >> OpenSIPS Founder and Developer >> http://www.opensips-solutions.com >> >> >> On 01/19/2017 06:01 PM, Ahmed Munir wrote: >>> Hi Razvan, >>> During starting up the opensips service, I see the first >>> opensips child process (pid"11172) consumes CPU process to >>> 70-80% and later drop downs to 0.3 - 0.0 % CPU per core. See >>> below; [root at qorblpsisprxyd1 ~]# top -c -u opensips top - >>> 10:49:54 up 76 days, 23:31, 5 users, load average: 0.00, >>> 0.00, 0.00 Tasks: 229 total, 1 running, 228 sleeping, 0 >>> stopped, 0 zombie Cpu(s): 0.0%us, 0.1%sy, 0.0%ni, >>> 99.9%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 65964364k >>> total, 2568124k used, 63396240k free, 180220k buffers >>> Swap: 1023996k total, 0k used, 1023996k free, >>> 1226104k cached PID USER PR NI VIRT RES SHR S >>> %CPU %MEM TIME+ COMMAND 11177 opensips 20 0 165m 5696 >>> 4528 S 0.3 0.0 0:00.23 /usr/sbin/opensips -P >>> /var/run/opensips.pid -m 64 -u opensips -g opensips 11187 >>> opensips 20 0 165m 5628 4460 S 0.3 0.0 0:00.41 >>> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u >>> opensips -g opensips 11166 opensips 20 0 165m 6892 5752 >>> S 0.0 0.0 0:00.23 /usr/sbin/opensips -P >>> /var/run/opensips.pid -m 64 -u opensips -g opensips 11168 >>> opensips 20 0 165m 1980 840 S 0.0 0.0 0:00.00 >>> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u >>> opensips -g opensips 11169 opensips 20 0 165m 1464 328 >>> S 0.0 0.0 0:00.53 /usr/sbin/opensips -P >>> /var/run/opensips.pid -m 64 -u opensips -g opensips 11171 >>> opensips 20 0 165m 1640 504 S 0.0 0.0 0:00.15 >>> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u >>> opensips -g opensips 11172 opensips 20 0 166m 40m 38m >>> S 0.0 0.1 0:02.61 /usr/sbin/opensips -P >>> /var/run/opensips.pid -m 64 -u opensips -g opensips 11174 >>> opensips 20 0 165m 6304 5136 S 0.0 0.0 0:00.24 >>> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u >>> opensips -g opensips 11175 opensips 20 0 165m 5884 4716 >>> S 0.0 0.0 0:00.22 /usr/sbin/opensips -P >>> /var/run/opensips.pid -m 64 -u opensips -g opensips 11179 >>> opensips 20 0 165m 7660 6492 S 0.0 0.0 0:00.27 >>> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u >>> opensips -g opensips 11181 opensips 20 0 165m 7756 6588 >>> S 0.0 0.0 0:00.33 /usr/sbin/opensips -P >>> /var/run/opensips.pid -m 64 -u opensips -g opensips 11183 >>> opensips 20 0 165m 5520 4352 S 0.0 0.0 0:00.34 >>> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u >>> opensips -g opensips 11185 opensips 20 0 165m 7336 6168 >>> S 0.0 0.0 0:00.36 /usr/sbin/opensips -P >>> /var/run/opensips.pid -m 64 -u opensips -g opensips 11189 >>> opensips 20 0 165m 7320 6152 S 0.0 0.0 0:00.36 >>> /usr/sbin/opensips -P /var/run/opensips.pid -m 64 -u >>> opensips -g opensips 11190 opensips 20 0 165m 4688 3528 >>> S 0.0 0.0 0:00.30 /usr/sbin/opensips -P >>> /var/run/opensips.pid -m 64 -u opensips -g opensips >>> [root at qorblpsisprxyd1 ~]# opensipsctl fifo ps Process:: >>> ID=0 PID=11166 Type=attendant Process:: ID=1 PID=11168 >>> Type=MI FIFO Process:: ID=2 PID=11169 Type=time_keeper >>> Process:: ID=3 PID=11171 Type=timer Process:: ID=4 >>> PID=11172 Type=SIP receiver udp:10.3.120.94:5060 >>> Process:: ID=5 PID=11174 Type=SIP >>> receiver udp:10.3.120.94:5060 >>> Process:: ID=6 PID=11175 Type=SIP receiver >>> udp:10.3.120.94:5060 Process:: >>> ID=7 PID=11177 Type=SIP receiver udp:10.3.120.94:5060 >>> Process:: ID=8 PID=11179 Type=SIP >>> receiver udp:10.3.120.94:5060 >>> Process:: ID=9 PID=11181 Type=SIP receiver >>> udp:10.3.120.94:5060 Process:: >>> ID=10 PID=11183 Type=SIP receiver udp:10.3.120.94:5060 >>> Process:: ID=11 PID=11185 >>> Type=SIP receiver udp:10.3.120.94:5060 >>> Process:: ID=12 PID=11187 >>> Type=SIP receiver udp:10.3.120.94:5060 >>> Process:: ID=13 PID=11189 >>> Type=SIP receiver udp:10.3.120.94:5060 >>> Process:: ID=14 PID=11190 >>> Type=Timer handler OpenSIPs used by each CPU processor; >>> [root at qorblpsisprxyd1 ~]# ps -o pid,psr,comm -C opensips >>> PID PSR COMMAND 11166 0 opensips 11168 2 opensips >>> 11169 6 opensips 11171 5 opensips 11172 5 opensips >>> 11174 5 opensips 11175 5 opensips 11177 5 opensips >>> 11179 7 opensips 11181 1 opensips 11183 0 opensips >>> 11185 2 opensips 11187 5 opensips 11189 5 opensips >>> 11190 4 opensips >> >> -- >> Regards, Ahmed Munir Chohan > > -- > Regards, Ahmed Munir Chohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From Agalya_Ramachandran at comcast.com Wed Jan 25 09:31:01 2017 From: Agalya_Ramachandran at comcast.com (Ramachandran, Agalya (Contractor)) Date: Wed, 25 Jan 2017 14:31:01 +0000 Subject: [OpenSIPS-Users] FW: OpenSIPs 2.2.2 warnings during start service In-Reply-To: <8a6a2556-c10b-b97f-1dfa-de3d71c31a55@opensips.org> References: <92c380d81d5c45a9a2bce09fe344188e@COPDCEX28.cable.comcast.com> <2d785128-affa-c955-e779-1d4305ec1119@opensips.org> <21840442533f445397309d17eec6bcbe@COPDCEX28.cable.comcast.com> <02f2179c-d838-cd83-d8ef-b0a67870c339@opensips.org> <9066a330ccf04484964a0c9e70ad7e2a@COPDCEX28.cable.comcast.com> <905e5006-a86e-9588-9f3f-4db33f9d864d@opensips.org> <8a6a2556-c10b-b97f-1dfa-de3d71c31a55@opensips.org> Message-ID: <886f28ea3cad41ec86c850d2b3516c77@COPDCEX28.cable.comcast.com> Hi Bogdan, Yes, am having tar ball of the 2.2 source code released in Oct 2016. On top of it, I have added the fix in timer.c . That’s all I have. https://github.com/OpenSIPS/opensips/commit/68d4240698e639490ab7dfa187b1458f00146fb3 I am running OpenSIPS in VM. Regards, Agaya From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Wednesday, January 25, 2017 4:23 AM To: Ramachandran, Agalya (Contractor) ; OpenSIPS users mailling list Subject: Re: FW: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service Hi Agalya, That is really weird - I suppose you are using the latest 2.2, right ? Are you using a VM or container to run OpenSIPS ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/24/2017 06:42 PM, Ramachandran, Agalya (Contractor) wrote: From: Ramachandran, Agalya (Contractor) Sent: Tuesday, January 24, 2017 11:42 AM To: 'Bogdan-Andrei Iancu' Subject: RE: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service Hi Bogdan, 1) do you get warning only for the tm-utimer job ? or do you see other too ? I rarely see from blcore-expire job too. 2) do you have some load on the server (in terms of traffic) ? or is it idle/almost-idle ? Mostly its idle, May be it will process 5 to 10 calls in an hour. That is the load it is been handling right now. Giving the Process id and its same logs. Process:: ID=0 PID=11744 Type=attendant Process:: ID=1 PID=11745 Type=MI FIFO Process:: ID=2 PID=11746 Type=time_keeper Process:: ID=3 PID=11747 Type=timer Process:: ID=4 PID=11748 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=5 PID=11749 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=6 PID=11750 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=7 PID=11751 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=8 PID=11752 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=9 PID=11753 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=10 PID=11754 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=11 PID=11755 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=12 PID=11756 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=13 PID=11757 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=14 PID=11758 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=15 PID=11759 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=16 PID=11760 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=17 PID=11761 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=18 PID=11762 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=19 PID=11763 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=20 PID=11764 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=21 PID=11765 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=22 PID=11766 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=23 PID=11767 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=24 PID=11768 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=25 PID=11769 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=26 PID=11770 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=27 PID=11771 Type=SIP receiver udp:10.0.0.1:5060 Process:: ID=28 PID=11772 Type=Timer handler Jan 23 22:36:29 /usr/local/sbin/opensips[11771]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 22:49:42 /usr/local/sbin/opensips[11767]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 22:53:15 /usr/local/sbin/opensips[11771]: WARNING:core:handle_timer_job: timer job has a 80000 us delay in execution Jan 23 22:53:15 /usr/local/sbin/opensips[11753]: WARNING:core:handle_timer_job: timer job has a 80000 us delay in execution Jan 23 22:55:06 /usr/local/sbin/opensips[11771]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 22:59:37 /usr/local/sbin/opensips[11767]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 23:07:20 /usr/local/sbin/opensips[11771]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 23:29:51 /usr/local/sbin/opensips[11771]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 23:30:11 /usr/local/sbin/opensips[11771]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 23:30:26 /usr/local/sbin/opensips[11772]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Jan 23 23:35:55 /usr/local/sbin/opensips[11758]: WARNING:core:handle_timer_job: utimer job has a 30000 us delay in execution Jan 23 23:35:55 /usr/local/sbin/opensips[11771]: WARNING:core:handle_timer_job: utimer job has a 20000 us delay in execution Regards, Agalya From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Tuesday, January 24, 2017 11:09 AM To: Ramachandran, Agalya (Contractor) >; OpenSIPS users mailling list > Subject: Re: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service Hi Agalya, 1) do you get warning only for the tm-utimer job ? or do you see other too ? 2) do you have some load on the server (in terms of traffic) ? or is it idle/almost-idle ? 3) the "ps" and the logs are not from the same run (the pid's do not match) - can you get the data from same run please ? Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rrobson at greenlightcrm.com Wed Jan 25 11:42:10 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Wed, 25 Jan 2017 16:42:10 +0000 Subject: [OpenSIPS-Users] calling create_dialog() on failover Message-ID: I'm wanting to check rate limits and channel limits for calls over several gateways. this I have working, but we are getting instances of failures on upstream carriers. this is due to one carrier in paricular not liking the CLIs our customers are calling from. In this case the call comes back as a 403, which I want to failover from the t_on_failure route to the next gateway. If I reuse my relay route it it will have a subsequent create_dialog() it also does the topology hiding and accounting in. Am I OK to recall the create dialog and reuse the relay route or am i better to do a second route to relay the call to the next gateway assuming that this will be the same dialog from the original call. Regards, -- Richard Robson Greenlight Support 01382 843843 support at greenlightcrm.com From rrobson at greenlightcrm.com Wed Jan 25 12:01:05 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Wed, 25 Jan 2017 17:01:05 +0000 Subject: [OpenSIPS-Users] calling create_dialog() on failover In-Reply-To: References: Message-ID: I may be answering my own question here, But I going to say Thay I should be using match_dialog to see if there is an existing dialog and only create one if there is not one already/ R On 25/01/2017 16:42, Richard Robson wrote: > I'm wanting to check rate limits and channel limits for calls over > several gateways. this I have working, but we are getting instances of > failures on upstream carriers. this is due to one carrier in paricular > not liking the CLIs our customers are calling from. In this case the > call comes back as a 403, which I want to failover from the > t_on_failure route to the next gateway. If I reuse my relay route it > it will have a subsequent create_dialog() it also does the topology > hiding and accounting in. Am I OK to recall the create dialog and > reuse the relay route or am i better to do a second route to relay the > call to the next gateway assuming that this will be the same dialog > from the original call. > > > Regards, > > -- Richard Robson Greenlight Support 01382 843843 support at greenlightcrm.com From razvan at opensips.org Wed Jan 25 13:06:41 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Wed, 25 Jan 2017 20:06:41 +0200 Subject: [OpenSIPS-Users] [BLOG] Real-time billing using OpenSIPS 2.3 and CGRateS Message-ID: Hello all! The upcoming OpenSIPS 2.3 will have built-in integration with the CGRateS engine, providing a simple way to do real-time billing/charging. Check out more information on our blog: https://blog.opensips.org/2017/01/25/real-time-billing-using-cgrates Best regards, -- Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com From basit.engg at gmail.com Wed Jan 25 16:08:03 2017 From: basit.engg at gmail.com (Abdul Basit) Date: Thu, 26 Jan 2017 02:08:03 +0500 Subject: [OpenSIPS-Users] scheduled concurrent call reporting In-Reply-To: References: Message-ID: Khalil, Why don't you consider snmpstat module for stats collection from opensips? On 25 Jan 2017 17:12, "Khalil Khamlichi" wrote: > Liviu, you just saved my day. my plan is to push information to redis > every 10s maybe 5s if need there is, when dashboard is complete I might > consider saving the stream of data for plotting and further analysis. > > > On Wed, Jan 25, 2017 at 11:45 AM, Liviu Chircu wrote: > >> I do not see any problems with calling "get_profile_size()" from timer >> routes, event routes, etc. As such, you can safely bypass the block >> restriction using the following example: >> >> route [get_prof_sz_inboundCalls] { >> get_profile_size("inboundCalls",,"$var(size)"); >> } >> >> route [get_prof_sz_outboundCalls] { >> get_profile_size("outboundCalls",,"$var(size)"); >> } >> >> timer_route [mytimer, 1] >> { >> route(get_prof_sz_inboundCalls); >> xlog("inboundCalls: $var(size)\n"); >> >> route(get_prof_sz_outboundCalls); >> xlog("outboundCalls: $var(size)\n"); >> } >> >> Regards, >> >> Liviu Chircu >> OpenSIPS Developerhttp://www.opensips-solutions.com >> >> On 24.01.2017 01:05, Khalil Khamlichi wrote: >> >> the idea is that I don't need to get the number of calls 30 times per >> second which would happens if I save to redis on each invite. scheduling >> the saving to redis every 10 seconds serves well my purpose but the >> timer_route doesn't seem to accept get_profile_size() >> >> any hints would be appreciated. >> >> On Mon, Jan 23, 2017 at 10:39 PM, Khalil Khamlichi < >> khamlichi.khalil at gmail.com> wrote: >> >>> Hi, >>> >>> I am trying to get call load information out of opensips at regular >>> intervals to get some sort of realtime view of the load on the server. >>> >>> After applying profiles on the the INVITEs, I have tried to call >>> get_profile_size from a timer_route. >>> I am getting error : >>> >>> CRITICAL:core:yyerror: parse error in config file >>> /usr/local//etc/opensips/opensips.cfg, line 483, column 38-39: Command >>> cannot be used in the block >>> >>> Any alternative solutions ? >>> >>> Thanks in advance. >>> >>> kkh >>> >> >> >> >> _______________________________________________ >> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tito at xsvoce.com Wed Jan 25 18:30:12 2017 From: tito at xsvoce.com (Tito Cumpen) Date: Wed, 25 Jan 2017 18:30:12 -0500 Subject: [OpenSIPS-Users] unsubscribe or 481 not working Message-ID: Group, I am having issues handling the removal of subscriptions in presence. I am using opensips 2.2.2 git revision b0fbe60. My UA is sending subscription with an expire 0 and opensips responds with 200 ok like this SIP/2.0 200 OK Via: SIP/2.0/WSS 192.0.2.67;received=xx.xx.xxx.xx;rport=49679;branch=z9hG4bK4495443 To: ;tag=688612044cccea408f6da88d48100390-629d From: "Dave Drummond, MD" ;tag=j58ltmkvo3 Call-ID: 2oc1fhb8h11j4qupkd4n CSeq: 4305 SUBSCRIBE Expires: 0 Contact: Server: domain.org Content-Length: 0 opensips continues to send notifies on reference to address th -------------- next part -------------- An HTML attachment was scrubbed... URL: From tito at xsvoce.com Wed Jan 25 18:33:34 2017 From: tito at xsvoce.com (Tito Cumpen) Date: Wed, 25 Jan 2017 18:33:34 -0500 Subject: [OpenSIPS-Users] unsubscribe or 481 not working In-Reply-To: References: Message-ID: the previously subscribed address. The UA will respond will respond with a 481 but opensips just continues to send the notifies although they are no longer subscribed. Is there any reason for this behavior? I am seeing this from opensips logs WARNING:presence:p_tm_callback: completed with status [481] and to_tag [688612044cccea408f6da88d48100390-629d], cseq [CSeq: 1] Does anyone have any idea why ? On Wed, Jan 25, 2017 at 6:30 PM, Tito Cumpen wrote: > Group, > > I am having issues handling the removal of subscriptions in presence. I am > using opensips 2.2.2 git revision b0fbe60. My UA is sending subscription > with an expire 0 and opensips responds with 200 ok like this > SIP/2.0 200 OK > Via: SIP/2.0/WSS 192.0.2.67;received=xx.xx.xxx.xx;rport=49679;branch= > z9hG4bK4495443 > To: ;tag=688612044cccea408f6da88d48100390-629d > From: "Dave Drummond, MD" ;tag=j58ltmkvo3 > Call-ID: 2oc1fhb8h11j4qupkd4n > CSeq: 4305 SUBSCRIBE > Expires: 0 > Contact: > Server: domain.org > Content-Length: 0 > > opensips continues to send notifies on reference to address th > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pat at voxtelesys.com Wed Jan 25 22:08:28 2017 From: pat at voxtelesys.com (Pat Burke) Date: Wed, 25 Jan 2017 21:08:28 -0600 Subject: [OpenSIPS-Users] send_reply from branch_route Message-ID: <1483b0bc32bcb3024971a5da985683d8@voxtelesys.com> Hello, I have an opensips server that I use for routing.  I receive a call and will attempt multiple carriers to complete the call.  My understanding is that in 2.2 I had to use branch_route to be able to make multiple attempts.  What I am running into now is that when I get a SIP response that indicates that I don't want to try another carrier, or I have tried as many as I want to try, then I want to send a SIP response (ether the response from the last carrier or a response of my own) and end the call.  When I t_reply I get the following error              "CRITICAL:tm:w_t_reply: unsupported route_type (8)". In a nutshell, the flow is 1)  Call flow leads to RELAY_TO_EGRESS to make the first call. 2)  RELAY_TO_EGRESS sets up the call information by calling OUTBOUND_SETUP (which will attempt to terminate the call if there are errors or no more carriers) and then creates a branch to handle the attempt (BRANCH_TO_EGRESS) 3)  BRANCH_TO_EGRESS does some final setup (setting up headers, etc) and sets the t_on_failure to "egress_failed" 4)  If the call attempt fails, "egress_failed" is called which may want to terminate the call (send_reply...) or attempt again by calling TRY_CARRIER_FAILOVER 5) TRY_CARRIER_FAILOVER will start the process again by calling RELAY_TO_EGRESS (which usually ends in the call to OUTBOUND_SETUP because that is where it determines when no more attempts are going to be made). In 1.11 without branching this worked fine. What is the correct way to architect the code.  Here is the general structure I have now. ... route[RELAY_TO_EGRESS] {     route(OUTBOUND_SETUP);     t_on_branch("BRANCH_TO_EGRESS");     if (!t_relay("0x01")) {         send_reply("500","Internal Error");         exit;     } } route[OUTBOUND_SETUP] { ...                 if ($avp(current_carrier_idx) == $avp(out_routes_no)) {                     route(NO_ROUTES_AVAILABLE, "No more routes available.");                 } ...     if (!route(VALIDATE_CARRIER)) {         route(TRY_CARRIER_FAILOVER, "503", "In supplemental exclusion.");         return(1);     } } branch_route[BRANCH_TO_EGRESS] { ...     t_on_failure("egress_failed"); ... } route[NO_ROUTES_AVAILABLE] {     xlog("L_WARN", "$rU SCRIPT:EGRESS:WARN: No carriers to route to.  Ending the call \n");     $avp(error_reason) := $avp(error_reason) + $param(1);     t_reply("503","Service not available.");     exit; } failure_route[egress_failed] { ...     if (t_was_cancelled()) {         route(ADD_STATUS_ERROR_REASON_TO_HISTORY, $(rs), $(rr));         xlog("L_WARN", "$rU SCRIPT:RADVANCE:WARN: Do not route advance replying with $(rs) - $(rr) \n");         $avp(error_reason) := $avp(error_reason) + "Call Terminated with " + $(rs) + ".";         t_reply("487","Request cancelled");         exit;     }     if ($(rs) != null) {         route(TRY_CARRIER_FAILOVER, $(rs), $(rr));     } else {         $avp(error_reason) := $avp(error_reason) + "Server Error V2 - empty response (rs).";         route(TRY_CARRIER_FAILOVER, "503", "Server Error");     }     exit; } route[TRY_CARRIER_FAILOVER] { ....    route(RELAY_TO_EGRESS); } } Thanks, Pat Burke -------------- next part -------------- An HTML attachment was scrubbed... URL: From aronp at guaranteedplus.com Wed Jan 25 22:51:03 2017 From: aronp at guaranteedplus.com (Aron Podrigal) Date: Thu, 26 Jan 2017 03:51:03 +0000 Subject: [OpenSIPS-Users] unsubscribe or 481 not working In-Reply-To: References: Message-ID: are the notifies you see after unsubscribing for new dialogs or for dialogs created while the UA was still subscribed? when a UA unsubscribes I think the presence server is stll suppose to continue notifying the ua for any remaining active dialogs. correct me if I'm wrong. On Wed, Jan 25, 2017, 6:34 PM Tito Cumpen wrote: > the previously subscribed address. The UA will respond will respond with a > 481 but opensips just continues to send the notifies although they are no > longer subscribed. Is there any reason for this behavior? I am seeing > this from opensips logs WARNING:presence:p_tm_callback: completed with > status [481] and to_tag [688612044cccea408f6da88d48100390-629d], cseq > [CSeq: 1] Does anyone have any idea why ? > > On Wed, Jan 25, 2017 at 6:30 PM, Tito Cumpen wrote: > > Group, > > I am having issues handling the removal of subscriptions in presence. I am > using opensips 2.2.2 git revision b0fbe60. My UA is sending subscription > with an expire 0 and opensips responds with 200 ok like this > SIP/2.0 200 OK > Via: SIP/2.0/WSS > 192.0.2.67;received=xx.xx.xxx.xx;rport=49679;branch=z9hG4bK4495443 > To: ;tag=688612044cccea408f6da88d48100390-629d > From: "Dave Drummond, MD" ;tag=j58ltmkvo3 > Call-ID: 2oc1fhb8h11j4qupkd4n > CSeq: 4305 SUBSCRIBE > Expires: 0 > Contact: > Server: domain.org > Content-Length: 0 > > opensips continues to send notifies on reference to address th > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Thu Jan 26 03:52:29 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Thu, 26 Jan 2017 10:52:29 +0200 Subject: [OpenSIPS-Users] number validation Message-ID: Hello, How Opensips 2.2 can validate number ? "491234567" is valid number , but "49a12b34567" is not valid Best regards, Dragomir -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Thu Jan 26 04:28:03 2017 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Thu, 26 Jan 2017 11:28:03 +0200 Subject: [OpenSIPS-Users] number validation In-Reply-To: References: Message-ID: <83dd909f-bb42-bf42-33f0-3b69180a7b73@opensips.org> You can use regular expressions: if ($var(number) =~ "^[0-9]*$") xlog("Number"); else xlog("Not a number"); Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com On 01/26/2017 10:52 AM, Dragomir Haralambiev wrote: > Hello, > > How Opensips 2.2 can validate number ? > > "491234567" is valid number , but > "49a12b34567" is not valid > > Best regards, > Dragomir > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Thu Jan 26 09:06:30 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Thu, 26 Jan 2017 14:06:30 +0000 Subject: [OpenSIPS-Users] scheduled concurrent call reporting In-Reply-To: References: Message-ID: snmpstat data seems a little cryptic and difficult to parse, it might be just me, so please tell me about your experience using snmpstat and how easy was it for you to make it useful for your business case ? On Wed, Jan 25, 2017 at 9:08 PM, Abdul Basit wrote: > Khalil, > > Why don't you consider snmpstat module for stats collection from opensips? > > > On 25 Jan 2017 17:12, "Khalil Khamlichi" > wrote: > >> Liviu, you just saved my day. my plan is to push information to redis >> every 10s maybe 5s if need there is, when dashboard is complete I might >> consider saving the stream of data for plotting and further analysis. >> >> >> On Wed, Jan 25, 2017 at 11:45 AM, Liviu Chircu >> wrote: >> >>> I do not see any problems with calling "get_profile_size()" from timer >>> routes, event routes, etc. As such, you can safely bypass the block >>> restriction using the following example: >>> >>> route [get_prof_sz_inboundCalls] { >>> get_profile_size("inboundCalls",,"$var(size)"); >>> } >>> >>> route [get_prof_sz_outboundCalls] { >>> get_profile_size("outboundCalls",,"$var(size)"); >>> } >>> >>> timer_route [mytimer, 1] >>> { >>> route(get_prof_sz_inboundCalls); >>> xlog("inboundCalls: $var(size)\n"); >>> >>> route(get_prof_sz_outboundCalls); >>> xlog("outboundCalls: $var(size)\n"); >>> } >>> >>> Regards, >>> >>> Liviu Chircu >>> OpenSIPS Developerhttp://www.opensips-solutions.com >>> >>> On 24.01.2017 01:05, Khalil Khamlichi wrote: >>> >>> the idea is that I don't need to get the number of calls 30 times per >>> second which would happens if I save to redis on each invite. scheduling >>> the saving to redis every 10 seconds serves well my purpose but the >>> timer_route doesn't seem to accept get_profile_size() >>> >>> any hints would be appreciated. >>> >>> On Mon, Jan 23, 2017 at 10:39 PM, Khalil Khamlichi < >>> khamlichi.khalil at gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I am trying to get call load information out of opensips at regular >>>> intervals to get some sort of realtime view of the load on the server. >>>> >>>> After applying profiles on the the INVITEs, I have tried to call >>>> get_profile_size from a timer_route. >>>> I am getting error : >>>> >>>> CRITICAL:core:yyerror: parse error in config file >>>> /usr/local//etc/opensips/opensips.cfg, line 483, column 38-39: Command >>>> cannot be used in the block >>>> >>>> Any alternative solutions ? >>>> >>>> Thanks in advance. >>>> >>>> kkh >>>> >>> >>> >>> >>> _______________________________________________ >>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Thu Jan 26 09:11:25 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Thu, 26 Jan 2017 16:11:25 +0200 Subject: [OpenSIPS-Users] scheduled concurrent call reporting In-Reply-To: References: Message-ID: Hi, You can do get_profile_size via MI interface, see: http://www.opensips.org/html/docs/modules/2.2.x/dialog.html#id297085 And you can use xmlrpc, jsonrpc, fifo and more for the MI backend. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/26/2017 04:06 PM, Khalil Khamlichi wrote: > snmpstat data seems a little cryptic and difficult to parse, it might > be just me, so please tell me about your experience using snmpstat and > how easy was it for you to make it useful for your business case ? > > On Wed, Jan 25, 2017 at 9:08 PM, Abdul Basit > wrote: > > Khalil, > > Why don't you consider snmpstat module for stats collection from > opensips? > > > On 25 Jan 2017 17:12, "Khalil Khamlichi" > > > wrote: > > Liviu, you just saved my day. my plan is to push information > to redis every 10s maybe 5s if need there is, when dashboard > is complete I might consider saving the stream of data for > plotting and further analysis. > > > On Wed, Jan 25, 2017 at 11:45 AM, Liviu Chircu > > wrote: > > I do not see any problems with calling > "get_profile_size()" from timer routes, event routes, etc. > As such, you can safely bypass the block restriction using > the following example: > > route [get_prof_sz_inboundCalls] { > get_profile_size("inboundCalls",,"$var(size)"); > } > > route [get_prof_sz_outboundCalls] { > get_profile_size("outboundCalls",,"$var(size)"); > } > > timer_route [mytimer, 1] > { > route(get_prof_sz_inboundCalls); > xlog("inboundCalls: $var(size)\n"); > > route(get_prof_sz_outboundCalls); > xlog("outboundCalls: $var(size)\n"); > } > > Regards, > > Liviu Chircu > OpenSIPS Developer > http://www.opensips-solutions.com > > > On 24.01.2017 01:05, Khalil Khamlichi wrote: >> the idea is that I don't need to get the number of calls >> 30 times per second which would happens if I save to >> redis on each invite. scheduling the saving to redis >> every 10 seconds serves well my purpose but the >> timer_route doesn't seem to accept get_profile_size() >> any hints would be appreciated. >> On Mon, Jan 23, 2017 at 10:39 PM, Khalil Khamlichi >> > > wrote: >> >> Hi, >> I am trying to get call load information out of >> opensips at regular intervals to get some sort of >> realtime view of the load on the server. >> After applying profiles on the the INVITEs, I have >> tried to call get_profile_size from a timer_route. >> I am getting error : >> CRITICAL:core:yyerror: parse error in config file >> /usr/local//etc/opensips/opensips.cfg, line 483, >> column 38-39: Command cannot be used in the block >> Any alternative solutions ? >> Thanks in advance. >> kkh >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > _______________________________________________ Users > mailing list Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ Users mailing > list Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Thu Jan 26 09:15:31 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Thu, 26 Jan 2017 16:15:31 +0200 Subject: [OpenSIPS-Users] unsubscribe or 481 not working In-Reply-To: References: Message-ID: Hi Tito, You can check the in-memory watchers (subscribers) via subs_phtable_list MI function: http://www.opensips.org/html/docs/modules/2.2.x/presence.html#id294364 Do you see any changes in the listed subscription after the un-subscribe is received ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/26/2017 01:33 AM, Tito Cumpen wrote: > the previously subscribed address. The UA will respond will respond > with a 481 but opensips just continues to send the notifies although > they are no longer subscribed. Is there any reason for this behavior? > I am seeing this from opensips logs WARNING:presence:p_tm_callback: > completed with status [481] and to_tag > [688612044cccea408f6da88d48100390-629d], cseq [CSeq: 1] Does anyone > have any idea why ? > > On Wed, Jan 25, 2017 at 6:30 PM, Tito Cumpen > wrote: > > Group, > > I am having issues handling the removal of subscriptions in > presence. I am using opensips 2.2.2 git revision b0fbe60. My UA is > sending subscription with an expire 0 and opensips responds with > 200 ok like this > SIP/2.0 200 OK > Via: SIP/2.0/WSS > 192.0.2.67;received=xx.xx.xxx.xx;rport=49679;branch=z9hG4bK4495443 > To: >;tag=688612044cccea408f6da88d48100390-629d > From: "Dave Drummond, MD" >;tag=j58ltmkvo3 > Call-ID: 2oc1fhb8h11j4qupkd4n > CSeq: 4305 SUBSCRIBE > Expires: 0 > Contact: > Server: domain.org > Content-Length: 0 > > opensips continues to send notifies on reference to address th > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From khamlichi.khalil at gmail.com Thu Jan 26 09:15:26 2017 From: khamlichi.khalil at gmail.com (Khalil Khamlichi) Date: Thu, 26 Jan 2017 14:15:26 +0000 Subject: [OpenSIPS-Users] scheduled concurrent call reporting In-Reply-To: References: Message-ID: I used Liviu technique, works beautifully, we are getting very clean reliable data right from the core of opensips into redis and from there the world is the limit :) On Thu, Jan 26, 2017 at 2:11 PM, Bogdan-Andrei Iancu wrote: > Hi, > > You can do get_profile_size via MI interface, see: > http://www.opensips.org/html/docs/modules/2.2.x/dialog.html#id297085 > > And you can use xmlrpc, jsonrpc, fifo and more for the MI backend. > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developerhttp://www.opensips-solutions.com > > On 01/26/2017 04:06 PM, Khalil Khamlichi wrote: > > snmpstat data seems a little cryptic and difficult to parse, it might be > just me, so please tell me about your experience using snmpstat and how > easy was it for you to make it useful for your business case ? > > On Wed, Jan 25, 2017 at 9:08 PM, Abdul Basit wrote: > >> Khalil, >> >> Why don't you consider snmpstat module for stats collection from >> opensips? >> >> >> On 25 Jan 2017 17:12, "Khalil Khamlichi" >> wrote: >> >>> Liviu, you just saved my day. my plan is to push information to redis >>> every 10s maybe 5s if need there is, when dashboard is complete I might >>> consider saving the stream of data for plotting and further analysis. >>> >>> >>> On Wed, Jan 25, 2017 at 11:45 AM, Liviu Chircu < >>> liviu at opensips.org> wrote: >>> >>>> I do not see any problems with calling "get_profile_size()" from timer >>>> routes, event routes, etc. As such, you can safely bypass the block >>>> restriction using the following example: >>>> >>>> route [get_prof_sz_inboundCalls] { >>>> get_profile_size("inboundCalls",,"$var(size)"); >>>> } >>>> >>>> route [get_prof_sz_outboundCalls] { >>>> get_profile_size("outboundCalls",,"$var(size)"); >>>> } >>>> >>>> timer_route [mytimer, 1] >>>> { >>>> route(get_prof_sz_inboundCalls); >>>> xlog("inboundCalls: $var(size)\n"); >>>> >>>> route(get_prof_sz_outboundCalls); >>>> xlog("outboundCalls: $var(size)\n"); >>>> } >>>> >>>> Regards, >>>> >>>> Liviu Chircu >>>> OpenSIPS Developerhttp://www.opensips-solutions.com >>>> >>>> On 24.01.2017 01:05, Khalil Khamlichi wrote: >>>> >>>> the idea is that I don't need to get the number of calls 30 times per >>>> second which would happens if I save to redis on each invite. scheduling >>>> the saving to redis every 10 seconds serves well my purpose but the >>>> timer_route doesn't seem to accept get_profile_size() >>>> any hints would be appreciated. >>>> On Mon, Jan 23, 2017 at 10:39 PM, Khalil Khamlichi < >>>> khamlichi.khalil at gmail.com> wrote: >>>>> >>>>> Hi, >>>>> I am trying to get call load information out of opensips at regular >>>>> intervals to get some sort of realtime view of the load on the server. >>>>> After applying profiles on the the INVITEs, I have tried to call >>>>> get_profile_size from a timer_route. >>>>> I am getting error : >>>>> CRITICAL:core:yyerror: parse error in config file >>>>> /usr/local//etc/opensips/opensips.cfg, line 483, column 38-39: >>>>> Command cannot be used in the block >>>>> Any alternative solutions ? >>>>> Thanks in advance. >>>>> kkh >>>>> >>>> _______________________________________________ >>>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>> >>>> _______________________________________________ Users mailing list >>>> Users at lists.opensips.org http://lists.opensips.org/cgi- >>>> bin/mailman/listinfo/users >>> >>> _______________________________________________ Users mailing list >>> Users at lists.opensips.org http://lists.opensips.org/cgi- >>> bin/mailman/listinfo/users >> >> _______________________________________________ Users mailing list >> Users at lists.opensips.org http://lists.opensips.org/cgi- >> bin/mailman/listinfo/users > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Thu Jan 26 09:20:11 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Thu, 26 Jan 2017 16:20:11 +0200 Subject: [OpenSIPS-Users] send_reply from branch_route In-Reply-To: <1483b0bc32bcb3024971a5da985683d8@voxtelesys.com> References: <1483b0bc32bcb3024971a5da985683d8@voxtelesys.com> Message-ID: Hi Pat, In the branch route you cannot use any signaling function - the branch route is there just for exploring and changing the SIP message (in a per branch manner). What you can do is to drop a branch (to tell OpenSIPS not to send that branch out) by using the "drop()" function. Still, you can do parallel forking without the need of branch route - again, the branch route is optionally there if you want to individually changes the branches (like for the branch going to a GW to add the RPID hdr, but not for the branch going to a user). If you deal with the branches in the same way, there is no need for a branch route. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/26/2017 05:08 AM, Pat Burke wrote: > Hello, > > I have an opensips server that I use for routing. I receive a call > and will attempt multiple carriers to complete the call. My > understanding is that in 2.2 I had to use branch_route to be able to > make multiple attempts. What I am running into now is that when I get > a SIP response that indicates that I don't want to try another > carrier, or I have tried as many as I want to try, then I want to send > a SIP response (ether the response from the last carrier or a response > of my own) and end the call. When I t_reply I get the following error > "CRITICAL:tm:w_t_reply: unsupported route_type (8)". > > In a nutshell, the flow is > > 1) Call flow leads to RELAY_TO_EGRESS to make the first call. > 2) RELAY_TO_EGRESS sets up the call information by calling > OUTBOUND_SETUP (which will attempt to terminate the call if there are > errors or no more carriers) and then creates a branch to handle the > attempt (BRANCH_TO_EGRESS) > 3) BRANCH_TO_EGRESS does some final setup (setting up headers, etc) > and sets the t_on_failure to "egress_failed" > 4) If the call attempt fails, "egress_failed" is called which may > want to terminate the call (send_reply...) or attempt again by calling > TRY_CARRIER_FAILOVER > 5) TRY_CARRIER_FAILOVER will start the process again by calling > RELAY_TO_EGRESS (which usually ends in the call to OUTBOUND_SETUP > because that is where it determines when no more attempts are going to > be made). > > In 1.11 without branching this worked fine. > > What is the correct way to architect the code. Here is the general > structure I have now. > > ... > > route[RELAY_TO_EGRESS] { > route(OUTBOUND_SETUP); > t_on_branch("BRANCH_TO_EGRESS"); > > if (!t_relay("0x01")) { > send_reply("500","Internal Error"); > exit; > } > } > > route[OUTBOUND_SETUP] { > ... > if ($avp(current_carrier_idx) == $avp(out_routes_no)) { > route(NO_ROUTES_AVAILABLE, "No more routes > available."); > } > ... > if (!route(VALIDATE_CARRIER)) { > route(TRY_CARRIER_FAILOVER, "503", "In supplemental exclusion."); > return(1); > } > } > > branch_route[BRANCH_TO_EGRESS] { > ... > t_on_failure("egress_failed"); > ... > } > > route[NO_ROUTES_AVAILABLE] { > xlog("L_WARN", "$rU SCRIPT:EGRESS:WARN: No carriers to route to. > Ending the call \n"); > $avp(error_reason) := $avp(error_reason) + $param(1); > t_reply("503","Service not available."); > exit; > } > > failure_route[egress_failed] { > ... > if (t_was_cancelled()) { > route(ADD_STATUS_ERROR_REASON_TO_HISTORY, $(rs), > $(rr)); > xlog("L_WARN", "$rU SCRIPT:RADVANCE:WARN: Do not route advance > replying with $(rs) - $(rr) \n"); > $avp(error_reason) := $avp(error_reason) + "Call Terminated > with " + $(rs) + "."; > t_reply("487","Request cancelled"); > exit; > } > > if ($(rs) != null) { > route(TRY_CARRIER_FAILOVER, $(rs), $(rr)); > } else { > $avp(error_reason) := $avp(error_reason) + "Server Error V2 - > empty response (rs)."; > route(TRY_CARRIER_FAILOVER, "503", "Server Error"); > } > > exit; > } > > route[TRY_CARRIER_FAILOVER] { > .... > route(RELAY_TO_EGRESS); > } > } > > Thanks, > Pat Burke > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Thu Jan 26 09:27:42 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Thu, 26 Jan 2017 16:27:42 +0200 Subject: [OpenSIPS-Users] calling create_dialog() on failover In-Reply-To: References: Message-ID: Hi Richard, The dialog creation should be done before any forking. Creating it during the forking may lead to bogus outcomes. So, be sure that the "relay" route doesn;t do any dialog creation ...as it may be trigger more than once for an INVITE. Also using match_dialog() may lead to bogus results, as this function does more than matching - it updates the internal dialog state machine, triggers callback. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/25/2017 07:01 PM, Richard Robson wrote: > I may be answering my own question here, But I going to say Thay I > should be using match_dialog to see if there is an existing dialog and > only create one if there is not one already/ > > R > > On 25/01/2017 16:42, Richard Robson wrote: >> I'm wanting to check rate limits and channel limits for calls over >> several gateways. this I have working, but we are getting instances >> of failures on upstream carriers. this is due to one carrier in >> paricular not liking the CLIs our customers are calling from. In this >> case the call comes back as a 403, which I want to failover from the >> t_on_failure route to the next gateway. If I reuse my relay route it >> it will have a subsequent create_dialog() it also does the topology >> hiding and accounting in. Am I OK to recall the create dialog and >> reuse the relay route or am i better to do a second route to relay >> the call to the next gateway assuming that this will be the same >> dialog from the original call. >> >> >> Regards, >> >> > > From rrobson at greenlightcrm.com Thu Jan 26 09:56:26 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Thu, 26 Jan 2017 14:56:26 +0000 Subject: [OpenSIPS-Users] calling create_dialog() on failover In-Reply-To: References: Message-ID: <649a4f14-5fee-963f-bcfa-1797eff0475b@greenlightcrm.com> Hi Bogdan, So I'd be better off creating the dialog on the initial INVITE?. Will this persist over the failure routes and the subsequent calls to the next gateway? Regards, Richard On 26/01/2017 14:27, Bogdan-Andrei Iancu wrote: > Hi Richard, > > The dialog creation should be done before any forking. Creating it > during the forking may lead to bogus outcomes. So, be sure that the > "relay" route doesn;t do any dialog creation ...as it may be trigger > more than once for an INVITE. Also using match_dialog() may lead to > bogus results, as this function does more than matching - it updates > the internal dialog state machine, triggers callback. > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 01/25/2017 07:01 PM, Richard Robson wrote: >> I may be answering my own question here, But I going to say Thay I >> should be using match_dialog to see if there is an existing dialog >> and only create one if there is not one already/ >> >> R >> >> On 25/01/2017 16:42, Richard Robson wrote: >>> I'm wanting to check rate limits and channel limits for calls over >>> several gateways. this I have working, but we are getting instances >>> of failures on upstream carriers. this is due to one carrier in >>> paricular not liking the CLIs our customers are calling from. In >>> this case the call comes back as a 403, which I want to failover >>> from the t_on_failure route to the next gateway. If I reuse my relay >>> route it it will have a subsequent create_dialog() it also does the >>> topology hiding and accounting in. Am I OK to recall the create >>> dialog and reuse the relay route or am i better to do a second route >>> to relay the call to the next gateway assuming that this will be the >>> same dialog from the original call. >>> >>> >>> Regards, >>> >>> >> >> > -- Richard Robson Greenlight Support 01382 843843 support at greenlightcrm.com From bogdan at opensips.org Thu Jan 26 10:02:55 2017 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Thu, 26 Jan 2017 17:02:55 +0200 Subject: [OpenSIPS-Users] calling create_dialog() on failover In-Reply-To: <649a4f14-5fee-963f-bcfa-1797eff0475b@greenlightcrm.com> References: <649a4f14-5fee-963f-bcfa-1797eff0475b@greenlightcrm.com> Message-ID: Yes and Yes. Keep in mind that all the branches of a parallel/serial fork belong to the _same_ call !! when you do failover to the next gateway, you do not create a new dialog, but a new branch in the same dialog. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/26/2017 04:56 PM, Richard Robson wrote: > Hi Bogdan, > > So I'd be better off creating the dialog on the initial INVITE?. Will > this persist over the failure routes and the subsequent calls to the > next gateway? > > Regards, > > Richard > > On 26/01/2017 14:27, Bogdan-Andrei Iancu wrote: >> Hi Richard, >> >> The dialog creation should be done before any forking. Creating it >> during the forking may lead to bogus outcomes. So, be sure that the >> "relay" route doesn;t do any dialog creation ...as it may be trigger >> more than once for an INVITE. Also using match_dialog() may lead to >> bogus results, as this function does more than matching - it updates >> the internal dialog state machine, triggers callback. >> >> Regards, >> >> Bogdan-Andrei Iancu >> OpenSIPS Founder and Developer >> http://www.opensips-solutions.com >> >> On 01/25/2017 07:01 PM, Richard Robson wrote: >>> I may be answering my own question here, But I going to say Thay I >>> should be using match_dialog to see if there is an existing dialog >>> and only create one if there is not one already/ >>> >>> R >>> >>> On 25/01/2017 16:42, Richard Robson wrote: >>>> I'm wanting to check rate limits and channel limits for calls over >>>> several gateways. this I have working, but we are getting instances >>>> of failures on upstream carriers. this is due to one carrier in >>>> paricular not liking the CLIs our customers are calling from. In >>>> this case the call comes back as a 403, which I want to failover >>>> from the t_on_failure route to the next gateway. If I reuse my >>>> relay route it it will have a subsequent create_dialog() it also >>>> does the topology hiding and accounting in. Am I OK to recall the >>>> create dialog and reuse the relay route or am i better to do a >>>> second route to relay the call to the next gateway assuming that >>>> this will be the same dialog from the original call. >>>> >>>> >>>> Regards, >>>> >>>> >>> >>> >> > > From rrobson at greenlightcrm.com Thu Jan 26 10:32:35 2017 From: rrobson at greenlightcrm.com (Richard Robson) Date: Thu, 26 Jan 2017 15:32:35 +0000 Subject: [OpenSIPS-Users] calling create_dialog() on failover In-Reply-To: References: <649a4f14-5fee-963f-bcfa-1797eff0475b@greenlightcrm.com> Message-ID: Hi Bogdan, I had thought that I'd create the dialog once the call had been excepted and processed. I'll move the Dialog creation to the Invite processing. Thanks, Richard On 26/01/2017 15:02, Bogdan-Andrei Iancu wrote: > Yes and Yes. > > Keep in mind that all the branches of a parallel/serial fork belong to > the _same_ call !! when you do failover to the next gateway, you do > not create a new dialog, but a new branch in the same dialog. > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 01/26/2017 04:56 PM, Richard Robson wrote: >> Hi Bogdan, >> >> So I'd be better off creating the dialog on the initial INVITE?. Will >> this persist over the failure routes and the subsequent calls to the >> next gateway? >> >> Regards, >> >> Richard >> >> On 26/01/2017 14:27, Bogdan-Andrei Iancu wrote: >>> Hi Richard, >>> >>> The dialog creation should be done before any forking. Creating it >>> during the forking may lead to bogus outcomes. So, be sure that the >>> "relay" route doesn;t do any dialog creation ...as it may be trigger >>> more than once for an INVITE. Also using match_dialog() may lead to >>> bogus results, as this function does more than matching - it updates >>> the internal dialog state machine, triggers callback. >>> >>> Regards, >>> >>> Bogdan-Andrei Iancu >>> OpenSIPS Founder and Developer >>> http://www.opensips-solutions.com >>> >>> On 01/25/2017 07:01 PM, Richard Robson wrote: >>>> I may be answering my own question here, But I going to say Thay I >>>> should be using match_dialog to see if there is an existing dialog >>>> and only create one if there is not one already/ >>>> >>>> R >>>> >>>> On 25/01/2017 16:42, Richard Robson wrote: >>>>> I'm wanting to check rate limits and channel limits for calls over >>>>> several gateways. this I have working, but we are getting >>>>> instances of failures on upstream carriers. this is due to one >>>>> carrier in paricular not liking the CLIs our customers are calling >>>>> from. In this case the call comes back as a 403, which I want to >>>>> failover from the t_on_failure route to the next gateway. If I >>>>> reuse my relay route it it will have a subsequent create_dialog() >>>>> it also does the topology hiding and accounting in. Am I OK to >>>>> recall the create dialog and reuse the relay route or am i better >>>>> to do a second route to relay the call to the next gateway >>>>> assuming that this will be the same dialog from the original call. >>>>> >>>>> >>>>> Regards, >>>>> >>>>> >>>> >>>> >>> >> >> > -- Richard Robson Greenlight Support 01382 843843 support at greenlightcrm.com From pat at voxtelesys.com Thu Jan 26 14:49:14 2017 From: pat at voxtelesys.com (Pat Burke) Date: Thu, 26 Jan 2017 13:49:14 -0600 Subject: [OpenSIPS-Users] send_reply from branch_route In-Reply-To: References: <1483b0bc32bcb3024971a5da985683d8@voxtelesys.com> Message-ID: Thanks Bogdan, I was able to make it work by making the decision to end the call prior to calling the branch.  Works like a charm. Regards, Pat Burke -----Original Message----- From: "Bogdan-Andrei Iancu" To: "OpenSIPS users mailling list" , "Pat Burke" Date: 01/26/17 08:20 Subject: Re: [OpenSIPS-Users] send_reply from branch_route Hi Pat, In the branch route you cannot use any signaling function - the branch route is there just for exploring and changing the SIP message (in a per branch manner). What you can do is to drop a branch (to tell OpenSIPS not to send that branch out) by using the "drop()" function. Still, you can do parallel forking without the need of branch route - again, the branch route is optionally there if you want to individually changes the branches (like for the branch going to a GW to add the RPID hdr, but not for the branch going to a user). If you deal with the branches in the same way, there is no need for a branch route. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developerhttp://www.opensips-solutions.com On 01/26/2017 05:08 AM, Pat Burke wrote: Hello, I have an opensips server that I use for routing. I receive a call and will attempt multiple carriers to complete the call. My understanding is that in 2.2 I had to use branch_route to be able to make multiple attempts. What I am running into now is that when I get a SIP response that indicates that I don't want to try another carrier, or I have tried as many as I want to try, then I want to send a SIP response (ether the response from the last carrier or a response of my own) and end the call. When I t_reply I get the following error "CRITICAL:tm:w_t_reply: unsupported route_type (8)". In a nutshell, the flow is 1) Call flow leads to RELAY_TO_EGRESS to make the first call. 2) RELAY_TO_EGRESS sets up the call information by calling OUTBOUND_SETUP (which will attempt to terminate the call if there are errors or no more carriers) and then creates a branch to handle the attempt (BRANCH_TO_EGRESS) 3) BRANCH_TO_EGRESS does some final setup (setting up headers, etc) and sets the t_on_failure to "egress_failed" 4) If the call attempt fails, "egress_failed" is called which may want to terminate the call (send_reply...) or attempt again by calling TRY_CARRIER_FAILOVER 5) TRY_CARRIER_FAILOVER will start the process again by calling RELAY_TO_EGRESS (which usually ends in the call to OUTBOUND_SETUP because that is where it determines when no more attempts are going to be made). In 1.11 without branching this worked fine. What is the correct way to architect the code. Here is the general structure I have now. ... route[RELAY_TO_EGRESS] { route(OUTBOUND_SETUP); t_on_branch("BRANCH_TO_EGRESS"); if (!t_relay("0x01")) { send_reply("500","Internal Error"); exit; } } route[OUTBOUND_SETUP] { ... if ($avp(current_carrier_idx) == $avp(out_routes_no)) { route(NO_ROUTES_AVAILABLE, "No more routes available."); } ... if (!route(VALIDATE_CARRIER)) { route(TRY_CARRIER_FAILOVER, "503", "In supplemental exclusion."); return(1); } } branch_route[BRANCH_TO_EGRESS] { ... t_on_failure("egress_failed"); ... } route[NO_ROUTES_AVAILABLE] { xlog("L_WARN", "$rU SCRIPT:EGRESS:WARN: No carriers to route to. Ending the call \n"); $avp(error_reason) := $avp(error_reason) + $param(1); t_reply("503","Service not available."); exit; } failure_route[egress_failed] { ... if (t_was_cancelled()) { route(ADD_STATUS_ERROR_REASON_TO_HISTORY, $(rs), $(rr)); xlog("L_WARN", "$rU SCRIPT:RADVANCE:WARN: Do not route advance replying with $(rs) - $(rr) \n"); $avp(error_reason) := $avp(error_reason) + "Call Terminated with " + $(rs) + "."; t_reply("487","Request cancelled"); exit; } if ($(rs) != null) { route(TRY_CARRIER_FAILOVER, $(rs), $(rr)); } else { $avp(error_reason) := $avp(error_reason) + "Server Error V2 - empty response (rs)."; route(TRY_CARRIER_FAILOVER, "503", "Server Error"); } exit; } route[TRY_CARRIER_FAILOVER] { .... route(RELAY_TO_EGRESS); } } Thanks, Pat Burke _______________________________________________ Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From jock.mckechnie at gmail.com Fri Jan 27 12:26:01 2017 From: jock.mckechnie at gmail.com (Jock McKechnie) Date: Fri, 27 Jan 2017 11:26:01 -0600 Subject: [OpenSIPS-Users] s.index madness and my waning grip on sanity Message-ID: Good morning all; I'm having a battle with s.index that I'd really like to believe no one should be waging, and I've come to the conclusion either 1.11 is seriously broken, or I'm utterly deranged, but at the risk of verifying the second, I wanted to reach out and figure out what I'm doing wrong here. I seem utterly incapable of getting s.index working at all, consider the following: $var(source) = "onetwothree"; $var(search) = "one"; $var(index) = $(var(source){s.index, $var(search), 0}); Which should look famaliar as it's based entirely on the example in the 1.11 documentation. This produces the following: ERROR:core:tr_parse_string: unknown transformation: index, $var(search), 0}/index/5! ERROR:core:parse_transformation: error parsing [{s.index, $var(search), 0}] ERROR:core:pv_parse_spec: ERROR:bad tr in pvar name "var" ERROR:core:pv_parse_spec: invalid parsing in [$(var(source){s.index, $var(search), 0})] at (4) CRITICAL:core:yyerror: parse error in config file /etc/opensips/opensips.cfg, line 92, column 166-206: unknown script variable Using a static search string: $var(index) = $(var(source){s.index, "one", 0}); Garners me the same with: ERROR:core:tr_parse_string: unknown transformation: index, "one", 0}/index/5! And not providing a starting offset is similar: $var(index) = $(var(source){s.index, $var(search)}); ERROR:core:tr_parse_string: unknown transformation: index, $var(search)}/index/5! Given these are core transformations and I'm using several others in my configs I'm running under the belief I'm not missing a module. I've tried copying the doc example verbatim with identical results. What am I missing here, people? Is it just staring me straight in the face? My thanks; - Jock From liviu at opensips.org Fri Jan 27 13:10:27 2017 From: liviu at opensips.org (Liviu Chircu) Date: Fri, 27 Jan 2017 20:10:27 +0200 Subject: [OpenSIPS-Users] s.index madness and my waning grip on sanity In-Reply-To: References: Message-ID: <8720a4cc-75fd-a4a8-28cc-13d5b9bbcf42@opensips.org> Hi, Jock! The answer is simple: you must be using a pre-2.2 OpenSIPS, which does not include this transformation, just like the error message says: "ERROR:core:tr_parse_string: unknown transformation: index" Future advice: before reading documentation, make sure you properly select your OpenSIPS version using the top-level switches [1] [1]: http://www.opensips.org/Documentation/Script-Tran-2-1 Regards, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 27.01.2017 19:26, Jock McKechnie wrote: > Good morning all; > > I'm having a battle with s.index that I'd really like to believe no > one should be waging, and I've come to the conclusion either 1.11 is > seriously broken, or I'm utterly deranged, but at the risk of > verifying the second, I wanted to reach out and figure out what I'm > doing wrong here. > > I seem utterly incapable of getting s.index working at all, consider > the following: > > $var(source) = "onetwothree"; > $var(search) = "one"; > $var(index) = $(var(source){s.index, $var(search), 0}); > > Which should look famaliar as it's based entirely on the example in > the 1.11 documentation. This produces the following: > ERROR:core:tr_parse_string: unknown transformation: index, > $var(search), 0}/index/5! ERROR:core:parse_transformation: error > parsing [{s.index, $var(search), 0}] ERROR:core:pv_parse_spec: > ERROR:bad tr in pvar name "var" ERROR:core:pv_parse_spec: invalid > parsing in [$(var(source){s.index, $var(search), 0})] at (4) > CRITICAL:core:yyerror: parse error in config file > /etc/opensips/opensips.cfg, line 92, column 166-206: unknown script > variable > > Using a static search string: > $var(index) = $(var(source){s.index, "one", 0}); > > Garners me the same with: > ERROR:core:tr_parse_string: unknown transformation: index, "one", 0}/index/5! > > And not providing a starting offset is similar: > $var(index) = $(var(source){s.index, $var(search)}); > > ERROR:core:tr_parse_string: unknown transformation: index, > $var(search)}/index/5! > > Given these are core transformations and I'm using several others in > my configs I'm running under the belief I'm not missing a module. I've > tried copying the doc example verbatim with identical results. What am > I missing here, people? Is it just staring me straight in the face? > > My thanks; > - Jock > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From Ben.Newlin at inin.com Fri Jan 27 13:17:18 2017 From: Ben.Newlin at inin.com (Newlin, Ben) Date: Fri, 27 Jan 2017 18:17:18 +0000 Subject: [OpenSIPS-Users] s.index madness and my waning grip on sanity In-Reply-To: <8720a4cc-75fd-a4a8-28cc-13d5b9bbcf42@opensips.org> References: <8720a4cc-75fd-a4a8-28cc-13d5b9bbcf42@opensips.org> Message-ID: That is not correct. OpenSIPS 1.11 definitely contains the index transformation [1]. I’m using it in my code! I think the problem is the quoting. For the example that uses a hard-coded search string it should work if you leave off the quotes. This is how I’m using it. For the variable example, the only thing I can see is that the example you copied is using single quotes, while you are using double quotes. I only use s.index with a $param variable, so I’m not sure what the proper quoting is our if it will make a difference. [1] http://www.opensips.org/Documentation/Script-Tran-1-11#toc19 Ben Newlin From: Users on behalf of Liviu Chircu Reply-To: OpenSIPS users mailling list Date: Friday, January 27, 2017 at 1:10 PM To: "users at lists.opensips.org" Subject: Re: [OpenSIPS-Users] s.index madness and my waning grip on sanity Hi, Jock! The answer is simple: you must be using a pre-2.2 OpenSIPS, which does not include this transformation, just like the error message says: "ERROR:core:tr_parse_string: unknown transformation: index" Future advice: before reading documentation, make sure you properly select your OpenSIPS version using the top-level switches [1] [1]: http://www.opensips.org/Documentation/Script-Tran-2-1 Regards, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 27.01.2017 19:26, Jock McKechnie wrote: Good morning all; I'm having a battle with s.index that I'd really like to believe no one should be waging, and I've come to the conclusion either 1.11 is seriously broken, or I'm utterly deranged, but at the risk of verifying the second, I wanted to reach out and figure out what I'm doing wrong here. I seem utterly incapable of getting s.index working at all, consider the following: $var(source) = "onetwothree"; $var(search) = "one"; $var(index) = $(var(source){s.index, $var(search), 0}); Which should look famaliar as it's based entirely on the example in the 1.11 documentation. This produces the following: ERROR:core:tr_parse_string: unknown transformation: index, $var(search), 0}/index/5! ERROR:core:parse_transformation: error parsing [{s.index, $var(search), 0}] ERROR:core:pv_parse_spec: ERROR:bad tr in pvar name "var" ERROR:core:pv_parse_spec: invalid parsing in [$(var(source){s.index, $var(search), 0})] at (4) CRITICAL:core:yyerror: parse error in config file /etc/opensips/opensips.cfg, line 92, column 166-206: unknown script variable Using a static search string: $var(index) = $(var(source){s.index, "one", 0}); Garners me the same with: ERROR:core:tr_parse_string: unknown transformation: index, "one", 0}/index/5! And not providing a starting offset is similar: $var(index) = $(var(source){s.index, $var(search)}); ERROR:core:tr_parse_string: unknown transformation: index, $var(search)}/index/5! Given these are core transformations and I'm using several others in my configs I'm running under the belief I'm not missing a module. I've tried copying the doc example verbatim with identical results. What am I missing here, people? Is it just staring me straight in the face? My thanks; - Jock _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From jock.mckechnie at gmail.com Fri Jan 27 14:11:07 2017 From: jock.mckechnie at gmail.com (Jock McKechnie) Date: Fri, 27 Jan 2017 13:11:07 -0600 Subject: [OpenSIPS-Users] s.index madness and my waning grip on sanity In-Reply-To: References: <8720a4cc-75fd-a4a8-28cc-13d5b9bbcf42@opensips.org> Message-ID: Thanks Ben; As you say, the s.index is in the 1.11 docs. I had a brief moment of panic when Liviu suggested otherwise until I checked, verified, and then your mail popped up confirming. I tried single quotes on both variable declarations, I tried the index with the var ($var(search)) and a string ('one') with the same error, so that doesn't appear to be it. I'd wonder if it didn't like this type of variable... except it's documented to work this way. $var(source) = 'onetwothree'; $var(search) = 'one' $var(index) = $(var(source){s.index, $var(search)}); $var(index) = $(var(source){s.index, 'one'}); Even though you use this differently, would you be willing to post your working example just so I have something else to stare at? And if anyone else has any bright ideas, I'm definitely all ears (or eyes); Thanks very much; - Jock On Fri, Jan 27, 2017 at 12:17 PM, Newlin, Ben wrote: > That is not correct. OpenSIPS 1.11 definitely contains the index > transformation [1]. I’m using it in my code! > > > > I think the problem is the quoting. For the example that uses a hard-coded > search string it should work if you leave off the quotes. This is how I’m > using it. > > > > For the variable example, the only thing I can see is that the example you > copied is using single quotes, while you are using double quotes. I only use > s.index with a $param variable, so I’m not sure what the proper quoting is > our if it will make a difference. > > > > [1] http://www.opensips.org/Documentation/Script-Tran-1-11#toc19 > > > > Ben Newlin > > > > > > From: Users on behalf of Liviu Chircu > > Reply-To: OpenSIPS users mailling list > Date: Friday, January 27, 2017 at 1:10 PM > To: "users at lists.opensips.org" > Subject: Re: [OpenSIPS-Users] s.index madness and my waning grip on sanity > > > > Hi, Jock! > > > > The answer is simple: you must be using a pre-2.2 OpenSIPS, which does > > not include this transformation, just like the error message says: > > > > "ERROR:core:tr_parse_string: unknown transformation: index" > > > > Future advice: before reading documentation, make sure you properly > > select your OpenSIPS version using the top-level switches [1] > > > > [1]: http://www.opensips.org/Documentation/Script-Tran-2-1 > > > > Regards, > > > > Liviu Chircu > > OpenSIPS Developer > > http://www.opensips-solutions.com > > > > On 27.01.2017 19:26, Jock McKechnie wrote: > > Good morning all; > > > > I'm having a battle with s.index that I'd really like to believe no > > one should be waging, and I've come to the conclusion either 1.11 is > > seriously broken, or I'm utterly deranged, but at the risk of > > verifying the second, I wanted to reach out and figure out what I'm > > doing wrong here. > > > > I seem utterly incapable of getting s.index working at all, consider > > the following: > > > > $var(source) = "onetwothree"; > > $var(search) = "one"; > > $var(index) = $(var(source){s.index, $var(search), 0}); > > > > Which should look famaliar as it's based entirely on the example in > > the 1.11 documentation. This produces the following: > > ERROR:core:tr_parse_string: unknown transformation: index, > > $var(search), 0}/index/5! ERROR:core:parse_transformation: error > > parsing [{s.index, $var(search), 0}] ERROR:core:pv_parse_spec: > > ERROR:bad tr in pvar name "var" ERROR:core:pv_parse_spec: invalid > > parsing in [$(var(source){s.index, $var(search), 0})] at (4) > > CRITICAL:core:yyerror: parse error in config file > > /etc/opensips/opensips.cfg, line 92, column 166-206: unknown script > > variable > > > > Using a static search string: > > $var(index) = $(var(source){s.index, "one", 0}); > > > > Garners me the same with: > > ERROR:core:tr_parse_string: unknown transformation: index, "one", > 0}/index/5! > > > > And not providing a starting offset is similar: > > $var(index) = $(var(source){s.index, $var(search)}); > > > > ERROR:core:tr_parse_string: unknown transformation: index, > > $var(search)}/index/5! > > > > Given these are core transformations and I'm using several others in > > my configs I'm running under the belief I'm not missing a module. I've > > tried copying the doc example verbatim with identical results. What am > > I missing here, people? Is it just staring me straight in the face? > > > > My thanks; > > - Jock > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > From Ben.Newlin at inin.com Fri Jan 27 15:18:38 2017 From: Ben.Newlin at inin.com (Newlin, Ben) Date: Fri, 27 Jan 2017 20:18:38 +0000 Subject: [OpenSIPS-Users] s.index madness and my waning grip on sanity In-Reply-To: References: <8720a4cc-75fd-a4a8-28cc-13d5b9bbcf42@opensips.org> Message-ID: <5A5FEB40-8D2E-4BEC-9ED3-C329C84F999D@inin.com> For the hard-coded string, my suggestion was to remove the quotes completely. Most transformations don’t want quotes, even on string-type input. $var(index) = $(var(source){s.index, one}); For the variable, I can’t help as I’m not using it. I can confirm it works with a route parameter: $var(index) = $(var(source){s.index, $param(1)}); Ben Newlin Lead Voice Network Engineer, PureCloud T: +1 317 957 1009 ben.newlin at inin.com From: Users on behalf of Jock McKechnie Reply-To: OpenSIPS users mailling list Date: Friday, January 27, 2017 at 2:11 PM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] s.index madness and my waning grip on sanity Thanks Ben; As you say, the s.index is in the 1.11 docs. I had a brief moment of panic when Liviu suggested otherwise until I checked, verified, and then your mail popped up confirming. I tried single quotes on both variable declarations, I tried the index with the var ($var(search)) and a string ('one') with the same error, so that doesn't appear to be it. I'd wonder if it didn't like this type of variable... except it's documented to work this way. $var(source) = 'onetwothree'; $var(search) = 'one' $var(index) = $(var(source){s.index, $var(search)}); $var(index) = $(var(source){s.index, 'one'}); Even though you use this differently, would you be willing to post your working example just so I have something else to stare at? And if anyone else has any bright ideas, I'm definitely all ears (or eyes); Thanks very much; - Jock On Fri, Jan 27, 2017 at 12:17 PM, Newlin, Ben > wrote: That is not correct. OpenSIPS 1.11 definitely contains the index transformation [1]. I’m using it in my code! I think the problem is the quoting. For the example that uses a hard-coded search string it should work if you leave off the quotes. This is how I’m using it. For the variable example, the only thing I can see is that the example you copied is using single quotes, while you are using double quotes. I only use s.index with a $param variable, so I’m not sure what the proper quoting is our if it will make a difference. [1] http://www.opensips.org/Documentation/Script-Tran-1-11#toc19 Ben Newlin From: Users > on behalf of Liviu Chircu > Reply-To: OpenSIPS users mailling list > Date: Friday, January 27, 2017 at 1:10 PM To: "users at lists.opensips.org" > Subject: Re: [OpenSIPS-Users] s.index madness and my waning grip on sanity Hi, Jock! The answer is simple: you must be using a pre-2.2 OpenSIPS, which does not include this transformation, just like the error message says: "ERROR:core:tr_parse_string: unknown transformation: index" Future advice: before reading documentation, make sure you properly select your OpenSIPS version using the top-level switches [1] [1]: http://www.opensips.org/Documentation/Script-Tran-2-1 Regards, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 27.01.2017 19:26, Jock McKechnie wrote: Good morning all; I'm having a battle with s.index that I'd really like to believe no one should be waging, and I've come to the conclusion either 1.11 is seriously broken, or I'm utterly deranged, but at the risk of verifying the second, I wanted to reach out and figure out what I'm doing wrong here. I seem utterly incapable of getting s.index working at all, consider the following: $var(source) = "onetwothree"; $var(search) = "one"; $var(index) = $(var(source){s.index, $var(search), 0}); Which should look famaliar as it's based entirely on the example in the 1.11 documentation. This produces the following: ERROR:core:tr_parse_string: unknown transformation: index, $var(search), 0}/index/5! ERROR:core:parse_transformation: error parsing [{s.index, $var(search), 0}] ERROR:core:pv_parse_spec: ERROR:bad tr in pvar name "var" ERROR:core:pv_parse_spec: invalid parsing in [$(var(source){s.index, $var(search), 0})] at (4) CRITICAL:core:yyerror: parse error in config file /etc/opensips/opensips.cfg, line 92, column 166-206: unknown script variable Using a static search string: $var(index) = $(var(source){s.index, "one", 0}); Garners me the same with: ERROR:core:tr_parse_string: unknown transformation: index, "one", 0}/index/5! And not providing a starting offset is similar: $var(index) = $(var(source){s.index, $var(search)}); ERROR:core:tr_parse_string: unknown transformation: index, $var(search)}/index/5! Given these are core transformations and I'm using several others in my configs I'm running under the belief I'm not missing a module. I've tried copying the doc example verbatim with identical results. What am I missing here, people? Is it just staring me straight in the face? My thanks; - Jock _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Fri Jan 27 16:10:43 2017 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Fri, 27 Jan 2017 23:10:43 +0200 Subject: [OpenSIPS-Users] Radius acc - wrong Sip-Call-Setuptime Message-ID: Hello, I try to use OpenSips 2.2 with Radius ACC. Radius server receive wrong Sip-Call-Setuptime like this Sip-Call-Setuptime = 2938 When use OpenSips 1.10 all is OK. Where is problem? Best regards, Dragomir -------------- next part -------------- An HTML attachment was scrubbed... URL: From aqsyounas at gmail.com Sat Jan 28 14:04:05 2017 From: aqsyounas at gmail.com (Aqs Younas) Date: Sat, 28 Jan 2017 19:04:05 +0000 Subject: [OpenSIPS-Users] Replace the old registration record with new registration Message-ID: Greetings list, I want to keep single AOR per registration. If new regitration comes i want to replace the old record with new. Suppose User Alice register from device A and after certain time it try to register with device B. I want just to have AOR for device B only. Any pointer is mush appreciated. Cheers, Aqs -------------- next part -------------- An HTML attachment was scrubbed... URL: From govoiper at gmail.com Sat Jan 28 14:17:08 2017 From: govoiper at gmail.com (SamyGo) Date: Sat, 28 Jan 2017 14:17:08 -0500 Subject: [OpenSIPS-Users] Replace the old registration record with new registration In-Reply-To: References: Message-ID: Hi Aqs, I think there is a mod param for usrloc or registrar which states the max number of Contacts per AoR. You can set it to 1 and hence you will only be keeping the latest Registering device. I hope thats what you needed. Thanks. Sammy On Jan 28, 2017 14:09, "Aqs Younas" wrote: Greetings list, I want to keep single AOR per registration. If new regitration comes i want to replace the old record with new. Suppose User Alice register from device A and after certain time it try to register with device B. I want just to have AOR for device B only. Any pointer is mush appreciated. Cheers, Aqs _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlos.oliva at numintec.com Sun Jan 29 17:05:33 2017 From: carlos.oliva at numintec.com (Carlos Oliva) Date: Sun, 29 Jan 2017 23:05:33 +0100 Subject: [OpenSIPS-Users] rtpengine xmlrpc integration with opensips. Teardown xmlrpc method Message-ID: Hi List! I'm using Opensips 1.11 and doing some tests to change my mediaproxy rtprelays to ngcp-rtpengine. My reasons to try this change are efficiency and that the mediaproxy project seems to be a little abandoned by AGProjects (not really abandoned but has no new features in years) After the change I started to see some dialogs in state 3 that ends at timeout (6 hours in my config) I tried to use the RTPTimeout function in rtpengine (in mediaproxy it works very well) to try to end the dialogs which don't have RTP. To try this I used the rtpengine flags --b2b-url=http://%%:8000/RPC2 --xmlrpc-format=1 to send Opensips the order to end the related dialog. It doesn't work. Doing some ngrep at xmlrpc interface seems that rtpengine send some commands to opensips RPC interface that Opensips does not understand. The command is: "teardown" and the callid, here is an example: POST /RPC2 HTTP/1.1..Host: XXX.XXX.XXX.XXX:8000..Accept: */*..Content-Type: text/xml..User-Agent: Xmlrpc-c/1.33.14 Curl/7.38.0..Content-Length: 204........teardown.... 822048991-40759-5 at BJC.BGI.B.GE .... and the opensips response: HTTP/1.1 200 OK..Connection: Keep-Alive..Content-Length: 48..Content-Type: text/xml; charset=utf-8..Date: Sun, 29 Jan 2017 20:31:36 GMT....Internal server error! Obviously OpenSips does not implement this "teardown" method. My questions are: Anybody has a good idea of how to deal with this? Devels: Do you think is a good idea to open a feature request in github about this? I'll try to backport to 1.11 later.if you accept the request. Thanks and Regards, Carlos Oliva -------------- next part -------------- An HTML attachment was scrubbed... URL: From sougol.gheissi at gmail.com Mon Jan 30 04:28:01 2017 From: sougol.gheissi at gmail.com (sougol gheissi) Date: Mon, 30 Jan 2017 12:58:01 +0330 Subject: [OpenSIPS-Users] Out of sh memory error Message-ID: Hello all, I have configured an opensips testbed, but when I want to make load tests on it, I get out of shared memory error. I have increased the shared memory by opensips -m 2500 -M 10 but I still get the error message. I also checked whether it is a leak or not. It was not. (based on this http://www.opensips.org/Documentation/TroubleShooting-OutOfMem) I also checked the opensipsctl fifo get_statistics all. here is the log file I will really appreciate the help. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: log Type: application/octet-stream Size: 2827 bytes Desc: not available URL: From husnain.taseer at gmail.com Mon Jan 30 13:20:55 2017 From: husnain.taseer at gmail.com (Husnain Taseer) Date: Mon, 30 Jan 2017 21:20:55 +0300 Subject: [OpenSIPS-Users] Replace the old registration record with new registration In-Reply-To: References: Message-ID: <25333803-C615-45B1-A596-A6B91FBAD76F@gmail.com> Hi Aqs, As SamyGO said you can set mod param “max_contacts” for registrar module to 1. It will automatically refresh the AOR on every registration and will not allow multiple entries in location table. Add the below line in your cfg. modparam("registrar", "max_contacts", 1) Regards, Husnain Taseer > On Jan 29, 2017, at 8:00 PM, users-request at lists.opensips.org wrote: > > Send Users mailing list submissions to > users at lists.opensips.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > or, via email, send a message with subject or body 'help' to > users-request at lists.opensips.org > > You can reach the person managing the list at > users-owner at lists.opensips.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Users digest..." > > > Today's Topics: > > 1. Replace the old registration record with new registration > (Aqs Younas) > 2. Re: Replace the old registration record with new registration > (SamyGo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 28 Jan 2017 19:04:05 +0000 > From: Aqs Younas > To: OpenSIPS users mailling list > Subject: [OpenSIPS-Users] Replace the old registration record with new > registration > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > Greetings list, > I want to keep single AOR per registration. If new regitration comes i want > to replace the old record with new. > Suppose User Alice register from device A and after certain time it try to > register with device B. I want just to have AOR for device B only. > Any pointer is mush appreciated. > > Cheers, > Aqs > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Message: 2 > Date: Sat, 28 Jan 2017 14:17:08 -0500 > From: SamyGo > To: OpenSIPS users mailling list > Subject: Re: [OpenSIPS-Users] Replace the old registration record with > new registration > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > Hi Aqs, > > I think there is a mod param for usrloc or registrar which states the max > number of Contacts per AoR. You can set it to 1 and hence you will only be > keeping the latest Registering device. > > I hope thats what you needed. > > Thanks. > Sammy > > > On Jan 28, 2017 14:09, "Aqs Younas" wrote: > > Greetings list, > I want to keep single AOR per registration. If new regitration comes i want > to replace the old record with new. > Suppose User Alice register from device A and after certain time it try to > register with device B. I want just to have AOR for device B only. > Any pointer is mush appreciated. > > Cheers, > Aqs > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > ------------------------------ > > End of Users Digest, Vol 102, Issue 97 > ************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From jock.mckechnie at gmail.com Mon Jan 30 14:07:23 2017 From: jock.mckechnie at gmail.com (Jock McKechnie) Date: Mon, 30 Jan 2017 13:07:23 -0600 Subject: [OpenSIPS-Users] s.index madness and my waning grip on sanity In-Reply-To: <5A5FEB40-8D2E-4BEC-9ED3-C329C84F999D@inin.com> References: <8720a4cc-75fd-a4a8-28cc-13d5b9bbcf42@opensips.org> <5A5FEB40-8D2E-4BEC-9ED3-C329C84F999D@inin.com> Message-ID: It is with staggering embarrassment that I'll admit that I figured this one out. The development OpenSIPS box I was trying to get this config to work on is running... 1.8.8 instead of 1.11 like all the production OpenSIPS we have and I assumed it was. There is no fault except my own gross stupidity. Move along, nothing to see here. - Jock crawling back under his rock (Thanks to Ben and Liviu for responding, regardless) On Fri, Jan 27, 2017 at 2:18 PM, Newlin, Ben wrote: > For the hard-coded string, my suggestion was to remove the quotes > completely. Most transformations don’t want quotes, even on string-type > input. > > > > $var(index) = $(var(source){s.index, one}); > > > > For the variable, I can’t help as I’m not using it. I can confirm it works > with a route parameter: > > > > $var(index) = $(var(source){s.index, $param(1)}); > > > > Ben Newlin > Lead Voice Network Engineer, PureCloud > T: +1 317 957 1009 > > ben.newlin at inin.com > > > > > > From: Users on behalf of Jock McKechnie > > Reply-To: OpenSIPS users mailling list > Date: Friday, January 27, 2017 at 2:11 PM > To: OpenSIPS users mailling list > > Subject: Re: [OpenSIPS-Users] s.index madness and my waning grip on sanity > > > > Thanks Ben; > > > > As you say, the s.index is in the 1.11 docs. I had a brief moment of > > panic when Liviu suggested otherwise until I checked, verified, and > > then your mail popped up confirming. > > > > I tried single quotes on both variable declarations, I tried the index > > with the var ($var(search)) and a string ('one') with the same error, > > so that doesn't appear to be it. I'd wonder if it didn't like this > > type of variable... except it's documented to work this way. > > $var(source) = 'onetwothree'; > > $var(search) = 'one' > > $var(index) = $(var(source){s.index, $var(search)}); > > $var(index) = $(var(source){s.index, 'one'}); > > > > Even though you use this differently, would you be willing to post > > your working example just so I have something else to stare at? > > > > And if anyone else has any bright ideas, I'm definitely all ears (or eyes); > > > > Thanks very much; > > > > - Jock > > > > > > On Fri, Jan 27, 2017 at 12:17 PM, Newlin, Ben wrote: > > That is not correct. OpenSIPS 1.11 definitely contains the index > > transformation [1]. I’m using it in my code! > > > > > > > > I think the problem is the quoting. For the example that uses a hard-coded > > search string it should work if you leave off the quotes. This is how I’m > > using it. > > > > > > > > For the variable example, the only thing I can see is that the example you > > copied is using single quotes, while you are using double quotes. I only use > > s.index with a $param variable, so I’m not sure what the proper quoting is > > our if it will make a difference. > > > > > > > > [1] http://www.opensips.org/Documentation/Script-Tran-1-11#toc19 > > > > > > > > Ben Newlin > > > > > > > > > > > > From: Users on behalf of Liviu Chircu > > > > Reply-To: OpenSIPS users mailling list > > Date: Friday, January 27, 2017 at 1:10 PM > > To: "users at lists.opensips.org" > > Subject: Re: [OpenSIPS-Users] s.index madness and my waning grip on sanity > > > > > > > > Hi, Jock! > > > > > > > > The answer is simple: you must be using a pre-2.2 OpenSIPS, which does > > > > not include this transformation, just like the error message says: > > > > > > > > "ERROR:core:tr_parse_string: unknown transformation: index" > > > > > > > > Future advice: before reading documentation, make sure you properly > > > > select your OpenSIPS version using the top-level switches [1] > > > > > > > > [1]: http://www.opensips.org/Documentation/Script-Tran-2-1 > > > > > > > > Regards, > > > > > > > > Liviu Chircu > > > > OpenSIPS Developer > > > > http://www.opensips-solutions.com > > > > > > > > On 27.01.2017 19:26, Jock McKechnie wrote: > > > > Good morning all; > > > > > > > > I'm having a battle with s.index that I'd really like to believe no > > > > one should be waging, and I've come to the conclusion either 1.11 is > > > > seriously broken, or I'm utterly deranged, but at the risk of > > > > verifying the second, I wanted to reach out and figure out what I'm > > > > doing wrong here. > > > > > > > > I seem utterly incapable of getting s.index working at all, consider > > > > the following: > > > > > > > > $var(source) = "onetwothree"; > > > > $var(search) = "one"; > > > > $var(index) = $(var(source){s.index, $var(search), 0}); > > > > > > > > Which should look famaliar as it's based entirely on the example in > > > > the 1.11 documentation. This produces the following: > > > > ERROR:core:tr_parse_string: unknown transformation: index, > > > > $var(search), 0}/index/5! ERROR:core:parse_transformation: error > > > > parsing [{s.index, $var(search), 0}] ERROR:core:pv_parse_spec: > > > > ERROR:bad tr in pvar name "var" ERROR:core:pv_parse_spec: invalid > > > > parsing in [$(var(source){s.index, $var(search), 0})] at (4) > > > > CRITICAL:core:yyerror: parse error in config file > > > > /etc/opensips/opensips.cfg, line 92, column 166-206: unknown script > > > > variable > > > > > > > > Using a static search string: > > > > $var(index) = $(var(source){s.index, "one", 0}); > > > > > > > > Garners me the same with: > > > > ERROR:core:tr_parse_string: unknown transformation: index, "one", > > 0}/index/5! > > > > > > > > And not providing a starting offset is similar: > > > > $var(index) = $(var(source){s.index, $var(search)}); > > > > > > > > ERROR:core:tr_parse_string: unknown transformation: index, > > > > $var(search)}/index/5! > > > > > > > > Given these are core transformations and I'm using several others in > > > > my configs I'm running under the belief I'm not missing a module. I've > > > > tried copying the doc example verbatim with identical results. What am > > > > I missing here, people? Is it just staring me straight in the face? > > > > > > > > My thanks; > > > > - Jock > > > > > > > > _______________________________________________ > > > > Users mailing list > > > > Users at lists.opensips.org > > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > > > > > > _______________________________________________ > > > > Users mailing list > > > > Users at lists.opensips.org > > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > From rosenberg11219 at gmail.com Tue Jan 31 06:54:53 2017 From: rosenberg11219 at gmail.com (Schneur Rosenberg) Date: Tue, 31 Jan 2017 13:54:53 +0200 Subject: [OpenSIPS-Users] ACK for invite with wrong Cseq Message-ID: Hi, I'm using OpenSIPS 2.2.2 and I'm using create_dialog with the "Pp" options, most calls run fine, but I have got complaints about calls getting disconnected after about 30 seconds, I ran a trace and I realized that OpenSIPS sent a INVITE with CSeq 601, the called party picked up after approx 34 seconds and sent a OK with CSeq 601 which the gateway (Freeswitch in this instance) forwarded to OpenSIPS, but before OpenSIPS responded with a ACK it sent a ping Options to the gateway with CSeq 602 and the gateway replied with a OK, and then OpenSIPS sent the ACK for the INVITE but used the CSeq of the Options 602 and not from the INVITE,601, therefore the gateway kept on sending OK's with CSeq 601 which OpenSIPS responded every time with the ACK but again with the CSeq 602. then after approx 30 seconds the gateway sent a bye with Reason: SIP;cause=408;text="ACK Timeout" From aqsyounas at gmail.com Tue Jan 31 07:45:39 2017 From: aqsyounas at gmail.com (Aqs Younas) Date: Tue, 31 Jan 2017 17:45:39 +0500 Subject: [OpenSIPS-Users] Replace the old registration record with new registration In-Reply-To: <25333803-C615-45B1-A596-A6B91FBAD76F@gmail.com> References: <25333803-C615-45B1-A596-A6B91FBAD76F@gmail.com> Message-ID: Thank you, guys. There is another flag "f" force registration to set for save function to replace the old registrations without exceeding the maximum number of contacts per AOR. Else you would be getting 503 in reply. On 30 January 2017 at 23:20, Husnain Taseer wrote: > Hi Aqs, > As SamyGO said you can set mod param “max_contacts” for registrar module > to 1. It will automatically refresh the AOR on every registration and will > not allow multiple entries in location table. Add the below line in your > cfg. > > modparam("registrar", "max_contacts", 1) > > Regards, > Husnain Taseer > > > > On Jan 29, 2017, at 8:00 PM, users-request at lists.opensips.org wrote: > > Send Users mailing list submissions to > users at lists.opensips.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > or, via email, send a message with subject or body 'help' to > users-request at lists.opensips.org > > You can reach the person managing the list at > users-owner at lists.opensips.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Users digest..." > > > Today's Topics: > > 1. Replace the old registration record with new registration > (Aqs Younas) > 2. Re: Replace the old registration record with new registration > (SamyGo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 28 Jan 2017 19:04:05 +0000 > From: Aqs Younas > To: OpenSIPS users mailling list > Subject: [OpenSIPS-Users] Replace the old registration record with new > registration > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > Greetings list, > I want to keep single AOR per registration. If new regitration comes i want > to replace the old record with new. > Suppose User Alice register from device A and after certain time it try to > register with device B. I want just to have AOR for device B only. > Any pointer is mush appreciated. > > Cheers, > Aqs > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: 20170128/9e167b4d/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Sat, 28 Jan 2017 14:17:08 -0500 > From: SamyGo > To: OpenSIPS users mailling list > Subject: Re: [OpenSIPS-Users] Replace the old registration record with > new registration > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > > Hi Aqs, > > I think there is a mod param for usrloc or registrar which states the max > number of Contacts per AoR. You can set it to 1 and hence you will only be > keeping the latest Registering device. > > I hope thats what you needed. > > Thanks. > Sammy > > > On Jan 28, 2017 14:09, "Aqs Younas" wrote: > > Greetings list, > I want to keep single AOR per registration. If new regitration comes i want > to replace the old record with new. > Suppose User Alice register from device A and after certain time it try to > register with device B. I want just to have AOR for device B only. > Any pointer is mush appreciated. > > Cheers, > Aqs > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: 20170128/f3df658c/attachment-0001.html> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > ------------------------------ > > End of Users Digest, Vol 102, Issue 97 > ************************************** > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Agalya_Ramachandran at comcast.com Tue Jan 31 11:54:22 2017 From: Agalya_Ramachandran at comcast.com (Ramachandran, Agalya (Contractor)) Date: Tue, 31 Jan 2017 16:54:22 +0000 Subject: [OpenSIPS-Users] FW: OpenSIPs 2.2.2 warnings during start service References: <92c380d81d5c45a9a2bce09fe344188e@COPDCEX28.cable.comcast.com> <2d785128-affa-c955-e779-1d4305ec1119@opensips.org> <21840442533f445397309d17eec6bcbe@COPDCEX28.cable.comcast.com> <02f2179c-d838-cd83-d8ef-b0a67870c339@opensips.org> <9066a330ccf04484964a0c9e70ad7e2a@COPDCEX28.cable.comcast.com> <905e5006-a86e-9588-9f3f-4db33f9d864d@opensips.org> <8a6a2556-c10b-b97f-1dfa-de3d71c31a55@opensips.org> Message-ID: Hi Bogdan, Any clue that I can stop these warnings? Regards, Agalya From: Ramachandran, Agalya (Contractor) Sent: Wednesday, January 25, 2017 9:31 AM To: 'Bogdan-Andrei Iancu' ; OpenSIPS users mailling list Subject: RE: FW: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service Hi Bogdan, Yes, am having tar ball of the 2.2 source code released in Oct 2016. On top of it, I have added the fix in timer.c . That’s all I have. https://github.com/OpenSIPS/opensips/commit/68d4240698e639490ab7dfa187b1458f00146fb3 I am running OpenSIPS in VM. Regards, Agaya From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Wednesday, January 25, 2017 4:23 AM To: Ramachandran, Agalya (Contractor) >; OpenSIPS users mailling list > Subject: Re: FW: [OpenSIPS-Users] OpenSIPs 2.2.2 warnings during start service Hi Agalya, That is really weird - I suppose you are using the latest 2.2, right ? Are you using a VM or container to run OpenSIPS ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 01/24/2017 06:42 PM, Ramachandran, Agalya (Contractor) wrote: -------------- next part -------------- An HTML attachment was scrubbed... URL: From ravitez.dondeti at gmail.com Fri Jan 27 15:14:11 2017 From: ravitez.dondeti at gmail.com (Ravitez Ravi) Date: Fri, 27 Jan 2017 15:14:11 -0500 Subject: [OpenSIPS-Users] Opensips(1.11.5) Crash - " #0 0x00007fcd7223ae2c in vfprintf () from /lib64/libc.so.6" Message-ID: Hi All, Good Day, OpenSips(1.11.5) is constantly crashing at " vfprintf ()" Logs are filled up with the following error message 2017-01-24T18:14:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:io_watch_del: trying to delete already erased entry 46 in the hash(0, 0, (nil)) ) 2017-01-24T18:14:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:tcp_read_req: bad request, state=0, error=2 buf: We see the following in tcp_connection list : Connection:: ID=4029 Type=*tcp* *State=18446744073709551615* Source=172.29.106.95:5060 Destination= 172.29.106.10:5060 Timeout=2017-01-25 19:35:35 Pending lifetime=0 not sure if its a valid state. Here's the debug log : [20758]: DBG:core:tcp_read_req: - received from: port 5060 [20758]: DBG:core:print_ip: - received from: ip *172.29.106.95* [20758]: DBG:core:io_watch_del: io_watch_del op on index -1 52 (0x8100e0, 52, -1, 0x10,0x3) fd_no=2 called [20758]: ERROR:core:io_watch_del: trying to delete already erased entry 52 in the hash(0, 0, (nil)) ) [20758]: DBG:core:release_tcpconn: releasing con 0x7f543179d700, state -2, fd=52, id=4029 [20758]: DBG:core:release_tcpconn: extra_data (nil) [20758]: DBG:core:tcp_read_req: Using the global ( per process ) buff [20758]: ERROR:core:tcp_read_req: bad request, state=0, error=2 buf Please find the attached Stack Trace and logs generated. Not sure if this is already address in a different version of OpenSips or a know issue,please share your thoughts. Thank you for your time. Attached Log File Contains Following Sections : Line 1: ###### Core 1 Time : 2017-01-24T18:04 ###### Line 174: ###### Log Information ###### Line 175: ###### Before Crash ###### Line 188: 2017-01-24T18:04:29.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[31607]: ERROR:core:tls_shutdown: something wrong in SSL: #### Crash ############ Line 190: ###### After Crash ###### Line 215: ###### Continuous Errors ###### Line 235: ###### Second Crash ###### Line 249: ###### Core 2 Time : 2017-01-25T09:08 ###### Line 421: ##### Core 3 Time : 2017-01-25T09:08 ##### Line 619: ##### Core 4 Time : 2017-01-25T09:08 ##### Line 820: ##### Core 5 Time : 2017-01-25T19:35 ##### Line 1011: ##### Additional Logs ##### --> This section contains TCP Connection list and Debug information from Opensips Regards, Ravitez.D -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- ###### Core 1 Time : 2017-01-24T18:04 ###### gdb /usr/sbin/opensips core.31643 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: ... Reading symbols from /usr/sbin/opensips...done. warning: core file may not match specified executable file. [New Thread 31643] Missing separate debuginfo for /usr/lib64/opensips/modules/signaling.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/a5/6fe5f3fb5f5a5945cd0fd8384403a1610ac723 Missing separate debuginfo for /usr/lib64/opensips/modules/sl.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/a0/3aa3c43c41ef6b5a3443edee6b57557f99e95f Missing separate debuginfo for /usr/lib64/opensips/modules/tm.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/86/ec031a2c632fc2c1c2ebc807d134588c879e8f Missing separate debuginfo for /usr/lib64/opensips/modules/rr.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/f9/5a55b1e8ec652178bbf56f1de12a130f2d3fc2 Missing separate debuginfo for /usr/lib64/opensips/modules/maxfwd.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/3c/bcedbe5e2cb56ce0232c168ce10d01549154e9 Missing separate debuginfo for /usr/lib64/opensips/modules/sipmsgops.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/68/3d8e3c5d0e47bb4e69df2e47f62b8a6c2b02e1 Missing separate debuginfo for /usr/lib64/opensips/modules/mi_fifo.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/25/0c6e832f8702623763334c66d80701abd2f757 Missing separate debuginfo for /usr/lib64/opensips/modules/uri.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/6c/8c7108c432cb039e548473b9c190265cb21c3c Missing separate debuginfo for /usr/lib64/opensips/modules/usrloc.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/7a/3f6b2b6c1c5e4d9143db3610667472c5b1f1fb Missing separate debuginfo for /usr/lib64/opensips/modules/nathelper.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/fe/eb381245a35d7cc8504f30496cbce200bc2a32 Missing separate debuginfo for /usr/lib64/opensips/modules/registrar.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/e1/e152c5eb09765db719d2de687674d4b38bec29 Missing separate debuginfo for /usr/lib64/opensips/modules/acc.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/0d/53590fb94de20cbeb1aee103e38332cdb6783c Missing separate debuginfo for Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/7f/719af91ee951b4fcb6647e7868f95f766a616b Reading symbols from /lib64/snoopy.so...done. Loaded symbols for /lib64/snoopy.so Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libresolv.so.2 Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl.so.10 Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcrypto.so.10 Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libgssapi_krb5.so.2 Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5.so.3 Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libcom_err.so.2 Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libk5crypto.so.3 Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libz.so.1 Reading symbols from /lib64/libkrb5support.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5support.so.0 Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libkeyutils.so.1 Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libselinux.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libselinux.so.1 Reading symbols from /usr/lib64/opensips/modules/signaling.so...done. Loaded symbols for /usr/lib64/opensips/modules/signaling.so Reading symbols from /usr/lib64/opensips/modules/sl.so...done. Loaded symbols for /usr/lib64/opensips/modules/sl.so Reading symbols from /usr/lib64/opensips/modules/tm.so...done. Loaded symbols for /usr/lib64/opensips/modules/tm.so Reading symbols from /usr/lib64/opensips/modules/rr.so...done. Loaded symbols for /usr/lib64/opensips/modules/rr.so Reading symbols from /usr/lib64/opensips/modules/maxfwd.so...done. Loaded symbols for /usr/lib64/opensips/modules/maxfwd.so Reading symbols from /usr/lib64/opensips/modules/sipmsgops.so...done. Loaded symbols for /usr/lib64/opensips/modules/sipmsgops.so Reading symbols from /usr/lib64/opensips/modules/mi_fifo.so...done. Loaded symbols for /usr/lib64/opensips/modules/mi_fifo.so Reading symbols from /usr/lib64/opensips/modules/uri.so...done. Loaded symbols for /usr/lib64/opensips/modules/uri.so Reading symbols from /usr/lib64/opensips/modules/usrloc.so...done. Loaded symbols for /usr/lib64/opensips/modules/usrloc.so Reading symbols from /usr/lib64/opensips/modules/nathelper.so...done. Loaded symbols for /usr/lib64/opensips/modules/nathelper.so Reading symbols from /usr/lib64/opensips/modules/registrar.so...done. Loaded symbols for /usr/lib64/opensips/modules/registrar.so Reading symbols from /usr/lib64/opensips/modules/acc.so...done. Loaded symbols for /usr/lib64/opensips/modules/acc.so Reading symbols from /lib64/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libnss_files.so.2 Core was generated by `/usr/sbin/opensips -u root -g root -P /var/run/opensips.pid -f'. Program terminated with signal 11, Segmentation fault. #0 0x00007fcd7223ae2c in vfprintf () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.166.el6_7.7.x86_64 keyutils-libs-1.4-4.el6.x86_64 krb5-libs-1.10.3-42z1.el6_7.x86_64 libcom_err-1.41.12-18.el6.x86_64 libselinux-2.0.94-5.3.el6_4.1.x86_64 openssl-1.0.1e-48.el6_8.1.x86_64 zlib-1.2.3-29.el6.x86_64 (gdb) bt full #0 0x00007fcd7223ae2c in vfprintf () from /lib64/libc.so.6 No symbol table info available. #1 0x00007fcd722d7ea0 in __vsyslog_chk () from /lib64/libc.so.6 No symbol table info available. #2 0x00007fcd722d80d0 in syslog () from /lib64/libc.so.6 No symbol table info available. #3 0x00000000004d1ab8 in tcp_read_req (con=0x7fcd4e9e9ec8, bytes_read=0x7ffe3a05943c) at tcp_read.c:597 bytes = total_bytes = resp = 0 size = req = 0x7fcd6fefeef0 c = local_rcv = {src_ip = {af = 973443984, len = 32766, u = {addrl = {1, 140729871864688}, addr32 = {1, 0, 973443952, 32766}, addr16 = {1, 0, 0, 0, 37744, 14853, 32766, 0}, addr = "\001\000\000\000\000\000\000\000p\223\005:\376\177\000"}}, dst_ip = {af = 24, len = 0, u = {addrl = {0, 0}, addr32 = {0, 0, 0, 0}, addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, addr = '\000' }}, src_port = 20, dst_port = 0, proto = 0, proto_reserved1 = 1, proto_reserved2 = 1, src_su = {s = {sa_family = 45, sa_data = "\000\000\254\035j_\000\000\000\000\000\000\000"}, sin = {sin_family = 45, sin_port = 0, sin_addr = { s_addr = 1600789932}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 45, sin6_port = 0, sin6_flowinfo = 1600789932, sin6_addr = {__in6_u = { __u6_addr8 = "\000\000\000\000\000\000\000\000\001\000\000\000X\376\344o", __u6_addr16 = {0, 0, 0, 0, 1, 0, 65112, 28644}, __u6_addr32 = {0, 0, 1, 1877278296}}}, sin6_scope_id = 32717}}, bind_address = 0x7fcd6fe39398} msg_buf = msg_len = __FUNCTION__ = "tcp_read_req" #4 0x00000000004d31e8 in handle_io (fm=, idx=-1, event_type=) at tcp_read.c:1033 ret = 0 n = con = 0x7fcd4e9e9ec8 s = rw = resp = response = {140519764041416, 1} __FUNCTION__ = "handle_io" #5 0x00000000004d5985 in io_wait_loop_epoll (unix_sock=) at io_wait.h:845 n = 1 r = #6 tcp_receive_loop (unix_sock=) at tcp_read.c:1141 __FUNCTION__ = "tcp_receive_loop" #7 0x00000000004bb82c in tcp_init_children (chd_rank=, startup_done=0x0) at tcp_main.c:2390 r = reader_fd = {43, 44} pid = si = load_p = 0x7fcd4e565bb0 __FUNCTION__ = "tcp_init_children" #8 0x000000000043d6b8 in main_loop (argc=, argv=) at main.c:1011 i = pid = si = 0x0 startup_done = 0x0 chd_rank = 33 rc = load_p = 0x7fcd4e572ed0 #9 main (argc=, argv=) at main.c:1612 cfg_log_stderr = cfg_stream = c = r = tmp = 0x7ffe3a05af40 "172.29.106.10" tmp_len = port = proto = options = 0x595880 "f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:" ret = -1 seed = 2270273504 rfd = __FUNCTION__ = "main" (gdb) ###### Log Information ###### ###### Before Crash ###### 2017-01-24T17:45:32.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[31644]: ERROR:core:tcpconn_async_connect: Internal error encountered when connecting 2017-01-24T17:45:32.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[31644]: ERROR:core:tcp_send: async TCP connect failed 2017-01-24T17:45:32.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[31644]: ERROR:core:msg_send: tcp_send failed 2017-01-24T17:45:32.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[31644]: ERROR:core:async_connect_or_pass: poll error: flags 1c 2017-01-24T17:45:32.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[31644]: ERROR:core:async_connect_or_pass: failed to retrieve SO_ERROR [server=172.29.106.10:56606] (111) Connection refused 2017-01-24T17:45:32.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[31644]: ERROR:core:tcpconn_async_connect: Internal error encountered when connecting 2017-01-24T17:45:32.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[31644]: ERROR:core:tcp_send: async TCP connect failed 2017-01-24T17:45:32.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[31644]: ERROR:core:msg_send: tcp_send failed 2017-01-24T18:04:29.000-05:00 [local2] [crit] E01Z01.dev.com /usr/sbin/opensips[31675]: CRITICAL:core:receive_fd: EOF on 45 2017-01-24T18:04:29.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[31607]: ERROR:core:tls_shutdown: something wrong in SSL: 2017-01-24T18:04:29.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[31607]: ERROR:core:tls_shutdown: something wrong in SSL: 2017-01-24T18:04:29.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[31607]: ERROR:core:tls_shutdown: something wrong in SSL: 2017-01-24T18:04:29.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[31607]: ERROR:core:tls_shutdown: something wrong in SSL: #### Crash ############ ###### After Crash ###### 2017-01-24T18:04:30.000-05:00 [local2] [warning] E01Z01.dev.com opensips[4415]: WARNING:core:init_tls: disabling compression due ZLIB problems 2017-01-24T18:04:30.000-05:00 [local2] [notice] E01Z01.dev.com opensips[4415]: NOTICE:core:init_ssl_ctx_behavior: No EC curve defined 2017-01-24T18:04:30.000-05:00 [local2] [notice] E01Z01.dev.com opensips[4415]: NOTICE:core:init_ssl_ctx_behavior: cipher list set to ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:AES128-GCM-SHA256:ECDHE-RSA-AES128-SHA256:AES128-SHA256:EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:!ECDHE-RSA-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES256-SHA256:AES256-SHA:AES128-SHA:!DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4 2017-01-24T18:04:30.000-05:00 [local2] [warning] E01Z01.dev.com opensips[4415]: WARNING:core:init_ssl_ctx_behavior: client verification NOT activated. Weaker security. 2017-01-24T18:04:30.000-05:00 [local2] [notice] E01Z01.dev.com opensips[4415]: NOTICE:core:init_tls_domains: no CA for tls[0.0.0.0:0] defined, using default '/etc/pki/CA/' 2017-01-24T18:04:30.000-05:00 [local2] [notice] E01Z01.dev.com opensips[4415]: NOTICE:core:init_ssl_ctx_behavior: No EC curve defined 2017-01-24T18:04:30.000-05:00 [local2] [notice] E01Z01.dev.com opensips[4415]: NOTICE:core:init_ssl_ctx_behavior: cipher list set to ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:AES128-GCM-SHA256:ECDHE-RSA-AES128-SHA256:AES128-SHA256:EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:!ECDHE-RSA-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES256-SHA256:AES256-SHA:AES128-SHA:!DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4 2017-01-24T18:04:30.000-05:00 [local2] [warning] E01Z01.dev.com opensips[4415]: WARNING:core:init_ssl_ctx_behavior: server verification activated. 2017-01-24T18:04:30.000-05:00 [local2] [notice] E01Z01.dev.com opensips[4415]: NOTICE:core:init_tls_domains: no CA for tls[0.0.0.0:0] defined, using default '/etc/pki/CA/' 2017-01-24T18:04:30.000-05:00 [local2] [notice] E01Z01.dev.com /usr/sbin/opensips[4432]: NOTICE:core:main: version: opensips 1.11.5-tls (x86_64/linux) 2017-01-24T18:04:30.000-05:00 [local2] [notice] E01Z01.dev.com /usr/sbin/opensips[4432]: NOTICE:signaling:mod_init: initializing module ... 2017-01-24T18:04:32.000-05:00 [local2] [notice] E01Z01.dev.com /usr/sbin/opensips[4445]: NOTICE:core:verify_callback: depth = 1 2017-01-24T18:04:32.000-05:00 [local2] [notice] E01Z01.dev.com /usr/sbin/opensips[4445]: NOTICE:core:verify_callback: preverify is good: verify return: 1 2017-01-24T18:04:32.000-05:00 [local2] [notice] E01Z01.dev.com /usr/sbin/opensips[4445]: NOTICE:core:verify_callback: depth = 0 2017-01-24T18:04:32.000-05:00 [local2] [notice] E01Z01.dev.com /usr/sbin/opensips[4445]: NOTICE:core:verify_callback: preverify is good: verify return: 1 2017-01-24T18:05:16.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:add_write_chunk: We have reached the limit of max async postponed chunks 2017-01-24T18:05:16.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:async_tsend_stream: Failed to add write chunk to connection 2017-01-24T18:05:16.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:tcp_send: failed to send 2017-01-24T18:05:16.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:msg_send: tcp_send failed 2017-01-24T18:05:54.000-05:00 [local2] [notice] E01Z01.dev.com /usr/sbin/opensips[4465]: NOTICE:core:verify_callback: depth = 1 2017-01-24T18:05:54.000-05:00 [local2] [notice] E01Z01.dev.com /usr/sbin/opensips[4465]: NOTICE:core:verify_callback: preverify is good: verify return: 1 2017-01-24T18:05:54.000-05:00 [local2] [notice] E01Z01.dev.com /usr/sbin/opensips[4465]: NOTICE:core:verify_callback: depth = 0 2017-01-24T18:05:54.000-05:00 [local2] [notice] E01Z01.dev.com /usr/sbin/opensips[4465]: NOTICE:core:verify_callback: preverify is good: verify return: 1 ###### Continuous Errors ###### 2017-01-24T18:14:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:io_watch_del: trying to delete already erased entry 46 in the hash(0, 0, (nil)) ) 2017-01-24T18:14:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:tcp_read_req: bad request, state=0, error=2 buf: parsed: 2017-01-24T18:14:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:io_watch_del: trying to delete already erased entry 46 in the hash(0, 0, (nil)) ) 2017-01-24T18:14:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:tcp_read_req: bad request, state=0, error=2 buf: parsed: 2017-01-24T18:14:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:io_watch_del: trying to delete already erased entry 46 in the hash(0, 0, (nil)) ) 2017-01-24T18:14:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:tcp_read_req: bad request, state=0, error=2 buf: parsed: 2017-01-24T23:52:03.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:io_watch_del: trying to delete already erased entry 46 in the hash(0, 0, (nil)) ) 2017-01-24T23:52:03.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:tcp_read_req: bad request, state=0, error=2 buf: parsed: 2017-01-24T23:52:03.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:io_watch_del: trying to delete already erased entry 46 in the hash(0, 0, (nil)) ) 2017-01-24T23:52:03.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:tcp_read_req: bad request, state=0, error=2 buf: ###### Second Crash ###### parsed: 2017-01-25T09:06:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:io_watch_del: trying to delete already erased entry 46 in the hash(0, 0, (nil)) ) 2017-01-25T09:06:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:tcp_read_req: bad request, state=0, error=2 buf: parsed: 2017-01-25T09:06:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:io_watch_del: trying to delete already erased entry 46 in the hash(0, 0, (nil)) ) 2017-01-25T09:06:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4473]: ERROR:core:tcp_read_req: bad request, state=0, error=2 buf: parsed: 2017-01-25T09:08:28.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4432]: ERROR:core:tls_shutdown: something wrong in SSL: 2017-01-25T09:08:30.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4432]: ERROR:core:tls_shutdown: something wrong in SSL: 2017-01-25T09:08:30.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[4432]: ERROR:core:tls_shutdown: something wrong in SSL: ###### Core 2 Time : 2017-01-25T09:08 ###### gdb /usr/sbin/opensips core.4475 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: ... Reading symbols from /usr/sbin/opensips...done. warning: core file may not match specified executable file. [New Thread 4475] Missing separate debuginfo for /usr/lib64/opensips/modules/signaling.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/a5/6fe5f3fb5f5a5945cd0fd8384403a1610ac723 Missing separate debuginfo for /usr/lib64/opensips/modules/sl.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/a0/3aa3c43c41ef6b5a3443edee6b57557f99e95f Missing separate debuginfo for /usr/lib64/opensips/modules/tm.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/86/ec031a2c632fc2c1c2ebc807d134588c879e8f Missing separate debuginfo for /usr/lib64/opensips/modules/rr.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/f9/5a55b1e8ec652178bbf56f1de12a130f2d3fc2 Missing separate debuginfo for /usr/lib64/opensips/modules/maxfwd.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/3c/bcedbe5e2cb56ce0232c168ce10d01549154e9 Missing separate debuginfo for /usr/lib64/opensips/modules/sipmsgops.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/68/3d8e3c5d0e47bb4e69df2e47f62b8a6c2b02e1 Missing separate debuginfo for /usr/lib64/opensips/modules/mi_fifo.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/25/0c6e832f8702623763334c66d80701abd2f757 Missing separate debuginfo for /usr/lib64/opensips/modules/uri.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/6c/8c7108c432cb039e548473b9c190265cb21c3c Missing separate debuginfo for /usr/lib64/opensips/modules/usrloc.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/7a/3f6b2b6c1c5e4d9143db3610667472c5b1f1fb Missing separate debuginfo for /usr/lib64/opensips/modules/nathelper.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/fe/eb381245a35d7cc8504f30496cbce200bc2a32 Missing separate debuginfo for /usr/lib64/opensips/modules/registrar.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/e1/e152c5eb09765db719d2de687674d4b38bec29 Missing separate debuginfo for /usr/lib64/opensips/modules/acc.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/0d/53590fb94de20cbeb1aee103e38332cdb6783c Missing separate debuginfo for Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/7f/719af91ee951b4fcb6647e7868f95f766a616b Reading symbols from /lib64/snoopy.so...done. Loaded symbols for /lib64/snoopy.so Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libresolv.so.2 Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl.so.10 Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcrypto.so.10 Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libgssapi_krb5.so.2 Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5.so.3 Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libcom_err.so.2 Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libk5crypto.so.3 Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libz.so.1 Reading symbols from /lib64/libkrb5support.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5support.so.0 Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libkeyutils.so.1 Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libselinux.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libselinux.so.1 Reading symbols from /usr/lib64/opensips/modules/signaling.so...done. Loaded symbols for /usr/lib64/opensips/modules/signaling.so Reading symbols from /usr/lib64/opensips/modules/sl.so...done. Loaded symbols for /usr/lib64/opensips/modules/sl.so Reading symbols from /usr/lib64/opensips/modules/tm.so...done. Loaded symbols for /usr/lib64/opensips/modules/tm.so Reading symbols from /usr/lib64/opensips/modules/rr.so...done. Loaded symbols for /usr/lib64/opensips/modules/rr.so Reading symbols from /usr/lib64/opensips/modules/maxfwd.so...done. Loaded symbols for /usr/lib64/opensips/modules/maxfwd.so Reading symbols from /usr/lib64/opensips/modules/sipmsgops.so...done. Loaded symbols for /usr/lib64/opensips/modules/sipmsgops.so Reading symbols from /usr/lib64/opensips/modules/mi_fifo.so...done. Loaded symbols for /usr/lib64/opensips/modules/mi_fifo.so Reading symbols from /usr/lib64/opensips/modules/uri.so...done. Loaded symbols for /usr/lib64/opensips/modules/uri.so Reading symbols from /usr/lib64/opensips/modules/usrloc.so...done. Loaded symbols for /usr/lib64/opensips/modules/usrloc.so Reading symbols from /usr/lib64/opensips/modules/nathelper.so...done. Loaded symbols for /usr/lib64/opensips/modules/nathelper.so Reading symbols from /usr/lib64/opensips/modules/registrar.so...done. Loaded symbols for /usr/lib64/opensips/modules/registrar.so Reading symbols from /usr/lib64/opensips/modules/acc.so...done. Loaded symbols for /usr/lib64/opensips/modules/acc.so Reading symbols from /lib64/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libnss_files.so.2 Core was generated by `/usr/sbin/opensips -u root -g root -P /var/run/opensips.pid -f'. Program terminated with signal 11, Segmentation fault. #0 0x00007f555a002e2c in vfprintf () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.166.el6_7.7.x86_64 keyutils-libs-1.4-4.el6.x86_64 krb5-libs-1.10.3-42z1.el6_7.x86_64 libcom_err-1.41.12-18.el6.x86_64 libselinux-2.0.94-5.3.el6_4.1.x86_64 openssl-1.0.1e-48.el6_8.1.x86_64 zlib-1.2.3-29.el6.x86_64 (gdb) bt full #0 0x00007f555a002e2c in vfprintf () from /lib64/libc.so.6 No symbol table info available. #1 0x00007f555a09fea0 in __vsyslog_chk () from /lib64/libc.so.6 No symbol table info available. #2 0x00007f555a0a00d0 in syslog () from /lib64/libc.so.6 No symbol table info available. #3 0x00000000004d1ab8 in tcp_read_req (con=0x7f55363848a8, bytes_read=0x7ffc1ba7eedc) at tcp_read.c:597 bytes = total_bytes = resp = 0 size = req = 0x7f5557cb9278 c = local_rcv = {src_ip = {af = 463990320, len = 32764, u = {addrl = {1, 140720772476432}, addr32 = {1, 0, 463990288, 32764}, addr16 = {1, 0, 0, 0, 60944, 7079, 32764, 0}, addr = "\001\000\000\000\000\000\000\000\020\356\247\033\374\177\000"}}, dst_ip = {af = 24, len = 0, u = {addrl = {0, 0}, addr32 = {0, 0, 0, 0}, addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, addr = '\000' }}, src_port = 20, dst_port = 0, proto = 0, proto_reserved1 = 1, proto_reserved2 = 1, src_su = {s = {sa_family = 52, sa_data = "\000\000\254\035j_\000\000\000\000\000\000\000"}, sin = {sin_family = 52, sin_port = 0, sin_addr = { s_addr = 1600789932}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 52, sin6_port = 0, sin6_flowinfo = 1600789932, sin6_addr = {__in6_u = { __u6_addr8 = "\000\000\000\000\000\000\000\000\001\000\000\000\000\177\301W", __u6_addr16 = {0, 0, 0, 0, 1, 0, 32512, 22465}, __u6_addr32 = {0, 0, 1, 1472298752}}}, sin6_scope_id = 32597}}, bind_address = 0x7f5557c01398} msg_buf = msg_len = __FUNCTION__ = "tcp_read_req" #4 0x00000000004d31e8 in handle_io (fm=, idx=-1, event_type=) at tcp_read.c:1033 ret = 0 n = con = 0x7f55363848a8 s = rw = resp = response = {140003958605992, 1} __FUNCTION__ = "handle_io" #5 0x00000000004d5985 in io_wait_loop_epoll (unix_sock=) at io_wait.h:845 n = 1 r = #6 tcp_receive_loop (unix_sock=) at tcp_read.c:1141 __FUNCTION__ = "tcp_receive_loop" #7 0x00000000004bb82c in tcp_init_children (chd_rank=, startup_done=0x0) at tcp_main.c:2390 r = reader_fd = {49, 51} pid = si = load_p = 0x7f553632dbb0 __FUNCTION__ = "tcp_init_children" #8 0x000000000043d6b8 in main_loop (argc=, argv=) at main.c:1011 i = pid = si = 0x0 startup_done = 0x0 chd_rank = 36 rc = load_p = 0x7f553633aed0 #9 main (argc=, argv=) at main.c:1612 cfg_log_stderr = cfg_stream = c = r = tmp = 0x7ffc1ba80f40 "172.29.106.10" tmp_len = port = proto = options = 0x595880 "f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:" ret = -1 seed = 3019838257 rfd = __FUNCTION__ = "main" (gdb) ##### Core 3 Time : 2017-01-25T09:08 ##### gdb /usr/sbin/opensips core.4474 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: ... Reading symbols from /usr/sbin/opensips...done. warning: core file may not match specified executable file. [New Thread 4474] Missing separate debuginfo for /usr/lib64/opensips/modules/signaling.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/a5/6fe5f3fb5f5a5945cd0fd8384403a1610ac723 Missing separate debuginfo for /usr/lib64/opensips/modules/sl.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/a0/3aa3c43c41ef6b5a3443edee6b57557f99e95f Missing separate debuginfo for /usr/lib64/opensips/modules/tm.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/86/ec031a2c632fc2c1c2ebc807d134588c879e8f Missing separate debuginfo for /usr/lib64/opensips/modules/rr.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/f9/5a55b1e8ec652178bbf56f1de12a130f2d3fc2 Missing separate debuginfo for /usr/lib64/opensips/modules/maxfwd.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/3c/bcedbe5e2cb56ce0232c168ce10d01549154e9 Missing separate debuginfo for /usr/lib64/opensips/modules/sipmsgops.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/68/3d8e3c5d0e47bb4e69df2e47f62b8a6c2b02e1 Missing separate debuginfo for /usr/lib64/opensips/modules/mi_fifo.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/25/0c6e832f8702623763334c66d80701abd2f757 Missing separate debuginfo for /usr/lib64/opensips/modules/uri.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/6c/8c7108c432cb039e548473b9c190265cb21c3c Missing separate debuginfo for /usr/lib64/opensips/modules/usrloc.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/7a/3f6b2b6c1c5e4d9143db3610667472c5b1f1fb Missing separate debuginfo for /usr/lib64/opensips/modules/nathelper.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/fe/eb381245a35d7cc8504f30496cbce200bc2a32 Missing separate debuginfo for /usr/lib64/opensips/modules/registrar.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/e1/e152c5eb09765db719d2de687674d4b38bec29 Missing separate debuginfo for /usr/lib64/opensips/modules/acc.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/0d/53590fb94de20cbeb1aee103e38332cdb6783c Missing separate debuginfo for Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/7f/719af91ee951b4fcb6647e7868f95f766a616b Reading symbols from /lib64/snoopy.so...done. Loaded symbols for /lib64/snoopy.so Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libresolv.so.2 Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl.so.10 Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcrypto.so.10 Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libgssapi_krb5.so.2 Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5.so.3 Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libcom_err.so.2 Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libk5crypto.so.3 Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libz.so.1 Reading symbols from /lib64/libkrb5support.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5support.so.0 Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libkeyutils.so.1 Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libselinux.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libselinux.so.1 Reading symbols from /usr/lib64/opensips/modules/signaling.so...done. Loaded symbols for /usr/lib64/opensips/modules/signaling.so Reading symbols from /usr/lib64/opensips/modules/sl.so...done. Loaded symbols for /usr/lib64/opensips/modules/sl.so Reading symbols from /usr/lib64/opensips/modules/tm.so...done. Loaded symbols for /usr/lib64/opensips/modules/tm.so Reading symbols from /usr/lib64/opensips/modules/rr.so...done. Loaded symbols for /usr/lib64/opensips/modules/rr.so Reading symbols from /usr/lib64/opensips/modules/maxfwd.so...done. Loaded symbols for /usr/lib64/opensips/modules/maxfwd.so Reading symbols from /usr/lib64/opensips/modules/sipmsgops.so...done. Loaded symbols for /usr/lib64/opensips/modules/sipmsgops.so Reading symbols from /usr/lib64/opensips/modules/mi_fifo.so...done. Loaded symbols for /usr/lib64/opensips/modules/mi_fifo.so Reading symbols from /usr/lib64/opensips/modules/uri.so...done. Loaded symbols for /usr/lib64/opensips/modules/uri.so Reading symbols from /usr/lib64/opensips/modules/usrloc.so...done. Loaded symbols for /usr/lib64/opensips/modules/usrloc.so Reading symbols from /usr/lib64/opensips/modules/nathelper.so...done. Loaded symbols for /usr/lib64/opensips/modules/nathelper.so Reading symbols from /usr/lib64/opensips/modules/registrar.so...done. Loaded symbols for /usr/lib64/opensips/modules/registrar.so Reading symbols from /usr/lib64/opensips/modules/acc.so...done. Loaded symbols for /usr/lib64/opensips/modules/acc.so Reading symbols from /lib64/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libnss_files.so.2 Core was generated by `/usr/sbin/opensips -u root -g root -P /var/run/opensips.pid -f'. Program terminated with signal 11, Segmentation fault. #0 0x00007f555a02fcea in _IO_cleanup () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.166.el6_7.7.x86_64 keyutils-libs-1.4-4.el6.x86_64 krb5-libs-1.10.3-42z1.el6_7.x86_64 libcom_err-1.41.12-18.el6.x86_64 libselinux-2.0.94-5.3.el6_4.1.x86_64 openssl-1.0.1e-48.el6_8.1.x86_64 zlib-1.2.3-29.el6.x86_64 (gdb) bt full #0 0x00007f555a02fcea in _IO_cleanup () from /lib64/libc.so.6 No symbol table info available. #1 0x00007f5559ff0ac2 in exit () from /lib64/libc.so.6 No symbol table info available. #2 0x000000000043df19 in sig_usr (signo=) at main.c:631 __FUNCTION__ = "sig_usr" #3 No symbol table info available. #4 0x00007f555a096560 in __write_nocancel () from /lib64/libc.so.6 No symbol table info available. #5 0x00007f555a02cad3 in _IO_new_file_write () from /lib64/libc.so.6 No symbol table info available. #6 0x00007f555a02e085 in _IO_new_do_write () from /lib64/libc.so.6 No symbol table info available. #7 0x00007f555a02d3df in _IO_new_file_overflow () from /lib64/libc.so.6 No symbol table info available. #8 0x00007f555a02f639 in _IO_default_xsputn_internal () from /lib64/libc.so.6 No symbol table info available. #9 0x00007f555a02c792 in _IO_new_file_xsputn () from /lib64/libc.so.6 No symbol table info available. #10 0x00007f555a003190 in vfprintf () from /lib64/libc.so.6 No symbol table info available. #11 0x00007f555a02a550 in vdprintf () from /lib64/libc.so.6 No symbol table info available. #12 0x00007f555a00a3d8 in dprintf () from /lib64/libc.so.6 No symbol table info available. #13 0x00007f555a09fe1b in __vsyslog_chk () from /lib64/libc.so.6 No symbol table info available. #14 0x00007f555a0a00d0 in syslog () from /lib64/libc.so.6 No symbol table info available. #15 0x00000000004d1ab8 in tcp_read_req (con=0x7f55363848a8, bytes_read=0x7ffc1ba7eedc) at tcp_read.c:597 bytes = total_bytes = resp = 0 size = req = 0x8449a0 c = local_rcv = {src_ip = {af = 909658280, len = 32597, u = {addrl = {18446744073709551614, 49}, addr32 = {4294967294, 4294967295, 49, 0}, addr16 = {65534, 65535, 65535, 65535, 49, 0, 0, 0}, addr = "\376\377\377\377\377\377\377\377\061\000\000\000\000\000\000"}}, dst_ip = {af = 1, len = 0, u = {addrl = {1, 5048363}, addr32 = {1, 0, 5048363, 0}, addr16 = {1, 0, 0, 0, 2091, 77, 0, 0}, addr = "\001\000\000\000\000\000\000\000+\bM\000\000\000\000"}}, src_port = 5060, dst_port = 5060, proto = 2, proto_reserved1 = 5046786, proto_reserved2 = 0, src_su = {s = {sa_family = 56296, sa_data = "36U\177\000\000\000\000\000\000\000\000\000"}, sin = {sin_family = 56296, sin_port = 13875, sin_addr = {s_addr = 32597}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 56296, sin6_port = 13875, sin6_flowinfo = 32597, sin6_addr = {__in6_u = {__u6_addr8 = "\000\000\000\000\000\000\000\000\250H86U\177\000", __u6_addr16 = {0, 0, 0, 0, 18600, 13880, 32597, 0}, __u6_addr32 = {0, 0, 909658280, 32597}}}, sin6_scope_id = 4294967294}}, bind_address = 0x7f5557c01398} msg_buf = msg_len = __FUNCTION__ = "tcp_read_req" #16 0x00000000004d31e8 in handle_io (fm=, idx=-1, event_type=) at tcp_read.c:1033 ret = 0 n = con = 0x7f55363848a8 s = rw = resp = response = {140003958605992, 1} __FUNCTION__ = "handle_io" #17 0x00000000004d5985 in io_wait_loop_epoll (unix_sock=) at io_wait.h:845 n = 1 r = #18 tcp_receive_loop (unix_sock=) at tcp_read.c:1141 __FUNCTION__ = "tcp_receive_loop" #19 0x00000000004bb82c in tcp_init_children (chd_rank=, startup_done=0x0) at tcp_main.c:2390 r = reader_fd = {47, 49} pid = si = load_p = 0x7f553632dbb0 __FUNCTION__ = "tcp_init_children" #20 0x000000000043d6b8 in main_loop (argc=, argv=) at main.c:1011 i = pid = ---Type to continue, or q to quit--- si = 0x0 startup_done = 0x0 chd_rank = 35 rc = load_p = 0x7f553633aed0 #21 main (argc=, argv=) at main.c:1612 cfg_log_stderr = cfg_stream = c = r = tmp = 0x7ffc1ba80f40 "172.29.106.10" tmp_len = port = proto = options = 0x595880 "f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:" ret = -1 seed = 3019838257 rfd = __FUNCTION__ = "main" (gdb) ##### Core 4 Time : 2017-01-25T09:08 ##### gdb /usr/sbin/opensips core.4473 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: ... Reading symbols from /usr/sbin/opensips...done. warning: core file may not match specified executable file. [New Thread 4473] Missing separate debuginfo for /usr/lib64/opensips/modules/signaling.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/a5/6fe5f3fb5f5a5945cd0fd8384403a1610ac723 Missing separate debuginfo for /usr/lib64/opensips/modules/sl.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/a0/3aa3c43c41ef6b5a3443edee6b57557f99e95f Missing separate debuginfo for /usr/lib64/opensips/modules/tm.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/86/ec031a2c632fc2c1c2ebc807d134588c879e8f Missing separate debuginfo for /usr/lib64/opensips/modules/rr.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/f9/5a55b1e8ec652178bbf56f1de12a130f2d3fc2 Missing separate debuginfo for /usr/lib64/opensips/modules/maxfwd.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/3c/bcedbe5e2cb56ce0232c168ce10d01549154e9 Missing separate debuginfo for /usr/lib64/opensips/modules/sipmsgops.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/68/3d8e3c5d0e47bb4e69df2e47f62b8a6c2b02e1 Missing separate debuginfo for /usr/lib64/opensips/modules/mi_fifo.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/25/0c6e832f8702623763334c66d80701abd2f757 Missing separate debuginfo for /usr/lib64/opensips/modules/uri.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/6c/8c7108c432cb039e548473b9c190265cb21c3c Missing separate debuginfo for /usr/lib64/opensips/modules/usrloc.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/7a/3f6b2b6c1c5e4d9143db3610667472c5b1f1fb Missing separate debuginfo for /usr/lib64/opensips/modules/nathelper.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/fe/eb381245a35d7cc8504f30496cbce200bc2a32 Missing separate debuginfo for /usr/lib64/opensips/modules/registrar.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/e1/e152c5eb09765db719d2de687674d4b38bec29 Missing separate debuginfo for /usr/lib64/opensips/modules/acc.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/0d/53590fb94de20cbeb1aee103e38332cdb6783c Missing separate debuginfo for Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/7f/719af91ee951b4fcb6647e7868f95f766a616b Reading symbols from /lib64/snoopy.so...done. Loaded symbols for /lib64/snoopy.so Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libresolv.so.2 Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl.so.10 Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcrypto.so.10 Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libgssapi_krb5.so.2 Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5.so.3 Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libcom_err.so.2 Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libk5crypto.so.3 Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libz.so.1 Reading symbols from /lib64/libkrb5support.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5support.so.0 Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libkeyutils.so.1 Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libselinux.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libselinux.so.1 Reading symbols from /usr/lib64/opensips/modules/signaling.so...done. Loaded symbols for /usr/lib64/opensips/modules/signaling.so Reading symbols from /usr/lib64/opensips/modules/sl.so...done. Loaded symbols for /usr/lib64/opensips/modules/sl.so Reading symbols from /usr/lib64/opensips/modules/tm.so...done. Loaded symbols for /usr/lib64/opensips/modules/tm.so Reading symbols from /usr/lib64/opensips/modules/rr.so...done. Loaded symbols for /usr/lib64/opensips/modules/rr.so Reading symbols from /usr/lib64/opensips/modules/maxfwd.so...done. Loaded symbols for /usr/lib64/opensips/modules/maxfwd.so Reading symbols from /usr/lib64/opensips/modules/sipmsgops.so...done. Loaded symbols for /usr/lib64/opensips/modules/sipmsgops.so Reading symbols from /usr/lib64/opensips/modules/mi_fifo.so...done. Loaded symbols for /usr/lib64/opensips/modules/mi_fifo.so Reading symbols from /usr/lib64/opensips/modules/uri.so...done. Loaded symbols for /usr/lib64/opensips/modules/uri.so Reading symbols from /usr/lib64/opensips/modules/usrloc.so...done. Loaded symbols for /usr/lib64/opensips/modules/usrloc.so Reading symbols from /usr/lib64/opensips/modules/nathelper.so...done. Loaded symbols for /usr/lib64/opensips/modules/nathelper.so Reading symbols from /usr/lib64/opensips/modules/registrar.so...done. Loaded symbols for /usr/lib64/opensips/modules/registrar.so Reading symbols from /usr/lib64/opensips/modules/acc.so...done. Loaded symbols for /usr/lib64/opensips/modules/acc.so Reading symbols from /lib64/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libnss_files.so.2 Core was generated by `/usr/sbin/opensips -u root -g root -P /var/run/opensips.pid -f'. Program terminated with signal 11, Segmentation fault. #0 0x00007f555a02fcea in _IO_cleanup () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.166.el6_7.7.x86_64 keyutils-libs-1.4-4.el6.x86_64 krb5-libs-1.10.3-42z1.el6_7.x86_64 libcom_err-1.41.12-18.el6.x86_64 libselinux-2.0.94-5.3.el6_4.1.x86_64 openssl-1.0.1e-48.el6_8.1.x86_64 zlib-1.2.3-29.el6.x86_64 (gdb) bt full #0 0x00007f555a02fcea in _IO_cleanup () from /lib64/libc.so.6 No symbol table info available. #1 0x00007f5559ff0ac2 in exit () from /lib64/libc.so.6 No symbol table info available. #2 0x000000000043df19 in sig_usr (signo=) at main.c:631 __FUNCTION__ = "sig_usr" #3 No symbol table info available. #4 0x00007f555a09655e in __write_nocancel () from /lib64/libc.so.6 No symbol table info available. #5 0x00007f555a02cad3 in _IO_new_file_write () from /lib64/libc.so.6 No symbol table info available. #6 0x00007f555a02e085 in _IO_new_do_write () from /lib64/libc.so.6 No symbol table info available. #7 0x00007f555a02d3df in _IO_new_file_overflow () from /lib64/libc.so.6 No symbol table info available. #8 0x00007f555a02f639 in _IO_default_xsputn_internal () from /lib64/libc.so.6 No symbol table info available. #9 0x00007f555a02c792 in _IO_new_file_xsputn () from /lib64/libc.so.6 No symbol table info available. #10 0x00007f555a003190 in vfprintf () from /lib64/libc.so.6 No symbol table info available. #11 0x00007f555a02a550 in vdprintf () from /lib64/libc.so.6 No symbol table info available. #12 0x00007f555a00a3d8 in dprintf () from /lib64/libc.so.6 No symbol table info available. #13 0x00007f555a09fe1b in __vsyslog_chk () from /lib64/libc.so.6 No symbol table info available. #14 0x00007f555a0a00d0 in syslog () from /lib64/libc.so.6 No symbol table info available. #15 0x00000000004d1ab8 in tcp_read_req (con=0x7f553636dfb8, bytes_read=0x7ffc1ba7eedc) at tcp_read.c:597 bytes = total_bytes = resp = 0 size = req = 0x8449a0 c = local_rcv = {src_ip = {af = 909565880, len = 32597, u = {addrl = {18446744073709551614, 47}, addr32 = {4294967294, 4294967295, 47, 0}, addr16 = {65534, 65535, 65535, 65535, 47, 0, 0, 0}, addr = "\376\377\377\377\377\377\377\377/\000\000\000\000\000\000"}}, dst_ip = {af = 1, len = 0, u = {addrl = {1, 5048363}, addr32 = {1, 0, 5048363, 0}, addr16 = {1, 0, 0, 0, 2091, 77, 0, 0}, addr = "\001\000\000\000\000\000\000\000+\bM\000\000\000\000"}}, src_port = 0, dst_port = 0, proto = 0, proto_reserved1 = 5046838, proto_reserved2 = 0, src_su = {s = {sa_family = 0, sa_data = '\000' }, sin = {sin_family = 0, sin_port = 0, sin_addr = {s_addr = 0}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 0, sin6_port = 0, sin6_flowinfo = 0, sin6_addr = {__in6_u = { __u6_addr8 = "\000\000\000\000\000\000\000\000\270\337\066\066U\177\000", __u6_addr16 = {0, 0, 0, 0, 57272, 13878, 32597, 0}, __u6_addr32 = {0, 0, 909565880, 32597}}}, sin6_scope_id = 4294967294}}, bind_address = 0x7f5557c01398} msg_buf = msg_len = __FUNCTION__ = "tcp_read_req" #16 0x00000000004d31e8 in handle_io (fm=, idx=-1, event_type=) at tcp_read.c:1033 ret = 0 n = con = 0x7f553636dfb8 s = rw = resp = response = {140003958513592, -2} __FUNCTION__ = "handle_io" #17 0x00000000004d5985 in io_wait_loop_epoll (unix_sock=) at io_wait.h:845 n = 1 r = #18 tcp_receive_loop (unix_sock=) at tcp_read.c:1141 __FUNCTION__ = "tcp_receive_loop" #19 0x00000000004bb82c in tcp_init_children (chd_rank=, startup_done=0x0) at tcp_main.c:2390 r = reader_fd = {45, 47} pid = si = load_p = 0x7f553632dbb0 __FUNCTION__ = "tcp_init_children" #20 0x000000000043d6b8 in main_loop (argc=, argv=) at main.c:1011 i = pid = ---Type to continue, or q to quit--- si = 0x0 startup_done = 0x0 chd_rank = 34 rc = load_p = 0x7f553633aed0 #21 main (argc=, argv=) at main.c:1612 cfg_log_stderr = cfg_stream = c = r = tmp = 0x7ffc1ba80f40 "172.29.106.10" tmp_len = port = proto = options = 0x595880 "f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:" ret = -1 seed = 3019838257 rfd = __FUNCTION__ = "main" (gdb) ##### Logs ##### Logs were not captured(logged during Core 2,3,4 failures) may be syslogs were being rotated and blocked further logging momentarily. ##### Core 5 Time : 2017-01-25T19:35 ##### gdb /usr/sbin/opensips core.12396 GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: ... Reading symbols from /usr/sbin/opensips...done. warning: core file may not match specified executable file. [New Thread 12396] Missing separate debuginfo for /usr/lib64/opensips/modules/signaling.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/a5/6fe5f3fb5f5a5945cd0fd8384403a1610ac723 Missing separate debuginfo for /usr/lib64/opensips/modules/sl.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/a0/3aa3c43c41ef6b5a3443edee6b57557f99e95f Missing separate debuginfo for /usr/lib64/opensips/modules/tm.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/86/ec031a2c632fc2c1c2ebc807d134588c879e8f Missing separate debuginfo for /usr/lib64/opensips/modules/rr.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/f9/5a55b1e8ec652178bbf56f1de12a130f2d3fc2 Missing separate debuginfo for /usr/lib64/opensips/modules/maxfwd.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/3c/bcedbe5e2cb56ce0232c168ce10d01549154e9 Missing separate debuginfo for /usr/lib64/opensips/modules/sipmsgops.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/68/3d8e3c5d0e47bb4e69df2e47f62b8a6c2b02e1 Missing separate debuginfo for /usr/lib64/opensips/modules/mi_fifo.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/25/0c6e832f8702623763334c66d80701abd2f757 Missing separate debuginfo for /usr/lib64/opensips/modules/uri.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/6c/8c7108c432cb039e548473b9c190265cb21c3c Missing separate debuginfo for /usr/lib64/opensips/modules/usrloc.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/7a/3f6b2b6c1c5e4d9143db3610667472c5b1f1fb Missing separate debuginfo for /usr/lib64/opensips/modules/nathelper.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/fe/eb381245a35d7cc8504f30496cbce200bc2a32 Missing separate debuginfo for /usr/lib64/opensips/modules/registrar.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/e1/e152c5eb09765db719d2de687674d4b38bec29 Missing separate debuginfo for /usr/lib64/opensips/modules/acc.so Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/0d/53590fb94de20cbeb1aee103e38332cdb6783c Missing separate debuginfo for Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/7f/719af91ee951b4fcb6647e7868f95f766a616b Reading symbols from /lib64/snoopy.so...done. Loaded symbols for /lib64/snoopy.so Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libresolv.so.2 Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl.so.10 Reading symbols from /usr/lib64/libcrypto.so.10...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcrypto.so.10 Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libgssapi_krb5.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libgssapi_krb5.so.2 Reading symbols from /lib64/libkrb5.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5.so.3 Reading symbols from /lib64/libcom_err.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libcom_err.so.2 Reading symbols from /lib64/libk5crypto.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libk5crypto.so.3 Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libz.so.1 Reading symbols from /lib64/libkrb5support.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libkrb5support.so.0 Reading symbols from /lib64/libkeyutils.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libkeyutils.so.1 Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /lib64/libselinux.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libselinux.so.1 Reading symbols from /usr/lib64/opensips/modules/signaling.so...done. Loaded symbols for /usr/lib64/opensips/modules/signaling.so Reading symbols from /usr/lib64/opensips/modules/sl.so...done. Loaded symbols for /usr/lib64/opensips/modules/sl.so Reading symbols from /usr/lib64/opensips/modules/tm.so...done. Loaded symbols for /usr/lib64/opensips/modules/tm.so Reading symbols from /usr/lib64/opensips/modules/rr.so...done. Loaded symbols for /usr/lib64/opensips/modules/rr.so Reading symbols from /usr/lib64/opensips/modules/maxfwd.so...done. Loaded symbols for /usr/lib64/opensips/modules/maxfwd.so Reading symbols from /usr/lib64/opensips/modules/sipmsgops.so...done. Loaded symbols for /usr/lib64/opensips/modules/sipmsgops.so Reading symbols from /usr/lib64/opensips/modules/mi_fifo.so...done. Loaded symbols for /usr/lib64/opensips/modules/mi_fifo.so Reading symbols from /usr/lib64/opensips/modules/uri.so...done. Loaded symbols for /usr/lib64/opensips/modules/uri.so Reading symbols from /usr/lib64/opensips/modules/usrloc.so...done. Loaded symbols for /usr/lib64/opensips/modules/usrloc.so Reading symbols from /usr/lib64/opensips/modules/nathelper.so...done. Loaded symbols for /usr/lib64/opensips/modules/nathelper.so Reading symbols from /usr/lib64/opensips/modules/registrar.so...done. Loaded symbols for /usr/lib64/opensips/modules/registrar.so Reading symbols from /usr/lib64/opensips/modules/acc.so...done. Loaded symbols for /usr/lib64/opensips/modules/acc.so Reading symbols from /lib64/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libnss_files.so.2 Core was generated by `/usr/sbin/opensips -u root -g root -P /var/run/opensips.pid -f'. Program terminated with signal 11, Segmentation fault. #0 fm_insert_free (qm=0x7f3e64fcf010, p=0x7f3e6508f260) at mem/f_malloc.c:147 147 mem/f_malloc.c: No such file or directory. in mem/f_malloc.c Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.166.el6_7.7.x86_64 keyutils-libs-1.4-4.el6.x86_64 krb5-libs-1.10.3-42z1.el6_7.x86_64 libcom_err-1.41.12-18.el6.x86_64 libselinux-2.0.94-5.3.el6_4.1.x86_64 openssl-1.0.1e-48.el6_8.1.x86_64 zlib-1.2.3-29.el6.x86_64 (gdb) bt full #0 fm_insert_free (qm=0x7f3e64fcf010, p=0x7f3e6508f260) at mem/f_malloc.c:147 f = 0x7f3e6508f0c8 hash = 2097 #1 fm_free (qm=0x7f3e64fcf010, p=0x7f3e6508f260) at mem/f_malloc.c:470 f = 0x7f3e6508f248 n = __FUNCTION__ = "fm_free" #2 0x00000000004d07f7 in release_tcpconn (c=0x7f3e43767ce8, state=-2, unix_sock=48) at tcp_read.c:443 response = {7277499135891079169, 32574} __FUNCTION__ = "release_tcpconn" #3 0x00000000004d3552 in handle_io (fm=, idx=, event_type=) at tcp_read.c:1040 ret = -1 n = con = 0x7f3e43767ce8 s = rw = resp = -2 response = {139905396538600, 1} __FUNCTION__ = "handle_io" #4 0x00000000004d5985 in io_wait_loop_epoll (unix_sock=) at io_wait.h:845 n = 1 r = #5 tcp_receive_loop (unix_sock=) at tcp_read.c:1141 __FUNCTION__ = "tcp_receive_loop" #6 0x00000000004bb82c in tcp_init_children (chd_rank=, startup_done=0x0) at tcp_main.c:2390 r = reader_fd = {46, 48} pid = si = load_p = 0x7f3e43703bb0 __FUNCTION__ = "tcp_init_children" #7 0x000000000043d6b8 in main_loop (argc=, argv=) at main.c:1011 i = pid = si = 0x0 startup_done = 0x0 chd_rank = 35 rc = load_p = 0x7f3e43710ed0 #8 main (argc=, argv=) at main.c:1612 cfg_log_stderr = cfg_stream = c = r = tmp = 0x7ffc16782f40 "172.29.106.10" tmp_len = port = proto = options = 0x595880 "f:cCm:M:b:l:n:N:rRvdDFETSVhw:t:u:g:P:G:W:o:" ret = -1 seed = 4155673706 rfd = __FUNCTION__ = "main" (gdb) ##### Logs ##### 2017-01-25T12:27:53.000-05:00 [local2] [debug] E01Z01.dev.com /usr/sbin/opensips[12395]: DBG:core:forward_request: orig. len=633, new_len=808, proto=1 2017-01-25T12:27:53.000-05:00 [local2] [debug] E01Z01.dev.com /usr/sbin/opensips[12395]: DBG:core:destroy_avp_list: destroying list (nil) 2017-01-25T12:27:53.000-05:00 [local2] [debug] E01Z01.dev.com /usr/sbin/opensips[12395]: DBG:core:receive_msg: cleaning up 2017-01-25T12:27:53.000-05:00 [local2] [debug] E01Z01.dev.com /usr/sbin/opensips[12395]: DBG:core:tcp_read_req: preparing for new request, kept 0 bytes 2017-01-25T12:27:53.000-05:00 [local2] [debug] E01Z01.dev.com /usr/sbin/opensips[12395]: DBG:core:tcp_read_req: tcp_read_req end 2017-01-25T13:58:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[12395]: ERROR:core:io_watch_del: trying to delete already erased entry 49 in the hash(-1, 0, 0x7f3e437111d0) ) 2017-01-25T13:58:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[12395]: ERROR:core:tcp_read_req: bad request, state=0, error=2 buf: parsed: 2017-01-25T13:58:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[12395]: ERROR:core:io_watch_del: trying to delete already erased entry 49 in the hash(-1, 0, 0x7f3e437111d0) ) 2017-01-25T13:58:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[12395]: ERROR:core:tcp_read_req: bad request, state=0, error=2 buf: parsed: 2017-01-25T13:58:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[12395]: ERROR:core:io_watch_del: trying to delete already erased entry 49 in the hash(-1, 0, 0x7f3e437111d0) ) 2017-01-25T13:58:02.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[12395]: ERROR:core:tcp_read_req: bad request, state=0, error=2 buf: parsed: 2017-01-25T19:35:33.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[12395]: ERROR:core:io_watch_del: trying to delete already erased entry 49 in the hash(-1, 0, 0x7f3e437111d0) ) 2017-01-25T19:35:33.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[12395]: ERROR:core:tcp_read_req: bad request, state=0, error=2 buf: parsed: 2017-01-25T19:35:33.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[12395]: ERROR:core:io_watch_del: trying to delete already erased entry 49 in the hash(-1, 0, 0x7f3e437111d0) ) 2017-01-25T19:35:33.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[12303]: ERROR:core:tls_shutdown: something wrong in SSL: 2017-01-25T19:35:33.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[12303]: ERROR:core:tls_shutdown: something wrong in SSL: 2017-01-25T19:35:33.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[12303]: ERROR:core:tls_shutdown: something wrong in SSL: 2017-01-25T19:35:33.000-05:00 [local2] [err] E01Z01.dev.com /usr/sbin/opensips[12303]: ERROR:core:tls_shutdown: something wrong in SSL: ##### Additional Logs ##### [root at E01Z01 opensips]# opensipsCtrl fifo list_tcp_conns Connection:: ID=1 Type=tcp State=3 Source=172.29.106.10:35384 Destination=172.29.106.10:5060 Timeout=2017-01-27 02:18:17 Pending lifetime=0 Connection:: ID=4 Type=tls State=0 Source=172.29.106.22:5071 Destination=172.29.106.10:5062 Timeout=2017-01-27 02:05:07 Pending lifetime=0 Connection:: ID=26 Type=tcp State=4 Source=172.29.106.22:5070 Destination=172.29.106.10:5060 Timeout=2017-01-27 02:15:09 Pending lifetime=0 Connection:: ID=27 Type=tcp State=4 Source=172.29.106.13:5070 Destination=172.29.106.10:5060 Timeout=2017-01-27 02:15:10 Pending lifetime=0 Connection:: ID=3241 Type=tcp State=3 Source=172.29.106.13:63523 Destination=172.29.106.10:5060 Timeout=2017-01-26 20:06:06 Pending lifetime=0 Connection:: ID=3242 Type=tcp State=3 Source=172.29.106.22:44879 Destination=172.29.106.10:5060 Timeout=2017-01-26 20:06:06 Pending lifetime=0 Connection:: ID=3243 Type=tcp State=3 Source=172.29.106.22:52354 Destination=172.29.106.10:5060 Timeout=2017-01-27 02:14:34 Pending lifetime=0 Connection:: ID=4791 Type=tcp State=3 Source=172.29.106.11:44876 Destination=172.29.106.10:5060 Timeout=2017-01-27 02:18:16 Pending lifetime=0 Connection:: ID=4830 Type=tcp State=3 Source=172.29.106.95:37611 Destination=172.29.106.10:5060 Timeout=2017-01-27 02:18:19 Pending lifetime=0 Connection:: ID=4871 Type=tcp State=3 Source=172.29.106.10:42402 Destination=172.29.106.10:5060 Timeout=2017-01-27 02:18:20 Pending lifetime=0 Connection:: ID=4872 Type=tcp State=3 Source=172.29.106.20:53258 Destination=172.29.106.10:5060 Timeout=2017-01-26 14:18:21 Pending lifetime=0 Connection:: ID=4029 Type=tcp State=18446744073709551615 Source=172.29.106.95:5060 Destination=172.29.106.10:5060 Timeout=2017-01-25 19:35:35 Pending lifetime=0 Connection:: ID=4030 Type=tcp State=4 Source=172.29.106.95:5060 Destination=172.29.106.10:5060 Timeout=2017-01-27 02:18:20 Pending lifetime=0 [root at E01Z01 opensips]# Debug Logs : [20758]: DBG:core:tcp_read_req: - received from: port 5060 [20758]: DBG:core:print_ip: - received from: ip 172.29.106.95 [20758]: DBG:core:io_watch_del: io_watch_del op on index -1 52 (0x8100e0, 52, -1, 0x10,0x3) fd_no=2 called [20758]: ERROR:core:io_watch_del: trying to delete already erased entry 52 in the hash(0, 0, (nil)) ) [20758]: DBG:core:release_tcpconn: releasing con 0x7f543179d700, state -2, fd=52, id=4029 [20758]: DBG:core:release_tcpconn: extra_data (nil) [20758]: DBG:core:tcp_read_req: Using the global ( per process ) buff [20758]: ERROR:core:tcp_read_req: bad request, state=0, error=2 buf