From aj.shirvani at gmail.com Sat Jun 1 11:30:59 2019 From: aj.shirvani at gmail.com (Ali Shirvani) Date: Sat, 1 Jun 2019 20:00:59 +0430 Subject: [OpenSIPS-Users] Sending multiple request from OpenSIPS to multiple destinations Message-ID: Hi all, Is it possible to send multiple initial request to multiple destinations? something like b2bua but with multiple destinations. I draw the diagram in this gist: https://gist.github.com/alishir/23d2bf5358ef138d1c1f2cfa72cde028 Regards, Ali -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Mon Jun 3 03:26:47 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Mon, 3 Jun 2019 10:26:47 +0300 Subject: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) In-Reply-To: <00cb01d512b3$03f3e860$0bdbb920$@wtild.com> References: <00cb01d512b3$03f3e860$0bdbb920$@wtild.com> Message-ID: <4e582929-c1ba-eed5-a9a9-24b83a8bdb56@opensips.org> Hi Frank, There were no changes in the db_unixodbc driver in OpenSIPS for some time. Maybe something changed in the unixodbc driver for MS SQL. Based on the this log: core:db_table_version: invalid type (1) or nul (0) I see that that the "table_version" from the version table is returned as BIGINT, while OpenSIPS expects INT. Of course, this is something we can quickly adjust. In regards to the 'avp_db_query', could you post the level 3 logs corresponding to the query ? Maybe it will give us a clue. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 05/25/2019 07:33 AM, Frank Lee wrote: > > Hello, > > Was there some major change between version 1.11 and 2.4.5 on > supporting of the ODBC connection of Microsoft SQL Server? It seems I > had 1.11 running fine on SQL server (or at least partial table on sql > server such as location table). But now I use 2.4.5 it seems all the > module that uses odbc connector instead of the mysql connector it will > have the error below > > core:db_table_version: invalid type (1) or nul (0) > > Thus, I changed all the module to use mysql connector (except the > AVPOPS Module because I have custom query in the script which need to > query the Microsoft sql server) which made Opensips start out fine. > But as soon as it uses the avp_db_query in the script it seems it > would not work. Alhtough I don’t see any error in the syslog file > (although I had log_level set to 3, do I need to set it higher?) > > Anyway, it just seems all the query/support to Microsoft SQL server > doesn’t run right in 2.4.5 vs 1.11. > > Is there some dependency that I am suppose to install which is different? > > I had my 1.11 run on Debian 7. Now we are moving to Azure cloud, I > had run Ubuntu 18.04 since Debian 7 is not support on Azure. > > I had install odbc version 2.3.4 and also tdsodbc 1.00 > > Are these not to correct version to interface between 2.4.5 and > Microsoft sql server (I tried both version msssql 2008 and 2016). > > Anyway, any pointer or help will be greatly appreciated! > > Thank you! > > *From:* Frank Lee [mailto:frank at wtild.com] > *Sent:* Friday, May 24, 2019 10:58 AM > *To:* 'users at lists.opensips.org' > *Subject:* Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) > > Hello, > > This is the first time I use this mail message, so let me know if this > is not the correct way of posting question. > > Anyway, I am running Opensips 2.4.5 and when I use MYSQL database on > all module, opensips runs fine. But as soon as I switch over the > database source to use ODBC driver (which is linked to Microsoft SQL > server 2016), I get this error. What is It mean? > > May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: > ERROR:core:db_table_version: invalid type (1) or nul (0) version > columns for subscriber > > May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: > ERROR:core:db_check_table_version: querying version for table subscriber > > May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: > ERROR:uri:mod_init: Invalid table version. > > I first created the MySQL table usinmg the command: > > opensipsdbctl create > > And then I transfer the tables to MSSQL using the: > > Microsoft SQL Server Migration Assistant 8.1 for MySQL > > All the table named corrected and all the index was created too. > > Thank you very much! > > Frank > > > > _______________________________________________ > 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 Jun 3 03:37:26 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Mon, 3 Jun 2019 10:37:26 +0300 Subject: [OpenSIPS-Users] ws and hold problem In-Reply-To: References: Message-ID: Hi Mikhail, When using WS(S), for the messages coming from the WS(S) endpoint ( with Contact with "invalid") you need to do "fix_nated_contact()", to transform that contact into a routable SIP URI. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 05/25/2019 03:35 AM, Mikhail wrote: > Hi > > opensips 2.4 and rtpengine. > webrtc SIP clients based on jsSIP 3.3.6 > to accounts jssip1 and jssip2 > > jssip1 calls jssip2 or jssip2 calls jssip1 - call established > jssip1 place call on hold and then unhold - no problem > now if jssip2 place call on hold it receives SIP/2.0 476 Unresolvable > destination (476/TM) from opensips and call brakes. > also in opensips.log there are a messages like this: > May 25 02:42:41 opensips-01 /usr/sbin/opensips[19704]: > CRITICAL:core:mk_proxy: could not resolve hostname: > "djgppiddv7t0.invalid" > May 25 02:42:41 opensips-01 /usr/sbin/opensips[19704]: > ERROR:tm:uri2proxy: bad host name in URI > > May 25 02:42:41 opensips-01 /usr/sbin/opensips[19704]: > ERROR:tm:t_forward_nonack: failure to add branches > > what i found: > > While call setup jsip1 sends initial invite: > INVITE sip:jsip2 at 192.168.18.78 SIP/2.0 > Contact: > > server resends to jsip2 invite and replaces Contact with the real ip > of jsip1: > INVITE sip:60s8k9ep at 192.168.21.117:49882;transport=ws SIP/2.0 > Contact: > > > When jssip1 place call on hold or unhold, it sends invite to server with > INVITE sip:60s8k9ep at 192.168.21.117:51630;transport=ws SIP/2.0 > Contact: > > server resends to jsip2 invite and do not changes Contact: > INVITE sip:60s8k9ep at 192.168.21.117:51630;transport=ws SIP/2.0 > Contact: > > Next, when jssip2 places call on hold, it sends invite: > INVITE sip:lp7tmvt6 at djgppiddv7t0.invalid;transport=ws;ob SIP/2.0 > and server can't resolve djgppiddv7t0.invalid, it expects real address > here > > > does anybody have an idea, who is responsible for the problem - jssip, > opensips or rtpengine ? > > > Laba Mikhail > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From bogdan at opensips.org Mon Jun 3 03:43:42 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Mon, 3 Jun 2019 10:43:42 +0300 Subject: [OpenSIPS-Users] local cache becomes empty In-Reply-To: <1559136435.117254524@f509.i.mail.ru> References: <1559136435.117254524@f509.i.mail.ru> Message-ID: <27270aee-32ef-e03f-1fb4-3fc063e67027@opensips.org> Hi Alexey, Try to see if you notice a pattern. Nevertheless I suspect some operational issue (removing the keys via MI or script). Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 05/29/2019 04:27 PM, Alexey Kazantsev via Users wrote: >> Values with timeout still existed. > I mean they exist the period of time defined as the timeout parameter. > > ----------------------------------------------- > BR, Alexey > http://alexeyka.zantsev.com/ > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From bogdan at opensips.org Mon Jun 3 03:53:43 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Mon, 3 Jun 2019 10:53:43 +0300 Subject: [OpenSIPS-Users] Load Balancer cluster Opensips 3.0 In-Reply-To: References: Message-ID: Hi Anton, That is an interesting combination - pinging via an anycast interface. Could you paste here the OPTIONS and its reply, to check if it is correctly built from the anycast perspective ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 05/27/2019 03:16 PM, Антон Ершов wrote: > > Hello friends! > > I'm testing new features of opensips 3. And I discovered the following > situation. > > Configured cluster module in Anycast Сonfiguration. Load balanser module > > has cluster_sharing_tag. The lb module sends "options" to the host > from the common address, but the answer goes to the nearest opensips > node of the cluster. From what the remote host in lb is considered > inaccessible. > > Something is not configured or I did not understand correctly how the > load balanser should work in a cluster > > > > _______________________________________________ > 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 Jun 3 04:00:11 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Mon, 3 Jun 2019 11:00:11 +0300 Subject: [OpenSIPS-Users] first_hit_counter In-Reply-To: <1559244737.510972547@f45.i.mail.ru> References: <1559244737.510972547@f45.i.mail.ru> Message-ID: <75291aa0-0b65-3861-a3ca-edea2c24bcf1@opensips.org> Hi Oleg, The "first_hit_counter" tells you how many times that destination was selected (from the first time/usage, and not via a failover) for routing. In regards to the provisioning fields, see https://opensips.org/Documentation/Install-DBSchema-2-4#AEN4366 Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 05/30/2019 10:32 PM, Олег Подгуйко via Users wrote: > Hello! > > The question is about dispatcher module. I'm interested in one parameter. > > Sometimes I use this command > > [opodguyko at xx-spx-1 ~]$ opensipsctl fifo ds_list > PARTITION:: default > SET:: 1 > URI:: sip:10.10.31.21:5060 state=Active first_hit_counter=13 > socket:: udp:10.10.31.11:5060 > attr:: test > [opodguyko at xx-spx-1 ~]$ > > > Could you explain what does it means "first_hit_counter" parameter? > > I haven't found anything at all about it in your documentation. > > It would also be interesting to understand why the following > parameters are needed > > state(int) weight(string) priority(int) > > The documentation gives a very poor description. > > > Thank you. > > -- > Oleg Podguyko > > > _______________________________________________ > 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 Jun 3 04:03:06 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Mon, 3 Jun 2019 11:03:06 +0300 Subject: [OpenSIPS-Users] Sending multiple request from OpenSIPS to multiple destinations In-Reply-To: References: Message-ID: Hi Ali, That is called SIP parallel forking and you can do it by using the append_branch() function [1] or $branch variable [2] in order to add multiple destinations for an INVITE. [1] https://opensips.org/Documentation/Script-CoreFunctions-2-4#toc3 [2] https://opensips.org/Documentation/Script-CoreVar-2-4#toc21 Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/01/2019 06:30 PM, Ali Shirvani wrote: > Hi all, > > Is it possible to send multiple initial request to multiple > destinations? something like b2bua but with multiple destinations. > > I draw the diagram in this gist: > https://gist.github.com/alishir/23d2bf5358ef138d1c1f2cfa72cde028 > > Regards, > Ali > > > _______________________________________________ > 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 Jun 3 04:04:59 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Mon, 3 Jun 2019 11:04:59 +0300 Subject: [OpenSIPS-Users] Removing a node from a cluster In-Reply-To: References: Message-ID: <48da57f1-2bc9-ee53-558f-fbca7de7a70c@opensips.org> Hi Vitalii, That's a good one and we are aware of it. Basically there is no nice way to remove a node from the cluster. The only way (and an unpleasant one) is to remove the node from DB, stop all nodes and start them again :( I will open a ticket for this. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 05/31/2019 06:44 PM, Vitalii Aleksandrov wrote: > Hi, > > What is the correct way of removing a cluster node? > I have a cluster with a number of proxies. Removed one of them from a > DB and called "opensipsctl fifo clusterer_reload" on all proxies. > Then checked "fifo clusterer_list" and removed node is still there > since it was learned from other nodes which still new about removed one. > Now removed node is no longer in a DB but all remained cluster nodes > try to establish connections to it. > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From podguiko at mail.ru Mon Jun 3 04:26:55 2019 From: podguiko at mail.ru (=?UTF-8?B?0J7Qu9C10LMg0J/QvtC00LPRg9C50LrQvg==?=) Date: Mon, 03 Jun 2019 11:26:55 +0300 Subject: [OpenSIPS-Users] =?utf-8?q?first=5Fhit=5Fcounter?= In-Reply-To: <75291aa0-0b65-3861-a3ca-edea2c24bcf1@opensips.org> References: <1559244737.510972547@f45.i.mail.ru> <75291aa0-0b65-3861-a3ca-edea2c24bcf1@opensips.org> Message-ID: <1559550415.262886137@f482.i.mail.ru> Thank you so much! >Понедельник, 3 июня 2019, 11:00 +03:00 от Bogdan-Andrei Iancu : > >Hi Oleg, > >The "first_hit_counter" tells you how many times that destination > was selected (from the first time/usage, and not via a failover) > for routing. > >In regards to the provisioning fields, see https://opensips.org/Documentation/Install-DBSchema-2-4#AEN4366 > >Regards, >Bogdan-Andrei Iancu > >OpenSIPS Founder and Developer > https://www.opensips-solutions.com >OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > >On 05/30/2019 10:32 PM, Олег Подгуйко > via Users wrote: >>Hello! >> >>The question is about dispatcher module. I'm interested in one >> parameter. >> >>Sometimes I use this command >> >>[opodguyko at xx-spx-1 ~]$ opensipsctl fifo ds_list >>PARTITION:: default >>SET:: 1 >>URI:: sip:10.10.31.21:5060 state=Active first_hit_counter=13 >>socket:: udp:10.10.31.11:5060 >>attr:: test >>[opodguyko at xx-spx-1 ~]$ >> >> >>Could you explain what does it means "first_hit_counter" >> parameter? >> >>I haven't found anything  at all about it in your documentation. >> >>It would also be interesting to understand why the following >> parameters are needed >> >>state(int) weight(string) priority(int) >> >>The documentation gives a very poor description. >>Thank you. >> >>-- >>Oleg Podguyko >> >>_______________________________________________ >>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 Jun 3 07:04:36 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Mon, 3 Jun 2019 14:04:36 +0300 Subject: [OpenSIPS-Users] Sending multiple request from OpenSIPS to multiple destinations In-Reply-To: References: Message-ID: <0fb76851-01cd-14ab-ff5e-d6eebd470327@opensips.org> Please keep the list CC'ed to the discussion. Parallel forking means to send an incoming INVITE to multiple SIP destinations in the same time - how / where the destinations are fetched from , it is not relevant. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/03/2019 01:56 PM, Ali Shirvani wrote: > Hi Bogdan-Andrei, > > Thanks for your reply. As I know parallel forking works when same user > registered with multiple devices. In this scenario we have multiple > users instead of same user. > Does parallel forking works for multiple users? I want to implement > simple PTT scenario. > > Regards, > Ali > > On Mon, Jun 3, 2019 at 12:33 PM Bogdan-Andrei Iancu > > wrote: > > Hi Ali, > > That is called SIP parallel forking and you can do it by using the > append_branch() function [1] or $branch variable [2] in order to > add multiple destinations for an INVITE. > > > [1] https://opensips.org/Documentation/Script-CoreFunctions-2-4#toc3 > [2] https://opensips.org/Documentation/Script-CoreVar-2-4#toc21 > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/01/2019 06:30 PM, Ali Shirvani wrote: >> Hi all, >> >> Is it possible to send multiple initial request to multiple >> destinations? something like b2bua but with multiple destinations. >> >> I draw the diagram in this gist: >> https://gist.github.com/alishir/23d2bf5358ef138d1c1f2cfa72cde028 >> >> Regards, >> Ali >> >> >> _______________________________________________ >> 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 Jun 3 07:13:57 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Mon, 3 Jun 2019 14:13:57 +0300 Subject: [OpenSIPS-Users] Load Balancer cluster Opensips 3.0 In-Reply-To: References: Message-ID: Please keep the list CC'ed to the discussion. Thanks for the info, it seems to be an OpenSIPS bug - the anycast token is missing in the locally generated requests (like this OPTIONS). Could you open a bug report on the github tracker please ? Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/03/2019 02:02 PM, Антон Ершов wrote: > Hi Bogdan, > node1 send > > 2019/06/03 16:01:17.484626 10.50.0.1:5060 -> > 10.7.0.201:5070 > OPTIONS sip:10.7.0.201:5070 SIP/2.0 > Via: SIP/2.0/UDP 10.50.0.1:5060;branch=z9hG4bK119b.69e9c536.0 > To: sip:10.7.0.201:5070 > From: >;tag=7f64a078bf34d12f31433ecf357bd91b-968b > CSeq: 10 OPTIONS > Call-ID: 0fa7a2ed14e0d2fe-14840 at 10.50.0.1 > > Max-Forwards: 70 > Content-Length: 0 > User-Agent: OpenSIPS (3.0.0 (x86_64/linux)) > > and does not receive an answer as it goes to the second node > > node 2 send and receive answer > > 2019/06/03 16:01:26.320354 10.50.0.1:5060 -> > 10.7.0.201:5070 > OPTIONS sip:10.7.0.201:5070 SIP/2.0 > Via: SIP/2.0/UDP 10.50.0.1:5060;branch=z9hG4bK894b.277e074.0 > To: sip:10.7.0.201:5070 > From: >;tag=7f64a078bf34d12f31433ecf357bd91b-9e0e > CSeq: 10 OPTIONS > Call-ID: 73aebff26b2035c7-17475 at 10.50.0.1 > > Max-Forwards: 70 > Content-Length: 0 > User-Agent: OpenSIPS (3.0.0 (x86_64/linux)) > > > 2019/06/03 15:52:26.490325 10.7.0.201:5070 -> > 10.50.0.1:5060 > SIP/2.0 200 OK > Via: SIP/2.0/UDP > 10.50.0.1:5060;rport=5060;received=10.50.0.1;branch=z9hG4bK894b.277e074.0 > Call-ID: 73aebff26b2035c7-17475 at 10.50.0.1 > > From: >;tag=7f64a078bf34d12f31433ecf357bd91b-9e0e > To: ;tag=z9hG4bK894b.277e074.0 > CSeq: 10 OPTIONS > Accept: application/dialog-info+xml, application/xpidf+xml, > application/cpim-pidf+xml, application/simple-message-summary, > application/pidf+xml, application/pidf+xml, > application/dialog-info+xml, application/simple-message-summary, > application/sdp, message/sipfrag;version=2.0 > Allow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, > BYE, CANCEL, UPDATE, PRACK, MESSAGE, REFER > Supported: 100rel, timer, replaces, norefersub > Accept-Encoding: text/plain > Accept-Language: en > Server: Asterisk PBX 16.1.0 > Content-Length: 0 > > my config node 1 > > loadmodule "load_balancer.so" > modparam("load_balancer", "db_url", > "postgres://postgres:1q2w3e4r at 10.3.0.1/opensips2 > ") > modparam("load_balancer", "probing_reply_codes", "501, 503, 403, 404") > modparam("load_balancer", "cluster_id", 1) > modparam("load_balancer", "cluster_sharing_tag", "node_SKN") > modparam("load_balancer", "probing_from", "sip:hchecker at 10.50.0.1 > ") > modparam("load_balancer", "probing_verbose", 1) > > and node 2 > > loadmodule "load_balancer.so" > modparam("load_balancer", "db_url", > "postgres://postgres:1q2w3e4r at 10.3.0.1/opensips2 > ") > modparam("load_balancer", "probing_reply_codes", "501, 503, 403, 404") > modparam("load_balancer", "cluster_id", 1) > modparam("load_balancer", "cluster_sharing_tag", "node_PRM") > modparam("load_balancer", "probing_from", "sip:hchecker at 10.50.0.1 > ") > modparam("load_balancer", "probing_verbose", 1) > > > maybe I misunderstood how it should work? > > > > пн, 3 июн. 2019 г. в 10:53, Bogdan-Andrei Iancu >: > > Hi Anton, > > That is an interesting combination - pinging via an anycast > interface. > > Could you paste here the OPTIONS and its reply, to check if it is > correctly built from the anycast perspective ? > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 05/27/2019 03:16 PM, Антон Ершов wrote: >> >> Hello friends! >> >> I'm testing new features of opensips 3. And I discovered the >> following situation. >> >> Configured cluster module in Anycast Сonfiguration. Load balanser >> module >> >> has cluster_sharing_tag. The lb module sends "options" to the >> host from the common address, but the answer goes to the nearest >> opensips node of the cluster. From what the remote host in lb is >> considered inaccessible. >> >> Something is not configured or I did not understand correctly how >> the load balanser should work in a cluster >> >> >> >> _______________________________________________ >> 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 aj.shirvani at gmail.com Mon Jun 3 07:44:54 2019 From: aj.shirvani at gmail.com (Ali Shirvani) Date: Mon, 3 Jun 2019 16:14:54 +0430 Subject: [OpenSIPS-Users] Sending multiple request from OpenSIPS to multiple destinations In-Reply-To: <0fb76851-01cd-14ab-ff5e-d6eebd470327@opensips.org> References: <0fb76851-01cd-14ab-ff5e-d6eebd470327@opensips.org> Message-ID: Sure, thanks for the clarification. Regards, Ali On Mon, Jun 3, 2019 at 3:34 PM Bogdan-Andrei Iancu wrote: > Please keep the list CC'ed to the discussion. > > > Parallel forking means to send an incoming INVITE to multiple SIP > destinations in the same time - how / where the destinations are fetched > from , it is not relevant. > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/03/2019 01:56 PM, Ali Shirvani wrote: > > Hi Bogdan-Andrei, > > Thanks for your reply. As I know parallel forking works when same user > registered with multiple devices. In this scenario we have multiple users > instead of same user. > Does parallel forking works for multiple users? I want to implement simple > PTT scenario. > > Regards, > Ali > > On Mon, Jun 3, 2019 at 12:33 PM Bogdan-Andrei Iancu > wrote: > >> Hi Ali, >> >> That is called SIP parallel forking and you can do it by using the >> append_branch() function [1] or $branch variable [2] in order to add >> multiple destinations for an INVITE. >> >> >> [1] https://opensips.org/Documentation/Script-CoreFunctions-2-4#toc3 >> [2] https://opensips.org/Documentation/Script-CoreVar-2-4#toc21 >> >> Regards, >> >> Bogdan-Andrei Iancu >> >> OpenSIPS Founder and Developer >> https://www.opensips-solutions.com >> OpenSIPS Summit 2019 >> https://www.opensips.org/events/Summit-2019Amsterdam/ >> >> On 06/01/2019 06:30 PM, Ali Shirvani wrote: >> >> Hi all, >> >> Is it possible to send multiple initial request to multiple destinations? >> something like b2bua but with multiple destinations. >> >> I draw the diagram in this gist: >> https://gist.github.com/alishir/23d2bf5358ef138d1c1f2cfa72cde028 >> >> Regards, >> Ali >> >> >> _______________________________________________ >> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Frank at wtild.com Mon Jun 3 09:55:27 2019 From: Frank at wtild.com (Frank Lee) Date: Mon, 3 Jun 2019 06:55:27 -0700 Subject: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) In-Reply-To: <4e582929-c1ba-eed5-a9a9-24b83a8bdb56@opensips.org> References: <00cb01d512b3$03f3e860$0bdbb920$@wtild.com> <4e582929-c1ba-eed5-a9a9-24b83a8bdb56@opensips.org> Message-ID: <028901d51a14$01fd4020$05f7c060$@wtild.com> Hello Bogdan, Thank you very much for looking into this for me. So you guys actually check the data type of each field before query is done? Do you know of anyone who has a TSQL script that generate all the tables for Opensips 2.4.5? I do see you guys have a link that has the table structure for opensips tables: https://opensips.org/html/docs/db/db-schema-devel.html#AEN9331 Is this information "complete" and is the data field type "correct" for 2.4.5? Because it seesm the table field type was used for 1.11 is "different" from the 2.4.5? And is that why my Microsoft sql server table that worked for 1.11 no longer works for 2.4.5? Frank From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Monday, June 3, 2019 12:27 AM To: OpenSIPS users mailling list ; Frank Lee Subject: Re: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) Hi Frank, There were no changes in the db_unixodbc driver in OpenSIPS for some time. Maybe something changed in the unixodbc driver for MS SQL. Based on the this log: core:db_table_version: invalid type (1) or nul (0) I see that that the "table_version" from the version table is returned as BIGINT, while OpenSIPS expects INT. Of course, this is something we can quickly adjust. In regards to the 'avp_db_query', could you post the level 3 logs corresponding to the query ? Maybe it will give us a clue. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 05/25/2019 07:33 AM, Frank Lee wrote: Hello, Was there some major change between version 1.11 and 2.4.5 on supporting of the ODBC connection of Microsoft SQL Server? It seems I had 1.11 running fine on SQL server (or at least partial table on sql server such as location table). But now I use 2.4.5 it seems all the module that uses odbc connector instead of the mysql connector it will have the error below core:db_table_version: invalid type (1) or nul (0) Thus, I changed all the module to use mysql connector (except the AVPOPS Module because I have custom query in the script which need to query the Microsoft sql server) which made Opensips start out fine. But as soon as it uses the avp_db_query in the script it seems it would not work. Alhtough I don't see any error in the syslog file (although I had log_level set to 3, do I need to set it higher?) Anyway, it just seems all the query/support to Microsoft SQL server doesn't run right in 2.4.5 vs 1.11. Is there some dependency that I am suppose to install which is different? I had my 1.11 run on Debian 7. Now we are moving to Azure cloud, I had run Ubuntu 18.04 since Debian 7 is not support on Azure. I had install odbc version 2.3.4 and also tdsodbc 1.00 Are these not to correct version to interface between 2.4.5 and Microsoft sql server (I tried both version msssql 2008 and 2016). Anyway, any pointer or help will be greatly appreciated! Thank you! From: Frank Lee [mailto:frank at wtild.com] Sent: Friday, May 24, 2019 10:58 AM To: 'users at lists.opensips.org ' Subject: Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) Hello, This is the first time I use this mail message, so let me know if this is not the correct way of posting question. Anyway, I am running Opensips 2.4.5 and when I use MYSQL database on all module, opensips runs fine. But as soon as I switch over the database source to use ODBC driver (which is linked to Microsoft SQL server 2016), I get this error. What is It mean? May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: ERROR:core:db_table_version: invalid type (1) or nul (0) version columns for subscriber May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: ERROR:core:db_check_table_version: querying version for table subscriber May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: ERROR:uri:mod_init: Invalid table version. I first created the MySQL table usinmg the command: opensipsdbctl create And then I transfer the tables to MSSQL using the: Microsoft SQL Server Migration Assistant 8.1 for MySQL All the table named corrected and all the index was created too. Thank you very much! Frank _______________________________________________ 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 harirkrishnan at gmail.com Mon Jun 3 16:09:01 2019 From: harirkrishnan at gmail.com (Hari Radhakrishnan) Date: Tue, 4 Jun 2019 06:09:01 +1000 Subject: [OpenSIPS-Users] dialog-dlg-repl capability State=not synced in a 2-node cluster, but dialog-prof-repl State=Ok Message-ID: Hi Opensips Team, We are facing an issue with a 2-node opensips cluster in opensips-2.4 running on Ubuntu. We would be really grateful if you could help with this. We have spent a few days putting DBG statements in the code, but didn't get anywhere significant. The setup uses db_text module, with two separate files (having same data), in each node. The opensips instances are running on AWS EC2 in the same subnet (security groups are enabled). With this setup (please see clusterer_list_cap output below), I get this. Ideally, we only require *dialog_replication_cluster* enabled. But if *profile_replication_cluster* is not enabled, the dialogs do not get replicated. Cluster:: 1 Capability:: dialog-dlg-repl State=not synced Capability:: dialog-prof-repl State=Ok This is an Active-Passive setup, with keepalived enabled to switch-over the Virtual IP. When I enable INFO logs, I see these messages on startup - *2019-06-04T05:14:53.909986+10:00 edge-opensips /usr/local/sbin/opensips[6519]: ERROR:dialog:dlg_replicate_profiles: Failed to replicate dialog profile* *2019-06-04T05:14:54.011064+10:00 edge-opensips /usr/local/sbin/opensips[6519]: ERROR:dialog:dlg_replicate_profiles: All destinations in cluster: 1 are down or probing* *2019-06-04T05:14:54.011096+10:00 edge-opensips /usr/local/sbin/opensips[6519]: ERROR:dialog:dlg_replicate_profiles: Failed to replicate dialog profile* *2019-06-04T05:14:54.013319+10:00 edge-opensips /usr/local/sbin/opensips[6414]: INFO:core:probe_max_sock_buff: using snd buffer of 416 kb* *2019-06-04T05:14:54.013336+10:00 edge-opensips /usr/local/sbin/opensips[6414]: INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 8* *2019-06-04T05:14:54.014216+10:00 edge-opensips /usr/local/sbin/opensips[6461]: INFO:clusterer:handle_internal_msg: Node [2] is UP* When I enable DBG logs, these messages appear. We saw that *dialog-dlg-repl* capability remains in *CAP_SYNC_PENDING state. * *2019-06-04T05:39:52.583634+10:00 edge-opensips /usr/local/sbin/opensips[8867]: DBG:clusterer:cl_register_cap: Registered capability: dialog-prof-repl* *2019-06-04T05:39:52.583651+10:00 edge-opensips /usr/local/sbin/opensips[8867]: DBG:clusterer:cl_register_cap: Registered capability: dialog-dlg-repl* *2019-06-04T05:39:52.583659+10:00 edge-opensips /usr/local/sbin/opensips[8867]: DBG:clusterer:cl_request_sync: requesting dialog-dlg-repl sync in cluster 1* *2019-06-04T05:39:52.583668+10:00 edge-opensips /usr/local/sbin/opensips[8867]: DBG:clusterer:cl_request_sync: failed to find sync source* The following logs keep running all the time (right after startup, without any calls). It appears that it is retrying to send some message but is stuck in a big loop due to a state which does not get changed. Similar logs are seen on the other node as well. *2019-06-04T05:39:53.599460+10:00 edge-opensips /usr/local/sbin/opensips[8919]: INFO:clusterer:handle_internal_msg: Node [2] is UP* *2019-06-04T05:39:53.599467+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:clusterer:match_node: matched node 2* *2019-06-04T05:39:53.599483+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:core:tcp_conn_get: con found in state 0* *2019-06-04T05:39:53.599485+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:core:tcp_conn_get: tcp connection found (0x7feee3585a98), acquiring fd* *2019-06-04T05:39:53.599492+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:core:tcp_conn_get: c= 0x7feee3585a98, n=16, Usock=303* *2019-06-04T05:39:53.599545+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:core:tcp_conn_get: after receive_fd: c= 0x7feee3585a98 n=8 fd=304* *2019-06-04T05:39:53.599552+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:proto_bin:proto_bin_send: sending via fd 304...* *2019-06-04T05:39:53.599560+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:proto_bin:async_tsend_stream: Async successful write from first try on 0x7feee3585a98* *2019-06-04T05:39:53.599562+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:proto_bin:proto_bin_send: after write: c= 0x7feee3585a98 n/len=48/48 fd=304* *2019-06-04T05:39:53.599565+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:clusterer:msg_send_retry: sent bin packet to node [2]* *2019-06-04T05:39:53.599574+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_read_req: tcp_read_req end* *2019-06-04T05:39:53.599689+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_read_req: Using the global ( per process ) buff* *2019-06-04T05:39:53.599698+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_parse_headers: received a COMPLETE message* *2019-06-04T05:39:53.599700+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_handle_req: completely received a message* *2019-06-04T05:39:53.599702+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_handle_req: Nothing more to read on TCP conn 0x7feee35857e0, currently in state 0* *2019-06-04T05:39:53.599706+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:core:call_callbacks: binary Packet CMD: 8. Capability: clusterer-internal* *2019-06-04T05:39:53.599709+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:clusterer:bin_rcv_cl_packets: received clusterer message from: 10.100.0.142:41737 with source id: 2 and cluster id: 1* *2019-06-04T05:39:53.599711+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:clusterer:handle_internal_msg: Received capability update with source [2]* *2019-06-04T05:39:53.599713+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:core:bin_pop_str: Popped: 'dialog-dlg-repl' [15]* *2019-06-04T05:39:53.599715+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:core:bin_pop_str: Popped: 'dialog-prof-repl' [16]* *2019-06-04T05:39:53.599718+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_read_req: tcp_read_req end* *2019-06-04T05:39:53.624271+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_read_req: Using the global ( per process ) buff* *2019-06-04T05:39:53.624280+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_parse_headers: received a COMPLETE message* *2019-06-04T05:39:53.624282+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_handle_req: completely received a message* *2019-06-04T05:39:53.624284+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_handle_req: Nothing more to read on TCP conn 0x7feee35857e0, currently in state 0* *2019-06-04T05:39:53.624288+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:core:call_callbacks: binary Packet CMD: 4. Capability: dialog-prof-repl* *2019-06-04T05:39:53.624291+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:clusterer:bin_rcv_mod_packets: received bin packet from: 10.100.0.142:41737 with source id: 2 and cluster id: 1* *2019-06-04T05:39:53.624295+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:core:bin_pop_str: Popped: 'inbound' [7]* *2019-06-04T05:39:53.624298+10:00 edge-opensips /usr/local/sbin/opensips[8919]: DBG:proto_bin:bin_read_req: tcp_read_req end* *2019-06-04T05:39:53.699828+10:00 edge-opensips /usr/local/sbin/opensips[8983]: DBG:clusterer:match_node: matched node 2* *2019-06-04T05:39:53.699852+10:00 edge-opensips /usr/local/sbin/opensips[8983]: DBG:core:tcp_conn_get: con found in state 0* *2019-06-04T05:39:53.699855+10:00 edge-opensips /usr/local/sbin/opensips[8983]: DBG:core:tcp_conn_get: tcp connection found (0x7feee3585a98), acquiring fd* *2019-06-04T05:39:53.699863+10:00 edge-opensips /usr/local/sbin/opensips[8983]: DBG:core:tcp_conn_get: c= 0x7feee3585a98, n=16, Usock=429* *2019-06-04T05:39:53.599515+10:00 edge-opensips /usr/local/sbin/opensips[8984]: message repeated 2 times: [ DBG:core:handle_worker: read response= 7feee3585a98, 1, fd -1 from 52 (8919)]* *2019-06-04T05:39:53.699885+10:00 edge-opensips /usr/local/sbin/opensips[8984]: DBG:core:handle_worker: read response= 7feee3585a98, 1, fd -1 from 116 (8983)* *2019-06-04T05:39:53.699899+10:00 edge-opensips /usr/local/sbin/opensips[8983]: DBG:core:tcp_conn_get: after receive_fd: c= 0x7feee3585a98 n=8 fd=8* *2019-06-04T05:39:53.699910+10:00 edge-opensips /usr/local/sbin/opensips[8983]: DBG:proto_bin:proto_bin_send: sending via fd 8...* *2019-06-04T05:39:53.699952+10:00 edge-opensips /usr/local/sbin/opensips[8983]: DBG:proto_bin:async_tsend_stream: Async successful write from first try on 0x7feee3585a98* *2019-06-04T05:39:53.699980+10:00 edge-opensips /usr/local/sbin/opensips[8983]: DBG:proto_bin:proto_bin_send: after write: c= 0x7feee3585a98 n/len=61/61 fd=8* *2019-06-04T05:39:53.699994+10:00 edge-opensips /usr/local/sbin/opensips[8983]: DBG:clusterer:msg_send_retry: sent bin packet to node [2]* ===================== SETUP ============================ # salt -G hosttype:edge-opensips cmd.run 'opensipsctl fifo clusterer_list' edge-opensips.10-100-0-142: Cluster:: 1 Node:: 1 DB_ID=-1 URL=bin:10.100.0.141:5555 Enabled=1 Link_state=Up Next_hop=1 Description=none edge-opensips.10-100-0-141: Cluster:: 1 Node:: 2 DB_ID=-1 URL=bin:10.100.0.142:5555 Enabled=1 Link_state=Up Next_hop=2 Description=none # salt -G hosttype:edge-opensips cmd.run 'opensipsctl fifo clusterer_list_topology' edge-opensips.10-100-0-141: Cluster:: 1 Node:: 1 Neighbours=2 Node:: 2 Neighbours=1 edge-opensips.10-100-0-142: Cluster:: 1 Node:: 2 Neighbours=1 Node:: 1 Neighbours=2 # salt -G hosttype:edge-opensips cmd.run 'opensipsctl fifo clusterer_list_cap' edge-opensips.10-100-0-142: Cluster:: 1 Capability:: dialog-dlg-repl State=not synced Capability:: dialog-prof-repl State=Ok edge-opensips.10-100-0-141: Cluster:: 1 Capability:: dialog-dlg-repl State=not synced Capability:: dialog-prof-repl State=Ok # salt -G hosttype:edge-opensips cmd.run 'netstat -anp | grep 5555' edge-opensips.10-100-0-141: tcp 0 0 10.100.0.141:5555 0.0.0.0:* LISTEN 6409/opensips tcp 0 0 10.100.0.141:38272 10.100.0.142:5555 ESTABLISHED 6526/opensips tcp 0 0 10.100.0.141:5555 10.100.0.142:38355 ESTABLISHED 6461/opensips edge-opensips.10-100-0-142: tcp 0 0 10.100.0.142:5555 0.0.0.0:* LISTEN 29658/opensips tcp 0 0 10.100.0.142:5555 10.100.0.141:38272 ESTABLISHED 29710/opensips tcp 0 0 10.100.0.142:38355 10.100.0.141:5555 ESTABLISHED 29775/opensips =========================================================== ******************* CONFIG ************************ loadmodule "proto_bin.so" modparam("proto_bin", "bin_port", 5555) modparam("proto_bin", "bin_send_timeout", 200) # CLUSTERER loadmodule "clusterer.so" modparam("clusterer", "db_mode", 0) modparam("clusterer", "db_url", "text:///etc/opensips/db/") modparam("clusterer", "db_table", "clusterer") modparam("clusterer", "ping_interval", 4) modparam("clusterer", "ping_timeout", 1000) # tried setting higher value modparam("clusterer", "node_timeout", 60) modparam("clusterer", "current_id", 1) modparam("clusterer", "current_info", "cluster_id=1,node_id=1,url=bin: 10.100.0.141:5555") modparam("clusterer", "neighbor_info", "cluster_id=1,node_id=2,url=bin: 10.100.0.142:5555") ## Dialog Module loadmodule "dialog.so" modparam("dialog", "dlg_match_mode", 1) # DID_FALLBACK best method for now modparam("dialog", "db_mode", 0) modparam("dialog", "db_url", "text:///etc/opensips/db/") modparam("dialog", "profiles_no_value", "inbound/b") # For dialog replication modparam("dialog", "profile_replication_cluster", 1) modparam("dialog", "dialog_replication_cluster", 1) modparam("dialog", "dlg_sharing_tag", "vip=active") # set to "vip=backup" in the other node --------------------------------- # DB_TEXT # cat /etc/opensips/db/clusterer id(int,auto) cluster_id(int) node_id(int) url(string) state(int) no_ping_retries(int) priority(int) sip_addr(string,null) flags(string,null) description(string,null) 10:1:1:bin\:10.100.0.141\:5555:1:3:50:NULL:NULL:primary 20:1:2:bin\:10.100.0.142\:5555:1:3:50:NULL:NULL:secondary ************************************************** best regards, Hari -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jun 4 12:42:21 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 4 Jun 2019 19:42:21 +0300 Subject: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) In-Reply-To: <028901d51a14$01fd4020$05f7c060$@wtild.com> References: <00cb01d512b3$03f3e860$0bdbb920$@wtild.com> <4e582929-c1ba-eed5-a9a9-24b83a8bdb56@opensips.org> <028901d51a14$01fd4020$05f7c060$@wtild.com> Message-ID: <980f8031-e0c0-115c-c47d-e68525f20346@opensips.org> Hi Frank, The official DB schema is here : https://github.com/OpenSIPS/opensips/tree/master/db/schema We use that in order to generate the DB engine specific schema, see: https://github.com/OpenSIPS/opensips/tree/master/scripts But as it is not native, there is nothing for MS SQL . Are you able to pull the latest master and check my fix (https://github.com/OpenSIPS/opensips/commit/dafa8f6a50958e1c6905621cceb2457f94163cc5 ) ? As I said, nothing changed in the OpenSIPS unixodbc support - but maybe something changed in the unixodbc lib or in the MS SQL driver. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/03/2019 04:55 PM, Frank Lee wrote: > > Hello Bogdan, > > Thank you very much for looking into this for me. So you guys > actually check the data type of each field before query is done? Do > you know of anyone who has a TSQL script that generate all the tables > for Opensips 2.4.5? I do see you guys have a link that has the table > structure for opensips tables: > > https://opensips.org/html/docs/db/db-schema-devel.html#AEN9331 > > Is this information “complete” and is the data field type “correct” > for 2.4.5? Because it seesm the table field type was used for 1.11 is > “different” from the 2.4.5? And is that why my Microsoft sql server > table that worked for 1.11 no longer works for 2.4.5? > > Frank > > *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] > *Sent:* Monday, June 3, 2019 12:27 AM > *To:* OpenSIPS users mailling list ; Frank > Lee > *Subject:* Re: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on > ODBC (MSSQL 2016 ) > > Hi Frank, > > There were no changes in the db_unixodbc driver in OpenSIPS for some > time. Maybe something changed in the unixodbc driver for MS SQL. > > Based on the this log: > core:db_table_version: invalid type (1) or nul (0) > > I see that that the "table_version" from the version table is returned > as BIGINT, while OpenSIPS expects INT. Of course, this is something we > can quickly adjust. > > In regards to the 'avp_db_query', could you post the level 3 logs > corresponding to the query ? Maybe it will give us a clue. > > Regards, > > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 05/25/2019 07:33 AM, Frank Lee wrote: > > Hello, > > Was there some major change between version 1.11 and 2.4.5 on > supporting of the ODBC connection of Microsoft SQL Server? It > seems I had 1.11 running fine on SQL server (or at least partial > table on sql server such as location table). But now I use 2.4.5 > it seems all the module that uses odbc connector instead of the > mysql connector it will have the error below > > core:db_table_version: invalid type (1) or nul (0) > > Thus, I changed all the module to use mysql connector (except the > AVPOPS Module because I have custom query in the script which need > to query the Microsoft sql server) which made Opensips start out > fine. But as soon as it uses the avp_db_query in the script it > seems it would not work. Alhtough I don’t see any error in the > syslog file (although I had log_level set to 3, do I need to set > it higher?) > > Anyway, it just seems all the query/support to Microsoft SQL > server doesn’t run right in 2.4.5 vs 1.11. > > Is there some dependency that I am suppose to install which is > different? > > I had my 1.11 run on Debian 7. Now we are moving to Azure cloud, > I had run Ubuntu 18.04 since Debian 7 is not support on Azure. > > I had install odbc version 2.3.4 and also tdsodbc 1.00 > > Are these not to correct version to interface between 2.4.5 and > Microsoft sql server (I tried both version msssql 2008 and 2016). > > Anyway, any pointer or help will be greatly appreciated! > > Thank you! > > *From:* Frank Lee [mailto:frank at wtild.com] > *Sent:* Friday, May 24, 2019 10:58 AM > *To:* 'users at lists.opensips.org ' > > *Subject:* Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) > > Hello, > > This is the first time I use this mail message, so let me know if > this is not the correct way of posting question. > > Anyway, I am running Opensips 2.4.5 and when I use MYSQL database > on all module, opensips runs fine. But as soon as I switch over > the database source to use ODBC driver (which is linked to > Microsoft SQL server 2016), I get this error. What is It mean? > > May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: > ERROR:core:db_table_version: invalid type (1) or nul (0) version > columns for subscriber > > May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: > ERROR:core:db_check_table_version: querying version for table > subscriber > > May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: > ERROR:uri:mod_init: Invalid table version. > > I first created the MySQL table usinmg the command: > > opensipsdbctl create > > And then I transfer the tables to MSSQL using the: > > Microsoft SQL Server Migration Assistant 8.1 for MySQL > > All the table named corrected and all the index was created too. > > Thank you very much! > > Frank > > > > > _______________________________________________ > > 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 volga629 at networklab.ca Tue Jun 4 22:16:55 2019 From: volga629 at networklab.ca (Slava Bendersky) Date: Tue, 4 Jun 2019 23:16:55 -0300 Subject: [OpenSIPS-Users] proto_smpp Message-ID: <973D8DBF-973D-49C4-86AF-6AA012FB9AF4@getmailspring.com> Hello Everyone, I am trying use proto_smpp and module produce errors in log. /usr/sbin/opensips[8876]: ERROR:proto_smpp:smpp_send_msg: cannot fetch connection for SMS_C (0) I checked mariadb and I don't think it even trying fetch it, because I am logging all queries and nothing in logs or SHOW FULL PROCESSLIST; MariaDB [opensips]> select * from smpp; +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ | id | name | ip | port | system_id | password | system_type | src_ton | src_npi | dst_ton | dst_npi | session_type | +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ | 1 | SMS_C | provider_ip | 2775 | username | pass | smpp | 2 | 1 | 2 | 1 | 1 | +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ 1 row in set (0.001 sec) Any help thank you volga629 -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Wed Jun 5 04:02:25 2019 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Wed, 5 Jun 2019 11:02:25 +0300 Subject: [OpenSIPS-Users] proto_smpp In-Reply-To: <973D8DBF-973D-49C4-86AF-6AA012FB9AF4@getmailspring.com> References: <973D8DBF-973D-49C4-86AF-6AA012FB9AF4@getmailspring.com> Message-ID: Hi, Slava! That error is logged when OpenSIPS tries to send a SMPP mode, but there's no available connection for it. I suspect OpenSIPS was not able to properly connect to the SMSC. Is this the only error you are seeing? Is this triggered periodically? Best regards, Răzvan On 6/5/19 5:16 AM, Slava Bendersky wrote: > Hello Everyone, > I am trying use proto_smpp and  module produce errors in log. > > /usr/sbin/opensips[8876]: ERROR:proto_smpp:smpp_send_msg: cannot fetch > connection for SMS_C (0) > > I checked mariadb and I don't think it even trying fetch it, because I > am logging all queries and nothing in logs or SHOW FULL PROCESSLIST; > MariaDB [opensips]> select * from smpp; > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > | id | name  | ip            | port | system_id | password | system_type > | src_ton | src_npi | dst_ton | dst_npi | session_type | > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > |  1 | SMS_C | provider_ip | 2775 | username   | pass | smpp > |       2 |       1 |       2 |       1 |            1 | > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > 1 row in set (0.001 sec) > > Any help thank you > volga629 > Sent from Mailspring > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com Meet the OpenSIPS team at the next OpenSIPS Summit: https://www.opensips.org/events From bogdan at opensips.org Wed Jun 5 07:29:20 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 5 Jun 2019 14:29:20 +0300 Subject: [OpenSIPS-Users] call_center module issues In-Reply-To: <55da4fab-ed98-5711-b49c-b6a7267250dd@yandex.ru> References: <7c5c9dbd-71a1-4e52-4262-8642e901ae72@opensips.org> <55da4fab-ed98-5711-b49c-b6a7267250dd@yandex.ru> Message-ID: Hi Mikhail, 1) I'm aware of the issue with the silence during the agent ringing - to be honest, we did some scripting workaround to use rtpproxy to inject a ringback tone to caller while we ring the agent :D. But the proposed solution is definitely better, still it needs to be evaluated if possible or not from the coding perspective (more or less, it depends on how the b2b works in OpenSIPS) Could you please take this report/issue/topic and create a new issue/ticket on the github tracker, so we can have it on the roadmap ? 2) I suppose the fault is related to frame 35-37 in callcenter.pcap, right ? Also please open a ticket here and attach the pcap + opensips logs in level 4 (dbg). Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 05/23/2019 08:25 PM, Mikhail wrote: > Hi Bogdan-Andrei, > > 1) > > Right. I'll try to explain more detailed what I mean: > > case 1 - as I see how opensips working > > Caller calls and Agent is not available > caller is listening intro > caller is listening music > Agent become available > Music stops, caller listening silence - Agent ringing > Agent don't answer within within defined period, for example 20 > seconds, and Caller is listening silence 20 seconds! > Call returned to queue > Caller starts to listening music from beginning, because opensips > makes new call to ivr server > Agent become available > Music stops, caller is listening silence - Agent ringing > in a 10 seconds Agent answers, so 10 seconds caller listen silence again. > > > case 2 - as I know how it should be > > Caller calls and Agent is not available > caller is listening intro > caller is listening music > Agent become available > Music don't stops, caller continue listening music without > interrupt - Agent ringing > Agent don't answer within within defined period, for example 20 > seconds, but Caller do not know about it, he sill listening music > without interrupt. > Call returned to queue, caller continue listening music without interrupt. > Agent become available > Music don't stops, caller continue listening music without > interrupt - Agent ringing > in a 10 seconds Agent answers, at this point caller stop listening > music and start talking to agent. > > > 2) > > I made 2 calls for test: > 1-st - direct call from caller to agent. Hold by caller and agent > works good. > 2-nd - call from caller to number 3001 routed to ivr by > cc_handle_call() command > call routed to intro 0081 and then to agent. Hold did not work. > I found that it seems that agent’s xLite did no receive some sip reply > and after 30 seconds after answer xLite sends bye by itself. > Also there are errors in opensips.log > > sip log captured with sngrep I uploaded to my server: > > video2dv.com/download/opensips/direct.pcap > video2dv.com/download/opensips/direct.txt > video2dv.com/download/opensips/callcenter.pcap > video2dv.com/download/opensips/callcenter.txt > video2dv.com/download/opensips/callcenter.log > > Regards, > Laba Mikhail > > 22.05.2019 10:09, Bogdan-Andrei Iancu wrote: >> Hi Anton, >> >> In regards to your experience with the call_center module: >> >> 1) You mean, while the call is ringing on the agent side, the caller >> gets dead-air, right ? >> >> 2) It should be working, do you have a pcap on that ? >> >> Regards, >> Bogdan-Andrei Iancu >> >> OpenSIPS Founder and Developer >> https://www.opensips-solutions.com >> OpenSIPS Summit 2019 >> https://www.opensips.org/events/Summit-2019Amsterdam/ >> On 04/28/2019 02:34 PM, Mikhail wrote: >>> >>> Hi Антон, >>> >>> in my tests I have working greeting and queue and I sill have >>> issues I described before: >>> >>> - when Invite is going to agent, caller hear silence, because >>> opensips stops call to medial server. >>> >>> - can't place on Hold either agent or caller, opensips sends "400 >>> Not Acceptable". >>> >>> I guess this is a feature/bugs in call_center module. >>> >>> My goal is to manage call_center with more then 1000 agents and >>> migrate from our current platform, but this troubles stops moving. >>> >>> It would be very cool if the developers or those who use the >>> call_center module have commented on these problems. >>> >>> >>> Laba Mikhail >>> >>> >>> 25.04.2019 16:12, Антон Ершов пишет: >>>> hi, did you manage to launch the call center module? >>>> >>>> _______________________________________________ >>>> 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 volga629 at networklab.ca Wed Jun 5 08:18:25 2019 From: volga629 at networklab.ca (Slava Bendersky) Date: Wed, 5 Jun 2019 08:18:25 -0400 (EDT) Subject: [OpenSIPS-Users] proto_smpp In-Reply-To: References: <973D8DBF-973D-49C4-86AF-6AA012FB9AF4@getmailspring.com> Message-ID: <881696120.214.1559737105320.JavaMail.zimbra@skillsearch.ca> Hello Razvan, After restart of opensips it shows in log that it connected to provider after that it start fill the log with bellow. Log level 4 is not helping no additional info in log. Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: INFO:proto_smpp:load_smpp_sessions_from_db: Loaded 1 SMSc servers Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: INFO:proto_smpp:send_bind: binding session with system_id "username" Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: INFO:core:probe_max_sock_buff: using snd buffer of 416 kb Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 5 Jun 5 04:15:40 smsc /usr/sbin/opensips[13977]: INFO:proto_smpp:child_init: initializing child #3 Jun 5 04:15:40 smsc /usr/sbin/opensips[13978]: INFO:proto_smpp:child_init: initializing child #4 Jun 5 04:15:40 smsc /usr/sbin/opensips[13979]: INFO:proto_smpp:child_init: initializing child #5 Jun 5 04:15:40 smsc /usr/sbin/opensips[13980]: INFO:proto_smpp:child_init: initializing child #6 Jun 5 04:15:40 smsc /usr/sbin/opensips[13981]: INFO:proto_smpp:child_init: initializing child #7 Jun 5 04:15:40 smsc /usr/sbin/opensips[13982]: INFO:proto_smpp:child_init: initializing child #8 Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: INFO:proto_smpp:smpp_conn_init: smpp_conn_init called Jun 5 04:15:40 smsc /usr/sbin/opensips[13983]: INFO:proto_smpp:child_init: initializing child #9 Jun 5 04:15:40 smsc /usr/sbin/opensips[13984]: INFO:proto_smpp:child_init: initializing child #10 Jun 5 04:15:40 smsc /usr/sbin/opensips[13985]: INFO:proto_smpp:child_init: initializing child #11 Jun 5 04:15:40 smsc /usr/sbin/opensips[13968]: INFO:proto_smpp:child_init: initializing child #0 Jun 5 04:15:40 smsc /usr/sbin/opensips[13986]: INFO:proto_smpp:child_init: initializing child #12 Jun 5 04:15:40 smsc /usr/sbin/opensips[13987]: INFO:proto_smpp:child_init: initializing child #13 Jun 5 04:15:40 smsc opensips[13966]: INFO:core:daemonize: pre-daemon process exiting with 0 Jun 5 04:15:40 smsc /usr/sbin/opensips[13979]: INFO:proto_smpp:handle_bind_transceiver_resp_cmd: Successfully bound transceiver "ISPT_SMPP03" volga629 From: "Răzvan Crainea" To: "OpenSIPS users mailling list" Sent: Wednesday, June 5, 2019 5:02:25 AM Subject: Re: [OpenSIPS-Users] proto_smpp Hi, Slava! That error is logged when OpenSIPS tries to send a SMPP mode, but there's no available connection for it. I suspect OpenSIPS was not able to properly connect to the SMSC. Is this the only error you are seeing? Is this triggered periodically? Best regards, Răzvan On 6/5/19 5:16 AM, Slava Bendersky wrote: > Hello Everyone, > I am trying use proto_smpp and module produce errors in log. > > /usr/sbin/opensips[8876]: ERROR:proto_smpp:smpp_send_msg: cannot fetch > connection for SMS_C (0) > > I checked mariadb and I don't think it even trying fetch it, because I > am logging all queries and nothing in logs or SHOW FULL PROCESSLIST; > MariaDB [opensips]> select * from smpp; > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > | id | name | ip | port | system_id | password | system_type > | src_ton | src_npi | dst_ton | dst_npi | session_type | > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > | 1 | SMS_C | provider_ip | 2775 | username | pass | smpp > | 2 | 1 | 2 | 1 | 1 | > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > 1 row in set (0.001 sec) > > Any help thank you > volga629 > Sent from Mailspring > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com Meet the OpenSIPS team at the next OpenSIPS Summit: https://www.opensips.org/events _______________________________________________ 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 Jun 5 08:54:43 2019 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Wed, 5 Jun 2019 15:54:43 +0300 Subject: [OpenSIPS-Users] proto_smpp In-Reply-To: <881696120.214.1559737105320.JavaMail.zimbra@skillsearch.ca> References: <973D8DBF-973D-49C4-86AF-6AA012FB9AF4@getmailspring.com> <881696120.214.1559737105320.JavaMail.zimbra@skillsearch.ca> Message-ID: <5e64f7b6-e94a-d6cf-43e8-810482d28a2a@opensips.org> Could you post all logs, including init and error on pastebin? On 6/5/19 3:18 PM, Slava Bendersky wrote: > > Hello Razvan, > After restart of opensips it shows in log that it connected to provider > after that it start fill the log with bellow. Log level 4 is not helping > no additional info in log. > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:proto_smpp:load_smpp_sessions_from_db: Loaded 1 SMSc servers > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:proto_smpp:send_bind: binding session with system_id "username" > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 5 > Jun  5 04:15:40 smsc /usr/sbin/opensips[13977]: > INFO:proto_smpp:child_init: initializing child #3 > Jun  5 04:15:40 smsc /usr/sbin/opensips[13978]: > INFO:proto_smpp:child_init: initializing child #4 > Jun  5 04:15:40 smsc /usr/sbin/opensips[13979]: > INFO:proto_smpp:child_init: initializing child #5 > Jun  5 04:15:40 smsc /usr/sbin/opensips[13980]: > INFO:proto_smpp:child_init: initializing child #6 > Jun  5 04:15:40 smsc /usr/sbin/opensips[13981]: > INFO:proto_smpp:child_init: initializing child #7 > Jun  5 04:15:40 smsc /usr/sbin/opensips[13982]: > INFO:proto_smpp:child_init: initializing child #8 > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:proto_smpp:smpp_conn_init: smpp_conn_init called > Jun  5 04:15:40 smsc /usr/sbin/opensips[13983]: > INFO:proto_smpp:child_init: initializing child #9 > Jun  5 04:15:40 smsc /usr/sbin/opensips[13984]: > INFO:proto_smpp:child_init: initializing child #10 > Jun  5 04:15:40 smsc /usr/sbin/opensips[13985]: > INFO:proto_smpp:child_init: initializing child #11 > Jun  5 04:15:40 smsc /usr/sbin/opensips[13968]: > INFO:proto_smpp:child_init: initializing child #0 > Jun  5 04:15:40 smsc /usr/sbin/opensips[13986]: > INFO:proto_smpp:child_init: initializing child #12 > Jun  5 04:15:40 smsc /usr/sbin/opensips[13987]: > INFO:proto_smpp:child_init: initializing child #13 > Jun  5 04:15:40 smsc opensips[13966]: INFO:core:daemonize: pre-daemon > process exiting with 0 > Jun  5 04:15:40 smsc /usr/sbin/opensips[13979]: > INFO:proto_smpp:handle_bind_transceiver_resp_cmd: Successfully bound > transceiver "ISPT_SMPP03" > > volga629 > ------------------------------------------------------------------------ > *From: *"Răzvan Crainea" > *To: *"OpenSIPS users mailling list" > *Sent: *Wednesday, June 5, 2019 5:02:25 AM > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > Hi, Slava! > > That error is logged when OpenSIPS tries to send a SMPP mode, but > there's no available connection for it. I suspect OpenSIPS was not able > to properly connect to the SMSC. > Is this the only error you are seeing? Is this triggered periodically? > > Best regards, > Răzvan > > On 6/5/19 5:16 AM, Slava Bendersky wrote: > > Hello Everyone, > > I am trying use proto_smpp and  module produce errors in log. > > > > /usr/sbin/opensips[8876]: ERROR:proto_smpp:smpp_send_msg: cannot fetch > > connection for SMS_C (0) > > > > I checked mariadb and I don't think it even trying fetch it, because I > > am logging all queries and nothing in logs or SHOW FULL PROCESSLIST; > > MariaDB [opensips]> select * from smpp; > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > | id | name  | ip            | port | system_id | password | system_type > > | src_ton | src_npi | dst_ton | dst_npi | session_type | > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > |  1 | SMS_C | provider_ip | 2775 | username   | pass | smpp > > |       2 |       1 |       2 |       1 |            1 | > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > 1 row in set (0.001 sec) > > > > Any help thank you > > volga629 > > Sent from Mailspring > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > -- > Răzvan Crainea > OpenSIPS Core Developer >    http://www.opensips-solutions.com > Meet the OpenSIPS team at the next OpenSIPS Summit: >    https://www.opensips.org/events > > _______________________________________________ > 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 > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com Meet the OpenSIPS team at the next OpenSIPS Summit: https://www.opensips.org/events From Frank at wtild.com Wed Jun 5 09:22:42 2019 From: Frank at wtild.com (Frank Lee) Date: Wed, 5 Jun 2019 06:22:42 -0700 Subject: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) In-Reply-To: <980f8031-e0c0-115c-c47d-e68525f20346@opensips.org> References: <00cb01d512b3$03f3e860$0bdbb920$@wtild.com> <4e582929-c1ba-eed5-a9a9-24b83a8bdb56@opensips.org> <028901d51a14$01fd4020$05f7c060$@wtild.com> <980f8031-e0c0-115c-c47d-e68525f20346@opensips.org> Message-ID: <007401d51ba1$c3471d80$49d55880$@wtild.com> Hello Bogdan, Thank you very much for your help. I will try out and see about the "int" type and my driver. So mostly in the code, when this error happens, are you guys looking for "int" type or do you check all type of all fields (e.g. Char has to be the right length or bit field) Thank you! From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Tuesday, June 4, 2019 9:42 AM To: Frank Lee ; 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) Hi Frank, The official DB schema is here : https://github.com/OpenSIPS/opensips/tree/master/db/schema We use that in order to generate the DB engine specific schema, see: https://github.com/OpenSIPS/opensips/tree/master/scripts But as it is not native, there is nothing for MS SQL . Are you able to pull the latest master and check my fix (https://github.com/OpenSIPS/opensips/commit/dafa8f6a50958e1c6905621cceb2457 f94163cc5 ) ? As I said, nothing changed in the OpenSIPS unixodbc support - but maybe something changed in the unixodbc lib or in the MS SQL driver. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/03/2019 04:55 PM, Frank Lee wrote: Hello Bogdan, Thank you very much for looking into this for me. So you guys actually check the data type of each field before query is done? Do you know of anyone who has a TSQL script that generate all the tables for Opensips 2.4.5? I do see you guys have a link that has the table structure for opensips tables: https://opensips.org/html/docs/db/db-schema-devel.html#AEN9331 Is this information "complete" and is the data field type "correct" for 2.4.5? Because it seesm the table field type was used for 1.11 is "different" from the 2.4.5? And is that why my Microsoft sql server table that worked for 1.11 no longer works for 2.4.5? Frank From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Monday, June 3, 2019 12:27 AM To: OpenSIPS users mailling list ; Frank Lee Subject: Re: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) Hi Frank, There were no changes in the db_unixodbc driver in OpenSIPS for some time. Maybe something changed in the unixodbc driver for MS SQL. Based on the this log: core:db_table_version: invalid type (1) or nul (0) I see that that the "table_version" from the version table is returned as BIGINT, while OpenSIPS expects INT. Of course, this is something we can quickly adjust. In regards to the 'avp_db_query', could you post the level 3 logs corresponding to the query ? Maybe it will give us a clue. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 05/25/2019 07:33 AM, Frank Lee wrote: Hello, Was there some major change between version 1.11 and 2.4.5 on supporting of the ODBC connection of Microsoft SQL Server? It seems I had 1.11 running fine on SQL server (or at least partial table on sql server such as location table). But now I use 2.4.5 it seems all the module that uses odbc connector instead of the mysql connector it will have the error below core:db_table_version: invalid type (1) or nul (0) Thus, I changed all the module to use mysql connector (except the AVPOPS Module because I have custom query in the script which need to query the Microsoft sql server) which made Opensips start out fine. But as soon as it uses the avp_db_query in the script it seems it would not work. Alhtough I don't see any error in the syslog file (although I had log_level set to 3, do I need to set it higher?) Anyway, it just seems all the query/support to Microsoft SQL server doesn't run right in 2.4.5 vs 1.11. Is there some dependency that I am suppose to install which is different? I had my 1.11 run on Debian 7. Now we are moving to Azure cloud, I had run Ubuntu 18.04 since Debian 7 is not support on Azure. I had install odbc version 2.3.4 and also tdsodbc 1.00 Are these not to correct version to interface between 2.4.5 and Microsoft sql server (I tried both version msssql 2008 and 2016). Anyway, any pointer or help will be greatly appreciated! Thank you! From: Frank Lee [mailto:frank at wtild.com] Sent: Friday, May 24, 2019 10:58 AM To: 'users at lists.opensips.org ' Subject: Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) Hello, This is the first time I use this mail message, so let me know if this is not the correct way of posting question. Anyway, I am running Opensips 2.4.5 and when I use MYSQL database on all module, opensips runs fine. But as soon as I switch over the database source to use ODBC driver (which is linked to Microsoft SQL server 2016), I get this error. What is It mean? May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: ERROR:core:db_table_version: invalid type (1) or nul (0) version columns for subscriber May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: ERROR:core:db_check_table_version: querying version for table subscriber May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: ERROR:uri:mod_init: Invalid table version. I first created the MySQL table usinmg the command: opensipsdbctl create And then I transfer the tables to MSSQL using the: Microsoft SQL Server Migration Assistant 8.1 for MySQL All the table named corrected and all the index was created too. Thank you very much! Frank _______________________________________________ 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 Jun 5 10:11:36 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 5 Jun 2019 17:11:36 +0300 Subject: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) In-Reply-To: <007401d51ba1$c3471d80$49d55880$@wtild.com> References: <00cb01d512b3$03f3e860$0bdbb920$@wtild.com> <4e582929-c1ba-eed5-a9a9-24b83a8bdb56@opensips.org> <028901d51a14$01fd4020$05f7c060$@wtild.com> <980f8031-e0c0-115c-c47d-e68525f20346@opensips.org> <007401d51ba1$c3471d80$49d55880$@wtild.com> Message-ID: Hi Frank, Usually we look for the most expected types (according to the DB schema we use)- there is not rule to try to cover all the types (maybe some of them have no meaning in conjunctionwith OpenSIPS). Give it a try and let me know. If it solves the problem, I can do a backport to 3.0 and 2.4 . Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/05/2019 04:22 PM, Frank Lee wrote: > > Hello Bogdan, > > Thank you very much for your help. I will try out and see about the > “int” type and my driver. So mostly in the code, when this error > happens, are you guys looking for “int” type or do you check all type > of all fields (e.g. Char has to be the right length or bit field) > > Thank you! > > *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] > *Sent:* Tuesday, June 4, 2019 9:42 AM > *To:* Frank Lee ; 'OpenSIPS users mailling list' > > *Subject:* Re: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on > ODBC (MSSQL 2016 ) > > Hi Frank, > > The official DB schema is here : > https://github.com/OpenSIPS/opensips/tree/master/db/schema > > We use that in order to generate the DB engine specific schema, see: > https://github.com/OpenSIPS/opensips/tree/master/scripts > > But as it is not native, there is nothing for MS SQL . > > Are you able to pull the latest master and check my fix > (https://github.com/OpenSIPS/opensips/commit/dafa8f6a50958e1c6905621cceb2457f94163cc5 > ) ? > > As I said, nothing changed in the OpenSIPS unixodbc support - but > maybe something changed in the unixodbc lib or in the MS SQL driver. > > Regards, > > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/03/2019 04:55 PM, Frank Lee wrote: > > Hello Bogdan, > > Thank you very much for looking into this for me. So you guys > actually check the data type of each field before query is done? > Do you know of anyone who has a TSQL script that generate all the > tables for Opensips 2.4.5? I do see you guys have a link that > has the table structure for opensips tables: > > https://opensips.org/html/docs/db/db-schema-devel.html#AEN9331 > > Is this information “complete” and is the data field type > “correct” for 2.4.5? Because it seesm the table field type was > used for 1.11 is “different” from the 2.4.5? And is that why my > Microsoft sql server table that worked for 1.11 no longer works > for 2.4.5? > > Frank > > *From:*Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] > *Sent:* Monday, June 3, 2019 12:27 AM > *To:* OpenSIPS users mailling list > ; Frank Lee > > *Subject:* Re: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on > ODBC (MSSQL 2016 ) > > Hi Frank, > > There were no changes in the db_unixodbc driver in OpenSIPS for > some time. Maybe something changed in the unixodbc driver for MS SQL. > > Based on the this log: > core:db_table_version: invalid type (1) or nul (0) > > I see that that the "table_version" from the version table is > returned as BIGINT, while OpenSIPS expects INT. Of course, this is > something we can quickly adjust. > > In regards to the 'avp_db_query', could you post the level 3 logs > corresponding to the query ? Maybe it will give us a clue. > > Regards, > > > > Bogdan-Andrei Iancu > > > > OpenSIPS Founder and Developer > > https://www.opensips-solutions.com > > OpenSIPS Summit 2019 > > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 05/25/2019 07:33 AM, Frank Lee wrote: > > Hello, > > Was there some major change between version 1.11 and 2.4.5 on > supporting of the ODBC connection of Microsoft SQL Server? It > seems I had 1.11 running fine on SQL server (or at least > partial table on sql server such as location table). But now > I use 2.4.5 it seems all the module that uses odbc connector > instead of the mysql connector it will have the error below > > core:db_table_version: invalid type (1) or nul (0) > > Thus, I changed all the module to use mysql connector (except > the AVPOPS Module because I have custom query in the script > which need to query the Microsoft sql server) which made > Opensips start out fine. But as soon as it uses the > avp_db_query in the script it seems it would not work. > Alhtough I don’t see any error in the syslog file (although I > had log_level set to 3, do I need to set it higher?) > > Anyway, it just seems all the query/support to Microsoft SQL > server doesn’t run right in 2.4.5 vs 1.11. > > Is there some dependency that I am suppose to install which is > different? > > I had my 1.11 run on Debian 7. Now we are moving to Azure > cloud, I had run Ubuntu 18.04 since Debian 7 is not support on > Azure. > > I had install odbc version 2.3.4 and also tdsodbc 1.00 > > Are these not to correct version to interface between 2.4.5 > and Microsoft sql server (I tried both version msssql 2008 and > 2016). > > Anyway, any pointer or help will be greatly appreciated! > > Thank you! > > *From:* Frank Lee [mailto:frank at wtild.com] > *Sent:* Friday, May 24, 2019 10:58 AM > *To:* 'users at lists.opensips.org > ' > > *Subject:* Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) > > Hello, > > This is the first time I use this mail message, so let me know > if this is not the correct way of posting question. > > Anyway, I am running Opensips 2.4.5 and when I use MYSQL > database on all module, opensips runs fine. But as soon as I > switch over the database source to use ODBC driver (which is > linked to Microsoft SQL server 2016), I get this error. What > is It mean? > > May 24 17:36:48 osipibDprimary > /usr/local/sbin/opensips[13534]: ERROR:core:db_table_version: > invalid type (1) or nul (0) version columns for subscriber > > May 24 17:36:48 osipibDprimary > /usr/local/sbin/opensips[13534]: > ERROR:core:db_check_table_version: querying version for table > subscriber > > May 24 17:36:48 osipibDprimary > /usr/local/sbin/opensips[13534]: ERROR:uri:mod_init: Invalid > table version. > > I first created the MySQL table usinmg the command: > > opensipsdbctl create > > And then I transfer the tables to MSSQL using the: > > Microsoft SQL Server Migration Assistant 8.1 for MySQL > > All the table named corrected and all the index was created too. > > Thank you very much! > > Frank > > > > > > _______________________________________________ > > 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 Jun 5 10:32:58 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 5 Jun 2019 17:32:58 +0300 Subject: [OpenSIPS-Users] Open Source Telecom Software Project Survey Message-ID: Hi everybody, Take 10-15 minutes and give Alan Quayle some useful data for his survey on Open Source Project in Telecom world. http://alanquayle.com/2019/05/open-source-telecom-software-project-survey/ Your opinion may be heard. PS: The Google Form is quite nice ;) Thanks! -- Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ From Frank at wtild.com Wed Jun 5 11:17:58 2019 From: Frank at wtild.com (Frank Lee) Date: Wed, 5 Jun 2019 08:17:58 -0700 Subject: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) In-Reply-To: References: <00cb01d512b3$03f3e860$0bdbb920$@wtild.com> <4e582929-c1ba-eed5-a9a9-24b83a8bdb56@opensips.org> <028901d51a14$01fd4020$05f7c060$@wtild.com> <980f8031-e0c0-115c-c47d-e68525f20346@opensips.org> <007401d51ba1$c3471d80$49d55880$@wtild.com> Message-ID: <009f01d51bb1$de585570$9b090050$@wtild.com> Hello Bogdan, Thank you for the explanation. The patch you did worked. Although I would think the "fault" would be on my part as I didn't realize the table field type was changed to BIGINT on the "new" table. I've checked the "version" table on my old database (that I used for 1.11), the field type was "INT". I guess the "conversion" program that I used (to convert MySQL tables to MSSQL), it used BIGINT instead. With that said, I guess, now I know what "invalid type (1) or nul (0)" error means, I can go ahead try to make sure that all field in the table (which I get this error), is same as the old tables. Thank you very much for your help! Frank From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Wednesday, June 5, 2019 7:12 AM To: Frank Lee ; 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) Hi Frank, Usually we look for the most expected types (according to the DB schema we use)- there is not rule to try to cover all the types (maybe some of them have no meaning in conjunction with OpenSIPS). Give it a try and let me know. If it solves the problem, I can do a backport to 3.0 and 2.4 . Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/05/2019 04:22 PM, Frank Lee wrote: Hello Bogdan, Thank you very much for your help. I will try out and see about the "int" type and my driver. So mostly in the code, when this error happens, are you guys looking for "int" type or do you check all type of all fields (e.g. Char has to be the right length or bit field) Thank you! From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Tuesday, June 4, 2019 9:42 AM To: Frank Lee ; 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) Hi Frank, The official DB schema is here : https://github.com/OpenSIPS/opensips/tree/master/db/schema We use that in order to generate the DB engine specific schema, see: https://github.com/OpenSIPS/opensips/tree/master/scripts But as it is not native, there is nothing for MS SQL . Are you able to pull the latest master and check my fix (https://github.com/OpenSIPS/opensips/commit/dafa8f6a50958e1c6905621cceb2457 f94163cc5 ) ? As I said, nothing changed in the OpenSIPS unixodbc support - but maybe something changed in the unixodbc lib or in the MS SQL driver. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/03/2019 04:55 PM, Frank Lee wrote: Hello Bogdan, Thank you very much for looking into this for me. So you guys actually check the data type of each field before query is done? Do you know of anyone who has a TSQL script that generate all the tables for Opensips 2.4.5? I do see you guys have a link that has the table structure for opensips tables: https://opensips.org/html/docs/db/db-schema-devel.html#AEN9331 Is this information "complete" and is the data field type "correct" for 2.4.5? Because it seesm the table field type was used for 1.11 is "different" from the 2.4.5? And is that why my Microsoft sql server table that worked for 1.11 no longer works for 2.4.5? Frank From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org] Sent: Monday, June 3, 2019 12:27 AM To: OpenSIPS users mailling list ; Frank Lee Subject: Re: [OpenSIPS-Users] Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) Hi Frank, There were no changes in the db_unixodbc driver in OpenSIPS for some time. Maybe something changed in the unixodbc driver for MS SQL. Based on the this log: core:db_table_version: invalid type (1) or nul (0) I see that that the "table_version" from the version table is returned as BIGINT, while OpenSIPS expects INT. Of course, this is something we can quickly adjust. In regards to the 'avp_db_query', could you post the level 3 logs corresponding to the query ? Maybe it will give us a clue. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 05/25/2019 07:33 AM, Frank Lee wrote: Hello, Was there some major change between version 1.11 and 2.4.5 on supporting of the ODBC connection of Microsoft SQL Server? It seems I had 1.11 running fine on SQL server (or at least partial table on sql server such as location table). But now I use 2.4.5 it seems all the module that uses odbc connector instead of the mysql connector it will have the error below core:db_table_version: invalid type (1) or nul (0) Thus, I changed all the module to use mysql connector (except the AVPOPS Module because I have custom query in the script which need to query the Microsoft sql server) which made Opensips start out fine. But as soon as it uses the avp_db_query in the script it seems it would not work. Alhtough I don't see any error in the syslog file (although I had log_level set to 3, do I need to set it higher?) Anyway, it just seems all the query/support to Microsoft SQL server doesn't run right in 2.4.5 vs 1.11. Is there some dependency that I am suppose to install which is different? I had my 1.11 run on Debian 7. Now we are moving to Azure cloud, I had run Ubuntu 18.04 since Debian 7 is not support on Azure. I had install odbc version 2.3.4 and also tdsodbc 1.00 Are these not to correct version to interface between 2.4.5 and Microsoft sql server (I tried both version msssql 2008 and 2016). Anyway, any pointer or help will be greatly appreciated! Thank you! From: Frank Lee [mailto:frank at wtild.com] Sent: Friday, May 24, 2019 10:58 AM To: 'users at lists.opensips.org ' Subject: Opensip 2.4.5 Subscriber module on ODBC (MSSQL 2016 ) Hello, This is the first time I use this mail message, so let me know if this is not the correct way of posting question. Anyway, I am running Opensips 2.4.5 and when I use MYSQL database on all module, opensips runs fine. But as soon as I switch over the database source to use ODBC driver (which is linked to Microsoft SQL server 2016), I get this error. What is It mean? May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: ERROR:core:db_table_version: invalid type (1) or nul (0) version columns for subscriber May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: ERROR:core:db_check_table_version: querying version for table subscriber May 24 17:36:48 osipibDprimary /usr/local/sbin/opensips[13534]: ERROR:uri:mod_init: Invalid table version. I first created the MySQL table usinmg the command: opensipsdbctl create And then I transfer the tables to MSSQL using the: Microsoft SQL Server Migration Assistant 8.1 for MySQL All the table named corrected and all the index was created too. Thank you very much! Frank _______________________________________________ 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 Jun 5 11:31:21 2019 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Wed, 5 Jun 2019 18:31:21 +0300 Subject: [OpenSIPS-Users] [RELEASE] OpenSIPS 2.2 End of Line Message-ID: Hi, everyone! Next week, on Tuesday, 11th of June 2019, we are planning to make a new minor release of the OpenSIPS 2.2 branch. The 2.2.8 version will be the last release of the 2.2 LTS branch, and will contain all the bug fixes gathered throughout the years. Starting with 12th of June we will no longer maintain this branch, and we will not do any commits or backport any fixes for it. Therefore we strongly suggest you to upgrade, if you haven't already, to the next stable LTS version, OpenSIPS 2.4. In the meantime, please let us know if there are any outstanding issues with 2.2.7 that we can sort out until the final release. Cheers, -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com Meet the OpenSIPS team at the next OpenSIPS Summit: https://www.opensips.org/events From carlos.oliva at invoxcontact.com Wed Jun 5 12:27:31 2019 From: carlos.oliva at invoxcontact.com (Carlos Oliva) Date: Wed, 5 Jun 2019 18:27:31 +0200 Subject: [OpenSIPS-Users] questions about tls_mgm DB provisioning Message-ID: Hello OpenSips Users: I'm trying to configure a OpenSips v2.4 proxy with TLS and certificate validation but I do not understand how to provision TLS using DB. With files everything works, the phone works well and validates the TLS certificate using a certificate signed by one of my authorized CAs on my ca_list file. But when I try to provision using DB with the same contents (CA_list, certificate, ciphers_list and private_key) I receive a "certificate verify failed" error. I counld not find any good documentation about using this in v2.4, and the TLS_MGM module documentation does not explain in deep how to get this working: https://opensips.org/html/docs/modules/2.4.x/tls_mgm.html Is there any extended documentation about how to use DB provisioning in TLS_MGM module? I'm trying to use only the default domain with the following parameters (private data is obfuscated) `id`, `domain`, `address`, `type`, `method`, `verify_cert`, `require_cert`, `certificate`, `private_key`, `crl_check_all`, `crl_dir`, `ca_list`, `ca_dir`, `cipher_list`, `dh_params`, `ec_curve` "8" "default" "0.0.0.0:5061" "1" "SSLv23" "1" "0" "-MY_CERTIFICATE" "MY_PRIVATE_KEY" "0" \N "MY_CA_LIST" \N "MY_CIPHER_LIST" \N \N "12" "default" "0.0.0.0:5061" "2" "SSLv23" "1" "0" "-MY_CERTIFICATE" "MY_PRIVATE_KEY" "0" \N "MY_CA_LIST" \N "MY_CIPHER_LIST" \N \N The CA of the cisco-linksys phones is on MY_CA_LIST (works if using files) but do not work if using DB. Only a note, as my ca_list is quite large, I had to modify tls_mgm table structure and use VARCHAR(1024) instead CHAR(255), but for my tests I think his is not the cause of the problem. This is the complete SSL error when I try to use DB. The macs and serial numbers are obfuscated. NOTICE:tls_mgm:verify_callback: depth = 0 NOTICE:tls_mgm:verify_callback: subject = /C=US/ST=0000000000/L=CBTXXXXXXXX/O=Cisco Systems/OU=cisco.com/CN=SPA508G, MAC: 0000000000, Serial: CBTXXXXXXXX/emailAddress= linksys-certadmin at cisco.com NOTICE:tls_mgm:verify_callback: verify error:num=20:unable to get local issuer certificate NOTICE:tls_mgm:verify_callback: something wrong with the cert ... error code is 20 (check x509_vfy.h) NOTICE:tls_mgm:verify_callback: verify return:0 ERROR:proto_tls:tls_accept: New TLS connection from 1.1.1.1:51757 failed to accept ERROR:proto_tls:tls_print_errstack: TLS errstack: error:1417C086:SSL routines:tls_process_client_certificate:certificate verify failed ERROR:proto_tls:tls_read_req: failed to do pre-tls reading Somebody can explain more deeply how to make tls_mgm work with DB? thanks and regrds, Carlos Oliva -------------- next part -------------- An HTML attachment was scrubbed... URL: From volga629 at networklab.ca Wed Jun 5 21:46:37 2019 From: volga629 at networklab.ca (Slava Bendersky) Date: Wed, 5 Jun 2019 21:46:37 -0400 (EDT) Subject: [OpenSIPS-Users] proto_smpp Message-ID: <1419646777.1297.1559785597245.JavaMail.zimbra@skillsearch.ca> Hello Razvan, Here are log in pastebin. [ https://paste.fedoraproject.org/paste/Ss4jWHGb5bDjGyn8v4AEMw | https://paste.fedoraproject.org/paste/Ss4jWHGb5bDjGyn8v4AEMw ] volga629 From: "Răzvan Crainea" To: "OpenSIPS users mailling list" Sent: Wednesday, June 5, 2019 9:54:43 AM Subject: Re: [OpenSIPS-Users] proto_smpp Could you post all logs, including init and error on pastebin? On 6/5/19 3:18 PM, Slava Bendersky wrote: > > Hello Razvan, > After restart of opensips it shows in log that it connected to provider > after that it start fill the log with bellow. Log level 4 is not helping > no additional info in log. > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:proto_smpp:load_smpp_sessions_from_db: Loaded 1 SMSc servers > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:proto_smpp:send_bind: binding session with system_id "username" > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 5 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13977]: > INFO:proto_smpp:child_init: initializing child #3 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13978]: > INFO:proto_smpp:child_init: initializing child #4 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13979]: > INFO:proto_smpp:child_init: initializing child #5 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13980]: > INFO:proto_smpp:child_init: initializing child #6 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13981]: > INFO:proto_smpp:child_init: initializing child #7 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13982]: > INFO:proto_smpp:child_init: initializing child #8 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:proto_smpp:smpp_conn_init: smpp_conn_init called > Jun 5 04:15:40 smsc /usr/sbin/opensips[13983]: > INFO:proto_smpp:child_init: initializing child #9 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13984]: > INFO:proto_smpp:child_init: initializing child #10 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13985]: > INFO:proto_smpp:child_init: initializing child #11 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13968]: > INFO:proto_smpp:child_init: initializing child #0 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13986]: > INFO:proto_smpp:child_init: initializing child #12 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13987]: > INFO:proto_smpp:child_init: initializing child #13 > Jun 5 04:15:40 smsc opensips[13966]: INFO:core:daemonize: pre-daemon > process exiting with 0 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13979]: > INFO:proto_smpp:handle_bind_transceiver_resp_cmd: Successfully bound > transceiver "ISPT_SMPP03" > > volga629 > ------------------------------------------------------------------------ > *From: *"Răzvan Crainea" > *To: *"OpenSIPS users mailling list" > *Sent: *Wednesday, June 5, 2019 5:02:25 AM > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > Hi, Slava! > > That error is logged when OpenSIPS tries to send a SMPP mode, but > there's no available connection for it. I suspect OpenSIPS was not able > to properly connect to the SMSC. > Is this the only error you are seeing? Is this triggered periodically? > > Best regards, > Răzvan > > On 6/5/19 5:16 AM, Slava Bendersky wrote: > > Hello Everyone, > > I am trying use proto_smpp and module produce errors in log. > > > > /usr/sbin/opensips[8876]: ERROR:proto_smpp:smpp_send_msg: cannot fetch > > connection for SMS_C (0) > > > > I checked mariadb and I don't think it even trying fetch it, because I > > am logging all queries and nothing in logs or SHOW FULL PROCESSLIST; > > MariaDB [opensips]> select * from smpp; > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > | id | name | ip | port | system_id | password | system_type > > | src_ton | src_npi | dst_ton | dst_npi | session_type | > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > | 1 | SMS_C | provider_ip | 2775 | username | pass | smpp > > | 2 | 1 | 2 | 1 | 1 | > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > 1 row in set (0.001 sec) > > > > Any help thank you > > volga629 > > Sent from Mailspring > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > -- > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > Meet the OpenSIPS team at the next OpenSIPS Summit: > https://www.opensips.org/events > > _______________________________________________ > 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 > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com Meet the OpenSIPS team at the next OpenSIPS Summit: https://www.opensips.org/events _______________________________________________ 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 volga629 at networklab.ca Wed Jun 5 22:28:51 2019 From: volga629 at networklab.ca (Slava Bendersky) Date: Wed, 5 Jun 2019 22:28:51 -0400 (EDT) Subject: [OpenSIPS-Users] proto_smpp In-Reply-To: <1419646777.1297.1559785597245.JavaMail.zimbra@skillsearch.ca> References: <1419646777.1297.1559785597245.JavaMail.zimbra@skillsearch.ca> Message-ID: <1527992389.1447.1559788131602.JavaMail.zimbra@skillsearch.ca> Hello Razvan, Here are more logs might be more detailed. [ https://paste.fedoraproject.org/paste/HXTHepUYsIF2Z9yjCmRR8w | https://paste.fedoraproject.org/paste/HXTHepUYsIF2Z9yjCmRR8w ] volga629 From: "Slava Bendersky" To: "OpenSIPS users mailling list" Sent: Wednesday, June 5, 2019 10:46:37 PM Subject: Re: [OpenSIPS-Users] proto_smpp Hello Razvan, Here are log in pastebin. [ https://paste.fedoraproject.org/paste/Ss4jWHGb5bDjGyn8v4AEMw | https://paste.fedoraproject.org/paste/Ss4jWHGb5bDjGyn8v4AEMw ] volga629 From: "Răzvan Crainea" To: "OpenSIPS users mailling list" Sent: Wednesday, June 5, 2019 9:54:43 AM Subject: Re: [OpenSIPS-Users] proto_smpp Could you post all logs, including init and error on pastebin? On 6/5/19 3:18 PM, Slava Bendersky wrote: > > Hello Razvan, > After restart of opensips it shows in log that it connected to provider > after that it start fill the log with bellow. Log level 4 is not helping > no additional info in log. > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:proto_smpp:load_smpp_sessions_from_db: Loaded 1 SMSc servers > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:proto_smpp:send_bind: binding session with system_id "username" > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 5 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13977]: > INFO:proto_smpp:child_init: initializing child #3 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13978]: > INFO:proto_smpp:child_init: initializing child #4 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13979]: > INFO:proto_smpp:child_init: initializing child #5 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13980]: > INFO:proto_smpp:child_init: initializing child #6 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13981]: > INFO:proto_smpp:child_init: initializing child #7 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13982]: > INFO:proto_smpp:child_init: initializing child #8 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:proto_smpp:smpp_conn_init: smpp_conn_init called > Jun 5 04:15:40 smsc /usr/sbin/opensips[13983]: > INFO:proto_smpp:child_init: initializing child #9 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13984]: > INFO:proto_smpp:child_init: initializing child #10 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13985]: > INFO:proto_smpp:child_init: initializing child #11 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13968]: > INFO:proto_smpp:child_init: initializing child #0 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13986]: > INFO:proto_smpp:child_init: initializing child #12 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13987]: > INFO:proto_smpp:child_init: initializing child #13 > Jun 5 04:15:40 smsc opensips[13966]: INFO:core:daemonize: pre-daemon > process exiting with 0 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13979]: > INFO:proto_smpp:handle_bind_transceiver_resp_cmd: Successfully bound > transceiver "ISPT_SMPP03" > > volga629 > ------------------------------------------------------------------------ > *From: *"Răzvan Crainea" > *To: *"OpenSIPS users mailling list" > *Sent: *Wednesday, June 5, 2019 5:02:25 AM > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > Hi, Slava! > > That error is logged when OpenSIPS tries to send a SMPP mode, but > there's no available connection for it. I suspect OpenSIPS was not able > to properly connect to the SMSC. > Is this the only error you are seeing? Is this triggered periodically? > > Best regards, > Răzvan > > On 6/5/19 5:16 AM, Slava Bendersky wrote: > > Hello Everyone, > > I am trying use proto_smpp and module produce errors in log. > > > > /usr/sbin/opensips[8876]: ERROR:proto_smpp:smpp_send_msg: cannot fetch > > connection for SMS_C (0) > > > > I checked mariadb and I don't think it even trying fetch it, because I > > am logging all queries and nothing in logs or SHOW FULL PROCESSLIST; > > MariaDB [opensips]> select * from smpp; > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > | id | name | ip | port | system_id | password | system_type > > | src_ton | src_npi | dst_ton | dst_npi | session_type | > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > | 1 | SMS_C | provider_ip | 2775 | username | pass | smpp > > | 2 | 1 | 2 | 1 | 1 | > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > 1 row in set (0.001 sec) > > > > Any help thank you > > volga629 > > Sent from Mailspring > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > -- > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > Meet the OpenSIPS team at the next OpenSIPS Summit: > https://www.opensips.org/events > > _______________________________________________ > 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 > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com Meet the OpenSIPS team at the next OpenSIPS Summit: https://www.opensips.org/events _______________________________________________ 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 alexei.vasilyev at gmail.com Thu Jun 6 01:51:40 2019 From: alexei.vasilyev at gmail.com (vasilevalex) Date: Wed, 5 Jun 2019 22:51:40 -0700 (MST) Subject: [OpenSIPS-Users] questions about tls_mgm DB provisioning In-Reply-To: References: Message-ID: <1559800300957-0.post@n2.nabble.com> Let me guess, you are using not the latest version of 2.4 branch DB provisioning of TLS configuration was incomplete. CA list took only first certificate from all the list. Certificate was loaded only first, not the chain. And yes, ca_list DB field was too small. But now, with 7fd38342bba96f732881dea769b9df9ce5ac3e03 and this 37a0d113296db7f009c3469f7f78940130b2f367 everything should be fine. It works for me, but it would be nice, if you can try this also :) ----- --- Alexey Vasilyev -- Sent from: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html From razvan at opensips.org Thu Jun 6 05:49:49 2019 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Thu, 6 Jun 2019 12:49:49 +0300 Subject: [OpenSIPS-Users] proto_smpp In-Reply-To: <1527992389.1447.1559788131602.JavaMail.zimbra@skillsearch.ca> References: <1419646777.1297.1559785597245.JavaMail.zimbra@skillsearch.ca> <1527992389.1447.1559788131602.JavaMail.zimbra@skillsearch.ca> Message-ID: <2ab1519b-dd1b-68ea-e5ea-864509f2e22a@opensips.org> Hi, Slava! Can you run `opensips-cli -x mi list_tcp_conns` immediately after OpenSIPS starts, and then when errors start appearing, then send us the output? Thanks, Răzvan On 6/6/19 5:28 AM, Slava Bendersky wrote: > Hello Razvan, > > Here are more logs might be more detailed. > > https://paste.fedoraproject.org/paste/HXTHepUYsIF2Z9yjCmRR8w > > volga629 > > > ------------------------------------------------------------------------ > *From: *"Slava Bendersky" > *To: *"OpenSIPS users mailling list" > *Sent: *Wednesday, June 5, 2019 10:46:37 PM > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > Hello Razvan, > Here are log in pastebin. > > https://paste.fedoraproject.org/paste/Ss4jWHGb5bDjGyn8v4AEMw > > volga629 > > ------------------------------------------------------------------------ > *From: *"Răzvan Crainea" > *To: *"OpenSIPS users mailling list" > *Sent: *Wednesday, June 5, 2019 9:54:43 AM > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > Could you post all logs, including init and error on pastebin? > > On 6/5/19 3:18 PM, Slava Bendersky wrote: > > > > Hello Razvan, > > After restart of opensips it shows in log that it connected to provider > > after that it start fill the log with bellow. Log level 4 is not helping > > no additional info in log. > > > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > > INFO:proto_smpp:load_smpp_sessions_from_db: Loaded 1 SMSc servers > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > > INFO:proto_smpp:send_bind: binding session with system_id "username" > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 5 > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13977]: > > INFO:proto_smpp:child_init: initializing child #3 > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13978]: > > INFO:proto_smpp:child_init: initializing child #4 > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13979]: > > INFO:proto_smpp:child_init: initializing child #5 > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13980]: > > INFO:proto_smpp:child_init: initializing child #6 > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13981]: > > INFO:proto_smpp:child_init: initializing child #7 > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13982]: > > INFO:proto_smpp:child_init: initializing child #8 > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > > INFO:proto_smpp:smpp_conn_init: smpp_conn_init called > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13983]: > > INFO:proto_smpp:child_init: initializing child #9 > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13984]: > > INFO:proto_smpp:child_init: initializing child #10 > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13985]: > > INFO:proto_smpp:child_init: initializing child #11 > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13968]: > > INFO:proto_smpp:child_init: initializing child #0 > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13986]: > > INFO:proto_smpp:child_init: initializing child #12 > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13987]: > > INFO:proto_smpp:child_init: initializing child #13 > > Jun  5 04:15:40 smsc opensips[13966]: INFO:core:daemonize: pre-daemon > > process exiting with 0 > > Jun  5 04:15:40 smsc /usr/sbin/opensips[13979]: > > INFO:proto_smpp:handle_bind_transceiver_resp_cmd: Successfully bound > > transceiver "ISPT_SMPP03" > > > > volga629 > > ------------------------------------------------------------------------ > > *From: *"Răzvan Crainea" > > *To: *"OpenSIPS users mailling list" > > *Sent: *Wednesday, June 5, 2019 5:02:25 AM > > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > > > Hi, Slava! > > > > That error is logged when OpenSIPS tries to send a SMPP mode, but > > there's no available connection for it. I suspect OpenSIPS was not able > > to properly connect to the SMSC. > > Is this the only error you are seeing? Is this triggered periodically? > > > > Best regards, > > Răzvan > > > > On 6/5/19 5:16 AM, Slava Bendersky wrote: > >  > Hello Everyone, > >  > I am trying use proto_smpp and  module produce errors in log. > >  > > >  > /usr/sbin/opensips[8876]: ERROR:proto_smpp:smpp_send_msg: cannot fetch > >  > connection for SMS_C (0) > >  > > >  > I checked mariadb and I don't think it even trying fetch it, because I > >  > am logging all queries and nothing in logs or SHOW FULL PROCESSLIST; > >  > MariaDB [opensips]> select * from smpp; > >  > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > >  > | id | name  | ip            | port | system_id | password | > system_type > >  > | src_ton | src_npi | dst_ton | dst_npi | session_type | > >  > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > >  > |  1 | SMS_C | provider_ip | 2775 | username   | pass | smpp > >  > |       2 |       1 |       2 |       1 |            1 | > >  > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > >  > 1 row in set (0.001 sec) > >  > > >  > Any help thank you > >  > volga629 > >  > Sent from Mailspring > >  > > >  > _______________________________________________ > >  > Users mailing list > >  > Users at lists.opensips.org > >  > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >  > > > > > -- > > Răzvan Crainea > > OpenSIPS Core Developer > >     http://www.opensips-solutions.com > > Meet the OpenSIPS team at the next OpenSIPS Summit: > >     https://www.opensips.org/events > > > > _______________________________________________ > > 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 > > > > -- > Răzvan Crainea > OpenSIPS Core Developer >    http://www.opensips-solutions.com > Meet the OpenSIPS team at the next OpenSIPS Summit: >    https://www.opensips.org/events > > _______________________________________________ > 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 > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com Meet the OpenSIPS team at the next OpenSIPS Summit: https://www.opensips.org/events From volga629 at networklab.ca Thu Jun 6 10:40:37 2019 From: volga629 at networklab.ca (Slava Bendersky) Date: Thu, 6 Jun 2019 10:40:37 -0400 (EDT) Subject: [OpenSIPS-Users] proto_smpp In-Reply-To: <2ab1519b-dd1b-68ea-e5ea-864509f2e22a@opensips.org> References: <1419646777.1297.1559785597245.JavaMail.zimbra@skillsearch.ca> <1527992389.1447.1559788131602.JavaMail.zimbra@skillsearch.ca> <2ab1519b-dd1b-68ea-e5ea-864509f2e22a@opensips.org> Message-ID: <1415248812.1908.1559832037522.JavaMail.zimbra@skillsearch.ca> Hello Razvan, Here tcp connection log [ https://paste.fedoraproject.org/paste/t-Ibs3BMVg7uPJqF1TCU7g | https://paste.fedoraproject.org/paste/t-Ibs3BMVg7uPJqF1TCU7g ] volga629 From: "Răzvan Crainea" To: "OpenSIPS users mailling list" Sent: Thursday, June 6, 2019 6:49:49 AM Subject: Re: [OpenSIPS-Users] proto_smpp Hi, Slava! Can you run `opensips-cli -x mi list_tcp_conns` immediately after OpenSIPS starts, and then when errors start appearing, then send us the output? Thanks, Răzvan On 6/6/19 5:28 AM, Slava Bendersky wrote: > Hello Razvan, > > Here are more logs might be more detailed. > > https://paste.fedoraproject.org/paste/HXTHepUYsIF2Z9yjCmRR8w > > volga629 > > > ------------------------------------------------------------------------ > *From: *"Slava Bendersky" > *To: *"OpenSIPS users mailling list" > *Sent: *Wednesday, June 5, 2019 10:46:37 PM > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > Hello Razvan, > Here are log in pastebin. > > https://paste.fedoraproject.org/paste/Ss4jWHGb5bDjGyn8v4AEMw > > volga629 > > ------------------------------------------------------------------------ > *From: *"Răzvan Crainea" > *To: *"OpenSIPS users mailling list" > *Sent: *Wednesday, June 5, 2019 9:54:43 AM > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > Could you post all logs, including init and error on pastebin? > > On 6/5/19 3:18 PM, Slava Bendersky wrote: > > > > Hello Razvan, > > After restart of opensips it shows in log that it connected to provider > > after that it start fill the log with bellow. Log level 4 is not helping > > no additional info in log. > > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > INFO:proto_smpp:load_smpp_sessions_from_db: Loaded 1 SMSc servers > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > INFO:proto_smpp:send_bind: binding session with system_id "username" > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 5 > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13977]: > > INFO:proto_smpp:child_init: initializing child #3 > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13978]: > > INFO:proto_smpp:child_init: initializing child #4 > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13979]: > > INFO:proto_smpp:child_init: initializing child #5 > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13980]: > > INFO:proto_smpp:child_init: initializing child #6 > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13981]: > > INFO:proto_smpp:child_init: initializing child #7 > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13982]: > > INFO:proto_smpp:child_init: initializing child #8 > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > INFO:proto_smpp:smpp_conn_init: smpp_conn_init called > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13983]: > > INFO:proto_smpp:child_init: initializing child #9 > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13984]: > > INFO:proto_smpp:child_init: initializing child #10 > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13985]: > > INFO:proto_smpp:child_init: initializing child #11 > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13968]: > > INFO:proto_smpp:child_init: initializing child #0 > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13986]: > > INFO:proto_smpp:child_init: initializing child #12 > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13987]: > > INFO:proto_smpp:child_init: initializing child #13 > > Jun 5 04:15:40 smsc opensips[13966]: INFO:core:daemonize: pre-daemon > > process exiting with 0 > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13979]: > > INFO:proto_smpp:handle_bind_transceiver_resp_cmd: Successfully bound > > transceiver "ISPT_SMPP03" > > > > volga629 > > ------------------------------------------------------------------------ > > *From: *"Răzvan Crainea" > > *To: *"OpenSIPS users mailling list" > > *Sent: *Wednesday, June 5, 2019 5:02:25 AM > > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > > > Hi, Slava! > > > > That error is logged when OpenSIPS tries to send a SMPP mode, but > > there's no available connection for it. I suspect OpenSIPS was not able > > to properly connect to the SMSC. > > Is this the only error you are seeing? Is this triggered periodically? > > > > Best regards, > > Răzvan > > > > On 6/5/19 5:16 AM, Slava Bendersky wrote: > > > Hello Everyone, > > > I am trying use proto_smpp and module produce errors in log. > > > > > > /usr/sbin/opensips[8876]: ERROR:proto_smpp:smpp_send_msg: cannot fetch > > > connection for SMS_C (0) > > > > > > I checked mariadb and I don't think it even trying fetch it, because I > > > am logging all queries and nothing in logs or SHOW FULL PROCESSLIST; > > > MariaDB [opensips]> select * from smpp; > > > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > > | id | name | ip | port | system_id | password | > system_type > > > | src_ton | src_npi | dst_ton | dst_npi | session_type | > > > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > > | 1 | SMS_C | provider_ip | 2775 | username | pass | smpp > > > | 2 | 1 | 2 | 1 | 1 | > > > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > > 1 row in set (0.001 sec) > > > > > > Any help thank you > > > volga629 > > > Sent from Mailspring > > > > > > _______________________________________________ > > > Users mailing list > > > Users at lists.opensips.org > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > -- > > Răzvan Crainea > > OpenSIPS Core Developer > > http://www.opensips-solutions.com > > Meet the OpenSIPS team at the next OpenSIPS Summit: > > https://www.opensips.org/events > > > > _______________________________________________ > > 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 > > > > -- > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > Meet the OpenSIPS team at the next OpenSIPS Summit: > https://www.opensips.org/events > > _______________________________________________ > 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 > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com Meet the OpenSIPS team at the next OpenSIPS Summit: https://www.opensips.org/events _______________________________________________ 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 Jun 6 10:47:09 2019 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Thu, 6 Jun 2019 17:47:09 +0300 Subject: [OpenSIPS-Users] proto_smpp In-Reply-To: <1415248812.1908.1559832037522.JavaMail.zimbra@skillsearch.ca> References: <1419646777.1297.1559785597245.JavaMail.zimbra@skillsearch.ca> <1527992389.1447.1559788131602.JavaMail.zimbra@skillsearch.ca> <2ab1519b-dd1b-68ea-e5ea-864509f2e22a@opensips.org> <1415248812.1908.1559832037522.JavaMail.zimbra@skillsearch.ca> Message-ID: <24a234be-8ee7-d494-d808-eae701a0d0bd@opensips.org> Can you please make a pcap of the communication, and also run OpenSIPS in debug mode, and send us the logs? Thanks! On 6/6/19 5:40 PM, Slava Bendersky wrote: > Hello Razvan, > Here tcp connection log > > https://paste.fedoraproject.org/paste/t-Ibs3BMVg7uPJqF1TCU7g > > volga629 > > ------------------------------------------------------------------------ > *From: *"Răzvan Crainea" > *To: *"OpenSIPS users mailling list" > *Sent: *Thursday, June 6, 2019 6:49:49 AM > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > Hi, Slava! > > Can you run `opensips-cli -x mi list_tcp_conns` immediately after > OpenSIPS starts, and then when errors start appearing, then send us the > output? > > Thanks, > Răzvan > > On 6/6/19 5:28 AM, Slava Bendersky wrote: > > Hello Razvan, > > > > Here are more logs might be more detailed. > > > > https://paste.fedoraproject.org/paste/HXTHepUYsIF2Z9yjCmRR8w > > > > volga629 > > > > > > ------------------------------------------------------------------------ > > *From: *"Slava Bendersky" > > *To: *"OpenSIPS users mailling list" > > *Sent: *Wednesday, June 5, 2019 10:46:37 PM > > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > > > Hello Razvan, > > Here are log in pastebin. > > > > https://paste.fedoraproject.org/paste/Ss4jWHGb5bDjGyn8v4AEMw > > > > volga629 > > > > ------------------------------------------------------------------------ > > *From: *"Răzvan Crainea" > > *To: *"OpenSIPS users mailling list" > > *Sent: *Wednesday, June 5, 2019 9:54:43 AM > > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > > > Could you post all logs, including init and error on pastebin? > > > > On 6/5/19 3:18 PM, Slava Bendersky wrote: > >  > > >  > Hello Razvan, > >  > After restart of opensips it shows in log that it connected to > provider > >  > after that it start fill the log with bellow. Log level 4 is not > helping > >  > no additional info in log. > >  > > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > >  > INFO:proto_smpp:load_smpp_sessions_from_db: Loaded 1 SMSc servers > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > >  > INFO:proto_smpp:send_bind: binding session with system_id "username" > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > >  > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > >  > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 5 > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13977]: > >  > INFO:proto_smpp:child_init: initializing child #3 > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13978]: > >  > INFO:proto_smpp:child_init: initializing child #4 > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13979]: > >  > INFO:proto_smpp:child_init: initializing child #5 > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13980]: > >  > INFO:proto_smpp:child_init: initializing child #6 > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13981]: > >  > INFO:proto_smpp:child_init: initializing child #7 > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13982]: > >  > INFO:proto_smpp:child_init: initializing child #8 > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13975]: > >  > INFO:proto_smpp:smpp_conn_init: smpp_conn_init called > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13983]: > >  > INFO:proto_smpp:child_init: initializing child #9 > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13984]: > >  > INFO:proto_smpp:child_init: initializing child #10 > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13985]: > >  > INFO:proto_smpp:child_init: initializing child #11 > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13968]: > >  > INFO:proto_smpp:child_init: initializing child #0 > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13986]: > >  > INFO:proto_smpp:child_init: initializing child #12 > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13987]: > >  > INFO:proto_smpp:child_init: initializing child #13 > >  > Jun  5 04:15:40 smsc opensips[13966]: INFO:core:daemonize: pre-daemon > >  > process exiting with 0 > >  > Jun  5 04:15:40 smsc /usr/sbin/opensips[13979]: > >  > INFO:proto_smpp:handle_bind_transceiver_resp_cmd: Successfully bound > >  > transceiver "ISPT_SMPP03" > >  > > >  > volga629 > >  > > ------------------------------------------------------------------------ > >  > *From: *"Răzvan Crainea" > >  > *To: *"OpenSIPS users mailling list" > >  > *Sent: *Wednesday, June 5, 2019 5:02:25 AM > >  > *Subject: *Re: [OpenSIPS-Users] proto_smpp > >  > > >  > Hi, Slava! > >  > > >  > That error is logged when OpenSIPS tries to send a SMPP mode, but > >  > there's no available connection for it. I suspect OpenSIPS was not > able > >  > to properly connect to the SMSC. > >  > Is this the only error you are seeing? Is this triggered periodically? > >  > > >  > Best regards, > >  > Răzvan > >  > > >  > On 6/5/19 5:16 AM, Slava Bendersky wrote: > >  >  > Hello Everyone, > >  >  > I am trying use proto_smpp and  module produce errors in log. > >  >  > > >  >  > /usr/sbin/opensips[8876]: ERROR:proto_smpp:smpp_send_msg: > cannot fetch > >  >  > connection for SMS_C (0) > >  >  > > >  >  > I checked mariadb and I don't think it even trying fetch it, > because I > >  >  > am logging all queries and nothing in logs or SHOW FULL > PROCESSLIST; > >  >  > MariaDB [opensips]> select * from smpp; > >  >  > > >  > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > >  >  > | id | name  | ip            | port | system_id | password | > > system_type > >  >  > | src_ton | src_npi | dst_ton | dst_npi | session_type | > >  >  > > >  > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > >  >  > |  1 | SMS_C | provider_ip | 2775 | username   | pass | smpp > >  >  > |       2 |       1 |       2 |       1 |            1 | > >  >  > > >  > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > >  >  > 1 row in set (0.001 sec) > >  >  > > >  >  > Any help thank you > >  >  > volga629 > >  >  > Sent from Mailspring > >  >  > > >  >  > _______________________________________________ > >  >  > Users mailing list > >  >  > Users at lists.opensips.org > >  >  > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > >  >  > > >  > > >  > -- > >  > Răzvan Crainea > >  > OpenSIPS Core Developer > >  >     http://www.opensips-solutions.com > >  > Meet the OpenSIPS team at the next OpenSIPS Summit: > >  >     https://www.opensips.org/events > >  > > >  > _______________________________________________ > >  > 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 > >  > > > > > -- > > Răzvan Crainea > > OpenSIPS Core Developer > >     http://www.opensips-solutions.com > > Meet the OpenSIPS team at the next OpenSIPS Summit: > >     https://www.opensips.org/events > > > > _______________________________________________ > > 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 > > > > -- > Răzvan Crainea > OpenSIPS Core Developer >    http://www.opensips-solutions.com > Meet the OpenSIPS team at the next OpenSIPS Summit: >    https://www.opensips.org/events > > _______________________________________________ > 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 > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com Meet the OpenSIPS team at the next OpenSIPS Summit: https://www.opensips.org/events From volga629 at networklab.ca Thu Jun 6 15:06:41 2019 From: volga629 at networklab.ca (Slava Bendersky) Date: Thu, 6 Jun 2019 15:06:41 -0400 (EDT) Subject: [OpenSIPS-Users] proto_smpp In-Reply-To: <24a234be-8ee7-d494-d808-eae701a0d0bd@opensips.org> References: <1419646777.1297.1559785597245.JavaMail.zimbra@skillsearch.ca> <1527992389.1447.1559788131602.JavaMail.zimbra@skillsearch.ca> <2ab1519b-dd1b-68ea-e5ea-864509f2e22a@opensips.org> <1415248812.1908.1559832037522.JavaMail.zimbra@skillsearch.ca> <24a234be-8ee7-d494-d808-eae701a0d0bd@opensips.org> Message-ID: <711411453.2272.1559848001203.JavaMail.zimbra@skillsearch.ca> Hello Razvan, I sent you pcap and here are some debug log. [ https://paste.fedoraproject.org/paste/H8lLXP13otKdL1wDR0jBzA | https://paste.fedoraproject.org/paste/H8lLXP13otKdL1wDR0jBzA ] Also interesting that I am trying use failure route, but it not working Script example [ https://paste.fedoraproject.org/paste/6dHJ281iKU~BY7~~CAuC7w | https://paste.fedoraproject.org/paste/6dHJ281iKU~BY7~~CAuC7w ] volga629 From: "Răzvan Crainea" To: "OpenSIPS users mailling list" Sent: Thursday, June 6, 2019 11:47:09 AM Subject: Re: [OpenSIPS-Users] proto_smpp Can you please make a pcap of the communication, and also run OpenSIPS in debug mode, and send us the logs? Thanks! On 6/6/19 5:40 PM, Slava Bendersky wrote: > Hello Razvan, > Here tcp connection log > > https://paste.fedoraproject.org/paste/t-Ibs3BMVg7uPJqF1TCU7g > > volga629 > > ------------------------------------------------------------------------ > *From: *"Răzvan Crainea" > *To: *"OpenSIPS users mailling list" > *Sent: *Thursday, June 6, 2019 6:49:49 AM > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > Hi, Slava! > > Can you run `opensips-cli -x mi list_tcp_conns` immediately after > OpenSIPS starts, and then when errors start appearing, then send us the > output? > > Thanks, > Răzvan > > On 6/6/19 5:28 AM, Slava Bendersky wrote: > > Hello Razvan, > > > > Here are more logs might be more detailed. > > > > https://paste.fedoraproject.org/paste/HXTHepUYsIF2Z9yjCmRR8w > > > > volga629 > > > > > > ------------------------------------------------------------------------ > > *From: *"Slava Bendersky" > > *To: *"OpenSIPS users mailling list" > > *Sent: *Wednesday, June 5, 2019 10:46:37 PM > > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > > > Hello Razvan, > > Here are log in pastebin. > > > > https://paste.fedoraproject.org/paste/Ss4jWHGb5bDjGyn8v4AEMw > > > > volga629 > > > > ------------------------------------------------------------------------ > > *From: *"Răzvan Crainea" > > *To: *"OpenSIPS users mailling list" > > *Sent: *Wednesday, June 5, 2019 9:54:43 AM > > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > > > Could you post all logs, including init and error on pastebin? > > > > On 6/5/19 3:18 PM, Slava Bendersky wrote: > > > > > > Hello Razvan, > > > After restart of opensips it shows in log that it connected to > provider > > > after that it start fill the log with bellow. Log level 4 is not > helping > > > no additional info in log. > > > > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > > INFO:proto_smpp:load_smpp_sessions_from_db: Loaded 1 SMSc servers > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > > INFO:proto_smpp:send_bind: binding session with system_id "username" > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 5 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13977]: > > > INFO:proto_smpp:child_init: initializing child #3 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13978]: > > > INFO:proto_smpp:child_init: initializing child #4 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13979]: > > > INFO:proto_smpp:child_init: initializing child #5 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13980]: > > > INFO:proto_smpp:child_init: initializing child #6 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13981]: > > > INFO:proto_smpp:child_init: initializing child #7 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13982]: > > > INFO:proto_smpp:child_init: initializing child #8 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > > INFO:proto_smpp:smpp_conn_init: smpp_conn_init called > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13983]: > > > INFO:proto_smpp:child_init: initializing child #9 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13984]: > > > INFO:proto_smpp:child_init: initializing child #10 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13985]: > > > INFO:proto_smpp:child_init: initializing child #11 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13968]: > > > INFO:proto_smpp:child_init: initializing child #0 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13986]: > > > INFO:proto_smpp:child_init: initializing child #12 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13987]: > > > INFO:proto_smpp:child_init: initializing child #13 > > > Jun 5 04:15:40 smsc opensips[13966]: INFO:core:daemonize: pre-daemon > > > process exiting with 0 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13979]: > > > INFO:proto_smpp:handle_bind_transceiver_resp_cmd: Successfully bound > > > transceiver "ISPT_SMPP03" > > > > > > volga629 > > > > ------------------------------------------------------------------------ > > > *From: *"Răzvan Crainea" > > > *To: *"OpenSIPS users mailling list" > > > *Sent: *Wednesday, June 5, 2019 5:02:25 AM > > > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > > > > > Hi, Slava! > > > > > > That error is logged when OpenSIPS tries to send a SMPP mode, but > > > there's no available connection for it. I suspect OpenSIPS was not > able > > > to properly connect to the SMSC. > > > Is this the only error you are seeing? Is this triggered periodically? > > > > > > Best regards, > > > Răzvan > > > > > > On 6/5/19 5:16 AM, Slava Bendersky wrote: > > > > Hello Everyone, > > > > I am trying use proto_smpp and module produce errors in log. > > > > > > > > /usr/sbin/opensips[8876]: ERROR:proto_smpp:smpp_send_msg: > cannot fetch > > > > connection for SMS_C (0) > > > > > > > > I checked mariadb and I don't think it even trying fetch it, > because I > > > > am logging all queries and nothing in logs or SHOW FULL > PROCESSLIST; > > > > MariaDB [opensips]> select * from smpp; > > > > > > > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > > > | id | name | ip | port | system_id | password | > > system_type > > > > | src_ton | src_npi | dst_ton | dst_npi | session_type | > > > > > > > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > > > | 1 | SMS_C | provider_ip | 2775 | username | pass | smpp > > > > | 2 | 1 | 2 | 1 | 1 | > > > > > > > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > > > 1 row in set (0.001 sec) > > > > > > > > Any help thank you > > > > volga629 > > > > Sent from Mailspring > > > > > > > > _______________________________________________ > > > > Users mailing list > > > > Users at lists.opensips.org > > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > > > > -- > > > Răzvan Crainea > > > OpenSIPS Core Developer > > > http://www.opensips-solutions.com > > > Meet the OpenSIPS team at the next OpenSIPS Summit: > > > https://www.opensips.org/events > > > > > > _______________________________________________ > > > 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 > > > > > > > -- > > Răzvan Crainea > > OpenSIPS Core Developer > > http://www.opensips-solutions.com > > Meet the OpenSIPS team at the next OpenSIPS Summit: > > https://www.opensips.org/events > > > > _______________________________________________ > > 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 > > > > -- > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > Meet the OpenSIPS team at the next OpenSIPS Summit: > https://www.opensips.org/events > > _______________________________________________ > 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 > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com Meet the OpenSIPS team at the next OpenSIPS Summit: https://www.opensips.org/events _______________________________________________ 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 farmorg at gmail.com Fri Jun 7 05:45:10 2019 From: farmorg at gmail.com (Mark Farmer) Date: Fri, 7 Jun 2019 10:45:10 +0100 Subject: [OpenSIPS-Users] t_on_reply not catching 183 Message-ID: Hi everyone, I'm trying to solve an issue related to reception of early media. I am getting 183 messages back to establish the audio path but OpenSIPS is passing the 183 back to an Asterisk box without changing the SDP "c" parameter. So Asterisk tries to send audio direct instead of to the rtpproxy. Doing some debugging, I can see that my reply route doesn't seem to be matching the 183 because I never get any logs from the reply route. Can anyone see anything wrong with it? I've checked the routing script & the reply route seems to be armed. onreply_route[DROUTING] { if (is_method("BYE|CANCEL")) { sip_trace("htid","d"); rtpproxy_unforce(); } #if ( $rs >= 200 ) #$acc_extra(to_usr) = $tU; if ($rs=~"(2[0-9][0-9])|(183)" && has_body("application/sdp")) { xlog("Processing reply $fU"); if (is_from_gw("1")) { xlog("Reply from Asterisk PBX"); setflag(INT_R); } else if (is_from_gw("2")) { xlog("Reply from Provider"); setflag(EXT_R); } } if (isflagset(INT_R)) { remove_hf("P-Asserted-Identity"); rtpproxy_answer("corwfei"); } else if (isflagset(EXT_R)) { rtpproxy_answer("corwfie"); } } Many thanks for any & all help. Mark. -------------- next part -------------- An HTML attachment was scrubbed... URL: From farmorg at gmail.com Fri Jun 7 05:53:11 2019 From: farmorg at gmail.com (Mark Farmer) Date: Fri, 7 Jun 2019 10:53:11 +0100 Subject: [OpenSIPS-Users] t_on_reply not catching 183 In-Reply-To: References: Message-ID: Sorry - version info: opensips -V version: opensips 2.4.5 (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, sigio_rt, select. git revision: d025b4f61 main.c compiled on 11:39:27 Apr 12 2019 with gcc 7 On Fri, 7 Jun 2019 at 10:45, Mark Farmer wrote: > Hi everyone, I'm trying to solve an issue related to reception of early > media. I am getting 183 messages back to establish the audio path but > OpenSIPS is passing the 183 back to an Asterisk box without changing the > SDP "c" parameter. So Asterisk tries to send audio direct instead of to the > rtpproxy. > > Doing some debugging, I can see that my reply route doesn't seem to be > matching the 183 because I never get any logs from the reply route. Can > anyone see anything wrong with it? I've checked the routing script & the > reply route seems to be armed. > > onreply_route[DROUTING] { > > if (is_method("BYE|CANCEL")) { > sip_trace("htid","d"); > rtpproxy_unforce(); > } > > #if ( $rs >= 200 ) > #$acc_extra(to_usr) = $tU; > > if ($rs=~"(2[0-9][0-9])|(183)" && has_body("application/sdp")) { > xlog("Processing reply $fU"); > if (is_from_gw("1")) { > xlog("Reply from Asterisk PBX"); > setflag(INT_R); > } else if (is_from_gw("2")) { > xlog("Reply from Provider"); > setflag(EXT_R); > } > } > > if (isflagset(INT_R)) { > remove_hf("P-Asserted-Identity"); > rtpproxy_answer("corwfei"); > } else if (isflagset(EXT_R)) { > rtpproxy_answer("corwfie"); > } > } > > > Many thanks for any & all help. > Mark. > > -- Mark Farmer farmorg at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From farmorg at gmail.com Fri Jun 7 07:10:25 2019 From: farmorg at gmail.com (Mark Farmer) Date: Fri, 7 Jun 2019 12:10:25 +0100 Subject: [OpenSIPS-Users] t_on_reply not catching 183 In-Reply-To: References: Message-ID: Never mind, it seems the issue was triggered by my soft client not using STUN Fixed that bit now :) Mark. On Fri, 7 Jun 2019 at 10:53, Mark Farmer wrote: > Sorry - version info: > > opensips -V > version: opensips 2.4.5 (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, sigio_rt, select. > git revision: d025b4f61 > main.c compiled on 11:39:27 Apr 12 2019 with gcc 7 > > > On Fri, 7 Jun 2019 at 10:45, Mark Farmer wrote: > >> Hi everyone, I'm trying to solve an issue related to reception of early >> media. I am getting 183 messages back to establish the audio path but >> OpenSIPS is passing the 183 back to an Asterisk box without changing the >> SDP "c" parameter. So Asterisk tries to send audio direct instead of to the >> rtpproxy. >> >> Doing some debugging, I can see that my reply route doesn't seem to be >> matching the 183 because I never get any logs from the reply route. Can >> anyone see anything wrong with it? I've checked the routing script & the >> reply route seems to be armed. >> >> onreply_route[DROUTING] { >> >> if (is_method("BYE|CANCEL")) { >> sip_trace("htid","d"); >> rtpproxy_unforce(); >> } >> >> #if ( $rs >= 200 ) >> #$acc_extra(to_usr) = $tU; >> >> if ($rs=~"(2[0-9][0-9])|(183)" && has_body("application/sdp")) { >> xlog("Processing reply $fU"); >> if (is_from_gw("1")) { >> xlog("Reply from Asterisk PBX"); >> setflag(INT_R); >> } else if (is_from_gw("2")) { >> xlog("Reply from Provider"); >> setflag(EXT_R); >> } >> } >> >> if (isflagset(INT_R)) { >> remove_hf("P-Asserted-Identity"); >> rtpproxy_answer("corwfei"); >> } else if (isflagset(EXT_R)) { >> rtpproxy_answer("corwfie"); >> } >> } >> >> >> Many thanks for any & all help. >> Mark. >> >> > > -- > Mark Farmer > farmorg at gmail.com > -- Mark Farmer farmorg at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From carlos.oliva at numintec.com Fri Jun 7 08:58:42 2019 From: carlos.oliva at numintec.com (Carlos Oliva) Date: Fri, 7 Jun 2019 14:58:42 +0200 Subject: [OpenSIPS-Users] questions about tls_mgm DB provisioning In-Reply-To: <1559800300957-0.post@n2.nabble.com> References: <1559800300957-0.post@n2.nabble.com> Message-ID: Thank you very much! I think is exactly what's happening. I'm using oficial deb packages, I'll try to recompile with the changes you mentioned. Is there any related issue in github? I can not find the commits 7fd38342bba96f732881dea769b9df9ce5ac3e03 and 37a0d113296db7f009c3469f7f78940130b2f367 I am sorry for my clumsiness. thanks and regards El jue., 6 jun. 2019 a las 7:53, vasilevalex () escribió: > Let me guess, you are using not the latest version of 2.4 branch > > DB provisioning of TLS configuration was incomplete. CA list took only > first > certificate from all the list. Certificate was loaded only first, not the > chain. And yes, ca_list DB field was too small. > > But now, with 7fd38342bba96f732881dea769b9df9ce5ac3e03 and this > 37a0d113296db7f009c3469f7f78940130b2f367 everything should be fine. > > It works for me, but it would be nice, if you can try this also :) > > > > ----- > --- > Alexey Vasilyev > -- > Sent from: > http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html > > _______________________________________________ > 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 alexei.vasilyev at gmail.com Fri Jun 7 09:07:27 2019 From: alexei.vasilyev at gmail.com (vasilevalex) Date: Fri, 7 Jun 2019 06:07:27 -0700 (MST) Subject: [OpenSIPS-Users] questions about tls_mgm DB provisioning In-Reply-To: References: <1559800300957-0.post@n2.nabble.com> Message-ID: <1559912847969-0.post@n2.nabble.com> Hi Carlos, Yes sure 2 issues on github: https://github.com/OpenSIPS/opensips/issues/1709 and https://github.com/OpenSIPS/opensips/issues/1714 There is patch for 2.4 in comments. ----- --- Alexey Vasilyev -- Sent from: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html From vladp at opensips.org Fri Jun 7 09:09:55 2019 From: vladp at opensips.org (Vlad Patrascu) Date: Fri, 7 Jun 2019 16:09:55 +0300 Subject: [OpenSIPS-Users] dialog-dlg-repl capability State=not synced in a 2-node cluster, but dialog-prof-repl State=Ok In-Reply-To: References: Message-ID: <771109e6-0a1e-187c-09bb-c3bec699f6fa@opensips.org> Hi Hari, I notice that you use 'db_mode' 0 and set the 'current_info'/'neighbor_info' modparams. In this case, there is no need to provision anything else in the DB, the nodes will automatically discover the topology. Usually this is useful when you want nodes dynamically joining the cluster. But the problem you're facing is probably caused by not setting any node in the cluster with the "seed" flag. You can read more about this here [1]. If everything is configured correctly, setting 'dialog_replication_cluster' should be enough in order to replicate dialogs. [1] https://opensips.org/html/docs/modules/3.0.x/clusterer.html#capabilities Regards, Vlad Patrascu OpenSIPS Developer http://www.opensips-solutions.com From vitalik.voip at gmail.com Fri Jun 7 12:33:59 2019 From: vitalik.voip at gmail.com (Vitalii Aleksandrov) Date: Fri, 7 Jun 2019 19:33:59 +0300 Subject: [OpenSIPS-Users] User location fields access Message-ID: <12954535-ae94-31cd-fbbf-eda9a0f010f1@gmail.com> Hi, Every contact of an AOR has a bunch of fields like Callid, Flags, Socket. Is there any way to reaf those additional fields of a contact after lookup()? From volga629 at networklab.ca Fri Jun 7 14:23:21 2019 From: volga629 at networklab.ca (Slava Bendersky) Date: Fri, 7 Jun 2019 14:23:21 -0400 (EDT) Subject: [OpenSIPS-Users] proto_smpp In-Reply-To: <711411453.2272.1559848001203.JavaMail.zimbra@skillsearch.ca> References: <1419646777.1297.1559785597245.JavaMail.zimbra@skillsearch.ca> <1527992389.1447.1559788131602.JavaMail.zimbra@skillsearch.ca> <2ab1519b-dd1b-68ea-e5ea-864509f2e22a@opensips.org> <1415248812.1908.1559832037522.JavaMail.zimbra@skillsearch.ca> <24a234be-8ee7-d494-d808-eae701a0d0bd@opensips.org> <711411453.2272.1559848001203.JavaMail.zimbra@skillsearch.ca> Message-ID: <1504281009.3918.1559931801246.JavaMail.zimbra@skillsearch.ca> Hello Razvan, I catch in log, message from provider and after trunk when down. I am not sure what is mean 00000006 Jun 7 10:02:34 smsc /usr/sbin/opensips[10821]: WARNING:proto_smpp:handle_smpp_msg: Unknown or unsupported command received 00000006 Jun 7 10:02:38 smsc /usr/sbin/opensips[10827]: ERROR:proto_smpp:smpp_send_msg: cannot fetch connection for SMS_C (0) Jun 7 10:02:43 smsc /usr/sbin/opensips[10823]: ERROR:proto_smpp:smpp_send_msg: cannot fetch connection for SMS_C (0) Jun 7 10:02:48 smsc /usr/sbin/opensips[10829]: ERROR:proto_smpp:smpp_send_msg: cannot fetch connection for SMS_C (0) Jun 7 10:02:53 smsc /usr/sbin/opensips[10829]: ERROR:proto_smpp:smpp_send_msg: cannot fetch connection for SMS_C (0) volga629 From: "Slava Bendersky" To: "OpenSIPS users mailling list" Sent: Thursday, June 6, 2019 4:06:41 PM Subject: Re: [OpenSIPS-Users] proto_smpp Hello Razvan, I sent you pcap and here are some debug log. [ https://paste.fedoraproject.org/paste/H8lLXP13otKdL1wDR0jBzA | https://paste.fedoraproject.org/paste/H8lLXP13otKdL1wDR0jBzA ] Also interesting that I am trying use failure route, but it not working Script example [ https://paste.fedoraproject.org/paste/6dHJ281iKU~BY7~~CAuC7w | https://paste.fedoraproject.org/paste/6dHJ281iKU~BY7~~CAuC7w ] volga629 From: "Răzvan Crainea" To: "OpenSIPS users mailling list" Sent: Thursday, June 6, 2019 11:47:09 AM Subject: Re: [OpenSIPS-Users] proto_smpp Can you please make a pcap of the communication, and also run OpenSIPS in debug mode, and send us the logs? Thanks! On 6/6/19 5:40 PM, Slava Bendersky wrote: > Hello Razvan, > Here tcp connection log > > https://paste.fedoraproject.org/paste/t-Ibs3BMVg7uPJqF1TCU7g > > volga629 > > ------------------------------------------------------------------------ > *From: *"Răzvan Crainea" > *To: *"OpenSIPS users mailling list" > *Sent: *Thursday, June 6, 2019 6:49:49 AM > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > Hi, Slava! > > Can you run `opensips-cli -x mi list_tcp_conns` immediately after > OpenSIPS starts, and then when errors start appearing, then send us the > output? > > Thanks, > Răzvan > > On 6/6/19 5:28 AM, Slava Bendersky wrote: > > Hello Razvan, > > > > Here are more logs might be more detailed. > > > > https://paste.fedoraproject.org/paste/HXTHepUYsIF2Z9yjCmRR8w > > > > volga629 > > > > > > ------------------------------------------------------------------------ > > *From: *"Slava Bendersky" > > *To: *"OpenSIPS users mailling list" > > *Sent: *Wednesday, June 5, 2019 10:46:37 PM > > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > > > Hello Razvan, > > Here are log in pastebin. > > > > https://paste.fedoraproject.org/paste/Ss4jWHGb5bDjGyn8v4AEMw > > > > volga629 > > > > ------------------------------------------------------------------------ > > *From: *"Răzvan Crainea" > > *To: *"OpenSIPS users mailling list" > > *Sent: *Wednesday, June 5, 2019 9:54:43 AM > > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > > > Could you post all logs, including init and error on pastebin? > > > > On 6/5/19 3:18 PM, Slava Bendersky wrote: > > > > > > Hello Razvan, > > > After restart of opensips it shows in log that it connected to > provider > > > after that it start fill the log with bellow. Log level 4 is not > helping > > > no additional info in log. > > > > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > > INFO:proto_smpp:load_smpp_sessions_from_db: Loaded 1 SMSc servers > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > > INFO:proto_smpp:send_bind: binding session with system_id "username" > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 5 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13977]: > > > INFO:proto_smpp:child_init: initializing child #3 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13978]: > > > INFO:proto_smpp:child_init: initializing child #4 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13979]: > > > INFO:proto_smpp:child_init: initializing child #5 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13980]: > > > INFO:proto_smpp:child_init: initializing child #6 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13981]: > > > INFO:proto_smpp:child_init: initializing child #7 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13982]: > > > INFO:proto_smpp:child_init: initializing child #8 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > > > INFO:proto_smpp:smpp_conn_init: smpp_conn_init called > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13983]: > > > INFO:proto_smpp:child_init: initializing child #9 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13984]: > > > INFO:proto_smpp:child_init: initializing child #10 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13985]: > > > INFO:proto_smpp:child_init: initializing child #11 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13968]: > > > INFO:proto_smpp:child_init: initializing child #0 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13986]: > > > INFO:proto_smpp:child_init: initializing child #12 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13987]: > > > INFO:proto_smpp:child_init: initializing child #13 > > > Jun 5 04:15:40 smsc opensips[13966]: INFO:core:daemonize: pre-daemon > > > process exiting with 0 > > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13979]: > > > INFO:proto_smpp:handle_bind_transceiver_resp_cmd: Successfully bound > > > transceiver "ISPT_SMPP03" > > > > > > volga629 > > > > ------------------------------------------------------------------------ > > > *From: *"Răzvan Crainea" > > > *To: *"OpenSIPS users mailling list" > > > *Sent: *Wednesday, June 5, 2019 5:02:25 AM > > > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > > > > > Hi, Slava! > > > > > > That error is logged when OpenSIPS tries to send a SMPP mode, but > > > there's no available connection for it. I suspect OpenSIPS was not > able > > > to properly connect to the SMSC. > > > Is this the only error you are seeing? Is this triggered periodically? > > > > > > Best regards, > > > Răzvan > > > > > > On 6/5/19 5:16 AM, Slava Bendersky wrote: > > > > Hello Everyone, > > > > I am trying use proto_smpp and module produce errors in log. > > > > > > > > /usr/sbin/opensips[8876]: ERROR:proto_smpp:smpp_send_msg: > cannot fetch > > > > connection for SMS_C (0) > > > > > > > > I checked mariadb and I don't think it even trying fetch it, > because I > > > > am logging all queries and nothing in logs or SHOW FULL > PROCESSLIST; > > > > MariaDB [opensips]> select * from smpp; > > > > > > > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > > > | id | name | ip | port | system_id | password | > > system_type > > > > | src_ton | src_npi | dst_ton | dst_npi | session_type | > > > > > > > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > > > | 1 | SMS_C | provider_ip | 2775 | username | pass | smpp > > > > | 2 | 1 | 2 | 1 | 1 | > > > > > > > > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > > > 1 row in set (0.001 sec) > > > > > > > > Any help thank you > > > > volga629 > > > > Sent from Mailspring > > > > > > > > _______________________________________________ > > > > Users mailing list > > > > Users at lists.opensips.org > > > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > > > > -- > > > Răzvan Crainea > > > OpenSIPS Core Developer > > > http://www.opensips-solutions.com > > > Meet the OpenSIPS team at the next OpenSIPS Summit: > > > https://www.opensips.org/events > > > > > > _______________________________________________ > > > 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 > > > > > > > -- > > Răzvan Crainea > > OpenSIPS Core Developer > > http://www.opensips-solutions.com > > Meet the OpenSIPS team at the next OpenSIPS Summit: > > https://www.opensips.org/events > > > > _______________________________________________ > > 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 > > > > -- > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > Meet the OpenSIPS team at the next OpenSIPS Summit: > https://www.opensips.org/events > > _______________________________________________ > 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 > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com Meet the OpenSIPS team at the next OpenSIPS Summit: https://www.opensips.org/events _______________________________________________ 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 rosenberg11219 at gmail.com Fri Jun 7 19:54:34 2019 From: rosenberg11219 at gmail.com (Schneur Rosenberg) Date: Sat, 8 Jun 2019 02:54:34 +0300 Subject: [OpenSIPS-Users] t_on_reply not catching 183 In-Reply-To: References: Message-ID: Are you missing a fix_natted_contact somewhere? That should in most cases eliminate the need of stun. On Fri, Jun 7, 2019, 2:14 PM Mark Farmer wrote: > Never mind, it seems the issue was triggered by my soft client not using > STUN > > Fixed that bit now :) > > Mark. > > > On Fri, 7 Jun 2019 at 10:53, Mark Farmer wrote: > >> Sorry - version info: >> >> opensips -V >> version: opensips 2.4.5 (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, sigio_rt, select. >> git revision: d025b4f61 >> main.c compiled on 11:39:27 Apr 12 2019 with gcc 7 >> >> >> On Fri, 7 Jun 2019 at 10:45, Mark Farmer wrote: >> >>> Hi everyone, I'm trying to solve an issue related to reception of early >>> media. I am getting 183 messages back to establish the audio path but >>> OpenSIPS is passing the 183 back to an Asterisk box without changing the >>> SDP "c" parameter. So Asterisk tries to send audio direct instead of to the >>> rtpproxy. >>> >>> Doing some debugging, I can see that my reply route doesn't seem to be >>> matching the 183 because I never get any logs from the reply route. Can >>> anyone see anything wrong with it? I've checked the routing script & the >>> reply route seems to be armed. >>> >>> onreply_route[DROUTING] { >>> >>> if (is_method("BYE|CANCEL")) { >>> sip_trace("htid","d"); >>> rtpproxy_unforce(); >>> } >>> >>> #if ( $rs >= 200 ) >>> #$acc_extra(to_usr) = $tU; >>> >>> if ($rs=~"(2[0-9][0-9])|(183)" && has_body("application/sdp")) { >>> xlog("Processing reply $fU"); >>> if (is_from_gw("1")) { >>> xlog("Reply from Asterisk PBX"); >>> setflag(INT_R); >>> } else if (is_from_gw("2")) { >>> xlog("Reply from Provider"); >>> setflag(EXT_R); >>> } >>> } >>> >>> if (isflagset(INT_R)) { >>> remove_hf("P-Asserted-Identity"); >>> rtpproxy_answer("corwfei"); >>> } else if (isflagset(EXT_R)) { >>> rtpproxy_answer("corwfie"); >>> } >>> } >>> >>> >>> Many thanks for any & all help. >>> Mark. >>> >>> >> >> -- >> Mark Farmer >> farmorg at gmail.com >> > > > -- > Mark Farmer > farmorg at gmail.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 Mon Jun 10 05:29:31 2019 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Mon, 10 Jun 2019 12:29:31 +0300 Subject: [OpenSIPS-Users] opensips and multiple rtpengine instances In-Reply-To: <79f8d6a9-a6cb-b17f-ae04-3d6419fa3fe6@gmail.com> References: <5fc440e3-7ae4-b2b0-04b0-687c823297ff@gmail.com> <79f8d6a9-a6cb-b17f-ae04-3d6419fa3fe6@gmail.com> Message-ID: <7dedf042-af16-1a26-78c5-5c6cd02e762f@opensips.org> The RTPengine module in OpenSIPS simply instructs the server to start/stop the sessions, and adds a few control flags. It does not, by any means, handle the RTP packets order. The module ensures that for a specific callid, *all* initial and sequential messages go to the same RTPengine go to the same instance, if, of course, you are using the same RTPEngine set for that call. So to be honest, I can't say I understand what's happening in your setup. Can you give us a few more indications? Best regards, Răzvan On 4/26/19 6:21 PM, Vitalii Aleksandrov wrote: > > It happened that rtpengine with multiple rtp workers sometimes receives > RTP packets ordered sequentially but forwards them a bit reordered > introducing out-of-order frames. With one rtp worker everything works > fine. The idea was to start a couple of single threaded rtpengines and > loadbalance from opensips. But it looks like not with the current > opensips/rtpengine module. >> I remember that somebody from smartvox  opened an issue on this (it >> was either Pete Kelly or John Quick). >> >> Pete,John >> do you recall ? >> >> Op vr 26 apr. 2019 om 15:15 schreef Vitalii Aleksandrov >> >: >> >> Hello opensips users, >> >> has anybody tried to configure opensips with multiple rtpengine >> sockets? >> >> Logically thinking offer/answer from initial INVITE/OK and from all >> in-dialog messages must go to the same instance and opensips can load >> balance only initial INVITEs. >> I briefly compared opensips/rtpengine and kamaio/rtpengine modules >> and >> found that this logic is present only in kamailio. Does it really >> work >> in opensips as expected? >> >> >> _______________________________________________ >> 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 > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com Meet the OpenSIPS team at the next OpenSIPS Summit: https://www.opensips.org/events From vitalik.voip at gmail.com Mon Jun 10 07:12:11 2019 From: vitalik.voip at gmail.com (Vitalii Aleksandrov) Date: Mon, 10 Jun 2019 14:12:11 +0300 Subject: [OpenSIPS-Users] opensips and multiple rtpengine instances In-Reply-To: <7dedf042-af16-1a26-78c5-5c6cd02e762f@opensips.org> References: <5fc440e3-7ae4-b2b0-04b0-687c823297ff@gmail.com> <79f8d6a9-a6cb-b17f-ae04-3d6419fa3fe6@gmail.com> <7dedf042-af16-1a26-78c5-5c6cd02e762f@opensips.org> Message-ID: <0f593faf-a23f-3482-ce53-0774a1b8e60b@gmail.com> Hi, > The RTPengine module in OpenSIPS simply instructs the server to > start/stop the sessions, and adds a few control flags. It does not, by > any means, handle the RTP packets order. Sure. It's an rtpengine's problem. Had a talk with Richard Fuchs and he explained what exactly happens in rtpengine. It can be rewritten a bit to avoid possible OOO packets generation, but that's completely another topic. Just explained why I need more than 1 rtpengine instance. > The module ensures that for a specific callid, *all* initial and > sequential messages go to the same RTPengine go to the same instance, > if, of course, you are using the same RTPEngine set for that call. > My bad. I've tested it and it works fine and all sip messages of a call were sent to the same rtpengine instance. Carefully checked rtpengine.c:select_rtpe_node() and finally understood how it selects an rtpengine node. Calculating it statelessly is even better than having a hash table with all active calls and their node_id like it's done in correspondent kamailio module. From farmorg at gmail.com Mon Jun 10 09:18:00 2019 From: farmorg at gmail.com (Mark Farmer) Date: Mon, 10 Jun 2019 14:18:00 +0100 Subject: [OpenSIPS-Users] t_on_reply not catching 183 In-Reply-To: References: Message-ID: Thanks. The soft client is registered to an Asterisk box so I don't think that's the issue here. On Sat, 8 Jun 2019 at 00:58, Schneur Rosenberg wrote: > Are you missing a fix_natted_contact somewhere? That should in most cases > eliminate the need of stun. > > On Fri, Jun 7, 2019, 2:14 PM Mark Farmer wrote: > >> Never mind, it seems the issue was triggered by my soft client not using >> STUN >> >> Fixed that bit now :) >> >> Mark. >> >> >> On Fri, 7 Jun 2019 at 10:53, Mark Farmer wrote: >> >>> Sorry - version info: >>> >>> opensips -V >>> version: opensips 2.4.5 (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, sigio_rt, select. >>> git revision: d025b4f61 >>> main.c compiled on 11:39:27 Apr 12 2019 with gcc 7 >>> >>> >>> On Fri, 7 Jun 2019 at 10:45, Mark Farmer wrote: >>> >>>> Hi everyone, I'm trying to solve an issue related to reception of early >>>> media. I am getting 183 messages back to establish the audio path but >>>> OpenSIPS is passing the 183 back to an Asterisk box without changing the >>>> SDP "c" parameter. So Asterisk tries to send audio direct instead of to the >>>> rtpproxy. >>>> >>>> Doing some debugging, I can see that my reply route doesn't seem to be >>>> matching the 183 because I never get any logs from the reply route. Can >>>> anyone see anything wrong with it? I've checked the routing script & the >>>> reply route seems to be armed. >>>> >>>> onreply_route[DROUTING] { >>>> >>>> if (is_method("BYE|CANCEL")) { >>>> sip_trace("htid","d"); >>>> rtpproxy_unforce(); >>>> } >>>> >>>> #if ( $rs >= 200 ) >>>> #$acc_extra(to_usr) = $tU; >>>> >>>> if ($rs=~"(2[0-9][0-9])|(183)" && has_body("application/sdp")) { >>>> xlog("Processing reply $fU"); >>>> if (is_from_gw("1")) { >>>> xlog("Reply from Asterisk PBX"); >>>> setflag(INT_R); >>>> } else if (is_from_gw("2")) { >>>> xlog("Reply from Provider"); >>>> setflag(EXT_R); >>>> } >>>> } >>>> >>>> if (isflagset(INT_R)) { >>>> remove_hf("P-Asserted-Identity"); >>>> rtpproxy_answer("corwfei"); >>>> } else if (isflagset(EXT_R)) { >>>> rtpproxy_answer("corwfie"); >>>> } >>>> } >>>> >>>> >>>> Many thanks for any & all help. >>>> Mark. >>>> >>>> >>> >>> -- >>> Mark Farmer >>> farmorg at gmail.com >>> >> >> >> -- >> Mark Farmer >> farmorg at gmail.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 > -- Mark Farmer farmorg at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From farmorg at gmail.com Mon Jun 10 09:23:17 2019 From: farmorg at gmail.com (Mark Farmer) Date: Mon, 10 Jun 2019 14:23:17 +0100 Subject: [OpenSIPS-Users] re-INVITE (Hold) looses audio Message-ID: Hi all I'm trying to solve an issue where if the call is placed on hold via a re-INVITE, my end stops the audio at that point so when another re-INVITE is received to resume the call, the audio does not restart. I can still hear the other party but they cannot hear me because I'm not sending any RTP any more. I'm really struggling to pin this one down. Can anyone give me any clues as to why this might be happening? I'm using OpenSIPS 2.4.5 with RTPProxy 2.0 Many thanks Mark. -- Mark Farmer farmorg at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Mon Jun 10 14:32:44 2019 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Mon, 10 Jun 2019 21:32:44 +0300 Subject: [OpenSIPS-Users] re-INVITE (Hold) looses audio In-Reply-To: References: Message-ID: <656c1c52-2dff-2b5e-5ceb-311eba285092@opensips.org> Hi, Mark! Are you engaging RTPProxy for the re-INVITEs too? Can you check if RTPProxy times out the session due to lack of audio from one side? You can see that in the logs. Best regards, Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 6/10/19 4:23 PM, Mark Farmer wrote: > Hi all > > I'm trying to solve an issue where if the call is placed on hold via a > re-INVITE, my end stops the audio at that point so when another > re-INVITE is received to resume the call, the audio does not restart. I > can still hear the other party but they cannot hear me because I'm not > sending any RTP any more. > > I'm really struggling to pin this one down. Can anyone give me any clues > as to why this might be happening? > > I'm using OpenSIPS 2.4.5 with RTPProxy 2.0 > > Many thanks > Mark. > > > -- > Mark Farmer > farmorg at gmail.com > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > From volga629 at skillsearch.ca Wed Jun 5 21:45:03 2019 From: volga629 at skillsearch.ca (Slava Bendersky) Date: Wed, 5 Jun 2019 21:45:03 -0400 (EDT) Subject: [OpenSIPS-Users] proto_smpp In-Reply-To: <5e64f7b6-e94a-d6cf-43e8-810482d28a2a@opensips.org> References: <973D8DBF-973D-49C4-86AF-6AA012FB9AF4@getmailspring.com> <881696120.214.1559737105320.JavaMail.zimbra@skillsearch.ca> <5e64f7b6-e94a-d6cf-43e8-810482d28a2a@opensips.org> Message-ID: <544542216.1288.1559785503507.JavaMail.zimbra@skillsearch.ca> Hello Razvan, Here are log in pastebin. [ https://paste.fedoraproject.org/paste/Ss4jWHGb5bDjGyn8v4AEMw | https://paste.fedoraproject.org/paste/Ss4jWHGb5bDjGyn8v4AEMw ] volga629 From: "Răzvan Crainea" To: "OpenSIPS users mailling list" Sent: Wednesday, June 5, 2019 9:54:43 AM Subject: Re: [OpenSIPS-Users] proto_smpp Could you post all logs, including init and error on pastebin? On 6/5/19 3:18 PM, Slava Bendersky wrote: > > Hello Razvan, > After restart of opensips it shows in log that it connected to provider > after that it start fill the log with bellow. Log level 4 is not helping > no additional info in log. > > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:proto_smpp:load_smpp_sessions_from_db: Loaded 1 SMSc servers > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:proto_smpp:send_bind: binding session with system_id "username" > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 5 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13977]: > INFO:proto_smpp:child_init: initializing child #3 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13978]: > INFO:proto_smpp:child_init: initializing child #4 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13979]: > INFO:proto_smpp:child_init: initializing child #5 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13980]: > INFO:proto_smpp:child_init: initializing child #6 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13981]: > INFO:proto_smpp:child_init: initializing child #7 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13982]: > INFO:proto_smpp:child_init: initializing child #8 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13975]: > INFO:proto_smpp:smpp_conn_init: smpp_conn_init called > Jun 5 04:15:40 smsc /usr/sbin/opensips[13983]: > INFO:proto_smpp:child_init: initializing child #9 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13984]: > INFO:proto_smpp:child_init: initializing child #10 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13985]: > INFO:proto_smpp:child_init: initializing child #11 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13968]: > INFO:proto_smpp:child_init: initializing child #0 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13986]: > INFO:proto_smpp:child_init: initializing child #12 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13987]: > INFO:proto_smpp:child_init: initializing child #13 > Jun 5 04:15:40 smsc opensips[13966]: INFO:core:daemonize: pre-daemon > process exiting with 0 > Jun 5 04:15:40 smsc /usr/sbin/opensips[13979]: > INFO:proto_smpp:handle_bind_transceiver_resp_cmd: Successfully bound > transceiver "ISPT_SMPP03" > > volga629 > ------------------------------------------------------------------------ > *From: *"Răzvan Crainea" > *To: *"OpenSIPS users mailling list" > *Sent: *Wednesday, June 5, 2019 5:02:25 AM > *Subject: *Re: [OpenSIPS-Users] proto_smpp > > Hi, Slava! > > That error is logged when OpenSIPS tries to send a SMPP mode, but > there's no available connection for it. I suspect OpenSIPS was not able > to properly connect to the SMSC. > Is this the only error you are seeing? Is this triggered periodically? > > Best regards, > Răzvan > > On 6/5/19 5:16 AM, Slava Bendersky wrote: > > Hello Everyone, > > I am trying use proto_smpp and module produce errors in log. > > > > /usr/sbin/opensips[8876]: ERROR:proto_smpp:smpp_send_msg: cannot fetch > > connection for SMS_C (0) > > > > I checked mariadb and I don't think it even trying fetch it, because I > > am logging all queries and nothing in logs or SHOW FULL PROCESSLIST; > > MariaDB [opensips]> select * from smpp; > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > | id | name | ip | port | system_id | password | system_type > > | src_ton | src_npi | dst_ton | dst_npi | session_type | > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > | 1 | SMS_C | provider_ip | 2775 | username | pass | smpp > > | 2 | 1 | 2 | 1 | 1 | > > > +----+-------+---------------+------+-----------+----------+-------------+---------+---------+---------+---------+--------------+ > > 1 row in set (0.001 sec) > > > > Any help thank you > > volga629 > > Sent from Mailspring > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > -- > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > Meet the OpenSIPS team at the next OpenSIPS Summit: > https://www.opensips.org/events > > _______________________________________________ > 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 > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com Meet the OpenSIPS team at the next OpenSIPS Summit: https://www.opensips.org/events _______________________________________________ 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 alexei.vasilyev at gmail.com Tue Jun 11 03:57:41 2019 From: alexei.vasilyev at gmail.com (vasilevalex) Date: Tue, 11 Jun 2019 00:57:41 -0700 (MST) Subject: [OpenSIPS-Users] User location fields access In-Reply-To: <12954535-ae94-31cd-fbbf-eda9a0f010f1@gmail.com> References: <12954535-ae94-31cd-fbbf-eda9a0f010f1@gmail.com> Message-ID: <1560239861880-0.post@n2.nabble.com> Hi Vitalii, Mostly used fields can be accessed after lookup. Socket: $fs, Flags: isbflagset(). If I need more fields, I just store them in external cache with E_UL_CONTACT_INSERT and E_UL_CONTACT_UPDATE. I understand, that this is duplication of data, but this is also good way to move all request to that data from OpenSIPS to cache. ----- --- Alexey Vasilyev -- Sent from: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html From callum.guy at x-on.co.uk Tue Jun 11 04:12:55 2019 From: callum.guy at x-on.co.uk (Callum Guy) Date: Tue, 11 Jun 2019 09:12:55 +0100 Subject: [OpenSIPS-Users] re-INVITE (Hold) looses audio In-Reply-To: <656c1c52-2dff-2b5e-5ceb-311eba285092@opensips.org> References: <656c1c52-2dff-2b5e-5ceb-311eba285092@opensips.org> Message-ID: Hi Mark, Can you confirm which engagement functions you are using? Does the SDP look like its being handled for the RE-INVITE transactions? I have dealt with some similar scenarios recently and would highly recommend using the separate rtpproxy_offer() and rtpproxy_answer() methods over the dialog bound rtpproxy_engage() - this will give you a more granular control. Generally speaking I would advise that you identity a loose routed INVITE and check for present of SDP and use this to trigger an offer, somewhat like this: if (loose_route() && is_method("INVITE") && has_body("application/sdp")) { rtpproxy_offer(OPTS); } You'll then need to consider the additional scenarios for last SDP and ACK processing to handle both the answer and edge cases however hopefully this will help you move forward in your config. Good luck, Callum On Mon, 10 Jun 2019 at 19:55, Răzvan Crainea wrote: > Hi, Mark! > > Are you engaging RTPProxy for the re-INVITEs too? Can you check if > RTPProxy times out the session due to lack of audio from one side? You > can see that in the logs. > > Best regards, > > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > > On 6/10/19 4:23 PM, Mark Farmer wrote: > > Hi all > > > > I'm trying to solve an issue where if the call is placed on hold via a > > re-INVITE, my end stops the audio at that point so when another > > re-INVITE is received to resume the call, the audio does not restart. I > > can still hear the other party but they cannot hear me because I'm not > > sending any RTP any more. > > > > I'm really struggling to pin this one down. Can anyone give me any clues > > as to why this might be happening? > > > > I'm using OpenSIPS 2.4.5 with RTPProxy 2.0 > > > > Many thanks > > Mark. > > > > > > -- > > Mark Farmer > > farmorg at gmail.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 > -- *0333 332 0000  |  www.x-on.co.uk   |   **      * X-on is a trading name of Storacall Technology Ltd a limited company registered in England and Wales. Registered Office : Avaland House, 110 London Road, Apsley, Hemel Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient, please notify X-on immediately on +44(0)333 332 0000 and delete the message from your computer. If you are not a named addressee you must not use, disclose, disseminate, distribute, copy, print or reply to this email. Views or opinions expressed by an individual within this email may not necessarily reflect the views of X-on or its associated companies. Although X-on routinely screens for viruses, addressees should scan this email and any attachments for viruses. X-on makes no representation or warranty as to the absence of viruses in this email or any attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: From farmorg at gmail.com Tue Jun 11 07:46:29 2019 From: farmorg at gmail.com (Mark Farmer) Date: Tue, 11 Jun 2019 12:46:29 +0100 Subject: [OpenSIPS-Users] re-INVITE (Hold) looses audio In-Reply-To: References: <656c1c52-2dff-2b5e-5ceb-311eba285092@opensips.org> Message-ID: Thank you both for your replies. I realised eventually that I was indeed missing rtpproxy_offer/answer for the RE-INVITEs. Callum, I am using rtpproxy_offer/answer but I will keep that in mind for the future. Seems to be working now although I think I need to tune the options in this case. Is there a generally recognised method of re-engaging rtpproxy when sessions already exist? I'm thinking the 'l' flag is required? Regards Mark. On Tue, 11 Jun 2019 at 09:16, Callum Guy wrote: > Hi Mark, > > Can you confirm which engagement functions you are using? Does the SDP > look like its being handled for the RE-INVITE transactions? > > I have dealt with some similar scenarios recently and would highly > recommend using the separate rtpproxy_offer() and rtpproxy_answer() methods > over the dialog bound rtpproxy_engage() - this will give you a more > granular control. Generally speaking I would advise that you identity a > loose routed INVITE and check for present of SDP and use this to trigger an > offer, somewhat like this: > > if (loose_route() && is_method("INVITE") && has_body("application/sdp")) { > rtpproxy_offer(OPTS); > } > > You'll then need to consider the additional scenarios for last SDP and ACK > processing to handle both the answer and edge cases however hopefully this > will help you move forward in your config. > > Good luck, > > Callum > > > On Mon, 10 Jun 2019 at 19:55, Răzvan Crainea wrote: > >> Hi, Mark! >> >> Are you engaging RTPProxy for the re-INVITEs too? Can you check if >> RTPProxy times out the session due to lack of audio from one side? You >> can see that in the logs. >> >> Best regards, >> >> Răzvan Crainea >> OpenSIPS Core Developer >> http://www.opensips-solutions.com >> >> On 6/10/19 4:23 PM, Mark Farmer wrote: >> > Hi all >> > >> > I'm trying to solve an issue where if the call is placed on hold via a >> > re-INVITE, my end stops the audio at that point so when another >> > re-INVITE is received to resume the call, the audio does not restart. I >> > can still hear the other party but they cannot hear me because I'm not >> > sending any RTP any more. >> > >> > I'm really struggling to pin this one down. Can anyone give me any >> clues >> > as to why this might be happening? >> > >> > I'm using OpenSIPS 2.4.5 with RTPProxy 2.0 >> > >> > Many thanks >> > Mark. >> > >> > >> > -- >> > Mark Farmer >> > farmorg at gmail.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 >> > > > *0333 332 0000 | www.x-on.co.uk | ** > > * > > X-on is a trading name of Storacall Technology Ltd a limited company > registered in England and Wales. > Registered Office : Avaland House, 110 London Road, Apsley, Hemel > Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. > The information in this e-mail is confidential and for use by the > addressee(s) only. If you are not the intended recipient, please notify > X-on immediately on +44(0)333 332 0000 and delete the > message from your computer. If you are not a named addressee you must not > use, disclose, disseminate, distribute, copy, print or reply to this email. Views > or opinions expressed by an individual > within this email may not necessarily reflect the views of X-on or its > associated companies. Although X-on routinely screens for viruses, > addressees should scan this email and any attachments > for viruses. X-on makes no representation or warranty as to the absence of > viruses in this email or any attachments. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- Mark Farmer farmorg at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From callum.guy at x-on.co.uk Tue Jun 11 08:56:18 2019 From: callum.guy at x-on.co.uk (Callum Guy) Date: Tue, 11 Jun 2019 13:56:18 +0100 Subject: [OpenSIPS-Users] re-INVITE (Hold) looses audio In-Reply-To: References: <656c1c52-2dff-2b5e-5ceb-311eba285092@opensips.org> Message-ID: I'm not 100% clear on your situation but if it helps I can confirm that I've not had to use that option in the past, my configs simply use the same options as used when rtpproxy was initially offered (in my case combinations of r,f,i,e - bridging mode) and I've found that it is smart enough to offer up the same individual proxy and the same ports for a matching dialog - I presume this is partly the modules responsibility and partly the rtpproxy software. Hope that helps On Tue, 11 Jun 2019 at 12:48, Mark Farmer wrote: > Thank you both for your replies. > I realised eventually that I was indeed missing rtpproxy_offer/answer for > the RE-INVITEs. > > Callum, I am using rtpproxy_offer/answer but I will keep that in mind for > the future. > > Seems to be working now although I think I need to tune the options in > this case. Is there a generally recognised method of re-engaging rtpproxy > when sessions already exist? I'm thinking the 'l' flag is required? > > Regards > Mark. > > > On Tue, 11 Jun 2019 at 09:16, Callum Guy wrote: > >> Hi Mark, >> >> Can you confirm which engagement functions you are using? Does the SDP >> look like its being handled for the RE-INVITE transactions? >> >> I have dealt with some similar scenarios recently and would highly >> recommend using the separate rtpproxy_offer() and rtpproxy_answer() methods >> over the dialog bound rtpproxy_engage() - this will give you a more >> granular control. Generally speaking I would advise that you identity a >> loose routed INVITE and check for present of SDP and use this to trigger an >> offer, somewhat like this: >> >> if (loose_route() && is_method("INVITE") && has_body("application/sdp")) { >> rtpproxy_offer(OPTS); >> } >> >> You'll then need to consider the additional scenarios for last SDP and >> ACK processing to handle both the answer and edge cases however hopefully >> this will help you move forward in your config. >> >> Good luck, >> >> Callum >> >> >> On Mon, 10 Jun 2019 at 19:55, Răzvan Crainea wrote: >> >>> Hi, Mark! >>> >>> Are you engaging RTPProxy for the re-INVITEs too? Can you check if >>> RTPProxy times out the session due to lack of audio from one side? You >>> can see that in the logs. >>> >>> Best regards, >>> >>> Răzvan Crainea >>> OpenSIPS Core Developer >>> http://www.opensips-solutions.com >>> >>> On 6/10/19 4:23 PM, Mark Farmer wrote: >>> > Hi all >>> > >>> > I'm trying to solve an issue where if the call is placed on hold via a >>> > re-INVITE, my end stops the audio at that point so when another >>> > re-INVITE is received to resume the call, the audio does not restart. >>> I >>> > can still hear the other party but they cannot hear me because I'm not >>> > sending any RTP any more. >>> > >>> > I'm really struggling to pin this one down. Can anyone give me any >>> clues >>> > as to why this might be happening? >>> > >>> > I'm using OpenSIPS 2.4.5 with RTPProxy 2.0 >>> > >>> > Many thanks >>> > Mark. >>> > >>> > >>> > -- >>> > Mark Farmer >>> > farmorg at gmail.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 >>> >> >> >> *0333 332 0000 | www.x-on.co.uk | ** >> >> * >> >> X-on is a trading name of Storacall Technology Ltd a limited company >> registered in England and Wales. >> Registered Office : Avaland House, 110 London Road, Apsley, Hemel >> Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. >> The information in this e-mail is confidential and for use by the >> addressee(s) only. If you are not the intended recipient, please notify >> X-on immediately on +44(0)333 332 0000 and delete the >> message from your computer. If you are not a named addressee you must not >> use, disclose, disseminate, distribute, copy, print or reply to this email. Views >> or opinions expressed by an individual >> within this email may not necessarily reflect the views of X-on or its >> associated companies. Although X-on routinely screens for viruses, >> addressees should scan this email and any attachments >> for viruses. X-on makes no representation or warranty as to the absence >> of viruses in this email or any attachments. >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > > > -- > Mark Farmer > farmorg at gmail.com > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- *0333 332 0000  |  www.x-on.co.uk   |   **      * X-on is a trading name of Storacall Technology Ltd a limited company registered in England and Wales. Registered Office : Avaland House, 110 London Road, Apsley, Hemel Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient, please notify X-on immediately on +44(0)333 332 0000 and delete the message from your computer. If you are not a named addressee you must not use, disclose, disseminate, distribute, copy, print or reply to this email. Views or opinions expressed by an individual within this email may not necessarily reflect the views of X-on or its associated companies. Although X-on routinely screens for viruses, addressees should scan this email and any attachments for viruses. X-on makes no representation or warranty as to the absence of viruses in this email or any attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: From farmorg at gmail.com Tue Jun 11 11:10:20 2019 From: farmorg at gmail.com (Mark Farmer) Date: Tue, 11 Jun 2019 16:10:20 +0100 Subject: [OpenSIPS-Users] re-INVITE (Hold) looses audio In-Reply-To: References: <656c1c52-2dff-2b5e-5ceb-311eba285092@opensips.org> Message-ID: Thanks for the info. I am using combinations of c,o,r,f,w,i,e I'll look into it more when I get to it & report back on what works for me :) Mark. On Tue, 11 Jun 2019 at 13:59, Callum Guy wrote: > I'm not 100% clear on your situation but if it helps I can confirm that > I've not had to use that option in the past, my configs simply use the same > options as used when rtpproxy was initially offered (in my case > combinations of r,f,i,e - bridging mode) and I've found that it is smart > enough to offer up the same individual proxy and the same ports for a > matching dialog - I presume this is partly the modules responsibility and > partly the rtpproxy software. > > Hope that helps > > On Tue, 11 Jun 2019 at 12:48, Mark Farmer wrote: > >> Thank you both for your replies. >> I realised eventually that I was indeed missing rtpproxy_offer/answer for >> the RE-INVITEs. >> >> Callum, I am using rtpproxy_offer/answer but I will keep that in mind for >> the future. >> >> Seems to be working now although I think I need to tune the options in >> this case. Is there a generally recognised method of re-engaging rtpproxy >> when sessions already exist? I'm thinking the 'l' flag is required? >> >> Regards >> Mark. >> >> >> On Tue, 11 Jun 2019 at 09:16, Callum Guy wrote: >> >>> Hi Mark, >>> >>> Can you confirm which engagement functions you are using? Does the SDP >>> look like its being handled for the RE-INVITE transactions? >>> >>> I have dealt with some similar scenarios recently and would highly >>> recommend using the separate rtpproxy_offer() and rtpproxy_answer() methods >>> over the dialog bound rtpproxy_engage() - this will give you a more >>> granular control. Generally speaking I would advise that you identity a >>> loose routed INVITE and check for present of SDP and use this to trigger an >>> offer, somewhat like this: >>> >>> if (loose_route() && is_method("INVITE") && has_body("application/sdp")) >>> { >>> rtpproxy_offer(OPTS); >>> } >>> >>> You'll then need to consider the additional scenarios for last SDP and >>> ACK processing to handle both the answer and edge cases however hopefully >>> this will help you move forward in your config. >>> >>> Good luck, >>> >>> Callum >>> >>> >>> On Mon, 10 Jun 2019 at 19:55, Răzvan Crainea >>> wrote: >>> >>>> Hi, Mark! >>>> >>>> Are you engaging RTPProxy for the re-INVITEs too? Can you check if >>>> RTPProxy times out the session due to lack of audio from one side? You >>>> can see that in the logs. >>>> >>>> Best regards, >>>> >>>> Răzvan Crainea >>>> OpenSIPS Core Developer >>>> http://www.opensips-solutions.com >>>> >>>> On 6/10/19 4:23 PM, Mark Farmer wrote: >>>> > Hi all >>>> > >>>> > I'm trying to solve an issue where if the call is placed on hold via >>>> a >>>> > re-INVITE, my end stops the audio at that point so when another >>>> > re-INVITE is received to resume the call, the audio does not restart. >>>> I >>>> > can still hear the other party but they cannot hear me because I'm >>>> not >>>> > sending any RTP any more. >>>> > >>>> > I'm really struggling to pin this one down. Can anyone give me any >>>> clues >>>> > as to why this might be happening? >>>> > >>>> > I'm using OpenSIPS 2.4.5 with RTPProxy 2.0 >>>> > >>>> > Many thanks >>>> > Mark. >>>> > >>>> > >>>> > -- >>>> > Mark Farmer >>>> > farmorg at gmail.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 >>>> >>> >>> >>> *0333 332 0000 | www.x-on.co.uk | ** >>> >>> * >>> >>> X-on is a trading name of Storacall Technology Ltd a limited company >>> registered in England and Wales. >>> Registered Office : Avaland House, 110 London Road, Apsley, Hemel >>> Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. >>> The information in this e-mail is confidential and for use by the >>> addressee(s) only. If you are not the intended recipient, please notify >>> X-on immediately on +44(0)333 332 0000 and delete the >>> message from your computer. If you are not a named addressee you must >>> not use, disclose, disseminate, distribute, copy, print or reply to this >>> email. Views or opinions expressed by an individual >>> within this email may not necessarily reflect the views of X-on or its >>> associated companies. Although X-on routinely screens for viruses, >>> addressees should scan this email and any attachments >>> for viruses. X-on makes no representation or warranty as to the absence >>> of viruses in this email or any attachments. >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >> >> >> -- >> Mark Farmer >> farmorg at gmail.com >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > > > *0333 332 0000 | www.x-on.co.uk | ** > > * > > X-on is a trading name of Storacall Technology Ltd a limited company > registered in England and Wales. > Registered Office : Avaland House, 110 London Road, Apsley, Hemel > Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. > The information in this e-mail is confidential and for use by the > addressee(s) only. If you are not the intended recipient, please notify > X-on immediately on +44(0)333 332 0000 and delete the > message from your computer. If you are not a named addressee you must not > use, disclose, disseminate, distribute, copy, print or reply to this email. Views > or opinions expressed by an individual > within this email may not necessarily reflect the views of X-on or its > associated companies. Although X-on routinely screens for viruses, > addressees should scan this email and any attachments > for viruses. X-on makes no representation or warranty as to the absence of > viruses in this email or any attachments. > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- Mark Farmer farmorg at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Tue Jun 11 11:21:04 2019 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Tue, 11 Jun 2019 18:21:04 +0300 Subject: [OpenSIPS-Users] [RELEASE] OpenSIPS 2.2 End of Line In-Reply-To: References: Message-ID: Hi, again! As promised, the last version of OpenSIPS 2.2 is now released[1,2]! OpenSIPS 2.2.8 is the last release for the 2.2 branch, and from now on this branch is discontinued. We strongly recommend you to upgrade to OpenSIPS 2.4 as soon as possible. [1] https://opensips.org/pub/opensips/2.2.8/opensips-2.2.8.tar.gz [2] https://opensips.org/pub/opensips/2.2.8/ChangeLog Best regards, Răzvan On 6/5/19 6:31 PM, Răzvan Crainea wrote: > Hi, everyone! > > Next week, on Tuesday, 11th of June 2019, we are planning to make a new > minor release of the OpenSIPS 2.2 branch. The 2.2.8 version will be the > last release of the 2.2 LTS branch, and will contain all the bug fixes > gathered throughout the years. > Starting with 12th of June we will no longer maintain this branch, and > we will not do any commits or backport any fixes for it. Therefore we > strongly suggest you to upgrade, if you haven't already, to the next > stable LTS version, OpenSIPS 2.4. > In the meantime, please let us know if there are any outstanding issues > with 2.2.7 that we can sort out until the final release. > > Cheers, -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com From razvan at opensips.org Tue Jun 11 11:28:15 2019 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Tue, 11 Jun 2019 18:28:15 +0300 Subject: [OpenSIPS-Users] [RELEASE] OpenSIPS 2.4.6 Minor Version Message-ID: <617e8142-1a1a-acc7-94c7-19d72d54c336@opensips.org> Hi, everyone! We are thrilled to announce you that we've just released a new minor version of the OpenSIPS 2.4 branch. The new OpenSIPS 2.4.6[1] contains all the bug fixes we've resolved during the last months, ensuring you your deployment more stable now! This minor release does not need any migration, so feel free to update to the latest version anytime! For a full list of changes, consult the ChangeLog[2]. [1] https://opensips.org/pub/opensips/2.4.6/opensips-2.4.6.tar.gz [2] https://opensips.org/pub/opensips/2.4.6/ChangeLog Cheers, -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com From carlos.oliva at numintec.com Tue Jun 11 16:05:13 2019 From: carlos.oliva at numintec.com (Carlos Oliva) Date: Tue, 11 Jun 2019 22:05:13 +0200 Subject: [OpenSIPS-Users] [OpenSIPS-Devel] [RELEASE] OpenSIPS 2.4.6 Minor Version In-Reply-To: <617e8142-1a1a-acc7-94c7-19d72d54c336@opensips.org> References: <617e8142-1a1a-acc7-94c7-19d72d54c336@opensips.org> Message-ID: great job! thank you Răzvan El mar., 11 jun. 2019 a las 17:29, Răzvan Crainea () escribió: > Hi, everyone! > > We are thrilled to announce you that we've just released a new minor > version of the OpenSIPS 2.4 branch. The new OpenSIPS 2.4.6[1] contains > all the bug fixes we've resolved during the last months, ensuring you > your deployment more stable now! > This minor release does not need any migration, so feel free to update > to the latest version anytime! For a full list of changes, consult the > ChangeLog[2]. > > [1] https://opensips.org/pub/opensips/2.4.6/opensips-2.4.6.tar.gz > [2] https://opensips.org/pub/opensips/2.4.6/ChangeLog > > Cheers, > -- > Răzvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > > _______________________________________________ > Devel mailing list > Devel at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/devel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From johan at democon.be Tue Jun 11 16:07:58 2019 From: johan at democon.be (johan de clercq) Date: Tue, 11 Jun 2019 22:07:58 +0200 Subject: [OpenSIPS-Users] problem with git branch for opensips 3.0 Message-ID: <005001d52091$5daf6460$190e2d20$@democon.be> Hello, I clone git using : git clone https://github.com/OpenSIPS/opensips.git -b 3.0 opensips-3.0 after installing I only have 2 files in sbin : opensips osipsconfig Can you check why I don't have opensipsctl and opensipsdbctl ? Johan De Clercq, Managing Director Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke Tel +3256980990 - GSM +32478720104 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From johan at democon.be Tue Jun 11 16:30:17 2019 From: johan at democon.be (johan de clercq) Date: Tue, 11 Jun 2019 22:30:17 +0200 Subject: [OpenSIPS-Users] problem with git branch for opensips 3.0 In-Reply-To: <005001d52091$5daf6460$190e2d20$@democon.be> References: <005001d52091$5daf6460$190e2d20$@democon.be> Message-ID: <00bc01d52094$7bc38f00$734aad00$@democon.be> Hello, I clone git using : git clone https://github.com/OpenSIPS/opensips.git -b 3.0 opensips-3.0 after installing I only have 2 files in sbin : opensips osipsconfig Can you check why I don't have opensipsctl and opensipsdbctl ? I looked on another system running opensips 3.0 beta : db_berkeley opensipsctl.base opensipsctlrc opensipsdbctl.dbtext oracle dbtext opensipsctl.db_berkeley opensipsctl.sqlbase opensipsdbctl.mysql pi_http dbtextdb opensipsctl.dbtext opensipsctl.sqlite opensipsdbctl.oracle postgres mysql opensipsctl.mysql opensipsdbctl opensipsdbctl.pgsql sqlite opensipsctl opensipsctl.oracle opensipsdbctl.base opensipsdbctl.sqlite opensipsctl.8 opensipsctl.pgsql opensipsdbctl.db_berkeley opensipsdbfunc.oracle this is what I have in latest git of 3. 0 : db_berkeley dbtext dbtextdb mysql oracle pi_http postgres sqlite so it seems to me that there is something wrong with latest git. Can you please have a look ? From: johan de clercq Sent: Tuesday, June 11, 2019 10:08 PM To: 'OpenSIPS users mailling list' Subject: problem with git branch for opensips 3.0 Hello, I clone git using : git clone https://github.com/OpenSIPS/opensips.git -b 3.0 opensips-3.0 after installing I only have 2 files in sbin : opensips osipsconfig Can you check why I don't have opensipsctl and opensipsdbctl ? Johan De Clercq, Managing Director Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke Tel +3256980990 - GSM +32478720104 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From alexei.vasilyev at gmail.com Wed Jun 12 03:23:34 2019 From: alexei.vasilyev at gmail.com (vasilevalex) Date: Wed, 12 Jun 2019 00:23:34 -0700 (MST) Subject: [OpenSIPS-Users] problem with git branch for opensips 3.0 In-Reply-To: <005001d52091$5daf6460$190e2d20$@democon.be> References: <005001d52091$5daf6460$190e2d20$@democon.be> Message-ID: <1560324214026-0.post@n2.nabble.com> Hi, Johan. Everything ok with git. Just check this commit: 8a7abc05195fb4a29d5439871d7691c090c60d32 (https://github.com/OpenSIPS/opensips/commit/8a7abc05195fb4a29d5439871d7691c090c60d32) ----- --- Alexey Vasilyev -- Sent from: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html From Johan at democon.be Wed Jun 12 03:31:52 2019 From: Johan at democon.be (Johan De Clercq) Date: Wed, 12 Jun 2019 09:31:52 +0200 Subject: [OpenSIPS-Users] problem with git branch for opensips 3.0 In-Reply-To: <1560324214026-0.post@n2.nabble.com> References: <005001d52091$5daf6460$190e2d20$@democon.be> <1560324214026-0.post@n2.nabble.com> Message-ID: Okay. So is there somewhere good documentation on this? In exact, how do I configure this, and how do I migrate 24 dB to opensips 30? On Wed, 12 Jun 2019, 09:25 vasilevalex, wrote: > Hi, Johan. > > Everything ok with git. > Just check this commit: 8a7abc05195fb4a29d5439871d7691c090c60d32 > ( > https://github.com/OpenSIPS/opensips/commit/8a7abc05195fb4a29d5439871d7691c090c60d32 > ) > > > > > ----- > --- > Alexey Vasilyev > -- > Sent from: > http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html > > _______________________________________________ > 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 alexei.vasilyev at gmail.com Wed Jun 12 03:47:00 2019 From: alexei.vasilyev at gmail.com (vasilevalex) Date: Wed, 12 Jun 2019 00:47:00 -0700 (MST) Subject: [OpenSIPS-Users] problem with git branch for opensips 3.0 In-Reply-To: References: <005001d52091$5daf6460$190e2d20$@democon.be> <1560324214026-0.post@n2.nabble.com> Message-ID: <1560325620490-0.post@n2.nabble.com> Hi Johan, opensips-cli should replace all the command line tools. https://github.com/OpenSIPS/opensips-cli But I think developers team can help more with docs about migration data. ----- --- Alexey Vasilyev -- Sent from: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html From bogdan at opensips.org Wed Jun 12 04:26:04 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 12 Jun 2019 11:26:04 +0300 Subject: [OpenSIPS-Users] problem with git branch for opensips 3.0 In-Reply-To: References: <005001d52091$5daf6460$190e2d20$@democon.be> <1560324214026-0.post@n2.nabble.com> Message-ID: <01d002c5-c9d8-a8c6-c7fe-d21cd402ee99@opensips.org> Hi Johan, The git contains good docs for the cli tool - if there is something you find as uncovered, please let us know. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/12/2019 10:31 AM, Johan De Clercq wrote: > Okay. > So is there somewhere good documentation on this? In exact, how do I > configure this, and how do I migrate 24 dB to opensips 30? > > On Wed, 12 Jun 2019, 09:25 vasilevalex, > wrote: > > Hi, Johan. > > Everything ok with git. > Just check this commit: 8a7abc05195fb4a29d5439871d7691c090c60d32 > (https://github.com/OpenSIPS/opensips/commit/8a7abc05195fb4a29d5439871d7691c090c60d32) > > > > > ----- > --- > Alexey Vasilyev > -- > Sent from: > http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html > > _______________________________________________ > 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 Johan at democon.be Wed Jun 12 04:29:07 2019 From: Johan at democon.be (Johan De Clercq) Date: Wed, 12 Jun 2019 10:29:07 +0200 Subject: [OpenSIPS-Users] problem with git branch for opensips 3.0 In-Reply-To: <01d002c5-c9d8-a8c6-c7fe-d21cd402ee99@opensips.org> References: <005001d52091$5daf6460$190e2d20$@democon.be> <1560324214026-0.post@n2.nabble.com> <01d002c5-c9d8-a8c6-c7fe-d21cd402ee99@opensips.org> Message-ID: Looking here https://github.com/OpenSIPS/opensips-cli/blob/master/docs/modules/database.md, I can't find back how to migrate a 24 db to 30. Can you have a look ? Thanks. Op wo 12 jun. 2019 om 10:26 schreef Bogdan-Andrei Iancu : > Hi Johan, > > The git contains good docs for the cli tool - if there is something you > find as uncovered, please let us know. > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/12/2019 10:31 AM, Johan De Clercq wrote: > > Okay. > So is there somewhere good documentation on this? In exact, how do I > configure this, and how do I migrate 24 dB to opensips 30? > > On Wed, 12 Jun 2019, 09:25 vasilevalex, wrote: > >> Hi, Johan. >> >> Everything ok with git. >> Just check this commit: 8a7abc05195fb4a29d5439871d7691c090c60d32 >> ( >> https://github.com/OpenSIPS/opensips/commit/8a7abc05195fb4a29d5439871d7691c090c60d32 >> ) >> >> >> >> >> ----- >> --- >> Alexey Vasilyev >> -- >> Sent from: >> http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html >> >> _______________________________________________ >> 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 Wed Jun 12 05:06:00 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 12 Jun 2019 12:06:00 +0300 Subject: [OpenSIPS-Users] problem with git branch for opensips 3.0 In-Reply-To: References: <005001d52091$5daf6460$190e2d20$@democon.be> <1560324214026-0.post@n2.nabble.com> <01d002c5-c9d8-a8c6-c7fe-d21cd402ee99@opensips.org> Message-ID: <7600dd61-bd03-4bcd-3295-fa054cb01ca9@opensips.org> You are right, the doc is missing the "migrate" part. Liviu will update the docs there. Thanks for the note ! Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/12/2019 11:29 AM, Johan De Clercq wrote: > Looking here > https://github.com/OpenSIPS/opensips-cli/blob/master/docs/modules/database.md, > > I can't find back how to migrate a 24 db to 30. Can you have a look ? > > Thanks. > > Op wo 12 jun. 2019 om 10:26 schreef Bogdan-Andrei Iancu > >: > > Hi Johan, > > The git contains good docs for the cli tool - if there is > something you find as uncovered, please let us know. > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/12/2019 10:31 AM, Johan De Clercq wrote: >> Okay. >> So is there somewhere good documentation on this? In exact, how >> do I configure this, and how do I migrate 24 dB to opensips 30? >> >> On Wed, 12 Jun 2019, 09:25 vasilevalex, >> > wrote: >> >> Hi, Johan. >> >> Everything ok with git. >> Just check this commit: 8a7abc05195fb4a29d5439871d7691c090c60d32 >> (https://github.com/OpenSIPS/opensips/commit/8a7abc05195fb4a29d5439871d7691c090c60d32) >> >> >> >> >> ----- >> --- >> Alexey Vasilyev >> -- >> Sent from: >> http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html >> >> _______________________________________________ >> 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 callum.guy at x-on.co.uk Wed Jun 12 05:08:06 2019 From: callum.guy at x-on.co.uk (Callum Guy) Date: Wed, 12 Jun 2019 10:08:06 +0100 Subject: [OpenSIPS-Users] Block lookups for WebRTC DNS .invalid Message-ID: Hi All, I am in the process of configuring a WebRTC/SIP proxy and wanted to know if there was any way to prevent OpenSIPs from attempting to resolve the .invalid domains present in the Via headers: INVITE sip:abc at us.net SIP/2.0 Via: SIP/2.0/WSS b7evbq9f9q22.invalid;branch=z9hG4bK5495466 Although all is working I'm seeing the following log message. CRITICAL:core:mk_proxy: could not resolve hostname: "b7evbq9f9q22.invalid" Certainly it seems that this is compliant with the RFC defined behaviour ( https://tools.ietf.org/html/rfc7118#appendix-B.1) however I am hoping there is a simple way to block lookups to this domain to save resources etc. On a side note I am typically reviewing SIP on our network using sngrep, when relaying these messages over UDP sngrep is failing to read the packets (presumably due to the extremely large SDP failing reassembly). While I'm writing I wondered if anyone has seen this before and could offer advice - the target endpoint (FreeSWITCH) has no issues reading it. One workaround could be to use TCP (tested and works) however I was curious if there was another solution? Thanks, Callum -- *0333 332 0000  |  www.x-on.co.uk   |   **      * X-on is a trading name of Storacall Technology Ltd a limited company registered in England and Wales. Registered Office : Avaland House, 110 London Road, Apsley, Hemel Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient, please notify X-on immediately on +44(0)333 332 0000 and delete the message from your computer. If you are not a named addressee you must not use, disclose, disseminate, distribute, copy, print or reply to this email. Views or opinions expressed by an individual within this email may not necessarily reflect the views of X-on or its associated companies. Although X-on routinely screens for viruses, addressees should scan this email and any attachments for viruses. X-on makes no representation or warranty as to the absence of viruses in this email or any attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: From liviu at opensips.org Wed Jun 12 05:12:09 2019 From: liviu at opensips.org (Liviu Chircu) Date: Wed, 12 Jun 2019 12:12:09 +0300 Subject: [OpenSIPS-Users] problem with git branch for opensips 3.0 In-Reply-To: References: <005001d52091$5daf6460$190e2d20$@democon.be> <1560324214026-0.post@n2.nabble.com> <01d002c5-c9d8-a8c6-c7fe-d21cd402ee99@opensips.org> Message-ID: <2ae4ce29-fc1c-ff3e-ef7f-21f8733e2d83@opensips.org> Hi Johan, I just pushed a docs update, so the "migrate" command is more visible.  Please try the CLI "database migrate" command, it should be self-explanatory. If you get stuck at any point, we're here to help (and learn more too, so we can improve the docs). Cheers, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 12.06.2019 11:29, Johan De Clercq wrote: > Looking here > https://github.com/OpenSIPS/opensips-cli/blob/master/docs/modules/database.md, > > I can't find back how to migrate a 24 db to 30.   Can you have a look ? > > Thanks. > > Op wo 12 jun. 2019 om 10:26 schreef Bogdan-Andrei Iancu > >: > > Hi Johan, > > The git contains good docs for the cli tool - if there is > something you find as uncovered, please let us know. > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/12/2019 10:31 AM, Johan De Clercq wrote: >> Okay. >> So is there somewhere good documentation on this? In exact, how >> do I configure this, and how do I migrate 24 dB to opensips 30? >> >> On Wed, 12 Jun 2019, 09:25 vasilevalex, >> > wrote: >> >> Hi, Johan. >> >> Everything ok with git. >> Just check this commit: 8a7abc05195fb4a29d5439871d7691c090c60d32 >> (https://github.com/OpenSIPS/opensips/commit/8a7abc05195fb4a29d5439871d7691c090c60d32) >> >> >> >> >> ----- >> --- >> Alexey Vasilyev >> -- >> Sent from: >> http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html >> >> _______________________________________________ >> 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 dan at ag-projects.com Wed Jun 12 05:22:46 2019 From: dan at ag-projects.com (Dan Pascu) Date: Wed, 12 Jun 2019 12:22:46 +0300 Subject: [OpenSIPS-Users] problem with git branch for opensips 3.0 In-Reply-To: <01d002c5-c9d8-a8c6-c7fe-d21cd402ee99@opensips.org> References: <005001d52091$5daf6460$190e2d20$@democon.be> <1560324214026-0.post@n2.nabble.com> <01d002c5-c9d8-a8c6-c7fe-d21cd402ee99@opensips.org> Message-ID: <6498B43D-CBC5-4F16-B79B-DD3B0DAC07FD@ag-projects.com> On 12 Jun 2019, at 11:26, Bogdan-Andrei Iancu wrote: > Hi Johan, > > The git contains good docs for the cli tool - if there is something you find as uncovered, please let us know. The database module doesn't allow one to specify a username/password to grant all access to that username to the created database. One has to manually perform this task that was previously done automatically by opensipsctldb -- Dan From Johan at democon.be Wed Jun 12 05:30:14 2019 From: Johan at democon.be (Johan De Clercq) Date: Wed, 12 Jun 2019 11:30:14 +0200 Subject: [OpenSIPS-Users] problem with git branch for opensips 3.0 In-Reply-To: <6498B43D-CBC5-4F16-B79B-DD3B0DAC07FD@ag-projects.com> References: <005001d52091$5daf6460$190e2d20$@democon.be> <1560324214026-0.post@n2.nabble.com> <01d002c5-c9d8-a8c6-c7fe-d21cd402ee99@opensips.org> <6498B43D-CBC5-4F16-B79B-DD3B0DAC07FD@ag-projects.com> Message-ID: Okay, please explain how? On Wed, 12 Jun 2019, 11:24 Dan Pascu, wrote: > > On 12 Jun 2019, at 11:26, Bogdan-Andrei Iancu wrote: > > > Hi Johan, > > > > The git contains good docs for the cli tool - if there is something you > find as uncovered, please let us know. > > The database module doesn't allow one to specify a username/password to > grant all access to that username to the created database. One has to > manually perform this task that was previously done automatically by > opensipsctldb > > -- > Dan > > > > > > _______________________________________________ > 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 spanda at 3clogic.com Wed Jun 12 08:34:02 2019 From: spanda at 3clogic.com (Sasmita Panda) Date: Wed, 12 Jun 2019 18:04:02 +0530 Subject: [OpenSIPS-Users] I need some help in websocket connection error . Message-ID: I am using opensips 2.2 version: opensips 2.2.4 (x86_64/linux) I am using the proto_wss and tls_mgm module for establishing websocket connection . I am getting bellow error again and again . Whats the reson behind this and how can I solve this problem ? Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: INFO:core:probe_max_sock_buff: using snd buffer of 416 kb Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 96 Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: ERROR:proto_wss:tls_accept: New TLS connection from 192.168.160.6:58616 failed to accept Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: ERROR:proto_wss:wss_read_req: cannot fix read connection Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: INFO:core:probe_max_sock_buff: using snd buffer of 416 kb Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 96 Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: ERROR:proto_wss:tls_accept: New TLS connection from 192.168.175.59:12918 failed to accept Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: ERROR:proto_wss:wss_read_req: cannot fix read connection Please do help . *Thanks & Regards* *Sasmita Panda* *Senior Network Testing and Software Engineer* *3CLogic , ph:07827611765* -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Wed Jun 12 09:03:21 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 12 Jun 2019 16:03:21 +0300 Subject: [OpenSIPS-Users] Block lookups for WebRTC DNS .invalid In-Reply-To: References: Message-ID: Hi, There was a similar email couple of days ago - the idea is to do fix_nated_contact() for all the traffic (replies and requests) coming from the WS(S) end point (as such endpoints are not able to provide a routable contact) Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/12/2019 12:08 PM, Callum Guy wrote: > Hi All, > > I am in the process of configuring a WebRTC/SIP proxy and wanted to > know if there was any way to prevent OpenSIPs from attempting to > resolve the .invalid domains present in the Via headers: > > INVITE sip:abc at us.net SIP/2.0 > Via: SIP/2.0/WSS b7evbq9f9q22.invalid;branch=z9hG4bK5495466 > > Although all is working I'm seeing the following log message. > > CRITICAL:core:mk_proxy: could not resolve hostname: "b7evbq9f9q22.invalid" > > Certainly it seems that this is compliant with the RFC defined > behaviour (https://tools.ietf.org/html/rfc7118#appendix-B.1) however I > am hoping there is a simple way to block lookups to this domain to > save resources etc. > > On a side note I am typically reviewing SIP on our network using > sngrep, when relaying these messages over UDP sngrep is failing to > read the packets (presumably due to the extremely large SDP failing > reassembly). While I'm writing I wondered if anyone has seen this > before and could offer advice - the target endpoint (FreeSWITCH) has > no issues reading it. One workaround could be to use TCP (tested and > works) however I was curious if there was another solution? > > Thanks, > > Callum > > > > *^0333 332 0000 | www.x-on.co.uk | > _**_^ > * > > X-on is a trading name of Storacall Technology Ltd a limited company > registered in England and Wales. > Registered Office : Avaland House, 110 London Road, Apsley, Hemel > Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. > The information in this e-mail is confidential and for use by the > addressee(s) only. If you are not the intended recipient, please > notify X-on immediately on +44(0)333 332 0000 and delete the > message from your computer. If you are not a named addressee you must > not use, disclose, disseminate, distribute, copy, print or reply to > this email. Views or opinions expressed by an individual > within this email may not necessarily reflect the views of X-on or its > associated companies. Although X-on routinely screens for viruses, > addressees should scan this email and any attachments > for viruses. X-on makes no representation or warranty as to the > absence of viruses in this email or any attachments. > > > > _______________________________________________ > 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 callum.guy at x-on.co.uk Wed Jun 12 09:23:21 2019 From: callum.guy at x-on.co.uk (Callum Guy) Date: Wed, 12 Jun 2019 14:23:21 +0100 Subject: [OpenSIPS-Users] Block lookups for WebRTC DNS .invalid In-Reply-To: References: Message-ID: Excellent, thanks Bogdan. That looks to be the solution, apologies for missing the recent email! All the best, Callum On Wed, 12 Jun 2019 at 14:03, Bogdan-Andrei Iancu wrote: > Hi, > > There was a similar email couple of days ago - the idea is to do > fix_nated_contact() for all the traffic (replies and requests) coming from > the WS(S) end point (as such endpoints are not able to provide a routable > contact) > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/12/2019 12:08 PM, Callum Guy wrote: > > Hi All, > > I am in the process of configuring a WebRTC/SIP proxy and wanted to know > if there was any way to prevent OpenSIPs from attempting to resolve the > .invalid domains present in the Via headers: > > INVITE sip:abc at us.net SIP/2.0 > Via: SIP/2.0/WSS b7evbq9f9q22.invalid;branch=z9hG4bK5495466 > > Although all is working I'm seeing the following log message. > > CRITICAL:core:mk_proxy: could not resolve hostname: "b7evbq9f9q22.invalid" > > Certainly it seems that this is compliant with the RFC defined behaviour ( > https://tools.ietf.org/html/rfc7118#appendix-B.1) however I am hoping > there is a simple way to block lookups to this domain to save resources etc. > > On a side note I am typically reviewing SIP on our network using sngrep, > when relaying these messages over UDP sngrep is failing to read the packets > (presumably due to the extremely large SDP failing reassembly). While I'm > writing I wondered if anyone has seen this before and could offer advice - > the target endpoint (FreeSWITCH) has no issues reading it. One workaround > could be to use TCP (tested and works) however I was curious if there was > another solution? > > Thanks, > > Callum > > > > *0333 332 0000 | www.x-on.co.uk | ** > > * > > X-on is a trading name of Storacall Technology Ltd a limited company > registered in England and Wales. > Registered Office : Avaland House, 110 London Road, Apsley, Hemel > Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. > The information in this e-mail is confidential and for use by the > addressee(s) only. If you are not the intended recipient, please notify > X-on immediately on +44(0)333 332 0000 and delete the > message from your computer. If you are not a named addressee you must not > use, disclose, disseminate, distribute, copy, print or reply to this email. Views > or opinions expressed by an individual > within this email may not necessarily reflect the views of X-on or its > associated companies. Although X-on routinely screens for viruses, > addressees should scan this email and any attachments > for viruses. X-on makes no representation or warranty as to the absence of > viruses in this email or any attachments. > > > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > -- *0333 332 0000  |  www.x-on.co.uk   |   **      * X-on is a trading name of Storacall Technology Ltd a limited company registered in England and Wales. Registered Office : Avaland House, 110 London Road, Apsley, Hemel Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient, please notify X-on immediately on +44(0)333 332 0000 and delete the message from your computer. If you are not a named addressee you must not use, disclose, disseminate, distribute, copy, print or reply to this email. Views or opinions expressed by an individual within this email may not necessarily reflect the views of X-on or its associated companies. Although X-on routinely screens for viruses, addressees should scan this email and any attachments for viruses. X-on makes no representation or warranty as to the absence of viruses in this email or any attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: From podguiko at mail.ru Wed Jun 12 12:42:51 2019 From: podguiko at mail.ru (=?UTF-8?B?0J7Qu9C10LMg0J/QvtC00LPRg9C50LrQvg==?=) Date: Wed, 12 Jun 2019 19:42:51 +0300 Subject: [OpenSIPS-Users] =?utf-8?q?How_to_add_ISUP_part_to_403_via_send?= =?utf-8?q?=5Freply_function=3F?= Message-ID: <1560357771.145299644@f386.i.mail.ru> My opensips works as state-full-proxy. At the one side it works via SIP-I, at another side via SIP. Everything is ok. In one of my business-cases I get some INVITE with ISUP body with certain parameters from SIP-I side I need to send 403 with ISUP body including ISUP reason. To do this I try to use function:  send_reply("403","Some reason"). It looks like  # Encapsulate a REL add_isup_part("REL"); $isup_param(Cause Indicators | Cause value) = 21; send_reply("403","The reason is 21"); xlog("L_WARN","The call was rejected with 21"); exit; But actually 403 is sending without any ISUP body. Is it possible to do such action?    -- Oleg Podguyko -------------- next part -------------- An HTML attachment was scrubbed... URL: From johan at democon.be Wed Jun 12 15:28:53 2019 From: johan at democon.be (johan de clercq) Date: Wed, 12 Jun 2019 21:28:53 +0200 Subject: [OpenSIPS-Users] problem with git branch for opensips 3.0 In-Reply-To: <7600dd61-bd03-4bcd-3295-fa054cb01ca9@opensips.org> References: <005001d52091$5daf6460$190e2d20$@democon.be> <1560324214026-0.post@n2.nabble.com> <01d002c5-c9d8-a8c6-c7fe-d21cd402ee99@opensips.org> <7600dd61-bd03-4bcd-3295-fa054cb01ca9@opensips.org> Message-ID: <005c01d52155$12a297c0$37e7c740$@democon.be> A few remarks on installing opensips-cli : pip3 install mysqlclient sqlalchemy sqlalchemy-utils Collecting mysqlclient Downloading https://files.pythonhosted.org/packages/f4/f1/3bb6f64ca7a429729413e6556b7ba5976df06019a5245a43d36032f1061e/mysqlclient-1.4.2.post1.tar.gz (85kB) 100% |████████████████████████████████| 92kB 4.2MB/s Complete output from command python setup.py egg_info: Traceback (most recent call last): File "", line 1, in ImportError: No module named 'setuptools' * apt install python-setuptools fixes this Next error : invalid command bdist-wheel * Pip3 install wheel fixes this. Next, MySQLdb/_mysql.c:37:20: fatal error: Python.h: No such file or directory #include "Python.h" ^ compilation terminated. error: command 'x86_64-linux-gnu-gcc' failed with exit status 1 * apt-get install python3-dev fixes this. While installing opensips-cli : there seems to be a hard coded dependency to sqlalchemy 1.3.3 : Installed /usr/local/lib/python3.5/dist-packages/opensipscli-0.1-py3.5.egg Processing dependencies for opensipscli==0.1 Searching for sqlalchemy==1.3.3 Reading https://pypi.org/simple/sqlalchemy/ ^Cinterrupted My installed version is 1.3.4 Installing collected packages: mysqlclient, sqlalchemy, six, sqlalchemy-utils Successfully installed mysqlclient-1.4.2.post1 six-1.12.0 sqlalchemy-1.3.4 sqlalchemy-utils-0.34.0 * pip3 uninstall sqlalchemy followed by pip3 install sqlalchemy==1.3.3 From: Bogdan-Andrei Iancu Sent: Wednesday, June 12, 2019 11:06 AM To: Johan De Clercq Cc: OpenSIPS users mailling list ; Liviu Chircu Subject: Re: [OpenSIPS-Users] problem with git branch for opensips 3.0 You are right, the doc is missing the "migrate" part. Liviu will update the docs there. Thanks for the note ! Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/12/2019 11:29 AM, Johan De Clercq wrote: Looking here https://github.com/OpenSIPS/opensips-cli/blob/master/docs/modules/database.md, I can't find back how to migrate a 24 db to 30. Can you have a look ? Thanks. Op wo 12 jun. 2019 om 10:26 schreef Bogdan-Andrei Iancu >: Hi Johan, The git contains good docs for the cli tool - if there is something you find as uncovered, please let us know. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/12/2019 10:31 AM, Johan De Clercq wrote: Okay. So is there somewhere good documentation on this? In exact, how do I configure this, and how do I migrate 24 dB to opensips 30? On Wed, 12 Jun 2019, 09:25 vasilevalex, > wrote: Hi, Johan. Everything ok with git. Just check this commit: 8a7abc05195fb4a29d5439871d7691c090c60d32 (https://github.com/OpenSIPS/opensips/commit/8a7abc05195fb4a29d5439871d7691c090c60d32) ----- --- Alexey Vasilyev -- Sent from: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html _______________________________________________ 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 johan at democon.be Wed Jun 12 15:55:46 2019 From: johan at democon.be (johan de clercq) Date: Wed, 12 Jun 2019 21:55:46 +0200 Subject: [OpenSIPS-Users] problem with git branch for opensips 3.0 In-Reply-To: <7600dd61-bd03-4bcd-3295-fa054cb01ca9@opensips.org> References: <005001d52091$5daf6460$190e2d20$@democon.be> <1560324214026-0.post@n2.nabble.com> <01d002c5-c9d8-a8c6-c7fe-d21cd402ee99@opensips.org> <7600dd61-bd03-4bcd-3295-fa054cb01ca9@opensips.org> Message-ID: <007501d52158$d3a2acf0$7ae806d0$@democon.be> It seems that database migrate x y has a problem when x has special characters. mysql -h 10.0.0.0 -u opensips3_x -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MySQL connection id is 34042687 Server version: 5.6.36-82.0-56 Percona XtraDB Cluster (GPL), Release rel82.0, Revision de7a681, WSREP version 26.20, wsrep_26.20 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MySQL [(none)]> show databases; +--------------------+ | Database | +--------------------+ | information_schema | | opensips3_x | +--------------------+ 2 rows in set (0.01 sec) When I do this in opensips-cli : (opensips-cli): database migrate "opensips3_x" "opensips_x_3_0" Please provide the URL of the database: mysql://opensips3_x:xxxxxxx at 10.0.0.0/ ERROR: the source database (opensips3_dust) does not exist! Can you please correct ? From: Bogdan-Andrei Iancu Sent: Wednesday, June 12, 2019 11:06 AM To: Johan De Clercq Cc: OpenSIPS users mailling list ; Liviu Chircu Subject: Re: [OpenSIPS-Users] problem with git branch for opensips 3.0 You are right, the doc is missing the "migrate" part. Liviu will update the docs there. Thanks for the note ! Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/12/2019 11:29 AM, Johan De Clercq wrote: Looking here https://github.com/OpenSIPS/opensips-cli/blob/master/docs/modules/database.md, I can't find back how to migrate a 24 db to 30. Can you have a look ? Thanks. Op wo 12 jun. 2019 om 10:26 schreef Bogdan-Andrei Iancu >: Hi Johan, The git contains good docs for the cli tool - if there is something you find as uncovered, please let us know. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/12/2019 10:31 AM, Johan De Clercq wrote: Okay. So is there somewhere good documentation on this? In exact, how do I configure this, and how do I migrate 24 dB to opensips 30? On Wed, 12 Jun 2019, 09:25 vasilevalex, > wrote: Hi, Johan. Everything ok with git. Just check this commit: 8a7abc05195fb4a29d5439871d7691c090c60d32 (https://github.com/OpenSIPS/opensips/commit/8a7abc05195fb4a29d5439871d7691c090c60d32) ----- --- Alexey Vasilyev -- Sent from: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html _______________________________________________ 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 johan at democon.be Wed Jun 12 16:17:03 2019 From: johan at democon.be (johan de clercq) Date: Wed, 12 Jun 2019 22:17:03 +0200 Subject: [OpenSIPS-Users] problem with git branch for opensips 3.0 In-Reply-To: <007501d52158$d3a2acf0$7ae806d0$@democon.be> References: <005001d52091$5daf6460$190e2d20$@democon.be> <1560324214026-0.post@n2.nabble.com> <01d002c5-c9d8-a8c6-c7fe-d21cd402ee99@opensips.org> <7600dd61-bd03-4bcd-3295-fa054cb01ca9@opensips.org> <007501d52158$d3a2acf0$7ae806d0$@democon.be> Message-ID: <007c01d5215b$ccae1940$660a4bc0$@democon.be> This I found : you need to drop the last / in the connection string (mysql://opensips3_x:xxxxxxx at 10.0.0.0 instead of mysql://opensips3_x:xxxxxxx at 10.0.0.0/) It creates the tables, but the import fails : The 'test' database has been successfully created! Migrating all matching OpenSIPS tables... Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/base.py", line 1244, in _execute_context cursor, statement, parameters, context File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/default.py", line 552, in do_execute cursor.execute(statement, parameters) File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 206, in execute res = self._query(query) File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 312, in _query db.query(q) File "/usr/local/lib/python3.5/dist-packages/MySQLdb/connections.py", line 224, in query _mysql.connection.query(self, query) MySQLdb._exceptions.OperationalError: (1136, "Column count doesn't match value count at row 1") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/bin/opensips-cli", line 4, in __import__('pkg_resources').run_script('opensipscli==0.1', 'opensips-cli') File "/usr/local/lib/python3.5/dist-packages/pkg_resources/__init__.py", line 666, in run_script self.require(requires)[0].run_script(script_name, ns) File "/usr/local/lib/python3.5/dist-packages/pkg_resources/__init__.py", line 1453, in run_script exec(code, namespace, namespace) File "/usr/local/lib/python3.5/dist-packages/opensipscli-0.1-py3.5.egg/EGG-INFO/scripts/opensips-cli", line 9, in run_console() File "/usr/local/lib/python3.5/dist-packages/opensipscli-0.1-py3.5.egg/EGG-INFO/scripts/opensips-cli", line 6, in run_console main.main() File "/usr/local/lib/python3.5/dist-packages/opensipscli-0.1-py3.5.egg/opensipscli/main.py", line 78, in main sys.exit(shell.cmdloop()) File "/usr/local/lib/python3.5/dist-packages/opensipscli-0.1-py3.5.egg/opensipscli/cli.py", line 206, in cmdloop super(OpenSIPSCLIShell, self).cmdloop(intro='') File "/usr/lib/python3.5/cmd.py", line 138, in cmdloop stop = self.onecmd(line) File "/usr/lib/python3.5/cmd.py", line 216, in onecmd return self.default(line) File "/usr/local/lib/python3.5/dist-packages/opensipscli-0.1-py3.5.egg/opensipscli/cli.py", line 304, in default self.run_command(module, cmd, params) File "/usr/local/lib/python3.5/dist-packages/opensipscli-0.1-py3.5.egg/opensipscli/cli.py", line 293, in run_command return mod[0].__invoke__(cmd, params) File "/usr/local/lib/python3.5/dist-packages/opensipscli-0.1-py3.5.egg/opensipscli/module.py", line 30, in __invoke__ return f(params) File "/usr/local/lib/python3.5/dist-packages/opensipscli-0.1-py3.5.egg/opensipscli/modules/database.py", line 344, in do_migrate db.migrate(migrate_scripts, old_db, new_db) File "/usr/local/lib/python3.5/dist-packages/opensipscli-0.1-py3.5.egg/opensipscli/db.py", line 174, in migrate old_db, old_db, new_db)).execution_options(autocommit=True)) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/base.py", line 988, in execute return meth(self, multiparams, params) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/sql/elements.py", line 287, in _execute_on_connection return connection._execute_clauseelement(self, multiparams, params) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/base.py", line 1107, in _execute_clauseelement distilled_params, File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/base.py", line 1248, in _execute_context e, statement, parameters, cursor, context File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/base.py", line 1466, in _handle_dbapi_exception util.raise_from_cause(sqlalchemy_exception, exc_info) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/util/compat.py", line 383, in raise_from_cause reraise(type(exception), exception, tb=exc_tb, cause=cause) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/util/compat.py", line 128, in reraise raise value.with_traceback(tb) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/base.py", line 1244, in _execute_context cursor, statement, parameters, context File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/default.py", line 552, in do_execute cursor.execute(statement, parameters) File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 206, in execute res = self._query(query) File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 312, in _query db.query(q) File "/usr/local/lib/python3.5/dist-packages/MySQLdb/connections.py", line 224, in query _mysql.connection.query(self, query) sqlalchemy.exc.OperationalError: (MySQLdb._exceptions.OperationalError) (1136, "Column count doesn't match value count at row 1") From: johan de clercq Sent: Wednesday, June 12, 2019 9:56 PM To: 'Bogdan-Andrei Iancu' Cc: 'OpenSIPS users mailling list' ; 'Liviu Chircu' Subject: RE: [OpenSIPS-Users] problem with git branch for opensips 3.0 It seems that database migrate x y has a problem when x has special characters. mysql -h 10.0.0.0 -u opensips3_x -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MySQL connection id is 34042687 Server version: 5.6.36-82.0-56 Percona XtraDB Cluster (GPL), Release rel82.0, Revision de7a681, WSREP version 26.20, wsrep_26.20 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MySQL [(none)]> show databases; +--------------------+ | Database | +--------------------+ | information_schema | | opensips3_x | +--------------------+ 2 rows in set (0.01 sec) When I do this in opensips-cli : (opensips-cli): database migrate "opensips3_x" "opensips_x_3_0" Please provide the URL of the database: mysql://opensips3_x:xxxxxxx at 10.0.0.0/ ERROR: the source database (opensips3_dust) does not exist! Can you please correct ? From: Bogdan-Andrei Iancu > Sent: Wednesday, June 12, 2019 11:06 AM To: Johan De Clercq > Cc: OpenSIPS users mailling list >; Liviu Chircu > Subject: Re: [OpenSIPS-Users] problem with git branch for opensips 3.0 You are right, the doc is missing the "migrate" part. Liviu will update the docs there. Thanks for the note ! Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/12/2019 11:29 AM, Johan De Clercq wrote: Looking here https://github.com/OpenSIPS/opensips-cli/blob/master/docs/modules/database.md, I can't find back how to migrate a 24 db to 30. Can you have a look ? Thanks. Op wo 12 jun. 2019 om 10:26 schreef Bogdan-Andrei Iancu >: Hi Johan, The git contains good docs for the cli tool - if there is something you find as uncovered, please let us know. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/12/2019 10:31 AM, Johan De Clercq wrote: Okay. So is there somewhere good documentation on this? In exact, how do I configure this, and how do I migrate 24 dB to opensips 30? On Wed, 12 Jun 2019, 09:25 vasilevalex, > wrote: Hi, Johan. Everything ok with git. Just check this commit: 8a7abc05195fb4a29d5439871d7691c090c60d32 (https://github.com/OpenSIPS/opensips/commit/8a7abc05195fb4a29d5439871d7691c090c60d32) ----- --- Alexey Vasilyev -- Sent from: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html _______________________________________________ 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 vladp at opensips.org Thu Jun 13 05:53:15 2019 From: vladp at opensips.org (Vlad Patrascu) Date: Thu, 13 Jun 2019 12:53:15 +0300 Subject: [OpenSIPS-Users] How to add ISUP part to 403 via send_reply function? In-Reply-To: <1560357771.145299644@f386.i.mail.ru> References: <1560357771.145299644@f386.i.mail.ru> Message-ID: <9e1c9d08-bebf-281d-23d7-b81e08b4fbc3@opensips.org> Hi Oleg, Unfortunately, at the moment there is no way to do this, as the /add_isup_part()/ function appends an ISUP body to the SIP message exposed in the current script route. So the only option is to add the ISUP body to a received reply, not a locally generated one. Also, it's not an easy/quick feature to implement, but if you don't find a way around it and think it would be useful, please open a feature request on Github. Regards, Vlad Patrascu OpenSIPS Developer http://www.opensips-solutions.com On 06/12/2019 07:42 PM, Олег Подгуйко via Users wrote: > My opensips works as state-full-proxy. At the one side it works via > SIP-I, at another side via SIP. Everything is ok. > In one of my business-cases I get some INVITE with ISUP body with > certain parameters from SIP-I side I need to send 403 with ISUP body > including ISUP reason. > To do this I try to use function:  send_reply("403","Some reason"). > > It looks like > > # Encapsulate a REL > add_isup_part("REL"); > $isup_param(Cause Indicators | Cause value) = 21; > send_reply("403","The reason is 21"); > xlog("L_WARN","The call was rejected with 21"); > exit; > > But actually 403 is sending without any ISUP body. > > Is it possible to do such action? > > > -- > Oleg Podguyko > > > _______________________________________________ > 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 farmorg at gmail.com Thu Jun 13 08:58:08 2019 From: farmorg at gmail.com (Mark Farmer) Date: Thu, 13 Jun 2019 13:58:08 +0100 Subject: [OpenSIPS-Users] Odd 503 Reply Message-ID: Hi all I've got a dialog profile setup to count calls from $si which if it hits the allowed limit responds with a 503 Service Unavailable as required by our provider. Looking at the 503 in Wireshark shows the SIP headers in the message body rather than message header. I'm getting the same thing using both send_reply() & t_reply() I followed the instructions here: https://www.opensips.org/Documentation/Tutorials-ConcurrentCallsLimitation Surely this can't be correct behaviour? What am I missing? opensips -V version: opensips 2.4.5 (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, sigio_rt, select. git revision: d025b4f61 main.c compiled on 11:39:27 Apr 12 2019 with gcc 7 TIA Mark. -- Mark Farmer farmorg at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From farmorg at gmail.com Thu Jun 13 09:09:32 2019 From: farmorg at gmail.com (Mark Farmer) Date: Thu, 13 Jun 2019 14:09:32 +0100 Subject: [OpenSIPS-Users] Odd 503 Reply In-Reply-To: References: Message-ID: Never mind, turns out I had a newline in the response text. My bad there but one to watch out for! Mark. On Thu, 13 Jun 2019 at 13:58, Mark Farmer wrote: > Hi all > > I've got a dialog profile setup to count calls from $si which if it hits > the allowed limit responds with a 503 Service Unavailable as required by > our provider. > > Looking at the 503 in Wireshark shows the SIP headers in the message body > rather than message header. > > I'm getting the same thing using both send_reply() & t_reply() > > I followed the instructions here: > https://www.opensips.org/Documentation/Tutorials-ConcurrentCallsLimitation > > Surely this can't be correct behaviour? What am I missing? > > opensips -V > version: opensips 2.4.5 (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, sigio_rt, select. > git revision: d025b4f61 > main.c compiled on 11:39:27 Apr 12 2019 with gcc 7 > > TIA > Mark. > > > -- > Mark Farmer > farmorg at gmail.com > -- Mark Farmer farmorg at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Thu Jun 13 09:18:54 2019 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Thu, 13 Jun 2019 16:18:54 +0300 Subject: [OpenSIPS-Users] I need some help in websocket connection error . In-Reply-To: References: Message-ID: Can you trace the SSL traffic between the two endpoints? Perhaps the SSL header give you a reason for not accepting the connection. Is this happening only for certain clients, or for everyone? Are you requiring any certificates validation? Best regards, Răzvan On 6/12/19 3:34 PM, Sasmita Panda wrote: > I am using opensips 2.2 >  version: opensips 2.2.4 (x86_64/linux) > > I am using the proto_wss and tls_mgm module for establishing websocket > connection . > > I am getting bellow error again and again . Whats the reson behind this > and how can I solve this problem ? > > > Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 96 > Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: > ERROR:proto_wss:tls_accept: New TLS connection from 192.168.160.6:58616 > failed to accept > Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: > ERROR:proto_wss:wss_read_req: cannot fix read connection > Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 96 > Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: > ERROR:proto_wss:tls_accept: New TLS connection from 192.168.175.59:12918 > failed to accept > Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: > ERROR:proto_wss:wss_read_req: cannot fix read connection > > > Please do help . > > > > */Thanks & Regards/* > /Sasmita Panda/ > /Senior 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 > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com From johan at democon.be Thu Jun 13 16:02:16 2019 From: johan at democon.be (johan de clercq) Date: Thu, 13 Jun 2019 22:02:16 +0200 Subject: [OpenSIPS-Users] proto_smtp questions. Message-ID: <00a801d52222$e6b12860$b4137920$@democon.be> Hello everybody, First of all, thanks for making proto_smtp. At one of my major customers, this saves me configuring kennel and creating messages myself. Having said that, I have a few questions: Reading the module doc, - is the module capable of being client and server (in exacto: when opensips wants to send an sms to sms-g, opensips issues the bind request; when sms-g wants to send an sms to opensips, sms-g opens the connection) ? - Does opensips automatically reconnect if the session with sms-g is dropped ? Best regards, Johan De Clercq, Managing Director Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke Tel +3256980990 - GSM +32478720104 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From spanda at 3clogic.com Fri Jun 14 04:15:01 2019 From: spanda at 3clogic.com (Sasmita Panda) Date: Fri, 14 Jun 2019 13:45:01 +0530 Subject: [OpenSIPS-Users] I need some help in websocket connection error . In-Reply-To: References: Message-ID: I had a dedicated server for 1 Client . When that client faces the issue I started looking into the logs . And this is what the error I got . but latter on when I saw other servers which is getting used by different client in that logs also same error coming everyday . As a conclusion its happening with everybody . Below is the configuration . modparam("tls_mgm", "tls_method", "tlsv1_2") modparam("tls_mgm", "verify_cert", "0") modparam("tls_mgm", "require_cert", "0") modparam("tls_mgm", "certificate", "/usr/etc/opensips/tls/3ccloudwebrtc2019.crt") modparam("tls_mgm", "private_key", "/usr/etc/opensips/tls/3ccloud.key") modparam("tls_mgm", "ca_list", "/usr/etc/opensips/tls/rootCA/cacert.pem") *Thanks & Regards* *Sasmita Panda* *Senior Network Testing and Software Engineer* *3CLogic , ph:07827611765* On Thu, Jun 13, 2019 at 6:50 PM Răzvan Crainea wrote: > Can you trace the SSL traffic between the two endpoints? Perhaps the SSL > header give you a reason for not accepting the connection. > Is this happening only for certain clients, or for everyone? > Are you requiring any certificates validation? > > Best regards, > Răzvan > > On 6/12/19 3:34 PM, Sasmita Panda wrote: > > I am using opensips 2.2 > > version: opensips 2.2.4 (x86_64/linux) > > > > I am using the proto_wss and tls_mgm module for establishing websocket > > connection . > > > > I am getting bellow error again and again . Whats the reson behind this > > and how can I solve this problem ? > > > > > > Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: > > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > > Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: > > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 96 > > Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: > > ERROR:proto_wss:tls_accept: New TLS connection from 192.168.160.6:58616 > > failed to accept > > Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: > > ERROR:proto_wss:wss_read_req: cannot fix read connection > > Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: > > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > > Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: > > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 96 > > Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: > > ERROR:proto_wss:tls_accept: New TLS connection from 192.168.175.59:12918 > > failed to accept > > Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: > > ERROR:proto_wss:wss_read_req: cannot fix read connection > > > > > > Please do help . > > > > > > > > */Thanks & Regards/* > > /Sasmita Panda/ > > /Senior 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 > > > > -- > Răzvan Crainea > OpenSIPS Core 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 callum.guy at x-on.co.uk Fri Jun 14 05:18:30 2019 From: callum.guy at x-on.co.uk (Callum Guy) Date: Fri, 14 Jun 2019 10:18:30 +0100 Subject: [OpenSIPS-Users] I need some help in websocket connection error . In-Reply-To: References: Message-ID: You might find that a tcpdump is the only way to get to grips with the underlying issue. Having said that I wonder if there is any chance that the connection isn't accepting simply due to a cipher incompatibility. Are you setting a cipher list that you know your clients accept? Maybe try: modparam("tls_mgm", "ciphers_list", "AES256-GCM-SHA384,AES256-SHA256,AES256-SHA,CAMELLIA256-SHA,AES128-SHA,CAMELLIA128-SHA,RC4-SHA") On Fri, 14 Jun 2019 at 09:17, Sasmita Panda wrote: > I had a dedicated server for 1 Client . When that client faces the issue I > started looking into the logs . And this is what the error I got . > > but latter on when I saw other servers which is getting used by different > client in that logs also same error coming everyday . > > As a conclusion its happening with everybody . > > Below is the configuration . > > modparam("tls_mgm", "tls_method", "tlsv1_2") > modparam("tls_mgm", "verify_cert", "0") > modparam("tls_mgm", "require_cert", "0") > modparam("tls_mgm", "certificate", > "/usr/etc/opensips/tls/3ccloudwebrtc2019.crt") > modparam("tls_mgm", "private_key", "/usr/etc/opensips/tls/3ccloud.key") > modparam("tls_mgm", "ca_list", "/usr/etc/opensips/tls/rootCA/cacert.pem") > > > > *Thanks & Regards* > *Sasmita Panda* > *Senior Network Testing and Software Engineer* > *3CLogic , ph:07827611765* > > > On Thu, Jun 13, 2019 at 6:50 PM Răzvan Crainea > wrote: > >> Can you trace the SSL traffic between the two endpoints? Perhaps the SSL >> header give you a reason for not accepting the connection. >> Is this happening only for certain clients, or for everyone? >> Are you requiring any certificates validation? >> >> Best regards, >> Răzvan >> >> On 6/12/19 3:34 PM, Sasmita Panda wrote: >> > I am using opensips 2.2 >> > version: opensips 2.2.4 (x86_64/linux) >> > >> > I am using the proto_wss and tls_mgm module for establishing websocket >> > connection . >> > >> > I am getting bellow error again and again . Whats the reson behind this >> > and how can I solve this problem ? >> > >> > >> > Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: >> > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb >> > Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: >> > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 96 >> > Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: >> > ERROR:proto_wss:tls_accept: New TLS connection from 192.168.160.6:58616 >> > failed to accept >> > Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: >> > ERROR:proto_wss:wss_read_req: cannot fix read connection >> > Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: >> > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb >> > Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: >> > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 96 >> > Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: >> > ERROR:proto_wss:tls_accept: New TLS connection from >> 192.168.175.59:12918 >> > failed to accept >> > Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: >> > ERROR:proto_wss:wss_read_req: cannot fix read connection >> > >> > >> > Please do help . >> > >> > >> > >> > */Thanks & Regards/* >> > /Sasmita Panda/ >> > /Senior 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 >> > >> >> -- >> Răzvan Crainea >> OpenSIPS Core 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 > -- *0333 332 0000  |  www.x-on.co.uk   |   **      * X-on is a trading name of Storacall Technology Ltd a limited company registered in England and Wales. Registered Office : Avaland House, 110 London Road, Apsley, Hemel Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient, please notify X-on immediately on +44(0)333 332 0000 and delete the message from your computer. If you are not a named addressee you must not use, disclose, disseminate, distribute, copy, print or reply to this email. Views or opinions expressed by an individual within this email may not necessarily reflect the views of X-on or its associated companies. Although X-on routinely screens for viruses, addressees should scan this email and any attachments for viruses. X-on makes no representation or warranty as to the absence of viruses in this email or any attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Fri Jun 14 08:37:33 2019 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Fri, 14 Jun 2019 15:37:33 +0300 Subject: [OpenSIPS-Users] proto_smtp questions. In-Reply-To: <00a801d52222$e6b12860$b4137920$@democon.be> References: <00a801d52222$e6b12860$b4137920$@democon.be> Message-ID: Hi, Johan! I'm glad the proto_smpp module is helpful :). Yes, it can both connect to a smsc, and accept connections from Kannel from example. Yes, opensips automatically reconnects - it would be nice to have an MI command that could trigger that, to prevent errors in the logs, but that's not yet implemented. Thanks for giving it a shot, let me know if there are any issues with it. And, of course, submit any feature requests that you find useful! Best regards, Răzvan On 6/13/19 11:02 PM, johan de clercq wrote: > Hello everybody, > > First of all, thanks for making proto_smtp.  At one of my major > customers, this saves me configuring kennel and creating messages myself. > > Having said that, I have a few questions: > > Reading the module doc, > > -is the  module capable of being client and server (in exacto: when > opensips wants to send an sms to sms-g, opensips issues the bind > request; when sms-g wants to send an sms to opensips, sms-g opens the > connection) ? > > -Does opensips automatically reconnect if the session with sms-g is > dropped ? > > Best regards, > > cid:F3100D46-F00D-4610-87ED-3E91DA790A82 > > Johan De Clercq, Managing Director > Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke > > Tel +3256980990– GSM +32478720104 > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com From vma at sip.solutions Sat Jun 15 12:51:10 2019 From: vma at sip.solutions (Vallimamod Abdullah) Date: Sat, 15 Jun 2019 18:51:10 +0200 Subject: [OpenSIPS-Users] hash mismatch error from debian stretch repo Message-ID: <4F570AC5-C848-4317-9426-8395D7C978EA@sip.solutions> Hello, I am trying to upgrade from 2.4 to version 3.0 from debian stretch apt repo and I am getting the following hash errors: Get: 1 http://apt.opensips.org stretch/3.0-releases amd64 opensips-redis-module amd64 3.0.0-1 [192 kB] Err http://apt.opensips.org stretch/3.0-releases amd64 opensips-redis-module amd64 3.0.0-1 Hash Sum mismatch Hashes of expected file: - SHA512:ff56e20fede1e8ff4475d6a00ead8687c2f66ccc37399b0e796e02bdd33826d8ed73502f123c9e3098a0b49913a773547616cdde2acb92ad27f5ba33514312b4 - SHA256:70dc8c94d9abdcf33d0a907dcec10c58de7118f2c0029e1b1ef846a2fd28ae37 - SHA1:360bc3d614bed8a82a8f71d64445574045fa5f98 [weak] - MD5Sum:1657a30f22d414d0dce67b8b7237a566 [weak] - Filesize:191548 [weak] Hashes of received file: - SHA512:cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e - SHA256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 - SHA1:da39a3ee5e6b4b0d3255bfef95601890afd80709 [weak] - MD5Sum:d41d8cd98f00b204e9800998ecf8427e [weak] - Filesize:0 [weak] Last modification reported: Thu, 30 May 2019 09:08:36 +0000 [...] After futher check it looks like a web server issue: curl -v http://apt.opensips.org/pool/stretch/3.0-releases/o/opensips/opensips-redis-module_3.0.0-1_amd64.deb * Trying 176.9.203.99... * TCP_NODELAY set * Connected to apt.opensips.org (176.9.203.99) port 80 (#0) > GET /pool/stretch/3.0-releases/o/opensips/opensips-redis-module_3.0.0-1_amd64.deb HTTP/1.1 > Host: apt.opensips.org > User-Agent: curl/7.52.1 > Accept: */* > < HTTP/1.1 200 OK < Server: nginx < Date: Sat, 15 Jun 2019 16:49:07 GMT < Content-Type: application/octet-stream < Content-Length: 191548 < Last-Modified: Thu, 30 May 2019 09:08:36 GMT < Connection: keep-alive < ETag: "5cef9d94-2ec3c" < Accept-Ranges: bytes < * transfer closed with 191548 bytes remaining to read * Curl_http_done: called premature == 1 * stopped the pause stream! * Closing connection 0 curl: (18) transfer closed with 191548 bytes remaining to read Anbody else getting the same error? Thank you. Best Regards, -- Vallimamod Abdullah SIP Solutions vma at sip.solutions linkedin.com/in/vallimamod . From nick at altmann.pro Sat Jun 15 14:30:45 2019 From: nick at altmann.pro (Nick Altmann) Date: Sat, 15 Jun 2019 20:30:45 +0200 Subject: [OpenSIPS-Users] hash mismatch error from debian stretch repo In-Reply-To: <4F570AC5-C848-4317-9426-8395D7C978EA@sip.solutions> References: <4F570AC5-C848-4317-9426-8395D7C978EA@sip.solutions> Message-ID: It's a hardware issue on the repository server. I'm working to fix this. сб, 15 июн. 2019 г. в 18:55, Vallimamod Abdullah : > Hello, > > I am trying to upgrade from 2.4 to version 3.0 from debian stretch apt > repo and I am getting the following hash errors: > > Get: 1 http://apt.opensips.org stretch/3.0-releases amd64 > opensips-redis-module amd64 3.0.0-1 [192 kB] > Err http://apt.opensips.org stretch/3.0-releases amd64 > opensips-redis-module amd64 3.0.0-1 > Hash Sum mismatch > Hashes of expected file: > - > SHA512:ff56e20fede1e8ff4475d6a00ead8687c2f66ccc37399b0e796e02bdd33826d8ed73502f123c9e3098a0b49913a773547616cdde2acb92ad27f5ba33514312b4 > - SHA256:70dc8c94d9abdcf33d0a907dcec10c58de7118f2c0029e1b1ef846a2fd28ae37 > - SHA1:360bc3d614bed8a82a8f71d64445574045fa5f98 [weak] > - MD5Sum:1657a30f22d414d0dce67b8b7237a566 [weak] > - Filesize:191548 [weak] > Hashes of received file: > - > SHA512:cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e > - SHA256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 > - SHA1:da39a3ee5e6b4b0d3255bfef95601890afd80709 [weak] > - MD5Sum:d41d8cd98f00b204e9800998ecf8427e [weak] > - Filesize:0 [weak] > Last modification reported: Thu, 30 May 2019 09:08:36 +0000 > > [...] > > > After futher check it looks like a web server issue: > > curl -v > http://apt.opensips.org/pool/stretch/3.0-releases/o/opensips/opensips-redis-module_3.0.0-1_amd64.deb > * Trying 176.9.203.99... > * TCP_NODELAY set > * Connected to apt.opensips.org (176.9.203.99) port 80 (#0) > > GET > /pool/stretch/3.0-releases/o/opensips/opensips-redis-module_3.0.0-1_amd64.deb > HTTP/1.1 > > Host: apt.opensips.org > > User-Agent: curl/7.52.1 > > Accept: */* > > > < HTTP/1.1 200 OK > < Server: nginx > < Date: Sat, 15 Jun 2019 16:49:07 GMT > < Content-Type: application/octet-stream > < Content-Length: 191548 > < Last-Modified: Thu, 30 May 2019 09:08:36 GMT > < Connection: keep-alive > < ETag: "5cef9d94-2ec3c" > < Accept-Ranges: bytes > < > * transfer closed with 191548 bytes remaining to read > * Curl_http_done: called premature == 1 > * stopped the pause stream! > * Closing connection 0 > curl: (18) transfer closed with 191548 bytes remaining to read > > Anbody else getting the same error? > > Thank you. > > Best Regards, > -- > Vallimamod Abdullah > SIP Solutions > vma at sip.solutions > linkedin.com/in/vallimamod > . > > > > _______________________________________________ > 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 vma at sip.solutions Sat Jun 15 14:43:25 2019 From: vma at sip.solutions (Vallimamod Abdullah) Date: Sat, 15 Jun 2019 20:43:25 +0200 Subject: [OpenSIPS-Users] hash mismatch error from debian stretch repo In-Reply-To: References: <4F570AC5-C848-4317-9426-8395D7C978EA@sip.solutions> Message-ID: <0E4178B1-5835-45F5-82FB-2321DBBDF24D@sip.solutions> Great! Thank you and good luck! Best Regards, -- Vallimamod Abdullah SIP Solutions vma at sip.solutions linkedin.com/in/vallimamod . > On 15 Jun 2019, at 20:30, Nick Altmann wrote: > > It's a hardware issue on the repository server. I'm working to fix this. > > сб, 15 июн. 2019 г. в 18:55, Vallimamod Abdullah : > Hello, > > I am trying to upgrade from 2.4 to version 3.0 from debian stretch apt repo and I am getting the following hash errors: > > Get: 1 http://apt.opensips.org stretch/3.0-releases amd64 opensips-redis-module amd64 3.0.0-1 [192 kB] > Err http://apt.opensips.org stretch/3.0-releases amd64 opensips-redis-module amd64 3.0.0-1 > Hash Sum mismatch > Hashes of expected file: > - SHA512:ff56e20fede1e8ff4475d6a00ead8687c2f66ccc37399b0e796e02bdd33826d8ed73502f123c9e3098a0b49913a773547616cdde2acb92ad27f5ba33514312b4 > - SHA256:70dc8c94d9abdcf33d0a907dcec10c58de7118f2c0029e1b1ef846a2fd28ae37 > - SHA1:360bc3d614bed8a82a8f71d64445574045fa5f98 [weak] > - MD5Sum:1657a30f22d414d0dce67b8b7237a566 [weak] > - Filesize:191548 [weak] > Hashes of received file: > - SHA512:cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e > - SHA256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 > - SHA1:da39a3ee5e6b4b0d3255bfef95601890afd80709 [weak] > - MD5Sum:d41d8cd98f00b204e9800998ecf8427e [weak] > - Filesize:0 [weak] > Last modification reported: Thu, 30 May 2019 09:08:36 +0000 > > [...] > > > After futher check it looks like a web server issue: > > curl -v http://apt.opensips.org/pool/stretch/3.0-releases/o/opensips/opensips-redis-module_3.0.0-1_amd64.deb > * Trying 176.9.203.99... > * TCP_NODELAY set > * Connected to apt.opensips.org (176.9.203.99) port 80 (#0) > > GET /pool/stretch/3.0-releases/o/opensips/opensips-redis-module_3.0.0-1_amd64.deb HTTP/1.1 > > Host: apt.opensips.org > > User-Agent: curl/7.52.1 > > Accept: */* > > > < HTTP/1.1 200 OK > < Server: nginx > < Date: Sat, 15 Jun 2019 16:49:07 GMT > < Content-Type: application/octet-stream > < Content-Length: 191548 > < Last-Modified: Thu, 30 May 2019 09:08:36 GMT > < Connection: keep-alive > < ETag: "5cef9d94-2ec3c" > < Accept-Ranges: bytes > < > * transfer closed with 191548 bytes remaining to read > * Curl_http_done: called premature == 1 > * stopped the pause stream! > * Closing connection 0 > curl: (18) transfer closed with 191548 bytes remaining to read > > Anbody else getting the same error? > > Thank you. > > Best Regards, > -- > Vallimamod Abdullah > SIP Solutions > vma at sip.solutions > linkedin.com/in/vallimamod > . > > > > _______________________________________________ > 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 nick at altmann.pro Sat Jun 15 14:43:53 2019 From: nick at altmann.pro (Nick Altmann) Date: Sat, 15 Jun 2019 20:43:53 +0200 Subject: [OpenSIPS-Users] hash mismatch error from debian stretch repo In-Reply-To: References: <4F570AC5-C848-4317-9426-8395D7C978EA@sip.solutions> Message-ID: It's fixed now. сб, 15 июн. 2019 г. в 20:30, Nick Altmann : > It's a hardware issue on the repository server. I'm working to fix this. > > сб, 15 июн. 2019 г. в 18:55, Vallimamod Abdullah : > >> Hello, >> >> I am trying to upgrade from 2.4 to version 3.0 from debian stretch apt >> repo and I am getting the following hash errors: >> >> Get: 1 http://apt.opensips.org stretch/3.0-releases amd64 >> opensips-redis-module amd64 3.0.0-1 [192 kB] >> Err http://apt.opensips.org stretch/3.0-releases amd64 >> opensips-redis-module amd64 3.0.0-1 >> Hash Sum mismatch >> Hashes of expected file: >> - >> SHA512:ff56e20fede1e8ff4475d6a00ead8687c2f66ccc37399b0e796e02bdd33826d8ed73502f123c9e3098a0b49913a773547616cdde2acb92ad27f5ba33514312b4 >> - SHA256:70dc8c94d9abdcf33d0a907dcec10c58de7118f2c0029e1b1ef846a2fd28ae37 >> - SHA1:360bc3d614bed8a82a8f71d64445574045fa5f98 [weak] >> - MD5Sum:1657a30f22d414d0dce67b8b7237a566 [weak] >> - Filesize:191548 [weak] >> Hashes of received file: >> - >> SHA512:cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e >> - SHA256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 >> - SHA1:da39a3ee5e6b4b0d3255bfef95601890afd80709 [weak] >> - MD5Sum:d41d8cd98f00b204e9800998ecf8427e [weak] >> - Filesize:0 [weak] >> Last modification reported: Thu, 30 May 2019 09:08:36 +0000 >> >> [...] >> >> >> After futher check it looks like a web server issue: >> >> curl -v >> http://apt.opensips.org/pool/stretch/3.0-releases/o/opensips/opensips-redis-module_3.0.0-1_amd64.deb >> * Trying 176.9.203.99... >> * TCP_NODELAY set >> * Connected to apt.opensips.org (176.9.203.99) port 80 (#0) >> > GET >> /pool/stretch/3.0-releases/o/opensips/opensips-redis-module_3.0.0-1_amd64.deb >> HTTP/1.1 >> > Host: apt.opensips.org >> > User-Agent: curl/7.52.1 >> > Accept: */* >> > >> < HTTP/1.1 200 OK >> < Server: nginx >> < Date: Sat, 15 Jun 2019 16:49:07 GMT >> < Content-Type: application/octet-stream >> < Content-Length: 191548 >> < Last-Modified: Thu, 30 May 2019 09:08:36 GMT >> < Connection: keep-alive >> < ETag: "5cef9d94-2ec3c" >> < Accept-Ranges: bytes >> < >> * transfer closed with 191548 bytes remaining to read >> * Curl_http_done: called premature == 1 >> * stopped the pause stream! >> * Closing connection 0 >> curl: (18) transfer closed with 191548 bytes remaining to read >> >> Anbody else getting the same error? >> >> Thank you. >> >> Best Regards, >> -- >> Vallimamod Abdullah >> SIP Solutions >> vma at sip.solutions >> linkedin.com/in/vallimamod >> . >> >> >> >> _______________________________________________ >> 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 vma at sip.solutions Sat Jun 15 14:55:37 2019 From: vma at sip.solutions (Vallimamod Abdullah) Date: Sat, 15 Jun 2019 20:55:37 +0200 Subject: [OpenSIPS-Users] hash mismatch error from debian stretch repo In-Reply-To: References: <4F570AC5-C848-4317-9426-8395D7C978EA@sip.solutions> Message-ID: <6FAFF77C-037B-4373-8E96-993BF99EF126@sip.solutions> I confirm, its working for me. Thank you again. Best Regards, -- Vallimamod Abdullah SIP Solutions vma at sip.solutions linkedin.com/in/vallimamod . > On 15 Jun 2019, at 20:43, Nick Altmann wrote: > > It's fixed now. > > сб, 15 июн. 2019 г. в 20:30, Nick Altmann >: > It's a hardware issue on the repository server. I'm working to fix this. > > сб, 15 июн. 2019 г. в 18:55, Vallimamod Abdullah : > Hello, > > I am trying to upgrade from 2.4 to version 3.0 from debian stretch apt repo and I am getting the following hash errors: > > Get: 1 http://apt.opensips.org stretch/3.0-releases amd64 opensips-redis-module amd64 3.0.0-1 [192 kB] > Err http://apt.opensips.org stretch/3.0-releases amd64 opensips-redis-module amd64 3.0.0-1 > Hash Sum mismatch > Hashes of expected file: > - SHA512:ff56e20fede1e8ff4475d6a00ead8687c2f66ccc37399b0e796e02bdd33826d8ed73502f123c9e3098a0b49913a773547616cdde2acb92ad27f5ba33514312b4 > - SHA256:70dc8c94d9abdcf33d0a907dcec10c58de7118f2c0029e1b1ef846a2fd28ae37 > - SHA1:360bc3d614bed8a82a8f71d64445574045fa5f98 [weak] > - MD5Sum:1657a30f22d414d0dce67b8b7237a566 [weak] > - Filesize:191548 [weak] > Hashes of received file: > - SHA512:cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e > - SHA256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 > - SHA1:da39a3ee5e6b4b0d3255bfef95601890afd80709 [weak] > - MD5Sum:d41d8cd98f00b204e9800998ecf8427e [weak] > - Filesize:0 [weak] > Last modification reported: Thu, 30 May 2019 09:08:36 +0000 > > [...] > > > After futher check it looks like a web server issue: > > curl -v http://apt.opensips.org/pool/stretch/3.0-releases/o/opensips/opensips-redis-module_3.0.0-1_amd64.deb > * Trying 176.9.203.99... > * TCP_NODELAY set > * Connected to apt.opensips.org (176.9.203.99) port 80 (#0) > > GET /pool/stretch/3.0-releases/o/opensips/opensips-redis-module_3.0.0-1_amd64.deb HTTP/1.1 > > Host: apt.opensips.org > > User-Agent: curl/7.52.1 > > Accept: */* > > > < HTTP/1.1 200 OK > < Server: nginx > < Date: Sat, 15 Jun 2019 16:49:07 GMT > < Content-Type: application/octet-stream > < Content-Length: 191548 > < Last-Modified: Thu, 30 May 2019 09:08:36 GMT > < Connection: keep-alive > < ETag: "5cef9d94-2ec3c" > < Accept-Ranges: bytes > < > * transfer closed with 191548 bytes remaining to read > * Curl_http_done: called premature == 1 > * stopped the pause stream! > * Closing connection 0 > curl: (18) transfer closed with 191548 bytes remaining to read > > Anbody else getting the same error? > > Thank you. > > Best Regards, > -- > Vallimamod Abdullah > SIP Solutions > vma at sip.solutions > linkedin.com/in/vallimamod > . > > > > _______________________________________________ > 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 david.villasmil.work at gmail.com Mon Jun 17 22:06:36 2019 From: david.villasmil.work at gmail.com (David Villasmil) Date: Mon, 17 Jun 2019 22:06:36 -0400 Subject: [OpenSIPS-Users] install from repo on debian 9 Message-ID: Hello guys, when trying to install from opensips' repo i'm getting: root at opensip1:~# apt-get install default-libmysqlclient-dev Reading package lists... Done Building dependency tree Reading state information... Done default-libmysqlclient-dev is already the newest version (1.0.2). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root at opensip1:~# apt-get install opensips opensips-mysql-module Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: opensips-mysql-module : Depends: libmysqlclient18 (>= 5.5.24+dfsg-1) but it is not installable E: Unable to correct problems, you have held broken packages. i can't figure out what package to install, since None of these work... root at opensip1:~# apt-cache search libmysqlclient libglpk40 - linear programming kit with integer (MIP) support libcrypt-mysql-perl - Perl module to emulate the MySQL PASSWORD() function libmariadbclient-dev-compat - MariaDB database development files (libmysqlclient compatibility) default-libmysqlclient-dev - MySQL database development files (metapackage) Any help is greatly appreciated. Thanks! David Villasmil email: david.villasmil.work at gmail.com phone: +34669448337 -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.villasmil.work at gmail.com Mon Jun 17 22:15:22 2019 From: david.villasmil.work at gmail.com (David Villasmil) Date: Mon, 17 Jun 2019 22:15:22 -0400 Subject: [OpenSIPS-Users] install from repo on debian 9 In-Reply-To: References: Message-ID: Hello all again, Ok i was using the wrong repo, I was able to install opensips 3, but now when trying to install opensips-console i'm getting: root at opensip1:~# apt-get install opensips-console Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: opensips-console : Depends: opensips (= 2.2.2-3) but 3.0.0-1 is to be installed E: Unable to correct problems, you have held broken packages. Any ideas? Regards, David Villasmil email: david.villasmil.work at gmail.com phone: +34669448337 On Mon, Jun 17, 2019 at 10:06 PM David Villasmil < david.villasmil.work at gmail.com> wrote: > Hello guys, > > when trying to install from opensips' repo i'm getting: > > root at opensip1:~# apt-get install default-libmysqlclient-dev > Reading package lists... Done > Building dependency tree > Reading state information... Done > default-libmysqlclient-dev is already the newest version (1.0.2). > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > root at opensip1:~# apt-get install opensips opensips-mysql-module > Reading package lists... Done > Building dependency tree > Reading state information... Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > opensips-mysql-module : Depends: libmysqlclient18 (>= 5.5.24+dfsg-1) but > it is not installable > E: Unable to correct problems, you have held broken packages. > > i can't figure out what package to install, since > > None of these work... > > root at opensip1:~# apt-cache search libmysqlclient > libglpk40 - linear programming kit with integer (MIP) support > libcrypt-mysql-perl - Perl module to emulate the MySQL PASSWORD() function > libmariadbclient-dev-compat - MariaDB database development files > (libmysqlclient compatibility) > default-libmysqlclient-dev - MySQL database development files (metapackage) > > > Any help is greatly appreciated. > > Thanks! > > David Villasmil > email: david.villasmil.work at gmail.com > phone: +34669448337 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.villasmil.work at gmail.com Mon Jun 17 22:57:51 2019 From: david.villasmil.work at gmail.com (David Villasmil) Date: Mon, 17 Jun 2019 22:57:51 -0400 Subject: [OpenSIPS-Users] OpenSIPS 3 - can't create database Message-ID: Hello guys, When executing `create database` with opensips-cli i'm getting: root at opensip1:~# opensips-cli mysql://opensips:password at 127.0.0.1 Welcome to OpenSIPS Command Line Interface! (opensips-cli): database create Please provide us the URL of the database: mysql://opensips:password@ 127.0.0.1 Create [a]ll tables or just the [c]urrently configured ones? (Default value is a): a Creating all tables ... Running standard-create.sql... Running cachedb_sql-create.sql... ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') Running tracer-create.sql... Running rtpengine-create.sql... Running rls-create.sql... ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') Running closeddial-create.sql... Running userblacklist-create.sql... Running rtpproxy-create.sql... Running call_center-create.sql... Running presence-create.sql... ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') Running alias_db-create.sql... Running carrierroute-create.sql... Running imc-create.sql... Running tls_mgm-create.sql... Running avpops-create.sql... Running load_balancer-create.sql... Running registrant-create.sql... ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') Running b2b_sca-create.sql... Running clusterer-create.sql... Running acc-create.sql... Running usrloc-create.sql... Running cpl-create.sql... Running b2b-create.sql... Running freeswitch_scripting-create.sql... Running auth_db-create.sql... Running emergency-create.sql... Running dialplan-create.sql... Running domain-create.sql... Running speeddial-create.sql... Running drouting-create.sql... Running domainpolicy-create.sql... ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') Running permissions-create.sql... Running smpp-create.sql... ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') Running fraud_detection-create.sql... Running dispatcher-create.sql... Running msilo-create.sql... Running group-create.sql... Running dialog-create.sql... The 'opensips' database has been successfully created! Regards, David Villasmil email: david.villasmil.work at gmail.com phone: +34669448337 -------------- next part -------------- An HTML attachment was scrubbed... URL: From callum.guy at x-on.co.uk Tue Jun 18 03:31:59 2019 From: callum.guy at x-on.co.uk (Callum Guy) Date: Tue, 18 Jun 2019 08:31:59 +0100 Subject: [OpenSIPS-Users] OpenSIPS 3 - can't create database In-Reply-To: References: Message-ID: Hi David, This seems to be a database collation issue - did you create the database manually and do you have the option to change the charset? https://stackoverflow.com/questions/1814532/1071-specified-key-was-too-long-max-key-length-is-767-bytes Not sure what the correct options would be for you however I am sure you can work that out :) Good luck! On Tue, 18 Jun 2019 at 03:59, David Villasmil < david.villasmil.work at gmail.com> wrote: > Hello guys, > > When executing `create database` with opensips-cli i'm getting: > > root at opensip1:~# opensips-cli > mysql://opensips:password at 127.0.0.1 > Welcome to OpenSIPS Command Line Interface! > (opensips-cli): database create > Please provide us the URL of the database: mysql://opensips:password@ > 127.0.0.1 > Create [a]ll tables or just the [c]urrently configured ones? (Default > value is a): a > Creating all tables ... > Running standard-create.sql... > Running cachedb_sql-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running tracer-create.sql... > Running rtpengine-create.sql... > Running rls-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running closeddial-create.sql... > Running userblacklist-create.sql... > Running rtpproxy-create.sql... > Running call_center-create.sql... > Running presence-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running alias_db-create.sql... > Running carrierroute-create.sql... > Running imc-create.sql... > Running tls_mgm-create.sql... > Running avpops-create.sql... > Running load_balancer-create.sql... > Running registrant-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running b2b_sca-create.sql... > Running clusterer-create.sql... > Running acc-create.sql... > Running usrloc-create.sql... > Running cpl-create.sql... > Running b2b-create.sql... > Running freeswitch_scripting-create.sql... > Running auth_db-create.sql... > Running emergency-create.sql... > Running dialplan-create.sql... > Running domain-create.sql... > Running speeddial-create.sql... > Running drouting-create.sql... > Running domainpolicy-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running permissions-create.sql... > Running smpp-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running fraud_detection-create.sql... > Running dispatcher-create.sql... > Running msilo-create.sql... > Running group-create.sql... > Running dialog-create.sql... > The 'opensips' database has been successfully created! > > > Regards, > > David Villasmil > email: david.villasmil.work at gmail.com > phone: +34669448337 > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- *0333 332 0000  |  www.x-on.co.uk   |   **      * X-on is a trading name of Storacall Technology Ltd a limited company registered in England and Wales. Registered Office : Avaland House, 110 London Road, Apsley, Hemel Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient, please notify X-on immediately on +44(0)333 332 0000 and delete the message from your computer. If you are not a named addressee you must not use, disclose, disseminate, distribute, copy, print or reply to this email. Views or opinions expressed by an individual within this email may not necessarily reflect the views of X-on or its associated companies. Although X-on routinely screens for viruses, addressees should scan this email and any attachments for viruses. X-on makes no representation or warranty as to the absence of viruses in this email or any attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: From liviu at opensips.org Tue Jun 18 03:39:38 2019 From: liviu at opensips.org (Liviu Chircu) Date: Tue, 18 Jun 2019 10:39:38 +0300 Subject: [OpenSIPS-Users] OpenSIPS 3 - can't create database In-Reply-To: References: Message-ID: <86eccdf9-0826-e006-dedd-2e72708ea9ed@opensips.org> Good spot, that is exactly the problem!  This issue seems to be more prevalent with MariaDB, where the default database charset is "utf8mb4", and not "latin1" as in the MySQL packages. This answer[1] also includes some MariaDB server settings which should allow the creation of keys on VARCHAR(255) columns even if using the utf8mb4 charset. [1]: https://stackoverflow.com/a/36405914/2054305 Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 18.06.2019 10:31, Callum Guy wrote: > Hi David, > > This seems to be a database collation issue - did you create the > database manually and do you have the option to change the charset? > > https://stackoverflow.com/questions/1814532/1071-specified-key-was-too-long-max-key-length-is-767-bytes > > Not sure what the correct options would be for you however I am sure > you can work that out :) > > Good luck! > > On Tue, 18 Jun 2019 at 03:59, David Villasmil > > wrote: > > Hello guys, > > When executing `create database` with opensips-cli i'm getting: > > root at opensip1:~# opensips-cli > mysql://opensips:password at 127.0.0.1 > Welcome to OpenSIPS Command Line Interface! > (opensips-cli): database create > Please provide us the URL of the database: > mysql://opensips:password at 127.0.0.1 > Create [a]ll tables or just the [c]urrently configured ones? > (Default value is a): a > Creating all tables ... > Running standard-create.sql... > Running cachedb_sql-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): >   File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >     func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute > 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): >   File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor >     cursor.close() >   File > "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close >     while self.nextset(): >   File > "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset >     nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was > too long; max key length is 767 bytes') > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.villasmil.work at gmail.com Mon Jun 17 23:16:52 2019 From: david.villasmil.work at gmail.com (David Villasmil) Date: Mon, 17 Jun 2019 23:16:52 -0400 Subject: [OpenSIPS-Users] OpenSIPS 3 - can't create database In-Reply-To: References: Message-ID: I tried removing mariaDB and installing mysql 5.6, but when creating the db i'm getting; Create [a]ll tables or just the [c]urrently configured ones? (Default value is a): a Creating all tables ... Running standard-create.sql... Running cachedb_sql-create.sql... ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') Running tracer-create.sql... Running rtpengine-create.sql... Running rls-create.sql... ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') Running closeddial-create.sql... Running userblacklist-create.sql... Running rtpproxy-create.sql... Running call_center-create.sql... Running presence-create.sql... ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') Running alias_db-create.sql... Running carrierroute-create.sql... Running imc-create.sql... Running tls_mgm-create.sql... Running avpops-create.sql... Running load_balancer-create.sql... Running registrant-create.sql... ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') Running b2b_sca-create.sql... Running clusterer-create.sql... Running acc-create.sql... Running usrloc-create.sql... Running cpl-create.sql... Running b2b-create.sql... Running freeswitch_scripting-create.sql... Running auth_db-create.sql... Running emergency-create.sql... Running dialplan-create.sql... Running domain-create.sql... Running speeddial-create.sql... Running drouting-create.sql... Running domainpolicy-create.sql... ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') Running permissions-create.sql... Running smpp-create.sql... ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') ERROR: Error closing cursor Traceback (most recent call last): File "/usr/lib/python3.5/cmd.py", line 214, in onecmd func = getattr(self, 'do_' + cmd) AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", line 1333, in _safe_close_cursor cursor.close() File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 86, in close while self.nextset(): File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line 136, in nextset nr = db.next_result() MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; max key length is 767 bytes') Running fraud_detection-create.sql... Running dispatcher-create.sql... Running msilo-create.sql... Running group-create.sql... Running dialog-create.sql... The 'opensips' database has been successfully created! Regards, David Villasmil email: david.villasmil.work at gmail.com phone: +34669448337 On Mon, Jun 17, 2019 at 10:57 PM David Villasmil < david.villasmil.work at gmail.com> wrote: > Hello guys, > > When executing `create database` with opensips-cli i'm getting: > > root at opensip1:~# opensips-cli > mysql://opensips:password at 127.0.0.1 > Welcome to OpenSIPS Command Line Interface! > (opensips-cli): database create > Please provide us the URL of the database: mysql://opensips:password@ > 127.0.0.1 > Create [a]ll tables or just the [c]urrently configured ones? (Default > value is a): a > Creating all tables ... > Running standard-create.sql... > Running cachedb_sql-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running tracer-create.sql... > Running rtpengine-create.sql... > Running rls-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running closeddial-create.sql... > Running userblacklist-create.sql... > Running rtpproxy-create.sql... > Running call_center-create.sql... > Running presence-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running alias_db-create.sql... > Running carrierroute-create.sql... > Running imc-create.sql... > Running tls_mgm-create.sql... > Running avpops-create.sql... > Running load_balancer-create.sql... > Running registrant-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running b2b_sca-create.sql... > Running clusterer-create.sql... > Running acc-create.sql... > Running usrloc-create.sql... > Running cpl-create.sql... > Running b2b-create.sql... > Running freeswitch_scripting-create.sql... > Running auth_db-create.sql... > Running emergency-create.sql... > Running dialplan-create.sql... > Running domain-create.sql... > Running speeddial-create.sql... > Running drouting-create.sql... > Running domainpolicy-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running permissions-create.sql... > Running smpp-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running fraud_detection-create.sql... > Running dispatcher-create.sql... > Running msilo-create.sql... > Running group-create.sql... > Running dialog-create.sql... > The 'opensips' database has been successfully created! > > > Regards, > > David Villasmil > email: david.villasmil.work at gmail.com > phone: +34669448337 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.villasmil.work at gmail.com Tue Jun 18 01:12:19 2019 From: david.villasmil.work at gmail.com (David Villasmil) Date: Tue, 18 Jun 2019 01:12:19 -0400 Subject: [OpenSIPS-Users] OpenSIPS 3 - can't create database In-Reply-To: References: Message-ID: Still getting errors: root at opensip1:~# opensips-cli -x database add presence Please provide us the URL of the database: mysql://opensips:password at localhost ERROR: cannot import: cannot deploy /usr/share/opensips/mysql/presence-create.sql file: (MySQLdb._exceptions.IntegrityError) (1062, "Duplicate entry 'presentity' for key 't_name_idx'") Regards, David Villasmil email: david.villasmil.work at gmail.com phone: +34669448337 On Mon, Jun 17, 2019 at 11:16 PM David Villasmil < david.villasmil.work at gmail.com> wrote: > I tried removing mariaDB and installing mysql 5.6, but when creating the > db i'm getting; > > Create [a]ll tables or just the [c]urrently configured ones? (Default > value is a): a > Creating all tables ... > Running standard-create.sql... > Running cachedb_sql-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running tracer-create.sql... > Running rtpengine-create.sql... > Running rls-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running closeddial-create.sql... > Running userblacklist-create.sql... > Running rtpproxy-create.sql... > Running call_center-create.sql... > Running presence-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running alias_db-create.sql... > Running carrierroute-create.sql... > Running imc-create.sql... > Running tls_mgm-create.sql... > Running avpops-create.sql... > Running load_balancer-create.sql... > Running registrant-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running b2b_sca-create.sql... > Running clusterer-create.sql... > Running acc-create.sql... > Running usrloc-create.sql... > Running cpl-create.sql... > Running b2b-create.sql... > Running freeswitch_scripting-create.sql... > Running auth_db-create.sql... > Running emergency-create.sql... > Running dialplan-create.sql... > Running domain-create.sql... > Running speeddial-create.sql... > Running drouting-create.sql... > Running domainpolicy-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running permissions-create.sql... > Running smpp-create.sql... > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > ERROR: Error closing cursor > Traceback (most recent call last): > File "/usr/lib/python3.5/cmd.py", line 214, in onecmd > func = getattr(self, 'do_' + cmd) > AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", > line 1333, in _safe_close_cursor > cursor.close() > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 86, in close > while self.nextset(): > File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line > 136, in nextset > nr = db.next_result() > MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; > max key length is 767 bytes') > Running fraud_detection-create.sql... > Running dispatcher-create.sql... > Running msilo-create.sql... > Running group-create.sql... > Running dialog-create.sql... > The 'opensips' database has been successfully created! > > Regards, > > David Villasmil > email: david.villasmil.work at gmail.com > phone: +34669448337 > > > On Mon, Jun 17, 2019 at 10:57 PM David Villasmil < > david.villasmil.work at gmail.com> wrote: > >> Hello guys, >> >> When executing `create database` with opensips-cli i'm getting: >> >> root at opensip1:~# opensips-cli >> mysql://opensips:password at 127.0.0.1 >> Welcome to OpenSIPS Command Line Interface! >> (opensips-cli): database create >> Please provide us the URL of the database: mysql://opensips:password@ >> 127.0.0.1 >> Create [a]ll tables or just the [c]urrently configured ones? (Default >> value is a): a >> Creating all tables ... >> Running standard-create.sql... >> Running cachedb_sql-create.sql... >> ERROR: Error closing cursor >> Traceback (most recent call last): >> File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >> func = getattr(self, 'do_' + cmd) >> AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' >> >> During handling of the above exception, another exception occurred: >> >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", >> line 1333, in _safe_close_cursor >> cursor.close() >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 86, in close >> while self.nextset(): >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 136, in nextset >> nr = db.next_result() >> MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; >> max key length is 767 bytes') >> ERROR: Error closing cursor >> Traceback (most recent call last): >> File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >> func = getattr(self, 'do_' + cmd) >> AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' >> >> During handling of the above exception, another exception occurred: >> >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", >> line 1333, in _safe_close_cursor >> cursor.close() >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 86, in close >> while self.nextset(): >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 136, in nextset >> nr = db.next_result() >> MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; >> max key length is 767 bytes') >> Running tracer-create.sql... >> Running rtpengine-create.sql... >> Running rls-create.sql... >> ERROR: Error closing cursor >> Traceback (most recent call last): >> File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >> func = getattr(self, 'do_' + cmd) >> AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' >> >> During handling of the above exception, another exception occurred: >> >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", >> line 1333, in _safe_close_cursor >> cursor.close() >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 86, in close >> while self.nextset(): >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 136, in nextset >> nr = db.next_result() >> MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; >> max key length is 767 bytes') >> ERROR: Error closing cursor >> Traceback (most recent call last): >> File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >> func = getattr(self, 'do_' + cmd) >> AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' >> >> During handling of the above exception, another exception occurred: >> >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", >> line 1333, in _safe_close_cursor >> cursor.close() >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 86, in close >> while self.nextset(): >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 136, in nextset >> nr = db.next_result() >> MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; >> max key length is 767 bytes') >> Running closeddial-create.sql... >> Running userblacklist-create.sql... >> Running rtpproxy-create.sql... >> Running call_center-create.sql... >> Running presence-create.sql... >> ERROR: Error closing cursor >> Traceback (most recent call last): >> File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >> func = getattr(self, 'do_' + cmd) >> AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' >> >> During handling of the above exception, another exception occurred: >> >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", >> line 1333, in _safe_close_cursor >> cursor.close() >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 86, in close >> while self.nextset(): >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 136, in nextset >> nr = db.next_result() >> MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; >> max key length is 767 bytes') >> ERROR: Error closing cursor >> Traceback (most recent call last): >> File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >> func = getattr(self, 'do_' + cmd) >> AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' >> >> During handling of the above exception, another exception occurred: >> >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", >> line 1333, in _safe_close_cursor >> cursor.close() >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 86, in close >> while self.nextset(): >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 136, in nextset >> nr = db.next_result() >> MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; >> max key length is 767 bytes') >> Running alias_db-create.sql... >> Running carrierroute-create.sql... >> Running imc-create.sql... >> Running tls_mgm-create.sql... >> Running avpops-create.sql... >> Running load_balancer-create.sql... >> Running registrant-create.sql... >> ERROR: Error closing cursor >> Traceback (most recent call last): >> File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >> func = getattr(self, 'do_' + cmd) >> AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' >> >> During handling of the above exception, another exception occurred: >> >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", >> line 1333, in _safe_close_cursor >> cursor.close() >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 86, in close >> while self.nextset(): >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 136, in nextset >> nr = db.next_result() >> MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; >> max key length is 767 bytes') >> ERROR: Error closing cursor >> Traceback (most recent call last): >> File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >> func = getattr(self, 'do_' + cmd) >> AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' >> >> During handling of the above exception, another exception occurred: >> >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", >> line 1333, in _safe_close_cursor >> cursor.close() >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 86, in close >> while self.nextset(): >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 136, in nextset >> nr = db.next_result() >> MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; >> max key length is 767 bytes') >> Running b2b_sca-create.sql... >> Running clusterer-create.sql... >> Running acc-create.sql... >> Running usrloc-create.sql... >> Running cpl-create.sql... >> Running b2b-create.sql... >> Running freeswitch_scripting-create.sql... >> Running auth_db-create.sql... >> Running emergency-create.sql... >> Running dialplan-create.sql... >> Running domain-create.sql... >> Running speeddial-create.sql... >> Running drouting-create.sql... >> Running domainpolicy-create.sql... >> ERROR: Error closing cursor >> Traceback (most recent call last): >> File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >> func = getattr(self, 'do_' + cmd) >> AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' >> >> During handling of the above exception, another exception occurred: >> >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", >> line 1333, in _safe_close_cursor >> cursor.close() >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 86, in close >> while self.nextset(): >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 136, in nextset >> nr = db.next_result() >> MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; >> max key length is 767 bytes') >> ERROR: Error closing cursor >> Traceback (most recent call last): >> File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >> func = getattr(self, 'do_' + cmd) >> AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' >> >> During handling of the above exception, another exception occurred: >> >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", >> line 1333, in _safe_close_cursor >> cursor.close() >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 86, in close >> while self.nextset(): >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 136, in nextset >> nr = db.next_result() >> MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; >> max key length is 767 bytes') >> Running permissions-create.sql... >> Running smpp-create.sql... >> ERROR: Error closing cursor >> Traceback (most recent call last): >> File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >> func = getattr(self, 'do_' + cmd) >> AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' >> >> During handling of the above exception, another exception occurred: >> >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", >> line 1333, in _safe_close_cursor >> cursor.close() >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 86, in close >> while self.nextset(): >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 136, in nextset >> nr = db.next_result() >> MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; >> max key length is 767 bytes') >> ERROR: Error closing cursor >> Traceback (most recent call last): >> File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >> func = getattr(self, 'do_' + cmd) >> AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' >> >> During handling of the above exception, another exception occurred: >> >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", >> line 1333, in _safe_close_cursor >> cursor.close() >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 86, in close >> while self.nextset(): >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 136, in nextset >> nr = db.next_result() >> MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; >> max key length is 767 bytes') >> Running fraud_detection-create.sql... >> Running dispatcher-create.sql... >> Running msilo-create.sql... >> Running group-create.sql... >> Running dialog-create.sql... >> The 'opensips' database has been successfully created! >> >> >> Regards, >> >> David Villasmil >> email: david.villasmil.work at gmail.com >> phone: +34669448337 >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.villasmil.work at gmail.com Tue Jun 18 08:29:49 2019 From: david.villasmil.work at gmail.com (David Villasmil) Date: Tue, 18 Jun 2019 08:29:49 -0400 Subject: [OpenSIPS-Users] OpenSIPS 3 - can't create database In-Reply-To: <86eccdf9-0826-e006-dedd-2e72708ea9ed@opensips.org> References: <86eccdf9-0826-e006-dedd-2e72708ea9ed@opensips.org> Message-ID: Thanks for replying guys, Yeah this also happens on K, but in K’s case I get. Prompt to provide a collation... I’ll try your suggestion, thanks!! David On Tue, 18 Jun 2019 at 03:39, Liviu Chircu wrote: > Good spot, that is exactly the problem! This issue seems to be more > prevalent with MariaDB, > where the default database charset is "utf8mb4", and not "latin1" as in > the MySQL packages. > > This answer[1] also includes some MariaDB server settings which should > allow the creation > of keys on VARCHAR(255) columns even if using the utf8mb4 charset. > [1]: https://stackoverflow.com/a/36405914/2054305 > > Liviu Chircu > OpenSIPS Developerhttp://www.opensips-solutions.com > > On 18.06.2019 10:31, Callum Guy wrote: > > Hi David, > > This seems to be a database collation issue - did you create the database > manually and do you have the option to change the charset? > > > https://stackoverflow.com/questions/1814532/1071-specified-key-was-too-long-max-key-length-is-767-bytes > > Not sure what the correct options would be for you however I am sure you > can work that out :) > > Good luck! > > On Tue, 18 Jun 2019 at 03:59, David Villasmil < > david.villasmil.work at gmail.com> wrote: > >> Hello guys, >> >> When executing `create database` with opensips-cli i'm getting: >> >> root at opensip1:~# opensips-cli >> mysql://opensips:password at 127.0.0.1 >> Welcome to OpenSIPS Command Line Interface! >> (opensips-cli): database create >> Please provide us the URL of the database: mysql://opensips:password@ >> 127.0.0.1 >> Create [a]ll tables or just the [c]urrently configured ones? (Default >> value is a): a >> Creating all tables ... >> Running standard-create.sql... >> Running cachedb_sql-create.sql... >> ERROR: Error closing cursor >> Traceback (most recent call last): >> File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >> func = getattr(self, 'do_' + cmd) >> AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' >> >> During handling of the above exception, another exception occurred: >> >> Traceback (most recent call last): >> File >> "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", >> line 1333, in _safe_close_cursor >> cursor.close() >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 86, in close >> while self.nextset(): >> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >> 136, in nextset >> nr = db.next_result() >> MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too long; >> max key length is 767 bytes') >> > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- Regards, David Villasmil email: david.villasmil.work at gmail.com phone: +34669448337 -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.villasmil.work at gmail.com Wed Jun 19 00:24:13 2019 From: david.villasmil.work at gmail.com (David Villasmil) Date: Wed, 19 Jun 2019 00:24:13 -0400 Subject: [OpenSIPS-Users] OpenSIPS 3 - can't create database In-Reply-To: References: <86eccdf9-0826-e006-dedd-2e72708ea9ed@opensips.org> Message-ID: Ok, so i uninstalled mysql 5.6 and installed 5.7 and all built properly. Thanks everyone! Regards, David Villasmil email: david.villasmil.work at gmail.com phone: +34669448337 On Tue, Jun 18, 2019 at 8:29 AM David Villasmil < david.villasmil.work at gmail.com> wrote: > Thanks for replying guys, > > Yeah this also happens on K, but in K’s case I get. Prompt to provide a > collation... > > I’ll try your suggestion, thanks!! > > David > > On Tue, 18 Jun 2019 at 03:39, Liviu Chircu wrote: > >> Good spot, that is exactly the problem! This issue seems to be more >> prevalent with MariaDB, >> where the default database charset is "utf8mb4", and not "latin1" as in >> the MySQL packages. >> >> This answer[1] also includes some MariaDB server settings which should >> allow the creation >> of keys on VARCHAR(255) columns even if using the utf8mb4 charset. >> [1]: https://stackoverflow.com/a/36405914/2054305 >> >> Liviu Chircu >> OpenSIPS Developerhttp://www.opensips-solutions.com >> >> On 18.06.2019 10:31, Callum Guy wrote: >> >> Hi David, >> >> This seems to be a database collation issue - did you create the database >> manually and do you have the option to change the charset? >> >> >> https://stackoverflow.com/questions/1814532/1071-specified-key-was-too-long-max-key-length-is-767-bytes >> >> Not sure what the correct options would be for you however I am sure you >> can work that out :) >> >> Good luck! >> >> On Tue, 18 Jun 2019 at 03:59, David Villasmil < >> david.villasmil.work at gmail.com> wrote: >> >>> Hello guys, >>> >>> When executing `create database` with opensips-cli i'm getting: >>> >>> root at opensip1:~# opensips-cli >>> mysql://opensips:password at 127.0.0.1 >>> Welcome to OpenSIPS Command Line Interface! >>> (opensips-cli): database create >>> Please provide us the URL of the database: mysql://opensips:password@ >>> 127.0.0.1 >>> Create [a]ll tables or just the [c]urrently configured ones? (Default >>> value is a): a >>> Creating all tables ... >>> Running standard-create.sql... >>> Running cachedb_sql-create.sql... >>> ERROR: Error closing cursor >>> Traceback (most recent call last): >>> File "/usr/lib/python3.5/cmd.py", line 214, in onecmd >>> func = getattr(self, 'do_' + cmd) >>> AttributeError: 'OpenSIPSCLIShell' object has no attribute 'do_database' >>> >>> During handling of the above exception, another exception occurred: >>> >>> Traceback (most recent call last): >>> File >>> "/usr/local/lib/python3.5/dist-packages/SQLAlchemy-1.3.3-py3.5-linux-x86_64.egg/sqlalchemy/engine/base.py", >>> line 1333, in _safe_close_cursor >>> cursor.close() >>> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >>> 86, in close >>> while self.nextset(): >>> File "/usr/local/lib/python3.5/dist-packages/MySQLdb/cursors.py", line >>> 136, in nextset >>> nr = db.next_result() >>> MySQLdb._exceptions.OperationalError: (1071, 'Specified key was too >>> long; max key length is 767 bytes') >>> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > -- > Regards, > > David Villasmil > email: david.villasmil.work at gmail.com > phone: +34669448337 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.villasmil.work at gmail.com Wed Jun 19 00:37:49 2019 From: david.villasmil.work at gmail.com (David Villasmil) Date: Wed, 19 Jun 2019 00:37:49 -0400 Subject: [OpenSIPS-Users] jabber/xmpp? Message-ID: Hello guys, I'm kind of confused as to what module exactly i need to user, let me explain: I have a service for DIDs and SMS from s.ms, i created a python script that connects to the service using xmpp to their jabber server with a user and a password, i.e.: xmpp_client.py MY-NUMBER at s.ms MY-PASSWORD What i do with that script is basically connect and wait to receive SMS, which i then insert in the proxy db (silo) and they get delivered by msilo. I have several numbers and doing this for every number seems stupid, so i started looking for a better solution, since the end user will be receive the message via SIP MESSAGE on they sip client. i came across openSIPS' jabber and xmpp modules, but i'm not sure which (if any) to use, and even HOW to, or the actual architecture, since the documentation keeps talking about a local xmpp server? I would REALLY appreciate some help here. Thanks! Regards, David Villasmil email: david.villasmil.work at gmail.com phone: +34669448337 -------------- next part -------------- An HTML attachment was scrubbed... URL: From johan at democon.be Wed Jun 19 10:48:06 2019 From: johan at democon.be (johan de clercq) Date: Wed, 19 Jun 2019 16:48:06 +0200 Subject: [OpenSIPS-Users] opensips-cp 30 Message-ID: <00c301d526ae$018e0fb0$04aa2f10$@democon.be> When can the control panel be expected for opensips 30 ? BR, Johan De Clercq, Managing Director Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke Tel +3256980990 - GSM +32478720104 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From johan at democon.be Wed Jun 19 10:52:59 2019 From: johan at democon.be (johan de clercq) Date: Wed, 19 Jun 2019 16:52:59 +0200 Subject: [OpenSIPS-Users] segfault in opensips30 Message-ID: <00c901d526ae$b05170f0$10f452d0$@democon.be> When trying to register an unknown user, I have a segfault. I can easily reproduce, so please tell me what I need to do to give you a dump. Johan De Clercq, Managing Director Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke Tel +3256980990 - GSM +32478720104 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From johan at democon.be Wed Jun 19 10:56:34 2019 From: johan at democon.be (johan de clercq) Date: Wed, 19 Jun 2019 16:56:34 +0200 Subject: [OpenSIPS-Users] segfault in opensips30 In-Reply-To: <00c901d526ae$b05170f0$10f452d0$@democon.be> References: <00c901d526ae$b05170f0$10f452d0$@democon.be> Message-ID: <00d301d526af$30820fa0$91862ee0$@democon.be> I forgot to insert the error : Jun 19 14:55:29 hendrix /data/opensips/sbin/opensips[30968]: CRITICAL:core:sig_usr: segfault in process pid: 30968, id: 5 Jun 19 14:55:29 hendrix kernel: [673177.336262] opensips[30968]: segfault at 0 ip 00007fef8de1e969 sp 00007fff0c4baa70 error 4 in registrar.so[7fef8de0e000+22000] From: johan de clercq Sent: Wednesday, June 19, 2019 4:53 PM To: 'OpenSIPS users mailling list' Subject: segfault in opensips30 When trying to register an unknown user, I have a segfault. I can easily reproduce, so please tell me what I need to do to give you a dump. Johan De Clercq, Managing Director Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke Tel +3256980990 - GSM +32478720104 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From jjackson at aninetworks.net Wed Jun 19 10:57:24 2019 From: jjackson at aninetworks.net (Joseph Jackson) Date: Wed, 19 Jun 2019 14:57:24 +0000 Subject: [OpenSIPS-Users] segfault in opensips30 In-Reply-To: <00d301d526af$30820fa0$91862ee0$@democon.be> References: <00c901d526ae$b05170f0$10f452d0$@democon.be> <00d301d526af$30820fa0$91862ee0$@democon.be> Message-ID: <1010d29f4ef544d0be764abb0a915a21@MBX080-W3-CO-2.exch080.serverpod.net> You should be able to follow these steps - https://www.opensips.org/Documentation/TroubleShooting-Crash From: Users [mailto:users-bounces at lists.opensips.org] On Behalf Of johan de clercq Sent: Wednesday, June 19, 2019 9:57 AM To: 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] segfault in opensips30 I forgot to insert the error : Jun 19 14:55:29 hendrix /data/opensips/sbin/opensips[30968]: CRITICAL:core:sig_usr: segfault in process pid: 30968, id: 5 Jun 19 14:55:29 hendrix kernel: [673177.336262] opensips[30968]: segfault at 0 ip 00007fef8de1e969 sp 00007fff0c4baa70 error 4 in registrar.so[7fef8de0e000+22000] From: johan de clercq Sent: Wednesday, June 19, 2019 4:53 PM To: 'OpenSIPS users mailling list' Subject: segfault in opensips30 When trying to register an unknown user, I have a segfault. I can easily reproduce, so please tell me what I need to do to give you a dump. [cid:F3100D46-F00D-4610-87ED-3E91DA790A82] Johan De Clercq, Managing Director Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke Tel +3256980990 - GSM +32478720104 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 15602 bytes Desc: image001.png URL: From johan at democon.be Wed Jun 19 11:11:50 2019 From: johan at democon.be (johan de clercq) Date: Wed, 19 Jun 2019 17:11:50 +0200 Subject: [OpenSIPS-Users] segfault in opensips30 In-Reply-To: <00c901d526ae$b05170f0$10f452d0$@democon.be> References: <00c901d526ae$b05170f0$10f452d0$@democon.be> Message-ID: <00e001d526b1$52e8c0f0$f8ba42d0$@democon.be> un 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:db_mysql:db_mysql_convert_rows: no rows returned from the query Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:usrloc:db_load_urecord: aor 32478720105 not found in table location Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_columns: freeing result columns at 0x7f0d8fa8c7f8 Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_rows: freeing 0 rows Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_result: freeing result set at 0x7f0d8fa8b320 Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:registrar:_remove: no record '32478720105' found! Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: CRITICAL:core:sig_usr: segfault in process pid: 31541, id: 5 From: johan de clercq Sent: Wednesday, June 19, 2019 4:53 PM To: 'OpenSIPS users mailling list' Subject: segfault in opensips30 When trying to register an unknown user, I have a segfault. I can easily reproduce, so please tell me what I need to do to give you a dump. Johan De Clercq, Managing Director Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke Tel +3256980990 - GSM +32478720104 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From bogdan at opensips.org Wed Jun 19 11:24:42 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 19 Jun 2019 18:24:42 +0300 Subject: [OpenSIPS-Users] segfault in opensips30 In-Reply-To: <00e001d526b1$52e8c0f0$f8ba42d0$@democon.be> References: <00c901d526ae$b05170f0$10f452d0$@democon.be> <00e001d526b1$52e8c0f0$f8ba42d0$@democon.be> Message-ID: Hi Johan, Can you extract the full backtrace from the core file ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/19/2019 06:11 PM, johan de clercq wrote: > > un 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:db_mysql:db_mysql_convert_rows: no rows returned from the query > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:usrloc:db_load_urecord: aor 32478720105 not found in table location > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:core:db_free_columns: freeing result columns at 0x7f0d8fa8c7f8 > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:core:db_free_rows: freeing 0 rows > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:core:db_free_result: freeing result set at 0x7f0d8fa8b320 > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:registrar:_remove: no record '32478720105' found! > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > CRITICAL:core:sig_usr: segfault in process pid: 31541, id: 5 > > *From:* johan de clercq > *Sent:* Wednesday, June 19, 2019 4:53 PM > *To:* 'OpenSIPS users mailling list' > *Subject:* segfault in opensips30 > > When trying to register an unknown user, I have a segfault. > > I can easily reproduce, so please tell me what I need to do to give > you a dump. > > cid:F3100D46-F00D-4610-87ED-3E91DA790A82 > > Johan De Clercq, Managing Director > Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke > > Tel +3256980990– GSM +32478720104 > > > > _______________________________________________ > 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: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From johan at democon.be Wed Jun 19 11:41:41 2019 From: johan at democon.be (johan de clercq) Date: Wed, 19 Jun 2019 17:41:41 +0200 Subject: [OpenSIPS-Users] segfault in opensips30 In-Reply-To: References: <00c901d526ae$b05170f0$10f452d0$@democon.be> <00e001d526b1$52e8c0f0$f8ba42d0$@democon.be> Message-ID: <00f801d526b5$7dd11c50$797354f0$@democon.be> Bogdan, see below output : what am I doing wrong ? root at hendrix:/tmp# gdb /tmp/core GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Copyright (C) 2016 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-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... "/tmp/core": not in executable format: File format not recognized From: Bogdan-Andrei Iancu Sent: Wednesday, June 19, 2019 5:25 PM To: OpenSIPS users mailling list ; johan de clercq Subject: Re: [OpenSIPS-Users] segfault in opensips30 Hi Johan, Can you extract the full backtrace from the core file ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/19/2019 06:11 PM, johan de clercq wrote: un 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:db_mysql:db_mysql_convert_rows: no rows returned from the query Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:usrloc:db_load_urecord: aor 32478720105 not found in table location Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_columns: freeing result columns at 0x7f0d8fa8c7f8 Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_rows: freeing 0 rows Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_result: freeing result set at 0x7f0d8fa8b320 Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:registrar:_remove: no record '32478720105' found! Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: CRITICAL:core:sig_usr: segfault in process pid: 31541, id: 5 From: johan de clercq Sent: Wednesday, June 19, 2019 4:53 PM To: 'OpenSIPS users mailling list' Subject: segfault in opensips30 When trying to register an unknown user, I have a segfault. I can easily reproduce, so please tell me what I need to do to give you a dump. Johan De Clercq, Managing Director Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke Tel +3256980990 - GSM +32478720104 _______________________________________________ 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: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From bogdan at opensips.org Wed Jun 19 11:43:07 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 19 Jun 2019 18:43:07 +0300 Subject: [OpenSIPS-Users] segfault in opensips30 In-Reply-To: <00f801d526b5$7dd11c50$797354f0$@democon.be> References: <00c901d526ae$b05170f0$10f452d0$@democon.be> <00e001d526b1$52e8c0f0$f8ba42d0$@democon.be> <00f801d526b5$7dd11c50$797354f0$@democon.be> Message-ID: <65999241-c5fd-c57f-a740-b285eccd1c7b@opensips.org> Do "gdb /path/to/opensips /path/to/corefile" Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/19/2019 06:41 PM, johan de clercq wrote: > > Bogdan, see below output : what am I doing wrong ? > > root at hendrix:/tmp# gdb /tmp/core > > GNU gdb (Debian 7.12-6) 7.12.0.20161007-git > > Copyright (C) 2016 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-linux-gnu". > > Type "show configuration" for configuration details. > > For bug reporting instructions, please see: > > . > > Find the GDB manual and other documentation resources online at: > > . > > For help, type "help". > > Type "apropos word" to search for commands related to "word"... > > "/tmp/core": not in executable format: File format not recognized > > *From:*Bogdan-Andrei Iancu > *Sent:* Wednesday, June 19, 2019 5:25 PM > *To:* OpenSIPS users mailling list ; johan > de clercq > *Subject:* Re: [OpenSIPS-Users] segfault in opensips30 > > Hi Johan, > > Can you extract the full backtrace from the core file ? > > Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/19/2019 06:11 PM, johan de clercq wrote: > > un 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:db_mysql:db_mysql_convert_rows: no rows returned from the query > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:usrloc:db_load_urecord: aor 32478720105 not found in table > location > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:core:db_free_columns: freeing result columns at 0x7f0d8fa8c7f8 > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:core:db_free_rows: freeing 0 rows > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:core:db_free_result: freeing result set at 0x7f0d8fa8b320 > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:registrar:_remove: no record '32478720105' found! > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > CRITICAL:core:sig_usr: segfault in process pid: 31541, id: 5 > > *From:* johan de clercq > *Sent:* Wednesday, June 19, 2019 4:53 PM > *To:* 'OpenSIPS users mailling list' > > *Subject:* segfault in opensips30 > > When trying to register an unknown user, I have a segfault. > > I can easily reproduce, so please tell me what I need to do to > give you a dump. > > cid:F3100D46-F00D-4610-87ED-3E91DA790A82 > > Johan De Clercq, Managing Director > Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke > > Tel +3256980990 – GSM +32478720104 > > > > > _______________________________________________ > > 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: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From johan at democon.be Wed Jun 19 11:45:39 2019 From: johan at democon.be (johan de clercq) Date: Wed, 19 Jun 2019 17:45:39 +0200 Subject: [OpenSIPS-Users] segfault in opensips30 In-Reply-To: <65999241-c5fd-c57f-a740-b285eccd1c7b@opensips.org> References: <00c901d526ae$b05170f0$10f452d0$@democon.be> <00e001d526b1$52e8c0f0$f8ba42d0$@democon.be> <00f801d526b5$7dd11c50$797354f0$@democon.be> <65999241-c5fd-c57f-a740-b285eccd1c7b@opensips.org> Message-ID: <010d01d526b6$0bfdbf60$23f93e20$@democon.be> Sorry, I overlooked that. Anyway here is the output, please let me know if this is sufficient. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `./opensips -f /data/opensips/etc/opensips/opensips.cfg -w /tmp'. Program terminated with signal SIGSEGV, Segmentation fault. #0 _remove (msg=, udomain=0x7f70323e5fb0, aor_uri=, match_ct=, match_next_hop=0x0, match_sin=) at save.c:1006 1006 if (match_next_hop->s) (gdb) bt full #0 _remove (msg=, udomain=0x7f70323e5fb0, aor_uri=, match_ct=, match_next_hop=0x0, match_sin=) at save.c:1006 delete_nh_he = {h_name = 0x7f7033fc78c0 "\001", h_aliases = 0x7ffdede87800, h_addrtype = 0, h_length = 0, h_addr_list = 0x55cc89463f54 } he = record = 0x0 contact = it = aor_user = {s = 0x7f702e8da280 "32478720105", len = 11} ret = 1 delete_port = 0 __FUNCTION__ = "_remove" #1 0x000055cc894b326a in do_action (a=a at entry=0x7f7033f092d8, msg=msg at entry=0x7f7033fc78c0) at action.c:1979 increment = decrement = j = num_rows = -1965494148 val_s = {s = 0x7ffdede87dc0 "", len = -1989512731} cdb_reply = 0x7ffdede87a00 num_cols = aux = {s = 0x7ffdede87dc0 "", len = -1989512731} i = it = ---Type to continue, or q to quit--- avp_val = avp_name = {n = -303530560, s = {s = 0x7ffdede87dc0 "", len = -1989512731}} avp_type = 24496 ret = 0 v = sec = usec = to = p = tmp = new_uri = end = crt = len = i = user = 0 expires = 0 vals = {{s = 0x55cc8ad8f07c "", len = 8180}, {s = 0x6 , len = 889497490}, { s = 0x7ffdede87c20 "\300\352\341\212\314U", len = -303531552}, {s = 0x7f703527dce0 "-\250\004\065p\177", len = -303531105}, { s = 0x55cc8ad8f0a0 "UTC", len = -303531520}} result = {s = 0x7ffdede87f00 "\200", len = -303530432} uri = {user = {s = 0x0, len = 0}, passwd = {s = 0xfbad8001 , len = -1965494148}, host = {s = 0x55cc8ad80000 , len = 0}, port = {s = 0x55cc8ad8f07b "0", ---Type to continue, or q to quit--- len = -1965494149}, params = {s = 0xffffffffffffffff , len = 0}, headers = {s = 0x55cc8ad8f07c "", len = 0}, port_no = 65535, proto = 65535, type = ERROR_URI_T, transport = { s = 0x7f7034f9723e "L\211\361L\213\\$\020\351\376\360\377\377\017\037D", len = 0}, ttl = { s = 0x1ff4 , len = 6}, user_param = { s = 0x3ede87cff , len = -303530592}, maddr = { s = 0x7ffdede87b60 "\030|\350\355\375\177", len = 891804896}, method = {s = 0x7ffdede87d1f "", len = -1965494112}, lr = { s = 0x7ffdede87b80 "8|\350\355\375\177", len = -303530992}, r2 = { s = 0x3000000010 , len = -303530976}, gr = { s = 0x7ffdede87b60 "\030|\350\355\375\177", len = -303530984}, transport_val = { s = 0x1ff4 , len = -303530954}, ttl_val = {s = 0x7ffdede87c3c "", len = -303530952}, user_param_val = {s = 0x7ffdede87c3c "", len = 891804896}, maddr_val = {s = 0x7ffdede87d8f "", len = -1965494112}, method_val = {s = 0x7ffdede87bf0 "", len = -1964913972}, lr_val = { s = 0x3000000010 , len = -303530864}, r2_val = { s = 0x55cc8ae1cacc "15:39:47 ./opensips[520]: DBG:core:restore_segv_handler: successfully restored system SIGSEGV handler\n", len = -1964913972}, gr_val = {s = 0x7f703504a792 "T ", len = 891811872}, u_name = {{ s = 0x8 , len = 0}, { s = 0x7f7034f95ede "Ic\307L\213\\$`D\213|$\020H\001\303M\001\363E\205\377\017\204V\023", len = 16}, { s = 0x1ffb , len = 0}, {s = 0x55cc8ae1cab0 "", len = -1964905792}, { s = 0x7f7035280b00 "", len = 0}, {s = 0x60 , len = 77}, { s = 0x7f7034f61114 "\351%\376\377\377\017\037\200", len = 889489931}, { s = 0x3000000018 , len = -303530704}, {s = 0x55cc8ae1cac0 "", len = -1964914000}, {s = 0x7f703527d080 "", len = 891816704}}, u_val = {{ s = 0x2010 , len = 77}, {s = 0x7f7034f62719 "I\211ă=\335/2", ---Type to continue, or q to quit--- len = -1}, {s = 0x5d0a5743 , len = 1}, {s = 0x55cc8adbd930 "X\v(5p\177", len = -303530672}, {s = 0x7f703527d080 "", len = -1965303504}, {s = 0x55cc8adbd930 "X\v(5p\177", len = 0}, { s = 0x7f703527d080 "", len = -1965303504}, {s = 0x1 , len = -1}, { s = 0xb , len = -1965303504}, {s = 0x7ffdede87e28 "0", len = 21}}, u_params_no = 44889} next_hop = {user = {s = 0x7ffdede87dc0 "", len = -1989512731}, passwd = {s = 0x55cc8adbd930 "X\v(5p\177", len = 1560958787}, host = {s = 0x55cc8ae1cac0 "", len = 76}, port = {s = 0x55cc8adbd930 "X\v(5p\177", len = 1}, params = { s = 0xffffffff , len = 11}, headers = {s = 0x55cc8adbd930 "X\v(5p\177", len = -303530344}, port_no = 21, proto = 0, type = ERROR_URI_T, transport = {s = 0x7f7034fcaf59 <__vsyslog_chk+681> "H\201ĸ", len = 47}, ttl = {s = 0x130000000f , len = 5}, user_param = { s = 0xa900000003 , len = 0}, maddr = {s = 0x0, len = -1965494112}, method = {s = 0xffffff7f , len = 872184000}, lr = {s = 0x0, len = 20}, r2 = { s = 0x7f7033f07d88 "tls", len = 3}, gr = {s = 0x0, len = 1}, transport_val = { s = 0x7f7034fcb28f "H\201\304", , len = 5}, ttl_val = { s = 0x3000000030 , len = -303530240}, user_param_val = { s = 0x7ffdede87e40 "\340ə\211\314U", len = -1986410016}, maddr_val = {s = 0x7ffdede87e78 "\300x\374\063p\177", len = -1989513168}, method_val = {s = 0x14 , len = 3}, lr_val = { s = 0x7f7033f08540 "\020", len = 2}, r2_val = {s = 0x7f7033fc78c0 "\001", len = -1986410016}, gr_val = { s = 0x7ffdede87eb8 "\255DF\211\314U", len = 0}, u_name = {{ s = 0x55cc894bae9a "\211Ņ\300u\a\203\r\221\232I", len = 871396736}, { s = 0x55cc8945d9c0 "\205\300A\017\224\302A\017\266\302\351\245\365\377\377L\213%\342\061N", len = 0}, { s = 0x55cc894644ad "\351*\375\377\377D\213\244$\220", len = 810412464}, {s = 0x0, len = 2}, { s = 0x7f7033fc78c0 "\001", len = 871401064}, {s = 0x0, len = 0}, { ---Type to continue, or q to quit--- s = 0x55cc894644ad "\351*\375\377\377D\213\244$\220", len = 128}, { s = 0x400 , len = 48}, { s = 0xffffffffffffffff , len = 0}, {s = 0x7f7033fc78c0 "\001", len = 812571664}}, u_val = {{s = 0x2a1c , len = 46}, { s = 0x7f70323c6170 "\005", len = -1989467371}, {s = 0x3 , len = 871398792}, { s = 0x3 , len = -303528704}, { s = 0x55cc896dd9d0 "DBG:core:%s: end of header reached, state=%d\n", len = -1989467371}, { s = 0x3 , len = 1}, {s = 0x2 , len = 872184000}, {s = 0x0, len = 0}, {s = 0x55cc89463f64 "\213\035&}N", len = -303530016}, { s = 0x2 , len = 871401064}}, u_params_no = 2} u = port = 0 cmatch = aitem = adefault = spec = model = val = {rs = {s = 0xede87d38 , len = -303530832}, ri = -303562752, flags = 14132} pve = name_s = {s = 0x7f70304ddeff "%s: no transaction found\n", len = 1} start = {tv_sec = 0, tv_usec = 140119823474456} aux_counter = 48 cmd = 0x7f702e8d9810 ---Type to continue, or q to quit--- acmd = cmdp = {0x7f70323e5fb0, 0x7ffdede879f0, 0x0, 0x0, 0x0, 0x55cc8ad8f07b, 0x55ccffffffff, 0x7f7034f9723e} tmp_vals = {{rs = {s = 0x7ffdede87a00 "(~\350\355\375\177", len = -1965494149}, ri = -303531224, flags = 32765}, {rs = { s = 0x55cc8ad8f07b "0", len = -303531488}, ri = -1965494149, flags = 21964}, {rs = { s = 0x7f7033f7c938 "sip:32478720105 at 10.200.0.153:5060;transport=UDP", len = 47}, ri = -303530456, flags = 32765}, {rs = { s = 0x7f7033f08948 "sip", len = 3}, ri = 888474535, flags = 32624}, {rs = { s = 0x55ccfbad8001 , len = -1965494148}, ri = -1965494148, flags = 21964}, {rs = {s = 0x55cc8ad8f07b "0", len = -1965494149}, ri = -1965494149, flags = 21964}, {rs = { s = 0x55cc8ad8f07b "0", len = -1965494149}, ri = -1965494148, flags = 21964}, {rs = {s = 0x0, len = 0}, ri = 0, flags = 0}} __FUNCTION__ = "do_action" #2 0x000055cc894bae9a in run_action_list (a=, msg=msg at entry=0x7f7033fc78c0) at action.c:176 ret = -1 t = 0x7f7033f092d8 #3 0x000055cc894b767e in do_action (a=a at entry=0x7f7033f0a830, msg=msg at entry=0x7f7033fc78c0) at action.c:1225 increment = decrement = j = num_rows = -303527896 val_s = {s = 0x0, len = 96} cdb_reply = 0x7ffdede882b0 num_cols = aux = {s = 0x0, len = 96} i = ---Type to continue, or q to quit--- it = avp_val = avp_name = {n = 0, s = {s = 0x0, len = 96}} avp_type = 3 ret = 1 v = 1 sec = usec = to = p = tmp = new_uri = end = crt = len = i = user = 0 expires = 0 vals = {{s = 0x7ffdede88828 "\300x\374\063p\177", len = 0}, {s = 0x55cc896b0a83 ": preparing to run routing scripts...\n", len = 888333497}, {s = 0x7ffdede88200 "", len = -1965494149}, {s = 0x7ffdede88328 "{\360؊\314U", len = -1965494149}, { s = 0x7ffdede88288 "\251\nk\211\314U", len = 16}} result = {s = 0x7ffdede881a8 "", len = 10} uri = {user = {s = 0x0, len = 0}, passwd = {s = 0xffffffff , len = 16}, host = { ---Type to continue, or q to quit--- s = 0x7ffdede88900 "", len = -303527872}, port = {s = 0x6 , len = 0}, params = { s = 0x7ffdede88580 "8\206\350\355\375\177", len = -303529152}, headers = {s = 0x7f703527dce0 "-\250\004\065p\177", len = -303528705}, port_no = 33616, proto = 60904, type = 32765, transport = {s = 0x55cc8ad8f07b "0", len = -303528840}, ttl = { s = 0x55cc8ad8f07b "0", len = -303528104}, user_param = {s = 0x7ffdede886d0 "\360\231ۊ\314U", len = 889495526}, maddr = { s = 0x7f7034f50ba7 "H\201\304", , len = -72515583}, method = {s = 0x55cc8ad8f07c "", len = -1965494148}, lr = {s = 0x55cc8ad8f07b "0", len = -1965494149}, r2 = {s = 0x55cc8ad8f07b "0", len = -1965494149}, gr = { s = 0x55cc8ad8f07b "0", len = -1965494148}, transport_val = {s = 0x0, len = 0}, ttl_val = {s = 0x0, len = 0}, user_param_val = { s = 0x0, len = 891811872}, maddr_val = {s = 0x8 , len = 0}, method_val = {s = 0x0, len = -303528928}, lr_val = {s = 0x55cc8ad8f07b "0", len = -303528632}, r2_val = {s = 0x55cc8ad8f07b "0", len = -303527896}, gr_val = {s = 0x7ffdede887a0 "/", len = 889495526}, u_name = {{ s = 0x7f7034f50ba7 "H\201\304", , len = -72515583}, {s = 0x55cc8ad8f07c "", len = -1965494148}, {s = 0x55cc8ad8f07b "0", len = -1965494149}, {s = 0x55cc8ad8f07b "0", len = -1965494149}, { s = 0x55cc8ad8f07b "0", len = -1965494148}, {s = 0x0, len = 0}, {s = 0x0, len = 0}, {s = 0x0, len = 1}, { s = 0x55cc8adb99f0 "\002", len = -303562752}, {s = 0x0, len = -303528600}}, u_val = {{s = 0x7ffdede8856c "", len = -1}, { s = 0x0, len = -1965319696}, {s = 0x1 , len = -1}, { s = 0x7f7034f9723e "L\211\361L\213\\$\020\351\376\360\377\377\017\037D", len = -1965319696}, { s = 0x1ff4 , len = 6}, { s = 0x33504a792 , len = -303528032}, {s = 0x7ffdede88560 "", len = 891804896}, {s = 0x7ffdede8871f "", len = -1965494112}, {s = 0x7ffdede88580 "8\206\350\355\375\177", len = 0}, { s = 0x3000000010 , len = -303528416}}, u_params_no = 34144} next_hop = {user = {s = 0x0, len = 96}, passwd = {s = 0x3734ede88636 , len = -303528388}, host = {s = 0x7ffdede88638 "p", len = -303528388}, port = {s = 0x7ffdede88660 "0\207\350\355\375\177", len = -1964920176}, params = {s = 0x55cc8ae1b280 "509]: DB\021\b", len = 891801728}, headers = {s = 0x7f7035280b00 "", ---Type to continue, or q to quit--- len = 8208}, port_no = 85, proto = 0, type = ERROR_URI_T, transport = {s = 0x55cc8ae1b29c "", len = -1964920164}, ttl = { s = 0x7f703504a792 "T ", len = 891811872}, user_param = {s = 0x8 , len = 0}, maddr = {s = 0x7f7034f95ede "Ic\307L\213\\$`D\213|$\020H\001\303M\001\363E\205\377\017\204V\023", len = 16}, method = { s = 0x1ffb , len = 0}, lr = {s = 0x55cc8ae1b280 "509]: DB\021\b", len = -1964911984}, r2 = {s = 0x7f7035280b00 "", len = 0}, gr = {s = 0x70 , len = 97}, transport_val = {s = 0x7f7034f61114 "\351%\376\377\377\017\037\200", len = 889489931}, ttl_val = { s = 0x3000000018 , len = -303528144}, user_param_val = { s = 0x55cc8ae1b290 "", len = -1964920192}, maddr_val = {s = 0x7f703527d080 "", len = 891816704}, method_val = { s = 0x2010 , len = 97}, lr_val = { s = 0x7f7034f62719 "I\211ă=\335/2", len = -1}, r2_val = { s = 0x5d0a5743 , len = 1}, gr_val = {s = 0x55cc8adb99f0 "\002", len = -303528112}, u_name = {{s = 0x7f703527d080 "", len = -1965319696}, {s = 0x55cc8adb99f0 "\002", len = 0}, { s = 0x7f703527d080 "", len = -1965319696}, {s = 0x1 , len = -1}, { s = 0xb , len = -1965319696}, {s = 0x7ffdede88828 "\300x\374\063p\177", len = 21}, {s = 0x7f7034fcaf59 <__vsyslog_chk+681> "H\201ĸ", len = -1989332788}, { s = 0x55cc896b0a78 "DBG:core:%s: preparing to run routing scripts...\n", len = 872184000}, { s = 0x5d0a5743 , len = -1964920176}, { s = 0x60 , len = -303527888}}, u_val = {{s = 0x7ffdede88770 "", len = 0}, { s = 0x55cc8997c37b "", len = -1989293616}, {s = 0x0, len = 842817904}, {s = 0x0, len = 47}, { s = 0x130000000f , len = 5}, { s = 0xa900000003 , len = 0}, {s = 0x0, len = -1965494112}, { s = 0x7ffdede887e0 "", len = 0}, {s = 0x7f7033fc78c0 "\001", len = -1986543328}, {s = 0x0, len = -303527456}}, u_params_no = 0} ---Type to continue, or q to quit--- u = port = 0 cmatch = aitem = adefault = spec = model = val = {rs = {s = 0x7ffd00000000 , len = 0}, ri = 0, flags = 21964} pve = name_s = {s = 0x7ffdede88605 "520\373\037", len = 100} start = {tv_sec = 0, tv_usec = 0} aux_counter = 0 cmd = 0x0 acmd = cmdp = {0x55cc00000003, 0x7f7034f5bc2e <_IO_default_xsputn+206>, 0x7ffdede88220, 0x26, 0xd68, 0x55cc8adb99f0, 0x7ffdede88720, 0x55cc896b0a78} tmp_vals = {{rs = {s = 0x7ffdede882b0 "", len = -303528336}, ri = 0, flags = 0}, {rs = { s = 0x7ffd00000000 , len = 0}, ri = -1, flags = -1}, {rs = { s = 0x55cc00000000 , len = 9}, ri = -1989473224, flags = 21964}, { rs = {s = 0x55cc00000000 , len = 0}, ri = 11, flags = 0}, {rs = { s = 0x7ffdede88300 "\340\334'5p\177", len = 0}, ri = 3432, flags = 0}, {rs = { s = 0x14 , len = -1989473663}, ri = 1, flags = 11}, {rs = {s = 0x0, len = -1989473623}, ri = 0, flags = 0}, {rs = {s = 0x0, len = -1}, ri = 0, flags = 0}} ---Type to continue, or q to quit--- __FUNCTION__ = "do_action" #4 0x000055cc894bae9a in run_action_list (a=a at entry=0x7f7033eff238, msg=msg at entry=0x7f7033fc78c0) at action.c:176 ret = -1 t = 0x7f7033f0a830 #5 0x000055cc894bb3ba in run_actions (msg=0x7f7033fc78c0, a=0x7f7033eff238) at action.c:141 ret = msg = 0x7f7033fc78c0 a = 0x7f7033eff238 ret = #6 run_top_route (a=0x7f7033eff238, msg=msg at entry=0x7f7033fc78c0) at action.c:218 bk_action_flags = 0 bk_rec_lev = 0 ret = ctx = 0x0 __FUNCTION__ = "run_top_route" #7 0x000055cc894c4f2d in receive_msg ( buf=0x55cc8997c120 "REGISTER sip:10.200.0.153:5060;transport=UDP SIP/2.0\r\nVia: SIP/2.0/UDP 10.204.0.29:37114;branch=z9hG4bK-524287-1---42810a0f5b9ff5d9;rport\r\nMax-Forwards: 69\r\nContact: , rcv_info=rcv_info at entry=0x7ffdede889e0, existing_context=existing_context at entry=0x0, flags=flags at entry=0) at receive.c:209 ctx = 0x7f7033fc71c0 msg = 0x7f7033fc78c0 start = {tv_sec = 0, tv_usec = 0} rc = 3 ---Type to continue, or q to quit--- in_buff = { s = 0x55cc8997c120 "REGISTER sip:10.200.0.153:5060;transport=UDP SIP/2.0\r\nVia: SIP/2.0/UDP 10.204.0.29:37114;branch=z9hG4bK-524287-1---42810a0f5b9ff5d9;rport\r\nMax-Forwards: 69\r\nContact: , bytes_read=) at net/proto_udp/proto_udp.c:183 ri = {src_ip = {af = 2, len = 4, u = {addrl = {486591498, 0}, addr32 = {486591498, 0, 0, 0}, addr16 = {52234, 7424, 0, 0, 0, 0, 0, 0}, addr = "\n\314\000\035", '\000' }}, dst_ip = {af = 2, len = 4, u = {addrl = {2566914826, 0}, addr32 = {2566914826, 0, 0, 0}, addr16 = {778, 39168, 0, 0, 0, 0, 0, 0}, addr = "\n\003\000\231", '\000' }}, src_port = 37114, dst_port = 5060, proto = 1, proto_reserved1 = 0, proto_reserved2 = 0, src_su = {s = {sa_family = 2, sa_data = "\220\372\n\314\000\035\000\000\000\000\000\000\000"}, sin = { sin_family = 2, sin_port = 64144, sin_addr = {s_addr = 486591498}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = { sin6_family = 2, sin6_port = 64144, sin6_flowinfo = 486591498, sin6_addr = {__in6_u = { __u6_addr8 = "\000\000\000\000\000\000\000\000W\335\366\355\375\177\000", __u6_addr16 = {0, 0, 0, 0, 56663, 60918, 32765, 0}, __u6_addr32 = {0, 0, 3992378711, 32765}}}, sin6_scope_id = 0}}, bind_address = 0x7f7033f74d68} len = buf = "REGISTER sip:10.200.0.153:5060;transport=UDP SIP/2.0\r\nVia: SIP/2.0/UDP 10.204.0.29:37114;branch=z9hG4bK-524287-1---42810a0f5b9ff5d9;rport\r\nMax-Forwards: 69\r\nContact: msg = { s = 0x55cc8997c120 "REGISTER sip:10.200.0.153:5060;transport=UDP SIP/2.0\r\nVia: SIP/2.0/UDP 10.204.0.29:37114;branch=z9hG4bK-524287-1---42810a0f5b9ff5d9;rport\r\nMax-Forwards: 69\r\nContact: to continue, or q to quit--- #9 0x000055cc8965f95f in handle_io (idx=0, event_type=1, fm=) at net/net_udp.c:272 n = 0 read = 21964 #10 io_wait_loop_epoll (repeat=, t=, h=) at net/../io_wait_loop.h:280 ret = 1 n = 1 r = 0 i = e = ep_event = {events = 1, data = {ptr = 0x323c60c000000000, fd = 0, u32 = 0, u64 = 3619874578249023488}} fd = #11 0x000055cc89664764 in udp_start_processes (chd_rank=, startup_done=) at net/net_udp.c:496 si = p_id = i = __FUNCTION__ = "udp_start_processes" #12 0x000055cc8945a713 in main_loop () at main.c:795 startup_done = 0x0 chd_rank = 2 last_check = 0 rc = chd_rank = 2 #13 main (argc=, argv=) at main.c:1480 ---Type to continue, or q to quit--- c = r = tmp = 0x7f7034f7ffe5 "H\205\300u\177L\211\351L\211\342D\211\376\211\357\350\266\374\377\377H\205\300uj\213t$\bL\211\351L\211\342\211\357\350\240\374\377\377H\205\300uTD9t$\fA\215V\001v0A\211ָ\002" tmp_len = port = proto = protos_no = options = 0x55cc896bdad0 "f:cCm:M:b:l:n:N:rRvdDFEVhw:t:u:g:p:P:G:W:o:a:k:s:" ret = -1 seed = 3897978920 rfd = __FUNCTION__ = "main" (gdb) From: Bogdan-Andrei Iancu Sent: Wednesday, June 19, 2019 5:43 PM To: johan de clercq ; 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] segfault in opensips30 Do "gdb /path/to/opensips /path/to/corefile" Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/19/2019 06:41 PM, johan de clercq wrote: Bogdan, see below output : what am I doing wrong ? root at hendrix:/tmp# gdb /tmp/core GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Copyright (C) 2016 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-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... "/tmp/core": not in executable format: File format not recognized From: Bogdan-Andrei Iancu Sent: Wednesday, June 19, 2019 5:25 PM To: OpenSIPS users mailling list ; johan de clercq Subject: Re: [OpenSIPS-Users] segfault in opensips30 Hi Johan, Can you extract the full backtrace from the core file ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/19/2019 06:11 PM, johan de clercq wrote: un 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:db_mysql:db_mysql_convert_rows: no rows returned from the query Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:usrloc:db_load_urecord: aor 32478720105 not found in table location Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_columns: freeing result columns at 0x7f0d8fa8c7f8 Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_rows: freeing 0 rows Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_result: freeing result set at 0x7f0d8fa8b320 Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:registrar:_remove: no record '32478720105' found! Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: CRITICAL:core:sig_usr: segfault in process pid: 31541, id: 5 From: johan de clercq Sent: Wednesday, June 19, 2019 4:53 PM To: 'OpenSIPS users mailling list' Subject: segfault in opensips30 When trying to register an unknown user, I have a segfault. I can easily reproduce, so please tell me what I need to do to give you a dump. Johan De Clercq, Managing Director Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke Tel +3256980990 – GSM +32478720104 _______________________________________________ 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: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From rrevels at bandwidth.com Wed Jun 19 18:06:18 2019 From: rrevels at bandwidth.com (Richard Revels) Date: Wed, 19 Jun 2019 18:06:18 -0400 Subject: [OpenSIPS-Users] CANCEL & INVITE In-Reply-To: <4D9B6E87.2060109@opensips.org> References: <4D9B200F.8050108@portaone.com> <4D9B6E87.2060109@opensips.org> Message-ID: I'm going to resurrect this as I've noticed that opensips 2.4.6 sends CANCEL for branches it never got a provisional response for. Was this changed intentionally? Also, it looks like the discussion I am responding on was about opensips 1.5 but if any testing is needed around fail-over scenarios I expect to be doing some of that over the next few days. Just let me know what still needs to be looked at and I'll try to get it in. [image: BandwidthMaroon.png] Richard Revels • System Architect II 900 Main Campus Drive, Suite 100, Raleigh, NC 27606 m: 919-578-3421 • o: 919-727-4614 e: rrevels at bandwidth.com On Tue, Apr 5, 2011 at 3:33 PM Bogdan-Andrei Iancu wrote: > Hi guys, > > Actually it will be great to have that patch tested to know for sure if > the problem is solved. I never got a 100% confirmation from Andrew, but > maybe Piotr can test and confirm. > > Thanks and regards, > Bogdan > > On 04/05/2011 04:58 PM, Andrew Pogrebennyk wrote: > > Hi Piotr, > > This sounds familiar to the problem I experienced some time ago - make > > sure to check comments here: > > > https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2940556&group_id=232389 > > > > I haven't been able to replicate that setup to confirm that the > > attached patch works. You are welcome to try it though :) Note RFC > > states it clearly that if no response has been received from the UAS > > at all, we should not attempt to send a CANCEL there. > > > > But it seems that in your case you received some provisional response > > so the issue has to do with the order in which CANCEL is fired - > > exactly what the patch is intended to fix. > > > > On 05.04.2011 15:56, Piotr Sobolewski wrote: > >> I'm having problem with specific gateway to which OpenSIPS sends > >> INVITE and then another INVITE (CallForward on no Aswer). > >> The problem is when after sending first INVITE to gateway (without > >> getting final response), OpenSIPS hits failure route and then sends > >> another INVITE (with different RURI) toward gateway before CANCEL is > >> sent, so the gateway responds to second INVITE with "482 Request > >> merged" (and gateway does not attempt to make second connection). > >> Is there a way to send CANCEL before sending second INVITE ? > > > > > -- > Bogdan-Andrei Iancu > OpenSIPS eBootcamp - 2nd of May 2011 > OpenSIPS solutions and "know-how" > > > _______________________________________________ > 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 Johan at democon.be Thu Jun 20 05:13:51 2019 From: Johan at democon.be (Johan De Clercq) Date: Thu, 20 Jun 2019 11:13:51 +0200 Subject: [OpenSIPS-Users] segfault in opensips30 In-Reply-To: <65999241-c5fd-c57f-a740-b285eccd1c7b@opensips.org> References: <00c901d526ae$b05170f0$10f452d0$@democon.be> <00e001d526b1$52e8c0f0$f8ba42d0$@democon.be> <00f801d526b5$7dd11c50$797354f0$@democon.be> <65999241-c5fd-c57f-a740-b285eccd1c7b@opensips.org> Message-ID: Hello bogdan, do you have everything you need? Br, On Wed, 19 Jun 2019, 17:43 Bogdan-Andrei Iancu, wrote: > Do "gdb /path/to/opensips /path/to/corefile" > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/19/2019 06:41 PM, johan de clercq wrote: > > Bogdan, see below output : what am I doing wrong ? > > > > root at hendrix:/tmp# gdb /tmp/core > > GNU gdb (Debian 7.12-6) 7.12.0.20161007-git > > Copyright (C) 2016 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-linux-gnu". > > Type "show configuration" for configuration details. > > For bug reporting instructions, please see: > > > . > > Find the GDB manual and other documentation resources online at: > > > . > > For help, type "help". > > Type "apropos word" to search for commands related to "word"... > > "/tmp/core": not in executable format: File format not recognized > > > > *From:* Bogdan-Andrei Iancu > *Sent:* Wednesday, June 19, 2019 5:25 PM > *To:* OpenSIPS users mailling list > ; johan de clercq > > *Subject:* Re: [OpenSIPS-Users] segfault in opensips30 > > > > Hi Johan, > > Can you extract the full backtrace from the core file ? > > Regards, > > Bogdan-Andrei Iancu > > > > OpenSIPS Founder and Developer > > https://www.opensips-solutions.com > > OpenSIPS Summit 2019 > > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/19/2019 06:11 PM, johan de clercq wrote: > > un 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:db_mysql:db_mysql_convert_rows: no rows returned from the query > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:usrloc:db_load_urecord: aor 32478720105 not found in table location > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:core:db_free_columns: freeing result columns at 0x7f0d8fa8c7f8 > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:core:db_free_rows: freeing 0 rows > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:core:db_free_result: freeing result set at 0x7f0d8fa8b320 > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > DBG:registrar:_remove: no record '32478720105' found! > > Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: > CRITICAL:core:sig_usr: segfault in process pid: 31541, id: 5 > > > > *From:* johan de clercq > *Sent:* Wednesday, June 19, 2019 4:53 PM > *To:* 'OpenSIPS users mailling list' > > *Subject:* segfault in opensips30 > > > > When trying to register an unknown user, I have a segfault. > > I can easily reproduce, so please tell me what I need to do to give you a > dump. > > > > [image: cid:F3100D46-F00D-4610-87ED-3E91DA790A82] > > Johan De Clercq, Managing Director > Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke > > Tel +3256980990 – GSM +32478720104 > > > > > > > _______________________________________________ > > 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: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From alexei.vasilyev at gmail.com Fri Jun 21 07:37:07 2019 From: alexei.vasilyev at gmail.com (Alexey Vasilyev) Date: Fri, 21 Jun 2019 04:37:07 -0700 (MST) Subject: [OpenSIPS-Users] How to pass in-dialog data with topology_hiding? Message-ID: <1561117027114-0.post@n2.nabble.com> Hello team, I'm using transaction statefull proxy with topology_hiding. Without dialog module. And I use rtpengine for part of calls. Decision, to use it or not, is made during initial INVITE. Without topology_hiding I can keep this decision in some param in RR and use on re-Invite: 1) add_rr_param(";rtpengine=yes"); ... 2) After loose_route() if (check_route_param("rtpengine=yes")) { route(rtpengine); exit; } With topology_hiding I have no RR and VIA headers. But instead of loose_route() I use topology_hiding_match() and it should restore RR headers. But it seems, that function topology_hiding() encodes only RR headers from original UAC request, not those ones that were added by OpenSIPS. So the question - how to pass this in-dialog data? Should we add functions add_th_param/get_th_param for this purpose? Thanks. ----- --- Alexey Vasilyev -- Sent from: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html From k.galinurov at gmail.com Fri Jun 21 09:17:10 2019 From: k.galinurov at gmail.com (Kirill Galinurov) Date: Fri, 21 Jun 2019 16:17:10 +0300 Subject: [OpenSIPS-Users] Latest opensips crashed after start. During loading drouting tables. Message-ID: Hi all. I try latest opensips. And it's crashed during loading drouting tables. version: opensips 3.0.0 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll, sigio_rt, select. git revision: bfd80ccde main.c compiled on 02:37:48 Jun 21 2019 with gcc 4.8.5 opensips -D -f /etc/opensips/opensips.cfg -m 4096 -M 4096 CRITICAL:core:fm_free: freeing already freed pkg pointer (0x7f9869850b98), first free: (null): (null)(0) - aborting! bt full (gdb) bt full #0 0x00007f9969862207 in ?? () No symbol table info available. #1 0x00007f99698638f8 in ?? () No symbol table info available. #2 0x0000000000000020 in ?? () No symbol table info available. #3 0x0000000000000000 in ?? () No symbol table info available. -------------- next part -------------- An HTML attachment was scrubbed... URL: From liviu at opensips.org Fri Jun 21 09:22:48 2019 From: liviu at opensips.org (Liviu Chircu) Date: Fri, 21 Jun 2019 16:22:48 +0300 Subject: [OpenSIPS-Users] Latest opensips crashed after start. During loading drouting tables. In-Reply-To: References: Message-ID: Hi Kirill, Can you restart your OpenSIPS using the "-a Q_MALLOC_DBG" command-line option and see if we can get that CRITICAL log to include the missing information?  Thanks! Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 21.06.2019 16:17, Kirill Galinurov wrote: > Hi all. I try latest opensips. And it's crashed  during loading > drouting tables. > version: opensips 3.0.0 (x86_64/linux) > flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, > Q_MALLOC, F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT > ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, > MAX_URI_SIZE 1024, BUF_SIZE 65535 > poll method support: poll, epoll, sigio_rt, select. > git revision: bfd80ccde > main.c compiled on 02:37:48 Jun 21 2019 with gcc 4.8.5 > > opensips -D -f /etc/opensips/opensips.cfg -m 4096 -M 4096 > CRITICAL:core:fm_free: freeing already freed pkg pointer > (0x7f9869850b98), first free: (null): (null)(0) - aborting! > > bt full > (gdb) bt full > #0  0x00007f9969862207 in ?? () > No symbol table info available. > #1  0x00007f99698638f8 in ?? () > No symbol table info available. > #2  0x0000000000000020 in ?? () > No symbol table info available. > #3  0x0000000000000000 in ?? () > No symbol table info available. > > > > > _______________________________________________ > 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 k.galinurov at gmail.com Fri Jun 21 09:39:49 2019 From: k.galinurov at gmail.com (Kirill Galinurov) Date: Fri, 21 Jun 2019 16:39:49 +0300 Subject: [OpenSIPS-Users] Latest opensips crashed after start. During loading drouting tables. In-Reply-To: References: Message-ID: opensips -D -f /etc/opensips/opensips.cfg -a Q_MALLOC_DBG -m 4096 -M 4096 Jun 21 09:30:27 [22590] ERROR:core:new_db_id: error while parsing database URL: 'postgres://opensips:8T2yJe7tqzolPdn171SO at master.naudb. service.consul' Jun 21 09:30:27 [22590] CRITICAL:core:qm_debug_frag: qm_*: fragm. 0x7f3eef53caf0 (address 0x7f3eef53cb20) end overwritten(0, 0)! So it's looks like my mistake in db_url field in dr_partitions tabel. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From liviu at opensips.org Fri Jun 21 10:01:19 2019 From: liviu at opensips.org (Liviu Chircu) Date: Fri, 21 Jun 2019 17:01:19 +0300 Subject: [OpenSIPS-Users] Latest opensips crashed after start. During loading drouting tables. In-Reply-To: References: Message-ID: <6304be38-fc8c-2d58-8992-82d6425ab30f@opensips.org> Good news!  I managed to reproduce this crash -- will push a fix soon. Cheers, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 21.06.2019 16:39, Kirill Galinurov wrote: > > > > opensips -D -f /etc/opensips/opensips.cfg -a Q_MALLOC_DBG -m 4096 -M 4096 > > Jun 21 09:30:27 [22590] ERROR:core:new_db_id: error while parsing > database URL: 'postgres://opensips:8T2yJe7tqzolPdn171SO at master.naudb. > service.consul' > Jun 21 09:30:27 [22590] CRITICAL:core:qm_debug_frag: qm_*: fragm. > 0x7f3eef53caf0 (address 0x7f3eef53cb20) end overwritten(0, 0)! > > So it's looks like my mistake in db_url field in dr_partitions tabel. > > > _______________________________________________ > 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 Fri Jun 21 10:57:43 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Fri, 21 Jun 2019 17:57:43 +0300 Subject: [OpenSIPS-Users] opensips-cp 30 In-Reply-To: <00c301d526ae$018e0fb0$04aa2f10$@democon.be> References: <00c301d526ae$018e0fb0$04aa2f10$@democon.be> Message-ID: <21011a97-0f10-0b4e-163a-a912e5d08c72@opensips.org> Hey Johan, I'm currently working in re-aligning the MI interface in CP with OpenSIPS 3.0 - I estimate 1-2 weeks to get it done. Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/19/2019 05:48 PM, johan de clercq wrote: > > When can the control panel be expected for opensips 30 ? > > BR, > > cid:F3100D46-F00D-4610-87ED-3E91DA790A82 > > Johan De Clercq, Managing Director > Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke > > Tel +3256980990– GSM +32478720104 > > > > _______________________________________________ > 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: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From bogdan at opensips.org Fri Jun 21 11:26:58 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Fri, 21 Jun 2019 18:26:58 +0300 Subject: [OpenSIPS-Users] CANCEL & INVITE In-Reply-To: References: <4D9B200F.8050108@portaone.com> <4D9B6E87.2060109@opensips.org> Message-ID: Woooow - we have a record here :) - resuming a discussion over 8 years !!!!! AFAIK, there was no intentional change (when comes to canceling branches with no reply) - do you have a pcap + logs to show such behavior ? And in regards to the sequence of CANCEL (on timeout) + forking, I think this was fixed starting 1.7 - first the CANCEL is sent out and then the new potential branches. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/20/2019 01:06 AM, Richard Revels wrote: > I'm going to resurrect this as I've noticed that opensips 2.4.6 sends > CANCEL for branches it never got a provisional response for. Was this > changed intentionally? > > Also, it looks like the discussion I am responding on was about > opensips 1.5 but if any testing is needed around fail-over scenarios I > expect to be doing some of that over the next few days. Just let me > know what still needs to be looked at and I'll try to get it in. > > > BandwidthMaroon.png > > > > Richard Revels•System Architect II > > 900 Main Campus Drive, Suite 100, Raleigh, NC 27606 > > m:919-578-3421 • o: 919-727-4614 > > e: rrevels at bandwidth.com > > > > On Tue, Apr 5, 2011 at 3:33 PM Bogdan-Andrei Iancu > > wrote: > > Hi guys, > > Actually it will be great to have that patch tested to know for > sure if > the problem is solved. I never got a 100% confirmation from > Andrew, but > maybe Piotr can test and confirm. > > Thanks and regards, > Bogdan > > On 04/05/2011 04:58 PM, Andrew Pogrebennyk wrote: > > Hi Piotr, > > This sounds familiar to the problem I experienced some time ago > - make > > sure to check comments here: > > > https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2940556&group_id=232389 > > > > I haven't been able to replicate that setup to confirm that the > > attached patch works. You are welcome to try it though :) Note RFC > > states it clearly that if no response has been received from the > UAS > > at all, we should not attempt to send a CANCEL there. > > > > But it seems that in your case you received some provisional > response > > so the issue has to do with the order in which CANCEL is fired - > > exactly what the patch is intended to fix. > > > > On 05.04.2011 15:56, Piotr Sobolewski wrote: > >> I'm having problem with specific gateway to which OpenSIPS sends > >> INVITE and then another INVITE (CallForward on no Aswer). > >> The problem is when after sending first INVITE to gateway (without > >> getting final response), OpenSIPS hits failure route and then sends > >> another INVITE (with different RURI) toward gateway before > CANCEL is > >> sent, so the gateway responds to second INVITE with "482 Request > >> merged" (and gateway does not attempt to make second connection). > >> Is there a way to send CANCEL before sending second INVITE ? > > > > > -- > Bogdan-Andrei Iancu > OpenSIPS eBootcamp - 2nd of May 2011 > OpenSIPS solutions and "know-how" > > > _______________________________________________ > 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 Fri Jun 21 11:30:35 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Fri, 21 Jun 2019 18:30:35 +0300 Subject: [OpenSIPS-Users] How to pass in-dialog data with topology_hiding? In-Reply-To: <1561117027114-0.post@n2.nabble.com> References: <1561117027114-0.post@n2.nabble.com> Message-ID: <2c25f424-836d-53c4-3841-00b0ebbead49@opensips.org> Hi Alexey, MAybe you should try to add some kind of parameter to the Contact URI - TH is replacing the hostport parts, not the full URI (double check it please :D). The Contact URI will be received back as RURI. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/21/2019 02:37 PM, Alexey Vasilyev wrote: > Hello team, > > I'm using transaction statefull proxy with topology_hiding. Without dialog > module. > > And I use rtpengine for part of calls. Decision, to use it or not, is made > during initial INVITE. Without topology_hiding I can keep this decision in > some param in RR and use on re-Invite: > 1) add_rr_param(";rtpengine=yes"); > ... > 2) After loose_route() > if (check_route_param("rtpengine=yes")) { > route(rtpengine); > exit; > } > With topology_hiding I have no RR and VIA headers. But instead of > loose_route() I use topology_hiding_match() and it should restore RR > headers. But it seems, that function topology_hiding() > encodes only RR headers from original UAC request, not those ones that were > added by OpenSIPS. > > So the question - how to pass this in-dialog data? > Should we add functions add_th_param/get_th_param for this purpose? > Thanks. > > > > ----- > --- > Alexey Vasilyev > -- > Sent from: http://opensips-open-sip-server.1449251.n2.nabble.com/OpenSIPS-Users-f1449235.html > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From liviu at opensips.org Fri Jun 21 11:42:08 2019 From: liviu at opensips.org (Liviu Chircu) Date: Fri, 21 Jun 2019 18:42:08 +0300 Subject: [OpenSIPS-Users] Latest opensips crashed after start. During loading drouting tables. In-Reply-To: <6304be38-fc8c-2d58-8992-82d6425ab30f@opensips.org> References: <6304be38-fc8c-2d58-8992-82d6425ab30f@opensips.org> Message-ID: <6b3e47de-10ad-d9d8-9b94-9a66ecd79bbb@opensips.org> Done[1], thanks for the report! [1]: https://github.com/OpenSIPS/opensips/commit/cba99632f1 Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 21.06.2019 17:01, Liviu Chircu wrote: > > Good news!  I managed to reproduce this crash -- will push a fix soon. > > Cheers, > > Liviu Chircu > OpenSIPS Developer > http://www.opensips-solutions.com > On 21.06.2019 16:39, Kirill Galinurov wrote: >> >> >> >> opensips -D -f /etc/opensips/opensips.cfg -a Q_MALLOC_DBG -m 4096 -M 4096 >> >> Jun 21 09:30:27 [22590] ERROR:core:new_db_id: error while parsing >> database URL: 'postgres://opensips:8T2yJe7tqzolPdn171SO at master.naudb. >> service.consul' >> Jun 21 09:30:27 [22590] CRITICAL:core:qm_debug_frag: qm_*: fragm. >> 0x7f3eef53caf0 (address 0x7f3eef53cb20) end overwritten(0, 0)! >> >> So it's looks like my mistake in db_url field in dr_partitions tabel. >> >> >> _______________________________________________ >> 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 Fri Jun 21 11:53:14 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Fri, 21 Jun 2019 18:53:14 +0300 Subject: [OpenSIPS-Users] segfault in opensips30 In-Reply-To: References: <00c901d526ae$b05170f0$10f452d0$@democon.be> <00e001d526b1$52e8c0f0$f8ba42d0$@democon.be> <00f801d526b5$7dd11c50$797354f0$@democon.be> <65999241-c5fd-c57f-a740-b285eccd1c7b@opensips.org> Message-ID: <421abc52-09af-265e-175b-f3437241d268@opensips.org> Hi Johan, Thank you for the backtrace - I just pushed a fix for this crash. Please updated from GIT and give it another try. Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/20/2019 12:13 PM, Johan De Clercq wrote: > Hello bogdan, do you have everything you need? > > Br, > > On Wed, 19 Jun 2019, 17:43 Bogdan-Andrei Iancu, > wrote: > > Do "gdb /path/to/opensips /path/to/corefile" > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/19/2019 06:41 PM, johan de clercq wrote: >> >> Bogdan, see below output : what am I doing wrong ? >> >> root at hendrix:/tmp# gdb /tmp/core >> >> GNU gdb (Debian 7.12-6) 7.12.0.20161007-git >> >> Copyright (C) 2016 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-linux-gnu". >> >> Type "show configuration" for configuration details. >> >> For bug reporting instructions, please see: >> >> >> . >> >> Find the GDB manual and other documentation resources online at: >> >> >> . >> >> For help, type "help". >> >> Type "apropos word" to search for commands related to "word"... >> >> "/tmp/core": not in executable format: File format not recognized >> >> *From:*Bogdan-Andrei Iancu >> >> *Sent:* Wednesday, June 19, 2019 5:25 PM >> *To:* OpenSIPS users mailling list >> ; johan de clercq >> >> *Subject:* Re: [OpenSIPS-Users] segfault in opensips30 >> >> Hi Johan, >> >> Can you extract the full backtrace from the core file ? >> >> Regards, >> >> Bogdan-Andrei Iancu >> >> OpenSIPS Founder and Developer >> https://www.opensips-solutions.com >> OpenSIPS Summit 2019 >> https://www.opensips.org/events/Summit-2019Amsterdam/ >> >> On 06/19/2019 06:11 PM, johan de clercq wrote: >> >> un 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: >> DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type >> >> Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: >> DBG:db_mysql:db_mysql_convert_rows: no rows returned from the >> query >> >> Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: >> DBG:usrloc:db_load_urecord: aor 32478720105 not found in >> table location >> >> Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: >> DBG:core:db_free_columns: freeing result columns at >> 0x7f0d8fa8c7f8 >> >> Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: >> DBG:core:db_free_rows: freeing 0 rows >> >> Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: >> DBG:core:db_free_result: freeing result set at 0x7f0d8fa8b320 >> >> Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: >> DBG:registrar:_remove: no record '32478720105' found! >> >> Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: >> CRITICAL:core:sig_usr: segfault in process pid: 31541, id: 5 >> >> *From:* johan de clercq >> >> *Sent:* Wednesday, June 19, 2019 4:53 PM >> *To:* 'OpenSIPS users mailling list' >> >> *Subject:* segfault in opensips30 >> >> When trying to register an unknown user, I have a segfault. >> >> I can easily reproduce, so please tell me what I need to do >> to give you a dump. >> >> cid:F3100D46-F00D-4610-87ED-3E91DA790A82 >> >> Johan De Clercq, Managing Director >> Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke >> >> Tel +3256980990 – GSM +32478720104 >> >> >> >> >> _______________________________________________ >> >> 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 johan at democon.be Sat Jun 22 08:55:15 2019 From: johan at democon.be (johan de clercq) Date: Sat, 22 Jun 2019 14:55:15 +0200 Subject: [OpenSIPS-Users] segfault in opensips30 In-Reply-To: <421abc52-09af-265e-175b-f3437241d268@opensips.org> References: <00c901d526ae$b05170f0$10f452d0$@democon.be> <00e001d526b1$52e8c0f0$f8ba42d0$@democon.be> <00f801d526b5$7dd11c50$797354f0$@democon.be> <65999241-c5fd-c57f-a740-b285eccd1c7b@opensips.org> <421abc52-09af-265e-175b-f3437241d268@opensips.org> Message-ID: <00bf01d528f9$bd4a2b60$37de8220$@democon.be> Bogdan, The fix works. Thanks and have a great weekend. From: Bogdan-Andrei Iancu Sent: Friday, June 21, 2019 5:53 PM To: Johan De Clercq Cc: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] segfault in opensips30 Hi Johan, Thank you for the backtrace - I just pushed a fix for this crash. Please updated from GIT and give it another try. Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/20/2019 12:13 PM, Johan De Clercq wrote: Hello bogdan, do you have everything you need? Br, On Wed, 19 Jun 2019, 17:43 Bogdan-Andrei Iancu, > wrote: Do "gdb /path/to/opensips /path/to/corefile" Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/19/2019 06:41 PM, johan de clercq wrote: Bogdan, see below output : what am I doing wrong ? root at hendrix:/tmp# gdb /tmp/core GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Copyright (C) 2016 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-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... "/tmp/core": not in executable format: File format not recognized From: Bogdan-Andrei Iancu Sent: Wednesday, June 19, 2019 5:25 PM To: OpenSIPS users mailling list ; johan de clercq Subject: Re: [OpenSIPS-Users] segfault in opensips30 Hi Johan, Can you extract the full backtrace from the core file ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/19/2019 06:11 PM, johan de clercq wrote: un 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:db_mysql:db_mysql_convert_rows: no rows returned from the query Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:usrloc:db_load_urecord: aor 32478720105 not found in table location Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_columns: freeing result columns at 0x7f0d8fa8c7f8 Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_rows: freeing 0 rows Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_result: freeing result set at 0x7f0d8fa8b320 Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:registrar:_remove: no record '32478720105' found! Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: CRITICAL:core:sig_usr: segfault in process pid: 31541, id: 5 From: johan de clercq Sent: Wednesday, June 19, 2019 4:53 PM To: 'OpenSIPS users mailling list' Subject: segfault in opensips30 When trying to register an unknown user, I have a segfault. I can easily reproduce, so please tell me what I need to do to give you a dump. Johan De Clercq, Managing Director Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke Tel +3256980990 – GSM +32478720104 _______________________________________________ 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 johan at democon.be Sat Jun 22 09:43:27 2019 From: johan at democon.be (johan de clercq) Date: Sat, 22 Jun 2019 15:43:27 +0200 Subject: [OpenSIPS-Users] problem with init on opensips3.0 Message-ID: <00f201d52900$7903f920$6b0beb60$@democon.be> Hello, Opensips3.0 doesn't start automatically. It times out on a remote mysqlconnection. Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: ERROR:db_mysql:db_mysql_connect: driver error(2003): Can't connect to MySQL server on '10.3.0.81' (110 "Connection timed out") Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: ERROR:db_mysql:db_mysql_new_connection: initial connect failed Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: ERROR:core:db_do_init: could not add connection to the pool Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: ERROR:domain:domain_db_init: Cannot initialize database connection Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: ERROR:core:init_mod: failed to initialize module domain Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: ERROR:core:main: error while initializing modules With 2.4, the problem was not there. Please advice on how I need to fix this. Johan De Clercq, Managing Director Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke Tel +3256980990 - GSM +32478720104 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Opensips_init_script.txt URL: From podguiko at mail.ru Sun Jun 23 05:13:56 2019 From: podguiko at mail.ru (=?UTF-8?B?0J7Qu9C10LMg0J/QvtC00LPRg9C50LrQvg==?=) Date: Sun, 23 Jun 2019 12:13:56 +0300 Subject: [OpenSIPS-Users] =?utf-8?q?Understanding_statefuli_proxy_mode_ope?= =?utf-8?q?nsips=2E?= Message-ID: <1561281236.38274084@f497.i.mail.ru> Hello everyone! I'm trying to understand the internal mechanisms of opensips. I assume that by default opensips works like a statefull proxy. In my installation, opensips serves as a sip proxy. Balances incoming traffic between multiple freeswitch. And so I get INVITE from the external system. The first. I look at the log debug and I do not see that any transaction is being created about this. Does this mean that incoming Invite starts being processed as stateless? Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_msg: SIP Request: Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_msg: method: Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_msg: uri: Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_msg: version: Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_headers: flags=2 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_via_param: found param type 232, = ; state=16 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_via: end of header reached, state=5 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_headers: via found, flags=2 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_headers: this is the first via Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:receive_msg: After parse_msg... Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:receive_msg: preparing to run routing scripts... Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_headers: flags=100 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:_parse_to: end of header reached, state=10 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:_parse_to: display={}, ruri={sip:+999999999 at My-server.ru;user=phone} Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:get_hdr_field: [49]; uri=[sip:+5555555555 at My-server.ru;user=phone] Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:get_hdr_field: to body [#015#012] Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:get_hdr_field: cseq : <1> Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:get_hdr_field: content_length=478 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:get_hdr_field: found end of header The second. At a certain stage of processing Invites, I need to send request to AS via http(using async_rest) and remove the ISUP body from this INVITE. As soon as the script does it, Opensips tries to find a transaction for this INVITE. Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: MIME part from INVITE was delete Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:t_newtran: transaction on entrance=(nil) Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_headers: flags=ffffffffffffffff Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_headers: flags=78 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:t_lookup_request: start searching: hash=25168, isACK=0 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:matching_3261: RFC3261 transaction matching failed Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:t_lookup_request: no transaction found Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:run_reqin_callbacks: trans=0x7fd9e490a6a0, callback type 1, id 0 entered As I understand, opensips says that still there is no transaction for this INVITE...  And here comes a new function "run_reqin_callbacks". Could you explain in more detail the essence of this function. After calling this functions opensips looks like to start to work as statefull proxy. Or I am wrong? Third. I get a response from AS via http and send 403. It's just my busines-logic for some INVITEs. For sending 403 I use "send_reply" functions. From documentation I have read that "send_reply" works as statefull if original request was statefull and stateless if original request was stateless. From debug log I don't understand how this message was sent in fact.  Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:rest_client:resume_async_http_req: HTTP response code: 200 Jun 23 07:05:55 xx-xxxx-1 /usr/sbin/opensips[18398]: DBG:tm:io_watch_del: [UDP_worker] io_watch_del op on index -1 7 (0x8024c0, 7, -1, 0x10,0x1) fd_no=5 called Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:comp_scriptvar: int 26 : 1 / 0 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:comp_scriptvar: int 29 : 200 / 200 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: rest_post(http://127.0.0.1:28080/vms/v1/call_action) success, resp={ "action": "reject", "isup_code": 21, "reason": "noservice", "sip_code": "403" } Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:comp_scriptvar: str 20 : reject Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:comp_scriptvar: str 20 : reject Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_headers: flags=ffffffffffffffff Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:run_trans_callbacks: trans=0x7fd9e490a6a0, callback type 64, id 0 entered Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:evi_param_set: adding string param Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:evi_param_set: adding string param Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:evi_param_set: adding string param Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:evi_param_set: adding string param Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:evi_param_set: adding string param Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:evi_param_set: adding int param Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:evi_param_set: adding int param Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:destroy_avp_list: destroying list (nil) Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:dialog:next_state_dlg: dialog 0x7fd9e4909910 changed from state 1 to state 5, due event 4 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:dialog:dlg_onreply: dialog 0x7fd9e4909910 failed (negative reply) Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:dialog:unref_dlg: unref dlg 0x7fd9e4909910 with 1 -> 2 in entry 0x7fd9e48cfa60 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:clean_msg_clone: removing hdr->parsed 7 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:cleanup_uac_timers: RETR/FR timers reset Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:insert_timer_unsafe: [0]: 0x7fd9e490a818 (35659) Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:_reply_light: reply sent out. buf=0x7fd9e8740a50: SIP/2.0 4..., shmem=0x7fd9e490ea50: SIP/2.0 4 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:run_trans_callbacks: trans=0x7fd9e490a6a0, callback type 32768, id 3 entered Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:siptrace:trace_tm_out: TM out triggered req=(nil), rpl=0xffffffffffffffff Jun 23 07:05:55 xx-spx-1 /usr/sbin/opensips[18396]: DBG:core:parse_msg: SIP Request: Jun 23 07:05:55 xx-spx-1 /usr/sbin/opensips[18396]: DBG:core:parse_msg: method: Jun 23 07:05:55 xx-spx-1 /usr/sbin/opensips[18396]: DBG:core:parse_msg: uri: Jun 23 07:05:55 xx-spx-1 /usr/sbin/opensips[18398]: DBG:siptrace:trace_onreply_out: trace onreply out Jun 23 07:05:55 xx-spx-1 /usr/sbin/opensips[18398]: DBG:core:parse_headers: flags=40 Jun 23 07:05:55 xx-spx-1 /usr/sbin/opensips[18398]: DBG:siptrace:pipport2su: proto 132, host 192.168.50.11 , port 5060 Jun 23 07:05:55 xx-spx-1 /usr/sbin/opensips[18398]: DBG:siptrace:pipport2su: proto 132, host 192.168.50.61 , port 5060 Jun 23 07:05:55 xx-spx-1 /usr/sbin/opensips[18398]: DBG:proto_hep:add_hep_chunk: Chunk with (id=17; vendor=0) not found! Creating! Jun 23 07:05:55 xx-spx-1 /usr/sbin/opensips[18398]: DBG:proto_hep:add_hep_chunk: Hep chunk with (id=17; vendor=0) successfully built! Jun 23 07:05:55 xx-spx-1 /usr/sbin/opensips[18398]: DBG:core:mk_proxy: doing DNS lookup... Jun 23 07:05:55 xx-spx-1 /usr/sbin/opensips[18398]: DBG:tm:_reply_light: finished Jun 23 07:05:55 xx-spx-1 /usr/sbin/opensips[18398]: The call was rejected with 403 and noservice Jun 23 07:05:55 xx-spx-1 /usr/sbin/opensips[18398]: DBG:tm:t_unref: UNREF_UNSAFE: [0x7fd9e490a6a0] after is 0 Jun 23 07:05:56 xx-spx-1 /usr/sbin/opensips[18398]: DBG:dialog:unref_dlg: unref dlg 0x7fd9e4909910 with 1 -> 1 in entry 0 ACK comes to 403 immediately, which is already processed as it seems to me as a statefull Jun 23 07:05:56 xx-xxx-1 /usr/sbin/opensips[18396]: DBG:core:parse_headers: flags=78 Jun 23 07:05:56 xx-xxx-1 /usr/sbin/opensips[18396]: DBG:tm:t_lookup_request: start searching: hash=25168, isACK=1 Jun 23 07:05:56 xx-xxx-1 /usr/sbin/opensips[18396]: DBG:tm:matching_3261: RFC3261 transaction matched, tid=-23003-1-0 Jun 23 07:05:56 xx-xxx-1 /usr/sbin/opensips[18396]: DBG:tm:t_lookup_request: REF_UNSAFE:[0x7fd9e490a6a0] after is 1 Jun 23 07:05:56 xx-xxx-1 /usr/sbin/opensips[18396]: DBG:tm:t_lookup_request: transaction found (T=0x7fd9e490a6a0) Jun 23 07:05:56 xx-xxx-1 /usr/sbin/opensips[18396]: DBG:tm:run_trans_callbacks: trans=0x7fd9e490a6a0, callback type 16384, id 2 entered Jun 23 07:05:56 xx-xxx-1 /usr/sbin/opensips[18396]: DBG:siptrace:trace_tm_in: TM in triggered req=0x7fd9e871a7f8, rpl=(nil) Jun 23 07:05:56 xx-xxx-1 /usr/sbin/opensips[18396]: DBG:core:parse_headers: flags=40 Results How to make opensips when accepting INVITE immediately start working as a statefull proxy? What is the function for "run_reqin_callbacks".? I want to achieve the following behavior from my system: I get an invite. I process it. Maybe I will complete some 403 calls right at opensips. If this happens. Then I want to re-send 403 until I get an ACK on 403 from the remote side.   -- Oleg Podguyko -------------- next part -------------- An HTML attachment was scrubbed... URL: From k.galinurov at gmail.com Mon Jun 24 02:58:19 2019 From: k.galinurov at gmail.com (Kirill Galinurov) Date: Mon, 24 Jun 2019 09:58:19 +0300 Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi reload_routes Message-ID: Hi all. Latest opensips from night build. I try command - opensips-cli -x mi reload_routes And get errors:: INFO:core:routes_reload_per_proc: dropping reload cmd due out of sequence reason Jun 24 02:53:14 callout-msk /usr/sbin/opensips[14198]: CRITICAL:core:sig_usr: segfault in process pid: 14198, id: 5 Jun 24 02:53:14 callout-msk kernel: opensips[14198]: segfault at 1 ip 00000000004652b0 sp 00007ffd7cf54050 error 4 in opensips[400000+1 f1000] Jun 24 02:53:15 callout-msk /usr/sbin/opensips[14193]: INFO:core:handle_sigs: child process 14198 exited by a signal 11 Jun 24 02:53:15 callout-msk /usr/sbin/opensips[14193]: INFO:core:handle_sigs: core was not generated Jun 24 02:53:15 callout-msk /usr/sbin/opensips[14193]: INFO:core:handle_sigs: terminating due to SIGCHLD -------------- next part -------------- An HTML attachment was scrubbed... URL: From liviu at opensips.org Mon Jun 24 11:04:29 2019 From: liviu at opensips.org (Liviu Chircu) Date: Mon, 24 Jun 2019 18:04:29 +0300 Subject: [OpenSIPS-Users] Understanding statefuli proxy mode opensips. In-Reply-To: <1561281236.38274084@f497.i.mail.ru> References: <1561281236.38274084@f497.i.mail.ru> Message-ID: <013fa54d-2eed-11d0-e1ea-e8af750d7fc3@opensips.org> Hey Oleg, When processing a SIP request, you can create the SIP transaction (go stateful) using either t_newtran() [1] or t_relay() [2].  Replies will be automatically intercepted, matched and handled afterwards.  To obtain script-level access to them, you must install a t_on_reply() [3] route callback. Regards, [1]: https://opensips.org/html/docs/modules/3.0.x/tm.html#func_t_newtran [2]: https://opensips.org/html/docs/modules/3.0.x/tm.html#func_t_relay [3]: https://opensips.org/html/docs/modules/3.0.x/tm.html#func_t_on_reply Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 23.06.2019 12:13, Олег Подгуйко via Users wrote: > How to make opensips when accepting INVITE immediately start working > as a statefull proxy? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ben.Newlin at genesys.com Mon Jun 24 17:33:31 2019 From: Ben.Newlin at genesys.com (Ben Newlin) Date: Mon, 24 Jun 2019 21:33:31 +0000 Subject: [OpenSIPS-Users] Rest Client Async operation Message-ID: <6ED95883-2E26-477B-A8DF-6F6C130093AF@genesys.com> Hello all, During testing I have found behavior that I cannot explain based on our current understanding of the operation of the async and rest_client functionality. I have reproduced this behavior with a fairly simple script configuration, the relevant piece of which is below: children=8 loadmodule "rest_client.so" modparam("rest_client", "connection_timeout", 5) modparam("rest_client", "connect_poll_interval", 1) modparam("rest_client", "curl_timeout", 5) route { xlog("L_ALERT", "before t_newtran()\r\n"); t_newtran(); xlog("L_ALERT", "after t_newtran()\r\n"); async(rest_post("http://0.0.0.0", "{}", "application/json", "$var(body)", "$var(ctype)", "$var(rcode)"), test_resume); xlog("L_ALERT", "after async\r\n"); } route[test_resume] { xlog("L_ALERT", "test_resume: $retcode\r\n"); t_reply("503", "Service Unavailable"); } The expected operation is to immediately trigger t_newtran() which sends a 100 response, then timeout on the rest_post call in 5 seconds and respond with a 503. For individual calls this does occur, although the timeout consistently takes several seconds too long, usually ~8s, as can be seen in the logs from the above code: Jun 24 19:10:56 [337] before t_newtran() Jun 24 19:10:56 [337] after t_newtran() Jun 24 19:11:04 [337] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 19:11:04 [337] test_resume: -2 The extra time is troubling, but the bigger concern is that when I run multiple concurrent calls, I find that the 8 UDP children are still all blocking against the rest_post call. Here are the logs for that test: Jun 24 21:19:51 [337] before t_newtran() Jun 24 21:19:51 [337] after t_newtran() Jun 24 21:19:51 [338] before t_newtran() Jun 24 21:19:51 [338] after t_newtran() Jun 24 21:19:51 [335] before t_newtran() Jun 24 21:19:51 [335] after t_newtran() Jun 24 21:19:51 [333] before t_newtran() Jun 24 21:19:51 [333] after t_newtran() Jun 24 21:19:52 [331] before t_newtran() Jun 24 21:19:52 [331] after t_newtran() Jun 24 21:19:52 [336] before t_newtran() Jun 24 21:19:52 [336] after t_newtran() Jun 24 21:19:52 [332] before t_newtran() Jun 24 21:19:52 [332] after t_newtran() Jun 24 21:19:52 [334] before t_newtran() Jun 24 21:19:52 [334] after t_newtran() Jun 24 21:19:59 [337] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:19:59 [337] test_resume: -2 Jun 24 21:19:59 [337] before t_newtran() Jun 24 21:19:59 [337] after t_newtran() Jun 24 21:19:59 [338] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:19:59 [338] test_resume: -2 Jun 24 21:19:59 [338] before t_newtran() Jun 24 21:19:59 [338] after t_newtran() Jun 24 21:19:59 [335] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:19:59 [335] test_resume: -2 Jun 24 21:19:59 [335] before t_newtran() Jun 24 21:19:59 [335] after t_newtran() Jun 24 21:19:59 [333] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:19:59 [333] test_resume: -2 Jun 24 21:19:59 [333] before t_newtran() Jun 24 21:19:59 [333] after t_newtran() Jun 24 21:19:59 [331] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:19:59 [331] test_resume: -2 Jun 24 21:19:59 [331] before t_newtran() Jun 24 21:19:59 [331] after t_newtran() Jun 24 21:19:59 [336] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:19:59 [336] test_resume: -2 Jun 24 21:19:59 [336] before t_newtran() Jun 24 21:19:59 [336] after t_newtran() Jun 24 21:19:59 [332] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:19:59 [332] test_resume: -2 Jun 24 21:19:59 [332] before t_newtran() Jun 24 21:19:59 [332] after t_newtran() Jun 24 21:20:00 [334] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:00 [334] test_resume: -2 Jun 24 21:20:00 [334] before t_newtran() Jun 24 21:20:00 [334] after t_newtran() Jun 24 21:20:07 [337] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [337] test_resume: -2 Jun 24 21:20:07 [338] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [338] test_resume: -2 Jun 24 21:20:07 [335] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [335] test_resume: -2 Jun 24 21:20:07 [333] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [333] test_resume: -2 Jun 24 21:20:07 [331] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [331] test_resume: -2 Jun 24 21:20:07 [336] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [336] test_resume: -2 Jun 24 21:20:07 [332] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [332] test_resume: -2 Jun 24 21:20:07 [334] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [334] test_resume: -2 You can clearly see that the first 8 Invites are processed immediately, but then no new messages are processed until the rest queries begin to timeout. As each query times out, freeing a child process, a new inbound request is processed. Clearly the message processing is being blocked on the rest queries, which is not supposed to happen when using async. Am I missing something in my configuration or am I not understanding how async is supposed to work somehow? Ben Newlin -------------- next part -------------- An HTML attachment was scrubbed... URL: From k.galinurov at gmail.com Tue Jun 25 04:47:13 2019 From: k.galinurov at gmail.com (Kirill Galinurov) Date: Tue, 25 Jun 2019 11:47:13 +0300 Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi reload_routes In-Reply-To: References: Message-ID: One more information I run opensips in debug mode with command: opensips -f /etc/opensips/opensips.cfg.j2 -p "python3 /etc/opensips/opensips-preproc.py" a Q_MALLOC_DBG -m 16832 -M 512 After opensips-cli -x mi reload_routes ERROR: communication exception for 'reload_routes' returned: ERROR: Is OpenSIPS running? Logs: Jun 25 04:37:33 [21481] DBG:core:fix_actions: fixing t_was_cancelled, /etc/opensips/opensips_routes.cfg:346 Jun 25 04:37:33 [21481] INFO:core:routes_reload_per_proc: process successfully parsed new cfg (seq 1) Jun 25 04:37:55 [21460] DBG:core:reload_routing_script: done with waiting after 20001 miliseconds Jun 25 04:38:13 [21457] DBG:core:handle_sigs: unknown child process 21458 ended. Ignoring Jun 25 04:38:13 [21457] DBG:core:handle_sigs: OpenSIPS exit status = 139 Jun 25 04:38:13 [21457] INFO:core:handle_sigs: child process 21463 exited by a signal 11 Jun 25 04:38:13 [21457] INFO:core:handle_sigs: core was generated Jun 25 04:38:13 [21457] INFO:core:handle_sigs: terminating due to SIGCHLD (gdb) bt full: #0 0x00000000004652b0 in ?? () No symbol table info available. #1 0x0000000000000044 in ?? () No symbol table info available. #2 0x000053d70577fc74 in ?? () No symbol table info available. #3 0x0000000000000000 in ?? () No symbol table info available. -------------- next part -------------- An HTML attachment was scrubbed... URL: From spanda at 3clogic.com Tue Jun 25 06:18:55 2019 From: spanda at 3clogic.com (Sasmita Panda) Date: Tue, 25 Jun 2019 15:48:55 +0530 Subject: [OpenSIPS-Users] I need some help in websocket connection error . In-Reply-To: References: Message-ID: I have tried to take ssldump in the webrtc server in run time . New TCP connection #19: 192.168.1.y(48530) <-> 192.168.0.x(443) 19 0.0011 (0.0011) C>S TCP FIN 19 0.0013 (0.0001) S>C TCP FIN New TCP connection #20: 192.168.0.y(52975) <-> 192.168.0.x(443) 20 1 0.0006 (0.0006) C>S Handshake ClientHello 20 2 0.0008 (0.0002) S>C Handshake ServerHello 20 3 0.0008 (0.0000) S>C Handshake Certificate 20 4 0.0008 (0.0000) S>C Handshake ServerHelloDone 20 5 0.0020 (0.0011) C>S Handshake ClientKeyExchange 20 6 0.0020 (0.0000) C>S ChangeCipherSpec 20 7 0.0020 (0.0000) C>S Handshake 20 8 0.0036 (0.0015) S>C Handshake20 9 0.0036 (0.0000) S>C ChangeCipherSpec 20 10 0.0036 (0.0000) S>C Handshake 20 11 0.0042 (0.0006) C>S Alert 20 0.0042 (0.0000) C>S TCP FIN 20 0.0043 (0.0000) S>C TCP FIN The portion I marked in red whenever appear there is error in opensips logs . For below portion the connection was accepted . I am not even getting any error in my browser side . How I will debug this ? please help . *Thanks & Regards* *Sasmita Panda* *Senior Network Testing and Software Engineer* *3CLogic , ph:07827611765* On Fri, Jun 14, 2019 at 2:51 PM Callum Guy wrote: > You might find that a tcpdump is the only way to get to grips with the > underlying issue. > > Having said that I wonder if there is any chance that the connection isn't > accepting simply due to a cipher incompatibility. Are you setting a cipher > list that you know your clients accept? Maybe try: > > modparam("tls_mgm", "ciphers_list", > "AES256-GCM-SHA384,AES256-SHA256,AES256-SHA,CAMELLIA256-SHA,AES128-SHA,CAMELLIA128-SHA,RC4-SHA") > > > On Fri, 14 Jun 2019 at 09:17, Sasmita Panda wrote: > >> I had a dedicated server for 1 Client . When that client faces the issue >> I started looking into the logs . And this is what the error I got . >> >> but latter on when I saw other servers which is getting used by different >> client in that logs also same error coming everyday . >> >> As a conclusion its happening with everybody . >> >> Below is the configuration . >> >> modparam("tls_mgm", "tls_method", "tlsv1_2") >> modparam("tls_mgm", "verify_cert", "0") >> modparam("tls_mgm", "require_cert", "0") >> modparam("tls_mgm", "certificate", >> "/usr/etc/opensips/tls/3ccloudwebrtc2019.crt") >> modparam("tls_mgm", "private_key", "/usr/etc/opensips/tls/3ccloud.key") >> modparam("tls_mgm", "ca_list", "/usr/etc/opensips/tls/rootCA/cacert.pem") >> >> >> >> *Thanks & Regards* >> *Sasmita Panda* >> *Senior Network Testing and Software Engineer* >> *3CLogic , ph:07827611765* >> >> >> On Thu, Jun 13, 2019 at 6:50 PM Răzvan Crainea >> wrote: >> >>> Can you trace the SSL traffic between the two endpoints? Perhaps the SSL >>> header give you a reason for not accepting the connection. >>> Is this happening only for certain clients, or for everyone? >>> Are you requiring any certificates validation? >>> >>> Best regards, >>> Răzvan >>> >>> On 6/12/19 3:34 PM, Sasmita Panda wrote: >>> > I am using opensips 2.2 >>> > version: opensips 2.2.4 (x86_64/linux) >>> > >>> > I am using the proto_wss and tls_mgm module for establishing websocket >>> > connection . >>> > >>> > I am getting bellow error again and again . Whats the reson behind >>> this >>> > and how can I solve this problem ? >>> > >>> > >>> > Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: >>> > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb >>> > Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: >>> > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 96 >>> > Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: >>> > ERROR:proto_wss:tls_accept: New TLS connection from >>> 192.168.160.6:58616 >>> > failed to accept >>> > Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: >>> > ERROR:proto_wss:wss_read_req: cannot fix read connection >>> > Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: >>> > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb >>> > Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: >>> > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 96 >>> > Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: >>> > ERROR:proto_wss:tls_accept: New TLS connection from >>> 192.168.175.59:12918 >>> > failed to accept >>> > Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: >>> > ERROR:proto_wss:wss_read_req: cannot fix read connection >>> > >>> > >>> > Please do help . >>> > >>> > >>> > >>> > */Thanks & Regards/* >>> > /Sasmita Panda/ >>> > /Senior 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 >>> > >>> >>> -- >>> Răzvan Crainea >>> OpenSIPS Core 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 >> > > > *0333 332 0000 | www.x-on.co.uk | ** > > * > > X-on is a trading name of Storacall Technology Ltd a limited company > registered in England and Wales. > Registered Office : Avaland House, 110 London Road, Apsley, Hemel > Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. > The information in this e-mail is confidential and for use by the > addressee(s) only. If you are not the intended recipient, please notify > X-on immediately on +44(0)333 332 0000 and delete the > message from your computer. If you are not a named addressee you must not > use, disclose, disseminate, distribute, copy, print or reply to this email. Views > or opinions expressed by an individual > within this email may not necessarily reflect the views of X-on or its > associated companies. Although X-on routinely screens for viruses, > addressees should scan this email and any attachments > for viruses. X-on makes no representation or warranty as to the absence of > viruses in this email or any attachments. > > _______________________________________________ > 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 Tue Jun 25 08:49:22 2019 From: liviu at opensips.org (Liviu Chircu) Date: Tue, 25 Jun 2019 15:49:22 +0300 Subject: [OpenSIPS-Users] Rest Client Async operation In-Reply-To: <6ED95883-2E26-477B-A8DF-6F6C130093AF@genesys.com> References: <6ED95883-2E26-477B-A8DF-6F6C130093AF@genesys.com> Message-ID: <20e603cc-3bd3-c31a-b9d9-fd0c7e3e5542@opensips.org> Hi Ben, Regarding the "blocking rest_get()" problem: due to the specifics of the libcurl API, there is no direct access to the socket file descriptors during the initial TCP connect handshake.  Thus, this phase will be synchronous (blocking), while all transfers (send HTTP req, receive reply) are done asynchronously, regardless of how the data gets send or arrives (all at once, in chunks, byte-by-byte, etc.). So, indeed: on the specific test case that the remote TCP endpoint is either unresponsive or it is blocked by a firewall, the throughput of your OpenSIPS may be significantly affected when talking HTTP to such peers even if you perform async HTTP requests.  Maybe this is just my opinion, but I believe that the average case is when the HTTP server/API is down and the TCP connect attempt will get rejected. See [1] for more on this topic. Regarding the 5s vs. 8s timeouts, I will have to confirm the behavior first and get back to you. Async is heavily reliant on tm, so I wouldn't exclude the possibility that the transaction timeout overrides, in some cases, the async logic's timeout. Best regards, [1]: https://serverfault.com/questions/521359/why-do-some-connections-time-out-and-others-get-refused Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 25.06.2019 00:33, Ben Newlin wrote: > > Hello all, > > During testing I have found behavior that I cannot explain based on > our current understanding of the operation of the async and > rest_client functionality. I have reproduced this behavior with a > fairly simple script configuration, the relevant piece of which is below: > > children=8 > > loadmodule "rest_client.so" > > modparam("rest_client", "connection_timeout", 5) > > modparam("rest_client", "connect_poll_interval", 1) > > modparam("rest_client", "curl_timeout", 5) > > route { > > xlog("L_ALERT", "before t_newtran()\r\n"); > > t_newtran(); > > xlog("L_ALERT", "after t_newtran()\r\n"); > > async(rest_post("http://0.0.0.0", "{}", "application/json", > "$var(body)", "$var(ctype)", "$var(rcode)"), test_resume); > > xlog("L_ALERT", "after async\r\n"); > > } > > route[test_resume] { > > xlog("L_ALERT", "test_resume: $retcode\r\n"); > > t_reply("503", "Service Unavailable"); > > } > > The expected operation is to immediately trigger t_newtran() which > sends a 100 response, then timeout on the rest_post call in 5 seconds > and respond with a 503. For individual calls this does occur, although > the timeout consistently takes several seconds too long, usually ~8s, > as can be seen in the logs from the above code: > > Jun 24 19:10:56 [337] before t_newtran() > > Jun 24 19:10:56 [337] after t_newtran() > > Jun 24 19:11:04 [337] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 19:11:04 [337] test_resume: -2 > > The extra time is troubling, but the bigger concern is that when I run > multiple concurrent calls, I find that the 8 UDP children are still > all blocking against the rest_post call. Here are the logs for that test: > > Jun 24 21:19:51 [337] before t_newtran() > > Jun 24 21:19:51 [337] after t_newtran() > > Jun 24 21:19:51 [338] before t_newtran() > > Jun 24 21:19:51 [338] after t_newtran() > > Jun 24 21:19:51 [335] before t_newtran() > > Jun 24 21:19:51 [335] after t_newtran() > > Jun 24 21:19:51 [333] before t_newtran() > > Jun 24 21:19:51 [333] after t_newtran() > > Jun 24 21:19:52 [331] before t_newtran() > > Jun 24 21:19:52 [331] after t_newtran() > > Jun 24 21:19:52 [336] before t_newtran() > > Jun 24 21:19:52 [336] after t_newtran() > > Jun 24 21:19:52 [332] before t_newtran() > > Jun 24 21:19:52 [332] after t_newtran() > > Jun 24 21:19:52 [334] before t_newtran() > > Jun 24 21:19:52 [334] after t_newtran() > > Jun 24 21:19:59 [337] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:19:59 [337] test_resume: -2 > > Jun 24 21:19:59 [337] before t_newtran() > > Jun 24 21:19:59 [337] after t_newtran() > > Jun 24 21:19:59 [338] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:19:59 [338] test_resume: -2 > > Jun 24 21:19:59 [338] before t_newtran() > > Jun 24 21:19:59 [338] after t_newtran() > > Jun 24 21:19:59 [335] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:19:59 [335] test_resume: -2 > > Jun 24 21:19:59 [335] before t_newtran() > > Jun 24 21:19:59 [335] after t_newtran() > > Jun 24 21:19:59 [333] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:19:59 [333] test_resume: -2 > > Jun 24 21:19:59 [333] before t_newtran() > > Jun 24 21:19:59 [333] after t_newtran() > > Jun 24 21:19:59 [331] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:19:59 [331] test_resume: -2 > > Jun 24 21:19:59 [331] before t_newtran() > > Jun 24 21:19:59 [331] after t_newtran() > > Jun 24 21:19:59 [336] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:19:59 [336] test_resume: -2 > > Jun 24 21:19:59 [336] before t_newtran() > > Jun 24 21:19:59 [336] after t_newtran() > > Jun 24 21:19:59 [332] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:19:59 [332] test_resume: -2 > > Jun 24 21:19:59 [332] before t_newtran() > > Jun 24 21:19:59 [332] after t_newtran() > > Jun 24 21:20:00 [334] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:20:00 [334] test_resume: -2 > > Jun 24 21:20:00 [334] before t_newtran() > > Jun 24 21:20:00 [334] after t_newtran() > > Jun 24 21:20:07 [337] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:20:07 [337] test_resume: -2 > > Jun 24 21:20:07 [338] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:20:07 [338] test_resume: -2 > > Jun 24 21:20:07 [335] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:20:07 [335] test_resume: -2 > > Jun 24 21:20:07 [333] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:20:07 [333] test_resume: -2 > > Jun 24 21:20:07 [331] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:20:07 [331] test_resume: -2 > > Jun 24 21:20:07 [336] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:20:07 [336] test_resume: -2 > > Jun 24 21:20:07 [332] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:20:07 [332] test_resume: -2 > > Jun 24 21:20:07 [334] ERROR:rest_client:start_async_http_req: connect > timeout on http://0.0.0.0 (5s) > > Jun 24 21:20:07 [334] test_resume: -2 > > You can clearly see that the first 8 Invites are processed > immediately, but then no new messages are processed until the rest > queries begin to timeout. As each query times out, freeing a child > process, a new inbound request is processed. Clearly the message > processing is being blocked on the rest queries, which is not supposed > to happen when using async. Am I missing something in my configuration > or am I not understanding how async is supposed to work somehow? > > Ben Newlin > > > _______________________________________________ > 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 Tue Jun 25 10:51:58 2019 From: liviu at opensips.org (Liviu Chircu) Date: Tue, 25 Jun 2019 17:51:58 +0300 Subject: [OpenSIPS-Users] problem with init on opensips3.0 In-Reply-To: <00f201d52900$7903f920$6b0beb60$@democon.be> References: <00f201d52900$7903f920$6b0beb60$@democon.be> Message-ID: <38c308e6-7833-1a63-08a1-63739323fff4@opensips.org> Hi Johan, Just to be 100% sure it's an OpenSIPS problem, can you confirm either: * the "db_url" credentials work when used with the "mysql" command-line client,   from the same source IP * the same "db_url" works with a 2.4 OpenSIPS, from the same source IP Regards, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 22.06.2019 16:43, johan de clercq wrote: > > Hello, > > Opensips3.0 doesn’t start automatically. It times out on a remote > mysqlconnection. > > Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: > ERROR:db_mysql:db_mysql_connect: driver error(2003): Can't connect to > MySQL server on '10.3.0.81' (110 "Connection timed out") > > Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: > ERROR:db_mysql:db_mysql_new_connection: initial connect failed > > Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: > ERROR:core:db_do_init: could not add connection to the pool > > Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: > ERROR:domain:domain_db_init: Cannot initialize database connection > > Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: > ERROR:core:init_mod: failed to initialize module domain > > Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: > ERROR:core:main: error while initializing modules > > With 2.4, the problem was not there. Please advice on how I need to > fix this. > > cid:F3100D46-F00D-4610-87ED-3E91DA790A82 > > Johan De Clercq, Managing Director > Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke > > Tel +3256980990– GSM +32478720104 > > > _______________________________________________ > 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: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From bogdan at opensips.org Tue Jun 25 11:06:13 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 25 Jun 2019 18:06:13 +0300 Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi reload_routes In-Reply-To: References: Message-ID: <3cfae2bb-9271-4582-9bea-a77d3c74b4c0@opensips.org> Hi Kirill, Does your opensips predictably crashes each time you do the routes reload ? if yes, do you get each time an invalid corefile ? Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/25/2019 11:47 AM, Kirill Galinurov wrote: > One more information > I run opensips in debug mode with command: > opensips -f /etc/opensips/opensips.cfg.j2 -p "python3 > /etc/opensips/opensips-preproc.py" a Q_MALLOC_DBG -m 16832 -M 512 > > After opensips-cli -x mi reload_routes > ERROR: communication exception for 'reload_routes' returned: > ERROR: Is OpenSIPS running? > > Logs: > > Jun 25 04:37:33 [21481] DBG:core:fix_actions: fixing t_was_cancelled, > /etc/opensips/opensips_routes.cfg:346 > Jun 25 04:37:33 [21481] INFO:core:routes_reload_per_proc: process > successfully parsed new cfg (seq 1) > Jun 25 04:37:55 [21460] DBG:core:reload_routing_script: done with > waiting after 20001 miliseconds > Jun 25 04:38:13 [21457] DBG:core:handle_sigs: unknown child process > 21458 ended. Ignoring > Jun 25 04:38:13 [21457] DBG:core:handle_sigs: OpenSIPS exit status = 139 > Jun 25 04:38:13 [21457] INFO:core:handle_sigs: child process 21463 > exited by a signal 11 > Jun 25 04:38:13 [21457] INFO:core:handle_sigs: core was generated > Jun 25 04:38:13 [21457] INFO:core:handle_sigs: terminating due to SIGCHLD > > (gdb) bt full: > #0 0x00000000004652b0 in ?? () > No symbol table info available. > #1 0x0000000000000044 in ?? () > No symbol table info available. > #2 0x000053d70577fc74 in ?? () > No symbol table info available. > #3 0x0000000000000000 in ?? () > No symbol table info available. > > > > _______________________________________________ > 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 Johan at democon.be Tue Jun 25 11:06:42 2019 From: Johan at democon.be (Johan De Clercq) Date: Tue, 25 Jun 2019 17:06:42 +0200 Subject: [OpenSIPS-Users] problem with init on opensips3.0 In-Reply-To: <38c308e6-7833-1a63-08a1-63739323fff4@opensips.org> References: <00f201d52900$7903f920$6b0beb60$@democon.be> <38c308e6-7833-1a63-08a1-63739323fff4@opensips.org> Message-ID: Yes, they work form command line. Op di 25 jun. 2019 om 16:54 schreef Liviu Chircu : > Hi Johan, > > Just to be 100% sure it's an OpenSIPS problem, can you confirm either: > > * the "db_url" credentials work when used with the "mysql" command-line > client, > from the same source IP > * the same "db_url" works with a 2.4 OpenSIPS, from the same source IP > > Regards, > > Liviu Chircu > OpenSIPS Developerhttp://www.opensips-solutions.com > > On 22.06.2019 16:43, johan de clercq wrote: > > Hello, > > > > Opensips3.0 doesn’t start automatically. It times out on a remote > mysqlconnection. > > > > Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: > ERROR:db_mysql:db_mysql_connect: driver error(2003): Can't connect to MySQL > server on '10.3.0.81' (110 "Connection timed out") > > Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: > ERROR:db_mysql:db_mysql_new_connection: initial connect failed > > Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: > ERROR:core:db_do_init: could not add connection to the pool > > Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: > ERROR:domain:domain_db_init: Cannot initialize database connection > > Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: > ERROR:core:init_mod: failed to initialize module domain > > Jun 22 13:27:09 hendrix /data/opensips/sbin/opensips[1291]: > ERROR:core:main: error while initializing modules > > > > With 2.4, the problem was not there. Please advice on how I need to fix > this. > > > > > > > > [image: cid:F3100D46-F00D-4610-87ED-3E91DA790A82] > > Johan De Clercq, Managing Director > Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke > > Tel +3256980990 – GSM +32478720104 > > > > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: From k.galinurov at gmail.com Tue Jun 25 11:28:05 2019 From: k.galinurov at gmail.com (Kirill Galinurov) Date: Tue, 25 Jun 2019 18:28:05 +0300 Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi reload_routes In-Reply-To: <3cfae2bb-9271-4582-9bea-a77d3c74b4c0@opensips.org> References: <3cfae2bb-9271-4582-9bea-a77d3c74b4c0@opensips.org> Message-ID: Hi Bogan, Yes my opensips predictably crashes, when I do routes reload. Even when I do not change anythihg. But I think.. It' s probably crashes when I use return statement like: if (is_method("INVITE")) { route(get_account_code); route(check_callerid); route(number_normalize); } route[check_callerid]{ xlog("L_INFO","Check callerid to path for operators\n"); if(! dp_translate(999,$fU,$avp(FromNum))){ send_reply(404,"Bad From User"); exit; } else { return; } } When Opensips run as systemd service It restarts and core was not generated. вт, 25 июн. 2019 г. в 18:06, Bogdan-Andrei Iancu : > Hi Kirill, > > Does your opensips predictably crashes each time you do the routes reload > ? if yes, do you get each time an invalid corefile ? > > Best regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/25/2019 11:47 AM, Kirill Galinurov wrote: > > One more information > I run opensips in debug mode with command: > opensips -f /etc/opensips/opensips.cfg.j2 -p "python3 > /etc/opensips/opensips-preproc.py" a Q_MALLOC_DBG -m 16832 -M 512 > > After opensips-cli -x mi reload_routes > ERROR: communication exception for 'reload_routes' returned: > ERROR: Is OpenSIPS running? > > Logs: > > Jun 25 04:37:33 [21481] DBG:core:fix_actions: fixing t_was_cancelled, > /etc/opensips/opensips_routes.cfg:346 > Jun 25 04:37:33 [21481] INFO:core:routes_reload_per_proc: process > successfully parsed new cfg (seq 1) > Jun 25 04:37:55 [21460] DBG:core:reload_routing_script: done with waiting > after 20001 miliseconds > Jun 25 04:38:13 [21457] DBG:core:handle_sigs: unknown child process 21458 > ended. Ignoring > Jun 25 04:38:13 [21457] DBG:core:handle_sigs: OpenSIPS exit status = 139 > Jun 25 04:38:13 [21457] INFO:core:handle_sigs: child process 21463 exited > by a signal 11 > Jun 25 04:38:13 [21457] INFO:core:handle_sigs: core was generated > Jun 25 04:38:13 [21457] INFO:core:handle_sigs: terminating due to SIGCHLD > > (gdb) bt full: > #0 0x00000000004652b0 in ?? () > No symbol table info available. > #1 0x0000000000000044 in ?? () > No symbol table info available. > #2 0x000053d70577fc74 in ?? () > No symbol table info available. > #3 0x0000000000000000 in ?? () > No symbol table info available. > > > > _______________________________________________ > 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 Jun 25 11:36:05 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 25 Jun 2019 18:36:05 +0300 Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi reload_routes In-Reply-To: References: <3cfae2bb-9271-4582-9bea-a77d3c74b4c0@opensips.org> Message-ID: Do you have any idea if OpenSIPS crashes exactly when reloading or does it crash when handling traffic after the reload ? Again, any chances to get a valid backtrace ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/25/2019 06:28 PM, Kirill Galinurov wrote: > Hi Bogan, > Yes my opensips predictably crashes, when I do routes reload. Even > when I do not change anythihg. But I think.. It' s probably crashes > when I use > return statement like: > if (is_method("INVITE")) { > route(get_account_code); > route(check_callerid); > route(number_normalize); > } > > route[check_callerid]{ > xlog("L_INFO","Check callerid to path for operators\n"); > if(! dp_translate(999,$fU,$avp(FromNum))){ > send_reply(404,"Bad From User"); > exit; > } else { > return; > } > } > When Opensips run as systemd service It restarts and core was not > generated. > > > > вт, 25 июн. 2019 г. в 18:06, Bogdan-Andrei Iancu >: > > Hi Kirill, > > Does your opensips predictably crashes each time you do the routes > reload ? if yes, do you get each time an invalid corefile ? > > Best regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/25/2019 11:47 AM, Kirill Galinurov wrote: >> One more information >> I run opensips in debug mode with command: >> opensips -f /etc/opensips/opensips.cfg.j2 -p "python3 >> /etc/opensips/opensips-preproc.py" a Q_MALLOC_DBG -m 16832 -M 512 >> >> After opensips-cli -x mi reload_routes >> ERROR: communication exception for 'reload_routes' returned: >> ERROR: Is OpenSIPS running? >> >> Logs: >> >> Jun 25 04:37:33 [21481] DBG:core:fix_actions: fixing >> t_was_cancelled, /etc/opensips/opensips_routes.cfg:346 >> Jun 25 04:37:33 [21481] INFO:core:routes_reload_per_proc: process >> successfully parsed new cfg (seq 1) >> Jun 25 04:37:55 [21460] DBG:core:reload_routing_script: done with >> waiting after 20001 miliseconds >> Jun 25 04:38:13 [21457] DBG:core:handle_sigs: unknown child >> process 21458 ended. Ignoring >> Jun 25 04:38:13 [21457] DBG:core:handle_sigs: OpenSIPS exit >> status = 139 >> Jun 25 04:38:13 [21457] INFO:core:handle_sigs: child process >> 21463 exited by a signal 11 >> Jun 25 04:38:13 [21457] INFO:core:handle_sigs: core was generated >> Jun 25 04:38:13 [21457] INFO:core:handle_sigs: terminating due to >> SIGCHLD >> >> (gdb) bt full: >> #0 0x00000000004652b0 in ?? () >> No symbol table info available. >> #1 0x0000000000000044 in ?? () >> No symbol table info available. >> #2 0x000053d70577fc74 in ?? () >> No symbol table info available. >> #3 0x0000000000000000 in ?? () >> No symbol table info available. >> >> >> >> _______________________________________________ >> 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 k.galinurov at gmail.com Tue Jun 25 11:48:18 2019 From: k.galinurov at gmail.com (Kirill Galinurov) Date: Tue, 25 Jun 2019 18:48:18 +0300 Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi reload_routes In-Reply-To: References: <3cfae2bb-9271-4582-9bea-a77d3c74b4c0@opensips.org> Message-ID: It's crashes exactly when reloading It's my test instance with no traffic at all yet. I rewrite my old 2.4 config to new syntax I paste block of code. Then change it. And it's crash. But if I restart opensips everything looks OK. вт, 25 июн. 2019 г. в 18:36, Bogdan-Andrei Iancu : > Do you have any idea if OpenSIPS crashes exactly when reloading or does it > crash when handling traffic after the reload ? Again, any chances to get a > valid backtrace ? > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/25/2019 06:28 PM, Kirill Galinurov wrote: > > Hi Bogan, > Yes my opensips predictably crashes, when I do routes reload. Even when I > do not change anythihg. But I think.. It' s probably crashes when I use > return statement like: > if (is_method("INVITE")) { > route(get_account_code); > route(check_callerid); > route(number_normalize); > } > > route[check_callerid]{ > xlog("L_INFO","Check callerid to path for operators\n"); > if(! dp_translate(999,$fU,$avp(FromNum))){ > send_reply(404,"Bad From User"); > exit; > } else { > return; > } > } > When Opensips run as systemd service It restarts and core was not > generated. > > > > вт, 25 июн. 2019 г. в 18:06, Bogdan-Andrei Iancu : > >> Hi Kirill, >> >> Does your opensips predictably crashes each time you do the routes reload >> ? if yes, do you get each time an invalid corefile ? >> >> Best regards, >> >> Bogdan-Andrei Iancu >> >> OpenSIPS Founder and Developer >> https://www.opensips-solutions.com >> OpenSIPS Summit 2019 >> https://www.opensips.org/events/Summit-2019Amsterdam/ >> >> On 06/25/2019 11:47 AM, Kirill Galinurov wrote: >> >> One more information >> I run opensips in debug mode with command: >> opensips -f /etc/opensips/opensips.cfg.j2 -p "python3 >> /etc/opensips/opensips-preproc.py" a Q_MALLOC_DBG -m 16832 -M 512 >> >> After opensips-cli -x mi reload_routes >> ERROR: communication exception for 'reload_routes' returned: >> ERROR: Is OpenSIPS running? >> >> Logs: >> >> Jun 25 04:37:33 [21481] DBG:core:fix_actions: fixing t_was_cancelled, >> /etc/opensips/opensips_routes.cfg:346 >> Jun 25 04:37:33 [21481] INFO:core:routes_reload_per_proc: process >> successfully parsed new cfg (seq 1) >> Jun 25 04:37:55 [21460] DBG:core:reload_routing_script: done with waiting >> after 20001 miliseconds >> Jun 25 04:38:13 [21457] DBG:core:handle_sigs: unknown child process 21458 >> ended. Ignoring >> Jun 25 04:38:13 [21457] DBG:core:handle_sigs: OpenSIPS exit status = 139 >> Jun 25 04:38:13 [21457] INFO:core:handle_sigs: child process 21463 >> exited by a signal 11 >> Jun 25 04:38:13 [21457] INFO:core:handle_sigs: core was generated >> Jun 25 04:38:13 [21457] INFO:core:handle_sigs: terminating due to SIGCHLD >> >> (gdb) bt full: >> #0 0x00000000004652b0 in ?? () >> No symbol table info available. >> #1 0x0000000000000044 in ?? () >> No symbol table info available. >> #2 0x000053d70577fc74 in ?? () >> No symbol table info available. >> #3 0x0000000000000000 in ?? () >> No symbol table info available. >> >> >> >> _______________________________________________ >> 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 Jun 25 11:57:01 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 25 Jun 2019 18:57:01 +0300 Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi reload_routes In-Reply-To: References: <3cfae2bb-9271-4582-9bea-a77d3c74b4c0@opensips.org> Message-ID: <94261deb-6d55-4d33-02e0-761ce7ee3882@opensips.org> OK, I see. And again, any useful backtrace during the crashes ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/25/2019 06:48 PM, Kirill Galinurov wrote: > It's crashes exactly when reloading It's my test instance with no > traffic at all yet. I rewrite my old 2.4 config to new syntax I paste > block of code. Then change it. And it's crash. But if I restart > opensips everything looks OK. > > вт, 25 июн. 2019 г. в 18:36, Bogdan-Andrei Iancu >: > > Do you have any idea if OpenSIPS crashes exactly when reloading or > does it crash when handling traffic after the reload ? Again, any > chances to get a valid backtrace ? > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/25/2019 06:28 PM, Kirill Galinurov wrote: >> Hi Bogan, >> Yes my opensips predictably crashes, when I do routes >> reload. Even when I do not change anythihg. But I think.. It' s >> probably crashes when I use >> return statement like: >> if (is_method("INVITE")) { >> route(get_account_code); >> route(check_callerid); >> route(number_normalize); >> } >> >> route[check_callerid]{ >> xlog("L_INFO","Check callerid to path for operators\n"); >> if(! dp_translate(999,$fU,$avp(FromNum))){ >> send_reply(404,"Bad From User"); >> exit; >> } else { >> return; >> } >> } >> When Opensips run as systemd service It restarts and core was not >> generated. >> >> >> >> вт, 25 июн. 2019 г. в 18:06, Bogdan-Andrei Iancu >> >: >> >> Hi Kirill, >> >> Does your opensips predictably crashes each time you do the >> routes reload ? if yes, do you get each time an invalid >> corefile ? >> >> Best regards, >> >> Bogdan-Andrei Iancu >> >> OpenSIPS Founder and Developer >> https://www.opensips-solutions.com >> OpenSIPS Summit 2019 >> https://www.opensips.org/events/Summit-2019Amsterdam/ >> >> On 06/25/2019 11:47 AM, Kirill Galinurov wrote: >>> One more information >>> I run opensips in debug mode with command: >>> opensips -f /etc/opensips/opensips.cfg.j2 -p "python3 >>> /etc/opensips/opensips-preproc.py" a Q_MALLOC_DBG -m 16832 >>> -M 512 >>> >>> After opensips-cli -x mi reload_routes >>> ERROR: communication exception for 'reload_routes' returned: >>> ERROR: Is OpenSIPS running? >>> >>> Logs: >>> >>> Jun 25 04:37:33 [21481] DBG:core:fix_actions: fixing >>> t_was_cancelled, /etc/opensips/opensips_routes.cfg:346 >>> Jun 25 04:37:33 [21481] INFO:core:routes_reload_per_proc: >>> process successfully parsed new cfg (seq 1) >>> Jun 25 04:37:55 [21460] DBG:core:reload_routing_script: done >>> with waiting after 20001 miliseconds >>> Jun 25 04:38:13 [21457] DBG:core:handle_sigs: unknown child >>> process 21458 ended. Ignoring >>> Jun 25 04:38:13 [21457] DBG:core:handle_sigs: OpenSIPS exit >>> status = 139 >>> Jun 25 04:38:13 [21457] INFO:core:handle_sigs: child process >>> 21463 exited by a signal 11 >>> Jun 25 04:38:13 [21457] INFO:core:handle_sigs: core was >>> generated >>> Jun 25 04:38:13 [21457] INFO:core:handle_sigs: terminating >>> due to SIGCHLD >>> >>> (gdb) bt full: >>> #0 0x00000000004652b0 in ?? () >>> No symbol table info available. >>> #1 0x0000000000000044 in ?? () >>> No symbol table info available. >>> #2 0x000053d70577fc74 in ?? () >>> No symbol table info available. >>> #3 0x0000000000000000 in ?? () >>> No symbol table info available. >>> >>> >>> >>> _______________________________________________ >>> 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 johan at democon.be Wed Jun 19 11:51:08 2019 From: johan at democon.be (johan de clercq) Date: Wed, 19 Jun 2019 17:51:08 +0200 Subject: [OpenSIPS-Users] segfault in opensips30 In-Reply-To: <65999241-c5fd-c57f-a740-b285eccd1c7b@opensips.org> References: <00c901d526ae$b05170f0$10f452d0$@democon.be> <00e001d526b1$52e8c0f0$f8ba42d0$@democon.be> <00f801d526b5$7dd11c50$797354f0$@democon.be> <65999241-c5fd-c57f-a740-b285eccd1c7b@opensips.org> Message-ID: <011401d526b6$cfc400d0$6f4c0270$@democon.be> Please find the output attached. From: Bogdan-Andrei Iancu Sent: Wednesday, June 19, 2019 5:43 PM To: johan de clercq ; 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] segfault in opensips30 Do "gdb /path/to/opensips /path/to/corefile" Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/19/2019 06:41 PM, johan de clercq wrote: Bogdan, see below output : what am I doing wrong ? root at hendrix:/tmp# gdb /tmp/core GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Copyright (C) 2016 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-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: . Find the GDB manual and other documentation resources online at: . For help, type "help". Type "apropos word" to search for commands related to "word"... "/tmp/core": not in executable format: File format not recognized From: Bogdan-Andrei Iancu Sent: Wednesday, June 19, 2019 5:25 PM To: OpenSIPS users mailling list ; johan de clercq Subject: Re: [OpenSIPS-Users] segfault in opensips30 Hi Johan, Can you extract the full backtrace from the core file ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/19/2019 06:11 PM, johan de clercq wrote: un 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:db_mysql:db_mysql_get_columns: use DB_STRING result type Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:db_mysql:db_mysql_convert_rows: no rows returned from the query Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:usrloc:db_load_urecord: aor 32478720105 not found in table location Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_columns: freeing result columns at 0x7f0d8fa8c7f8 Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_rows: freeing 0 rows Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:core:db_free_result: freeing result set at 0x7f0d8fa8b320 Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: DBG:registrar:_remove: no record '32478720105' found! Jun 19 15:07:16 hendrix /data/opensips/sbin/opensips[31541]: CRITICAL:core:sig_usr: segfault in process pid: 31541, id: 5 From: johan de clercq Sent: Wednesday, June 19, 2019 4:53 PM To: 'OpenSIPS users mailling list' Subject: segfault in opensips30 When trying to register an unknown user, I have a segfault. I can easily reproduce, so please tell me what I need to do to give you a dump. Johan De Clercq, Managing Director Democon bvba - Ooigemstraat 41 - 8780 Oostrozebeke Tel +3256980990 - GSM +32478720104 _______________________________________________ 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: image001.png Type: image/png Size: 15602 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: crashdump.zip Type: application/x-zip-compressed Size: 5459 bytes Desc: not available URL: From Ben.Newlin at genesys.com Tue Jun 25 11:41:04 2019 From: Ben.Newlin at genesys.com (Ben Newlin) Date: Tue, 25 Jun 2019 15:41:04 +0000 Subject: [OpenSIPS-Users] Rest Client Async operation In-Reply-To: <20e603cc-3bd3-c31a-b9d9-fd0c7e3e5542@opensips.org> References: <6ED95883-2E26-477B-A8DF-6F6C130093AF@genesys.com> <20e603cc-3bd3-c31a-b9d9-fd0c7e3e5542@opensips.org> Message-ID: <4D9686A3-C7F3-4316-B9AF-C938797D6D78@genesys.com> Liviu, Thank you for the response and explanation, and for investigating the timing discrepancies. I must say though that this answer is very disappointing. We are not transferring large files or data sets during realtime call processing (I hope no one is!), so the transfer time is not really a concern; it is the connect time that can cause severe backlogs when the far end is not available, as in my test case. So as it stands the async functionality for rest_client is mostly useless to us as it doesn’t prevent the most common cause of congestion. I can appreciate that libcurl does not provide access during the connect, but I guess my question would be why isn’t the entire operation run in async? Why must the connect be performed in the current process and only the transfer be in another process? My expectation when using any async function was that all execution of the underlying function called would be performed in a separate process, not that the function could pick and choose which parts would block and which would not. Are other async function implementations similar to this? For example, does an async_db_query establish the DB connection in the current thread in blocking mode and only perform the actual query as async? I would also recommend updating the documentation for both async and rest_client specifically to make this limitation clear, as it was not at all clear to us. Ben Newlin From: Users on behalf of Liviu Chircu Reply-To: OpenSIPS users mailling list Date: Tuesday, June 25, 2019 at 8:52 AM To: "users at lists.opensips.org" Subject: Re: [OpenSIPS-Users] Rest Client Async operation Hi Ben, Regarding the "blocking rest_get()" problem: due to the specifics of the libcurl API, there is no direct access to the socket file descriptors during the initial TCP connect handshake. Thus, this phase will be synchronous (blocking), while all transfers (send HTTP req, receive reply) are done asynchronously, regardless of how the data gets send or arrives (all at once, in chunks, byte-by-byte, etc.). So, indeed: on the specific test case that the remote TCP endpoint is either unresponsive or it is blocked by a firewall, the throughput of your OpenSIPS may be significantly affected when talking HTTP to such peers even if you perform async HTTP requests. Maybe this is just my opinion, but I believe that the average case is when the HTTP server/API is down and the TCP connect attempt will get rejected. See [1] for more on this topic. Regarding the 5s vs. 8s timeouts, I will have to confirm the behavior first and get back to you. Async is heavily reliant on tm, so I wouldn't exclude the possibility that the transaction timeout overrides, in some cases, the async logic's timeout. Best regards, [1]: https://serverfault.com/questions/521359/why-do-some-connections-time-out-and-others-get-refused Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 25.06.2019 00:33, Ben Newlin wrote: Hello all, During testing I have found behavior that I cannot explain based on our current understanding of the operation of the async and rest_client functionality. I have reproduced this behavior with a fairly simple script configuration, the relevant piece of which is below: children=8 loadmodule "rest_client.so" modparam("rest_client", "connection_timeout", 5) modparam("rest_client", "connect_poll_interval", 1) modparam("rest_client", "curl_timeout", 5) route { xlog("L_ALERT", "before t_newtran()\r\n"); t_newtran(); xlog("L_ALERT", "after t_newtran()\r\n"); async(rest_post("http://0.0.0.0", "{}", "application/json", "$var(body)", "$var(ctype)", "$var(rcode)"), test_resume); xlog("L_ALERT", "after async\r\n"); } route[test_resume] { xlog("L_ALERT", "test_resume: $retcode\r\n"); t_reply("503", "Service Unavailable"); } The expected operation is to immediately trigger t_newtran() which sends a 100 response, then timeout on the rest_post call in 5 seconds and respond with a 503. For individual calls this does occur, although the timeout consistently takes several seconds too long, usually ~8s, as can be seen in the logs from the above code: Jun 24 19:10:56 [337] before t_newtran() Jun 24 19:10:56 [337] after t_newtran() Jun 24 19:11:04 [337] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 19:11:04 [337] test_resume: -2 The extra time is troubling, but the bigger concern is that when I run multiple concurrent calls, I find that the 8 UDP children are still all blocking against the rest_post call. Here are the logs for that test: Jun 24 21:19:51 [337] before t_newtran() Jun 24 21:19:51 [337] after t_newtran() Jun 24 21:19:51 [338] before t_newtran() Jun 24 21:19:51 [338] after t_newtran() Jun 24 21:19:51 [335] before t_newtran() Jun 24 21:19:51 [335] after t_newtran() Jun 24 21:19:51 [333] before t_newtran() Jun 24 21:19:51 [333] after t_newtran() Jun 24 21:19:52 [331] before t_newtran() Jun 24 21:19:52 [331] after t_newtran() Jun 24 21:19:52 [336] before t_newtran() Jun 24 21:19:52 [336] after t_newtran() Jun 24 21:19:52 [332] before t_newtran() Jun 24 21:19:52 [332] after t_newtran() Jun 24 21:19:52 [334] before t_newtran() Jun 24 21:19:52 [334] after t_newtran() Jun 24 21:19:59 [337] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:19:59 [337] test_resume: -2 Jun 24 21:19:59 [337] before t_newtran() Jun 24 21:19:59 [337] after t_newtran() Jun 24 21:19:59 [338] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:19:59 [338] test_resume: -2 Jun 24 21:19:59 [338] before t_newtran() Jun 24 21:19:59 [338] after t_newtran() Jun 24 21:19:59 [335] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:19:59 [335] test_resume: -2 Jun 24 21:19:59 [335] before t_newtran() Jun 24 21:19:59 [335] after t_newtran() Jun 24 21:19:59 [333] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:19:59 [333] test_resume: -2 Jun 24 21:19:59 [333] before t_newtran() Jun 24 21:19:59 [333] after t_newtran() Jun 24 21:19:59 [331] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:19:59 [331] test_resume: -2 Jun 24 21:19:59 [331] before t_newtran() Jun 24 21:19:59 [331] after t_newtran() Jun 24 21:19:59 [336] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:19:59 [336] test_resume: -2 Jun 24 21:19:59 [336] before t_newtran() Jun 24 21:19:59 [336] after t_newtran() Jun 24 21:19:59 [332] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:19:59 [332] test_resume: -2 Jun 24 21:19:59 [332] before t_newtran() Jun 24 21:19:59 [332] after t_newtran() Jun 24 21:20:00 [334] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:00 [334] test_resume: -2 Jun 24 21:20:00 [334] before t_newtran() Jun 24 21:20:00 [334] after t_newtran() Jun 24 21:20:07 [337] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [337] test_resume: -2 Jun 24 21:20:07 [338] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [338] test_resume: -2 Jun 24 21:20:07 [335] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [335] test_resume: -2 Jun 24 21:20:07 [333] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [333] test_resume: -2 Jun 24 21:20:07 [331] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [331] test_resume: -2 Jun 24 21:20:07 [336] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [336] test_resume: -2 Jun 24 21:20:07 [332] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [332] test_resume: -2 Jun 24 21:20:07 [334] ERROR:rest_client:start_async_http_req: connect timeout on http://0.0.0.0 (5s) Jun 24 21:20:07 [334] test_resume: -2 You can clearly see that the first 8 Invites are processed immediately, but then no new messages are processed until the rest queries begin to timeout. As each query times out, freeing a child process, a new inbound request is processed. Clearly the message processing is being blocked on the rest queries, which is not supposed to happen when using async. Am I missing something in my configuration or am I not understanding how async is supposed to work somehow? Ben Newlin _______________________________________________ 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 k.galinurov at gmail.com Tue Jun 25 12:10:02 2019 From: k.galinurov at gmail.com (Kirill Galinurov) Date: Tue, 25 Jun 2019 19:10:02 +0300 Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi reload_routes In-Reply-To: <94261deb-6d55-4d33-02e0-761ce7ee3882@opensips.org> References: <3cfae2bb-9271-4582-9bea-a77d3c74b4c0@opensips.org> <94261deb-6d55-4d33-02e0-761ce7ee3882@opensips.org> Message-ID: I am very sorry Bogdan. But I have no any useful information for you. I can try to rewrite my config step by step... > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jun 25 12:11:24 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 25 Jun 2019 19:11:24 +0300 Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi reload_routes In-Reply-To: References: <3cfae2bb-9271-4582-9bea-a77d3c74b4c0@opensips.org> <94261deb-6d55-4d33-02e0-761ce7ee3882@opensips.org> Message-ID: Kirill, Could you share (off-list, privately) your script with me to see if I can reproduce the crash ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/25/2019 07:10 PM, Kirill Galinurov wrote: > I am very sorry Bogdan. But I have no any useful information for you. > I can try to rewrite my config step by step... > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From podguiko at mail.ru Tue Jun 25 12:13:17 2019 From: podguiko at mail.ru (=?UTF-8?B?0J7Qu9C10LMg0J/QvtC00LPRg9C50LrQvg==?=) Date: Tue, 25 Jun 2019 19:13:17 +0300 Subject: [OpenSIPS-Users] =?utf-8?q?Users_Digest=2C_Vol_131=2C_Issue_58?= In-Reply-To: References: Message-ID: <1561479197.180807484@f405.i.mail.ru> Hey Liviu, Thank you for information. Could you explaiin what does it means " run_reqin_callbacks" at the debug log. It looks like  Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: MIME part from INVITE was delete Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:t_newtran: transaction on entrance=(nil) Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_headers: flags=ffffffffffffffff Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:core:parse_headers: flags=78 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:t_lookup_request: start searching: hash=25168, isACK=0 Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:matching_3261: RFC3261 transaction matching failed Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:t_lookup_request: no transaction found Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:run_reqin_callbacks: trans=0x7fd9e490a6a0, callback type 1, id 0 entered Does this function has any relation to statefull mode of opensips? >Понедельник, 24 июня 2019, 19:00 +03:00 от users-request at lists.opensips.org: > >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. Opensips 3.0 segfault on opensips-cli -x mi reload_routes >      (Kirill Galinurov) >   2. Re: Understanding statefuli proxy mode opensips. (Liviu Chircu) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Mon, 24 Jun 2019 09:58:19 +0300 >From: Kirill Galinurov < k.galinurov at gmail.com > >To: OpenSIPS users mailling list < users at lists.opensips.org > >Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi >reload_routes >Message-ID: >< CAPDUut-ohr4kybnH7qkhY1O8Z002ZrfobiOX7JybA_RJWYWCVg at mail.gmail.com > >Content-Type: text/plain; charset="utf-8" > >Hi all. Latest opensips from night build. >I try command - opensips-cli -x mi reload_routes >And get errors:: > INFO:core:routes_reload_per_proc: dropping reload cmd due out of sequence >reason >Jun 24 02:53:14 callout-msk /usr/sbin/opensips[14198]: >CRITICAL:core:sig_usr: segfault in process pid: 14198, id: 5 >Jun 24 02:53:14 callout-msk kernel: opensips[14198]: segfault at 1 ip >00000000004652b0 sp 00007ffd7cf54050 error 4 in opensips[400000+1 >f1000] >Jun 24 02:53:15 callout-msk /usr/sbin/opensips[14193]: >INFO:core:handle_sigs: child process 14198 exited by a signal 11 >Jun 24 02:53:15 callout-msk /usr/sbin/opensips[14193]: >INFO:core:handle_sigs: core was not generated >Jun 24 02:53:15 callout-msk /usr/sbin/opensips[14193]: >INFO:core:handle_sigs: terminating due to SIGCHLD >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: < http://lists.opensips.org/pipermail/users/attachments/20190624/54891b0f/attachment-0001.html > > >------------------------------ > >Message: 2 >Date: Mon, 24 Jun 2019 18:04:29 +0300 >From: Liviu Chircu < liviu at opensips.org > >To: OpenSIPS users mailling list < users at lists.opensips.org > >Subject: Re: [OpenSIPS-Users] Understanding statefuli proxy mode >opensips. >Message-ID: < 013fa54d-2eed-11d0-e1ea-e8af750d7fc3 at opensips.org > >Content-Type: text/plain; charset="utf-8"; Format="flowed" > >Hey Oleg, > >When processing a SIP request, you can create the SIP transaction (go >stateful) >using either t_newtran() [1] or t_relay() [2].  Replies will be >automatically >intercepted, matched and handled afterwards.  To obtain script-level >access to >them, you must install a t_on_reply() [3] route callback. > >Regards, > >[1]: https://opensips.org/html/docs/modules/3.0.x/tm.html#func_t_newtran >[2]: https://opensips.org/html/docs/modules/3.0.x/tm.html#func_t_relay >[3]: https://opensips.org/html/docs/modules/3.0.x/tm.html#func_t_on_reply >< https://opensips.org/html/docs/modules/3.0.x/tm.html#func_t_relay > > >Liviu Chircu >OpenSIPS Developer >http://www.opensips-solutions.com > >On 23.06.2019 12:13, Олег Подгуйко via Users wrote: >> How to make opensips when accepting INVITE immediately start working >> as a statefull proxy? >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: < http://lists.opensips.org/pipermail/users/attachments/20190624/92402913/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 131, Issue 58 >************************************** -- Олег Подгуйко -------------- next part -------------- An HTML attachment was scrubbed... URL: From liviu at opensips.org Tue Jun 25 12:18:58 2019 From: liviu at opensips.org (Liviu Chircu) Date: Tue, 25 Jun 2019 19:18:58 +0300 Subject: [OpenSIPS-Users] Users Digest, Vol 131, Issue 58 In-Reply-To: <1561479197.180807484@f405.i.mail.ru> References: <1561479197.180807484@f405.i.mail.ru> Message-ID: <6bda59de-425b-1c60-6a88-65e54094b10b@opensips.org> Yes it has, since it means: we've gone stateful, a transaction is being created, let's announce this to any modules which have subscribed to this creation event. Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 25.06.2019 19:13, Олег Подгуйко via Users wrote: > Hey Liviu, > > Thank you for information. > > Could you explaiin what does it means "run_reqin_callbacks" at the > debug log. It looks like > > Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: MIME part from > INVITE was delete > Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: DBG:tm:t_newtran: > transaction on entrance=(nil) > Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: > DBG:core:parse_headers: flags=ffffffffffffffff > Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: > DBG:core:parse_headers: flags=78 > Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: > DBG:tm:t_lookup_request: start searching: hash=25168, isACK=0 > Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: > DBG:tm:matching_3261: RFC3261 transaction matching failed > Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: > DBG:tm:t_lookup_request: no transaction found > > *Jun 23 07:05:55 xx-xxx-1 /usr/sbin/opensips[18398]: > DBG:tm:run_reqin_callbacks: trans=0x7fd9e490a6a0, callback type 1, id > 0 entered* > > > Does this function has any relation to statefull mode of opensips? > > Понедельник, 24 июня 2019, 19:00 +03:00 от > users-request at lists.opensips.org: > > 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. Opensips 3.0 segfault on opensips-cli -x mi reload_routes >       (Kirill Galinurov) >    2. Re: Understanding statefuli proxy mode opensips. (Liviu Chircu) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 24 Jun 2019 09:58:19 +0300 > From: Kirill Galinurov > > To: OpenSIPS users mailling list > > Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi > reload_routes > Message-ID: > > > Content-Type: text/plain; charset="utf-8" > > Hi all. Latest opensips from night build. > I try command - opensips-cli -x mi reload_routes > And get errors:: >  INFO:core:routes_reload_per_proc: dropping reload cmd due out of > sequence > reason > Jun 24 02:53:14 callout-msk /usr/sbin/opensips[14198]: > CRITICAL:core:sig_usr: segfault in process pid: 14198, id: 5 > Jun 24 02:53:14 callout-msk kernel: opensips[14198]: segfault at 1 ip > 00000000004652b0 sp 00007ffd7cf54050 error 4 in opensips[400000+1 > f1000] > Jun 24 02:53:15 callout-msk /usr/sbin/opensips[14193]: > INFO:core:handle_sigs: child process 14198 exited by a signal 11 > Jun 24 02:53:15 callout-msk /usr/sbin/opensips[14193]: > INFO:core:handle_sigs: core was not generated > Jun 24 02:53:15 callout-msk /usr/sbin/opensips[14193]: > INFO:core:handle_sigs: terminating due to SIGCHLD > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > > ------------------------------ > > Message: 2 > Date: Mon, 24 Jun 2019 18:04:29 +0300 > From: Liviu Chircu > > To: OpenSIPS users mailling list > > Subject: Re: [OpenSIPS-Users] Understanding statefuli proxy mode > opensips. > Message-ID: <013fa54d-2eed-11d0-e1ea-e8af750d7fc3 at opensips.org > > > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hey Oleg, > > When processing a SIP request, you can create the SIP transaction (go > stateful) > using either t_newtran() [1] or t_relay() [2].  Replies will be > automatically > intercepted, matched and handled afterwards.  To obtain script-level > access to > them, you must install a t_on_reply() [3] route callback. > > Regards, > > [1]: > https://opensips.org/html/docs/modules/3.0.x/tm.html#func_t_newtran > [2]: https://opensips.org/html/docs/modules/3.0.x/tm.html#func_t_relay > [3]: > https://opensips.org/html/docs/modules/3.0.x/tm.html#func_t_on_reply > > > Liviu Chircu > OpenSIPS Developer > http://www.opensips-solutions.com > > On 23.06.2019 12:13, Олег Подгуйко via Users wrote: > > How to make opensips when accepting INVITE immediately start > working > > as a statefull proxy? > -------------- 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 131, Issue 58 > ************************************** > > > > -- > Олег Подгуйко > > _______________________________________________ > 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 k.galinurov at gmail.com Tue Jun 25 12:30:31 2019 From: k.galinurov at gmail.com (Kirill Galinurov) Date: Tue, 25 Jun 2019 19:30:31 +0300 Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi reload_routes In-Reply-To: References: <3cfae2bb-9271-4582-9bea-a77d3c74b4c0@opensips.org> <94261deb-6d55-4d33-02e0-761ce7ee3882@opensips.org> Message-ID: Bogdan I am very stupped... I am sorry... But I am found problem... I use uac_replace_from("$avp(fU)","sip:$avp(fU)@{{anycast_ip}}"); To template my config. And when I comment this line all became good. I guess ... I should not use templating in routes... вт, 25 июн. 2019 г. в 19:11, Bogdan-Andrei Iancu : > Kirill, > > Could you share (off-list, privately) your script with me to see if I can > reproduce the crash ? > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/25/2019 07:10 PM, Kirill Galinurov wrote: > > I am very sorry Bogdan. But I have no any useful information for you. I > can try to rewrite my config step by step... > > >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Tue Jun 25 12:32:50 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Tue, 25 Jun 2019 19:32:50 +0300 Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi reload_routes In-Reply-To: References: <3cfae2bb-9271-4582-9bea-a77d3c74b4c0@opensips.org> <94261deb-6d55-4d33-02e0-761ce7ee3882@opensips.org> Message-ID: Still, whatever syntax (with errors) you have in the cfg, the reload should not crash :(... my offer of trying to reproduce it with your script is still available. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/25/2019 07:30 PM, Kirill Galinurov wrote: > Bogdan I am very stupped... I am sorry... But I am found problem... > I use uac_replace_from("$avp(fU)","sip:$avp(fU)@{{anycast_ip}}"); > To template my config. > And when I comment this line all became good. > I guess ... I should not use templating in routes... > > вт, 25 июн. 2019 г. в 19:11, Bogdan-Andrei Iancu >: > > Kirill, > > Could you share (off-list, privately) your script with me to see > if I can reproduce the crash ? > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/25/2019 07:10 PM, Kirill Galinurov wrote: >> I am very sorry Bogdan. But I have no any useful information for >> you. I can try to rewrite my config step by step... >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alain.bieuzent at free.fr Wed Jun 26 03:18:26 2019 From: alain.bieuzent at free.fr (Alain Bieuzent) Date: Wed, 26 Jun 2019 09:18:26 +0200 Subject: [OpenSIPS-Users] Number of Children's vs number of cores Message-ID: <373BE854-B28B-4635-93C7-F185B5CF7031@free.fr> Hi all, I’m using an opensips 2.4 with only dispatcher module. This server handle around 800 CPAS for 16 000 simultaneous calls. We run it under VMWARE/Debian with 4 cores and 8 children’s and we have a pic of CPU load to 0,8. I will upgrade this VM to six cores, but what about number of children’s, do you have a rules to determine the number of children or there is  no link with number of core ? Thanks Alain -------------- next part -------------- An HTML attachment was scrubbed... URL: From efelin.novak at gmail.com Wed Jun 26 08:11:38 2019 From: efelin.novak at gmail.com (Efelin Novak) Date: Wed, 26 Jun 2019 14:11:38 +0200 Subject: [OpenSIPS-Users] Call_control and JSON-RPC Message-ID: Hi, I'm using a Kamailio version that does not support MI interface anymore. Call_control module works nice in all situations expect when it wants to kill the call (credit is gone). Is the Call_control module capable of using JSON-RPC instead of MI command? When I change class ManagementInterface() so that the RPC command is not sent and I only call os.system(command to kill a call using JSON-RPC), I get a Error messages like this: kamailio[19687]: ERROR: call_control [call_control.c:839]: send_command(): did timeout waiting for an answer The call is killed but I'm afraid that such error might cause errors in future (e.g.: memory leaking). Is there any workaround? Is it possible the call_control ends the call in a different way than MI interface? Can I use os.system hack? Can I ignore these errors or I can get rid of them somehow? Kind regards Kamailio and Call-control are at newest version. Efelin -------------- next part -------------- An HTML attachment was scrubbed... URL: From Johan at democon.be Wed Jun 26 08:17:15 2019 From: Johan at democon.be (Johan De Clercq) Date: Wed, 26 Jun 2019 14:17:15 +0200 Subject: [OpenSIPS-Users] Call_control and JSON-RPC In-Reply-To: References: Message-ID: I think that you posted on the wrong list On Wed, 26 Jun 2019, 14:14 Efelin Novak, wrote: > Hi, > > I'm using a Kamailio version that does not support MI interface anymore. > Call_control module works nice in all situations expect when it wants to > kill the call (credit is gone). Is the Call_control module capable of using > JSON-RPC instead of MI command? > > When I change class ManagementInterface() so that the RPC command is not > sent and I only call os.system(command to kill a call using JSON-RPC), I > get a Error messages like this: > > kamailio[19687]: ERROR: call_control [call_control.c:839]: send_command(): > did timeout waiting for an answer > > The call is killed but I'm afraid that such error might cause errors in > future (e.g.: memory leaking). > > Is there any workaround? > Is it possible the call_control ends the call in a different way than MI > interface? > Can I use os.system hack? Can I ignore these errors or I can get rid of > them somehow? > > Kind regards > > Kamailio and Call-control are at newest version. > > Efelin > _______________________________________________ > 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 Jun 26 09:06:55 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 26 Jun 2019 16:06:55 +0300 Subject: [OpenSIPS-Users] Call_control and JSON-RPC In-Reply-To: References: Message-ID: Just use OpenSIPS and you will be fine :) Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/26/2019 03:11 PM, Efelin Novak wrote: > Hi, > > I'm using a Kamailio version that does not support MI interface > anymore. Call_control module works nice in all situations expect when > it wants to kill the call (credit is gone). Is the Call_control module > capable of using JSON-RPC instead of MI command? > > When I change class ManagementInterface() so that the RPC command is > not sent and I only call os.system(command to kill a call using > JSON-RPC), I get a Error messages like this: > > kamailio[19687]: ERROR: call_control [call_control.c:839]: > send_command(): did timeout waiting for an answer > > The call is killed but I'm afraid that such error might cause errors > in future (e.g.: memory leaking). > > Is there any workaround? > Is it possible the call_control ends the call in a different way than > MI interface? > Can I use os.system hack? Can I ignore these errors or I can get rid > of them somehow? > > Kind regards > > Kamailio and Call-control are at newest version. > > Efelin > > > _______________________________________________ > 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 Jun 26 09:09:00 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 26 Jun 2019 16:09:00 +0300 Subject: [OpenSIPS-Users] Number of Children's vs number of cores In-Reply-To: <373BE854-B28B-4635-93C7-F185B5CF7031@free.fr> References: <373BE854-B28B-4635-93C7-F185B5CF7031@free.fr> Message-ID: <08feebda-dd41-974e-0e51-f1e2204b11c6@opensips.org> Hi Alain, Monitor the internal load of OpenSIPS (via load: class statistics) and see if you really need to add more processes. If you your processing is mostly CPU intensive (no DB, no DNS or other I/Os) and you want to take full advantage of all your CPU resources (if you need them) maybe a x1.5 or x2 factor (between cores and procs) will do it. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/26/2019 10:18 AM, Alain Bieuzent wrote: > > Hi all, > > I’m using an opensips 2.4 with only dispatcher module. > > This server handle around 800 CPAS for 16 000 simultaneous calls. > > We run it under VMWARE/Debian with 4 cores and 8 children’s and we > have a pic of CPU load to 0,8. > > I will upgrade this VM to six cores, but what about number of > children’s, do you have a rules to determine the number of children or > there is no link with number of core ? > > Thanks > > 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 liviu at opensips.org Wed Jun 26 09:21:23 2019 From: liviu at opensips.org (Liviu Chircu) Date: Wed, 26 Jun 2019 16:21:23 +0300 Subject: [OpenSIPS-Users] Rest Client Async operation In-Reply-To: <4D9686A3-C7F3-4316-B9AF-C938797D6D78@genesys.com> References: <6ED95883-2E26-477B-A8DF-6F6C130093AF@genesys.com> <20e603cc-3bd3-c31a-b9d9-fd0c7e3e5542@opensips.org> <4D9686A3-C7F3-4316-B9AF-C938797D6D78@genesys.com> Message-ID: <927a8096-c4a8-7a42-b366-a587cfa73e7a@opensips.org> It's the same process doing both the connect and the transfer.  The problem is that libcurl, as it stands now, is not able to give me a file descriptor to poll on, until it connects [1].  See this section: "When libcurl returns -1 in max_fd, it is because libcurl currently does something that isn't possible for your application to monitor with a socket and unfortunately you can then not know exactly when the current action is completed using select(). You then need to wait a while before you proceed and call curl_multi_perform anyway. How long to wait? Unless curl_multi_timeout gives you a lower number, we suggest 100 milliseconds or so, but you may want to test it out in your own particular conditions to find a suitable value." Regarding your issue: I would investigate further the reason why the connect is hanging, and not getting rejected immediately when your server is down.  That would solve all your blocking issues. The same with MySQL connections which go down: only after the connection is up are we able to obtain its file descriptor to asynchronously poll on.  So if connect to DB_HOST:3306 hangs, so will OpenSIPS. Regards, [1]: https://curl.haxx.se/libcurl/c/curl_multi_fdset.html Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 25.06.2019 18:41, Ben Newlin wrote: > but I guess my question would be why isn’t the entire operation run in > async? Why must the connect be performed in the current process and > only the transfer be in another process? -------------- next part -------------- An HTML attachment was scrubbed... URL: From spanda at 3clogic.com Wed Jun 26 09:24:24 2019 From: spanda at 3clogic.com (Sasmita Panda) Date: Wed, 26 Jun 2019 18:54:24 +0530 Subject: [OpenSIPS-Users] I need some help in websocket connection error . In-Reply-To: References: Message-ID: Is there any update on this issue . How I can solve this error message from my opensips logs . *Thanks & Regards* *Sasmita Panda* *Senior Network Testing and Software Engineer* *3CLogic , ph:07827611765* On Tue, Jun 25, 2019 at 3:48 PM Sasmita Panda wrote: > I have tried to take ssldump in the webrtc server in run time . > > New TCP connection #19: 192.168.1.y(48530) <-> 192.168.0.x(443) > 19 0.0011 (0.0011) C>S TCP FIN > 19 0.0013 (0.0001) S>C TCP FIN > > New TCP connection #20: 192.168.0.y(52975) <-> 192.168.0.x(443) > 20 1 0.0006 (0.0006) C>S Handshake ClientHello > 20 2 0.0008 (0.0002) S>C Handshake ServerHello > 20 3 0.0008 (0.0000) S>C Handshake Certificate > 20 4 0.0008 (0.0000) S>C Handshake ServerHelloDone > 20 5 0.0020 (0.0011) C>S Handshake ClientKeyExchange > 20 6 0.0020 (0.0000) C>S ChangeCipherSpec > 20 7 0.0020 (0.0000) C>S Handshake > 20 8 0.0036 (0.0015) S>C Handshake20 9 0.0036 (0.0000) S>C > ChangeCipherSpec > 20 10 0.0036 (0.0000) S>C Handshake > 20 11 0.0042 (0.0006) C>S Alert > 20 0.0042 (0.0000) C>S TCP FIN > 20 0.0043 (0.0000) S>C TCP FIN > > The portion I marked in red whenever appear there is error in opensips > logs . For below portion the connection was accepted . > > I am not even getting any error in my browser side . How I will debug > this ? please help . > > *Thanks & Regards* > *Sasmita Panda* > *Senior Network Testing and Software Engineer* > *3CLogic , ph:07827611765* > > > On Fri, Jun 14, 2019 at 2:51 PM Callum Guy wrote: > >> You might find that a tcpdump is the only way to get to grips with the >> underlying issue. >> >> Having said that I wonder if there is any chance that the connection >> isn't accepting simply due to a cipher incompatibility. Are you setting a >> cipher list that you know your clients accept? Maybe try: >> >> modparam("tls_mgm", "ciphers_list", >> "AES256-GCM-SHA384,AES256-SHA256,AES256-SHA,CAMELLIA256-SHA,AES128-SHA,CAMELLIA128-SHA,RC4-SHA") >> >> >> On Fri, 14 Jun 2019 at 09:17, Sasmita Panda wrote: >> >>> I had a dedicated server for 1 Client . When that client faces the issue >>> I started looking into the logs . And this is what the error I got . >>> >>> but latter on when I saw other servers which is getting used by >>> different client in that logs also same error coming everyday . >>> >>> As a conclusion its happening with everybody . >>> >>> Below is the configuration . >>> >>> modparam("tls_mgm", "tls_method", "tlsv1_2") >>> modparam("tls_mgm", "verify_cert", "0") >>> modparam("tls_mgm", "require_cert", "0") >>> modparam("tls_mgm", "certificate", >>> "/usr/etc/opensips/tls/3ccloudwebrtc2019.crt") >>> modparam("tls_mgm", "private_key", "/usr/etc/opensips/tls/3ccloud.key") >>> modparam("tls_mgm", "ca_list", "/usr/etc/opensips/tls/rootCA/cacert.pem") >>> >>> >>> >>> *Thanks & Regards* >>> *Sasmita Panda* >>> *Senior Network Testing and Software Engineer* >>> *3CLogic , ph:07827611765* >>> >>> >>> On Thu, Jun 13, 2019 at 6:50 PM Răzvan Crainea >>> wrote: >>> >>>> Can you trace the SSL traffic between the two endpoints? Perhaps the >>>> SSL >>>> header give you a reason for not accepting the connection. >>>> Is this happening only for certain clients, or for everyone? >>>> Are you requiring any certificates validation? >>>> >>>> Best regards, >>>> Răzvan >>>> >>>> On 6/12/19 3:34 PM, Sasmita Panda wrote: >>>> > I am using opensips 2.2 >>>> > version: opensips 2.2.4 (x86_64/linux) >>>> > >>>> > I am using the proto_wss and tls_mgm module for establishing >>>> websocket >>>> > connection . >>>> > >>>> > I am getting bellow error again and again . Whats the reson behind >>>> this >>>> > and how can I solve this problem ? >>>> > >>>> > >>>> > Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: >>>> > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb >>>> > Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: >>>> > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 96 >>>> > Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: >>>> > ERROR:proto_wss:tls_accept: New TLS connection from >>>> 192.168.160.6:58616 >>>> > failed to accept >>>> > Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: >>>> > ERROR:proto_wss:wss_read_req: cannot fix read connection >>>> > Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: >>>> > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb >>>> > Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: >>>> > INFO:core:init_sock_keepalive: TCP keepalive enabled on socket 96 >>>> > Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: >>>> > ERROR:proto_wss:tls_accept: New TLS connection from >>>> 192.168.175.59:12918 >>>> > failed to accept >>>> > Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: >>>> > ERROR:proto_wss:wss_read_req: cannot fix read connection >>>> > >>>> > >>>> > Please do help . >>>> > >>>> > >>>> > >>>> > */Thanks & Regards/* >>>> > /Sasmita Panda/ >>>> > /Senior 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 >>>> > >>>> >>>> -- >>>> Răzvan Crainea >>>> OpenSIPS Core 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 >>> >> >> >> *0333 332 0000 | www.x-on.co.uk | ** >> >> * >> >> X-on is a trading name of Storacall Technology Ltd a limited company >> registered in England and Wales. >> Registered Office : Avaland House, 110 London Road, Apsley, Hemel >> Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. >> The information in this e-mail is confidential and for use by the >> addressee(s) only. If you are not the intended recipient, please notify >> X-on immediately on +44(0)333 332 0000 and delete the >> message from your computer. If you are not a named addressee you must not >> use, disclose, disseminate, distribute, copy, print or reply to this email. Views >> or opinions expressed by an individual >> within this email may not necessarily reflect the views of X-on or its >> associated companies. Although X-on routinely screens for viruses, >> addressees should scan this email and any attachments >> for viruses. X-on makes no representation or warranty as to the absence >> of viruses in this email or any attachments. >> >> _______________________________________________ >> 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 efelin.novak at gmail.com Wed Jun 26 09:34:57 2019 From: efelin.novak at gmail.com (Efelin Novak) Date: Wed, 26 Jun 2019 15:34:57 +0200 Subject: [OpenSIPS-Users] Call_control and JSON-RPC In-Reply-To: References: Message-ID: Hi, @Johan: Call-control webpage says to post questions/bugs here. http://callcontrol.ag-projects.com/contact/ @Bogdan: That is not an answer I was looking for but I understand :) So the call-control project only works with OpenSIPS now? Thanks. Efelin st 26. 6. 2019 o 15:07 Bogdan-Andrei Iancu napísal(a): > Just use OpenSIPS and you will be fine :) > > Best regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/26/2019 03:11 PM, Efelin Novak wrote: > > Hi, > > I'm using a Kamailio version that does not support MI interface anymore. > Call_control module works nice in all situations expect when it wants to > kill the call (credit is gone). Is the Call_control module capable of using > JSON-RPC instead of MI command? > > When I change class ManagementInterface() so that the RPC command is not > sent and I only call os.system(command to kill a call using JSON-RPC), I > get a Error messages like this: > > kamailio[19687]: ERROR: call_control [call_control.c:839]: send_command(): > did timeout waiting for an answer > > The call is killed but I'm afraid that such error might cause errors in > future (e.g.: memory leaking). > > Is there any workaround? > Is it possible the call_control ends the call in a different way than MI > interface? > Can I use os.system hack? Can I ignore these errors or I can get rid of > them somehow? > > Kind regards > > Kamailio and Call-control are at newest version. > > Efelin > > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From govoiper at gmail.com Wed Jun 26 09:38:18 2019 From: govoiper at gmail.com (SamyGo) Date: Wed, 26 Jun 2019 09:38:18 -0400 Subject: [OpenSIPS-Users] Rest Client Async operation In-Reply-To: <927a8096-c4a8-7a42-b366-a587cfa73e7a@opensips.org> References: <6ED95883-2E26-477B-A8DF-6F6C130093AF@genesys.com> <20e603cc-3bd3-c31a-b9d9-fd0c7e3e5542@opensips.org> <4D9686A3-C7F3-4316-B9AF-C938797D6D78@genesys.com> <927a8096-c4a8-7a42-b366-a587cfa73e7a@opensips.org> Message-ID: Hi Liviu, Is it possible to suspend the transaction and resume it once we somehow get the event from libcurl as soon as the connect is done? Im imagining the way usually APNS is done these days. The only thing missing here is the event from the rest_client ! Can this mechanism help with the problem of backlog on the opensips thread ? Best Regards, Sammy On Wed., Jun. 26, 2019, 9:23 a.m. Liviu Chircu, wrote: > It's the same process doing both the connect and the transfer. The > problem is that libcurl, as it stands now, > is not able to give me a file descriptor to poll on, until it connects > [1]. See this section: > > "When libcurl returns -1 in max_fd, it is because libcurl currently does > something that isn't possible > for your application to monitor with a socket and unfortunately you can > then not know exactly when the > current action is completed using select(). You then need to wait a while > before you proceed and call > curl_multi_perform anyway. How long to wait? Unless curl_multi_timeout > gives you a lower number, we > suggest 100 milliseconds or so, but you may want to test it out in your > own particular conditions to > find a suitable value." > > Regarding your issue: I would investigate further the reason why the > connect is hanging, and not getting > rejected immediately when your server is down. That would solve all your > blocking issues. > > The same with MySQL connections which go down: only after the connection > is up are we able to obtain > its file descriptor to asynchronously poll on. So if connect to > DB_HOST:3306 hangs, so will OpenSIPS. > > Regards, > > [1]: https://curl.haxx.se/libcurl/c/curl_multi_fdset.html > > Liviu Chircu > OpenSIPS Developerhttp://www.opensips-solutions.com > > On 25.06.2019 18:41, Ben Newlin wrote: > > but I guess my question would be why isn’t the entire operation run in > async? Why must the connect be performed in the current process and only > the transfer be in another process? > > _______________________________________________ > 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 Jun 26 09:41:39 2019 From: liviu at opensips.org (Liviu Chircu) Date: Wed, 26 Jun 2019 16:41:39 +0300 Subject: [OpenSIPS-Users] Rest Client Async operation In-Reply-To: References: <6ED95883-2E26-477B-A8DF-6F6C130093AF@genesys.com> <20e603cc-3bd3-c31a-b9d9-fd0c7e3e5542@opensips.org> <4D9686A3-C7F3-4316-B9AF-C938797D6D78@genesys.com> <927a8096-c4a8-7a42-b366-a587cfa73e7a@opensips.org> Message-ID: That is exactly why we need to extract the connection/transfer fd in the first place: so we can throw it into epoll_wait() and have it act as an event generator :) Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 26.06.2019 16:38, SamyGo wrote: > once we somehow get the event from libcurl From bogdan at opensips.org Wed Jun 26 10:26:36 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 26 Jun 2019 17:26:36 +0300 Subject: [OpenSIPS-Users] Call_control and JSON-RPC In-Reply-To: References: Message-ID: <4157ef55-5da3-e412-e349-95ecdd8991ed@opensips.org> Hey Efelin, I cannot make statements in regards to the Call-Control project as I'm not involved. I CC'ed here Dan, he may be able to bring some light. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/26/2019 04:34 PM, Efelin Novak wrote: > Hi, > > @Johan: Call-control webpage says to post questions/bugs here. > http://callcontrol.ag-projects.com/contact/ > @Bogdan: That is not an answer I was looking for but I understand :) > So the call-control project only works with OpenSIPS now? > > Thanks. > > Efelin > > st 26. 6. 2019 o 15:07 Bogdan-Andrei Iancu > napísal(a): > > Just use OpenSIPS and you will be fine :) > > Best regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/26/2019 03:11 PM, Efelin Novak wrote: >> Hi, >> >> I'm using a Kamailio version that does not support MI interface >> anymore. Call_control module works nice in all situations expect >> when it wants to kill the call (credit is gone). Is the >> Call_control module capable of using JSON-RPC instead of MI command? >> >> When I change class ManagementInterface() so that the RPC command >> is not sent and I only call os.system(command to kill a call >> using JSON-RPC), I get a Error messages like this: >> >> kamailio[19687]: ERROR: call_control [call_control.c:839]: >> send_command(): did timeout waiting for an answer >> >> The call is killed but I'm afraid that such error might cause >> errors in future (e.g.: memory leaking). >> >> Is there any workaround? >> Is it possible the call_control ends the call in a different way >> than MI interface? >> Can I use os.system hack? Can I ignore these errors or I can get >> rid of them somehow? >> >> Kind regards >> >> Kamailio and Call-control are at newest version. >> >> Efelin >> >> >> _______________________________________________ >> 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 Jun 26 10:37:48 2019 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Wed, 26 Jun 2019 17:37:48 +0300 Subject: [OpenSIPS-Users] I need some help in websocket connection error . In-Reply-To: References: Message-ID: <3cd8b1dd-d450-7798-7f0c-d9f639481fab@opensips.org> TBH, all I can see in the logs you sent is that a connection was terminated (without even being started), and a connection that was started, but closed by the client. So in order to understand what's happening, you need to understand why the client is closing the connection. Check logs, documentation, anything, but this doesn't seem to be related to OpenSIPS, it looks like some SSL misconfiguration. Best regards, Răzvan On 6/26/19 4:24 PM, Sasmita Panda wrote: > Is there any update on this issue . How I can solve this error message > from my opensips logs . > > > */Thanks & Regards/* > /Sasmita Panda/ > /Senior Network Testing and Software Engineer/ > /3CLogic , ph:07827611765/ > > > On Tue, Jun 25, 2019 at 3:48 PM Sasmita Panda > wrote: > > I have tried to take ssldump in the webrtc server in run time . > > New TCP connection #19: 192.168.1.y(48530) <-> 192.168.0.x(443) > 19    0.0011 (0.0011)  C>S  TCP FIN > 19    0.0013 (0.0001)  S>C  TCP FIN > > New TCP connection #20: 192.168.0.y(52975) <-> 192.168.0.x(443) > 20 1  0.0006 (0.0006)  C>S  Handshake      ClientHello > 20 2  0.0008 (0.0002)  S>C  Handshake      ServerHello > 20 3  0.0008 (0.0000)  S>C  Handshake      Certificate > 20 4  0.0008 (0.0000)  S>C  Handshake      ServerHelloDone > 20 5  0.0020 (0.0011)  C>S  Handshake      ClientKeyExchange > 20 6  0.0020 (0.0000)  C>S  ChangeCipherSpec > 20 7  0.0020 (0.0000)  C>S  Handshake > 20 8  0.0036 (0.0015)  S>C  Handshake20 9  0.0036 (0.0000)  S>C >  ChangeCipherSpec > 20 10 0.0036 (0.0000)  S>C  Handshake > 20 11 0.0042 (0.0006)  C>S  Alert > 20    0.0042 (0.0000)  C>S  TCP FIN > 20    0.0043 (0.0000)  S>C  TCP FIN > > The portion I marked in red whenever appear there is error in > opensips logs  . For below portion the connection was accepted  . > > I am not even getting any error  in my browser side .  How I will > debug this ? please help . > > */Thanks & Regards/* > /Sasmita Panda/ > /Senior Network Testing and Software Engineer/ > /3CLogic , ph:07827611765/ > > > On Fri, Jun 14, 2019 at 2:51 PM Callum Guy > wrote: > > You might find that a tcpdump is the only way to get to grips > with the underlying issue. > > Having said that I wonder if there is any chance that the > connection isn't accepting simply due to a cipher > incompatibility. Are you setting a cipher list that you know > your clients accept? Maybe try: > > modparam("tls_mgm", "ciphers_list", > "AES256-GCM-SHA384,AES256-SHA256,AES256-SHA,CAMELLIA256-SHA,AES128-SHA,CAMELLIA128-SHA,RC4-SHA") > > > On Fri, 14 Jun 2019 at 09:17, Sasmita Panda > wrote: > > I had a dedicated server for 1 Client . When that client > faces the issue I started looking into the logs . And this > is what the error I got . > > but latter on when I saw other servers which is getting used > by different client in that logs also same error coming > everyday . > > As a conclusion its happening with everybody . > > Below is the configuration . > > modparam("tls_mgm", "tls_method", "tlsv1_2") > modparam("tls_mgm", "verify_cert", "0") > modparam("tls_mgm", "require_cert", "0") > modparam("tls_mgm", "certificate", > "/usr/etc/opensips/tls/3ccloudwebrtc2019.crt") > modparam("tls_mgm", "private_key", > "/usr/etc/opensips/tls/3ccloud.key") > modparam("tls_mgm", "ca_list", > "/usr/etc/opensips/tls/rootCA/cacert.pem") > > > > */Thanks & Regards/* > /Sasmita Panda/ > /Senior Network Testing and Software Engineer/ > /3CLogic , ph:07827611765/ > > > On Thu, Jun 13, 2019 at 6:50 PM Răzvan Crainea > > wrote: > > Can you trace the SSL traffic between the two endpoints? > Perhaps the SSL > header give you a reason for not accepting the connection. > Is this happening only for certain clients, or for everyone? > Are you requiring any certificates validation? > > Best regards, > Răzvan > > On 6/12/19 3:34 PM, Sasmita Panda wrote: > > I am using opensips 2.2 > >   version: opensips 2.2.4 (x86_64/linux) > > > > I am using the proto_wss and tls_mgm module for > establishing websocket > > connection . > > > > I am getting bellow error again and again . Whats the > reson behind this > > and how can I solve this problem ? > > > > > > Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: > > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > > Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: > > INFO:core:init_sock_keepalive: TCP keepalive enabled > on socket 96 > > Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: > > ERROR:proto_wss:tls_accept: New TLS connection from > 192.168.160.6:58616 > > failed to accept > > Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: > > ERROR:proto_wss:wss_read_req: cannot fix read connection > > Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: > > INFO:core:probe_max_sock_buff: using snd buffer of 416 kb > > Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: > > INFO:core:init_sock_keepalive: TCP keepalive enabled > on socket 96 > > Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: > > ERROR:proto_wss:tls_accept: New TLS connection from > 192.168.175.59:12918 > > failed to accept > > Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: > > ERROR:proto_wss:wss_read_req: cannot fix read connection > > > > > > Please do help . > > > > > > > > */Thanks & Regards/* > > /Sasmita Panda/ > > /Senior 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 > > > > -- > Răzvan Crainea > OpenSIPS Core 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 > > > > *^0333 332 0000  | www.x-on.co.uk   | > _**_^ > * > > X-on is a trading name of Storacall Technology Ltd a limited > company registered in England and Wales. > Registered Office : Avaland House, 110 London Road, Apsley, > Hemel Hempstead, Herts, HP3 9SD. Company Registration No. 2578478. > The information in this e-mail is confidential and for use by > the addressee(s) only. If you are not the intended recipient, > please notify X-on immediately on +44(0)333 332 0000 and delete the > message from your computer. If you are not a named addressee you > must not use, disclose, disseminate, distribute, copy, print or > reply to this email. Views or opinions expressed by an individual > within this email may not necessarily reflect the views of X-on > or its associated companies. Although X-on routinely screens for > viruses, addressees should scan this email and any attachments > for viruses. X-on makes no representation or warranty as to the > absence of viruses in this email or any attachments. > > _______________________________________________ > 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 > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com From Ben.Newlin at genesys.com Wed Jun 26 10:48:28 2019 From: Ben.Newlin at genesys.com (Ben Newlin) Date: Wed, 26 Jun 2019 14:48:28 +0000 Subject: [OpenSIPS-Users] Rest Client Async operation In-Reply-To: <927a8096-c4a8-7a42-b366-a587cfa73e7a@opensips.org> References: <6ED95883-2E26-477B-A8DF-6F6C130093AF@genesys.com> <20e603cc-3bd3-c31a-b9d9-fd0c7e3e5542@opensips.org> <4D9686A3-C7F3-4316-B9AF-C938797D6D78@genesys.com> <927a8096-c4a8-7a42-b366-a587cfa73e7a@opensips.org> Message-ID: Liviu, Thanks again for the info. I think what you are saying is that the async operation is not launching a new process to handle the called function, but is performing the function in the original worker thread and only taking advantage of any suspend/resume or polling functionality already exposed by the underlying function itself. This is very different from the way I had hoped async would work. The documentation does not speak to the specific implementation of async, so it was all assumptions on my part. But to me when you say async it means a separate process or thread is being created to perform the function. This would allow that process to block on the connect or any other aspect of the called function as necessary without blocking call processing, which is the desired outcome of any async operation. I understand that the practicalities of the implementation in OpenSIPS may have required this design, but I must re-iterate that these limitations need to be documented very carefully as they are very important to understand when designing OpenSIPS scripts with async functionality and are not described anywhere. I could not find anywhere in the documentation that indicates that async operations can potentially still block the original worker thread and block call processing. The closest is: “The current OpenSIPS worker will launch the asynchronous operation, after which it will continue to process other pending tasks” But this provides no elaboration on what it means for the worker to “launch” the operation, and more importantly it does not indicate that the launching itself can block, which is the key issue here. As I said, this unfortunately makes async processing mostly useless for us. For both DB and REST queries if only the data transfer is async then it is only useful when the data being transferred is extremely large or prone to delays/jitter. Such transfers should be avoided during realtime processing whether async or not, as they will still delay the individual call even if not others. For small payloads, like the single JSON object common in REST responses, it is the connection itself that is the concern. Once connected, running the data transfer in async mode represents no real gain. As far as investigating why the server is not responding, of course we will always do this. But we cannot anticipate or fix every cause of remote system failure. In order to design a resilient system we cannot assume the remote server will always be there. We had believed async would allow call processing to proceed in failure cases like this without blocking. Ben Newlin From: Users on behalf of Liviu Chircu Reply-To: OpenSIPS users mailling list Date: Wednesday, June 26, 2019 at 9:23 AM To: "users at lists.opensips.org" Subject: Re: [OpenSIPS-Users] Rest Client Async operation It's the same process doing both the connect and the transfer. The problem is that libcurl, as it stands now, is not able to give me a file descriptor to poll on, until it connects [1]. See this section: "When libcurl returns -1 in max_fd, it is because libcurl currently does something that isn't possible for your application to monitor with a socket and unfortunately you can then not know exactly when the current action is completed using select(). You then need to wait a while before you proceed and call curl_multi_perform anyway. How long to wait? Unless curl_multi_timeout gives you a lower number, we suggest 100 milliseconds or so, but you may want to test it out in your own particular conditions to find a suitable value." Regarding your issue: I would investigate further the reason why the connect is hanging, and not getting rejected immediately when your server is down. That would solve all your blocking issues. The same with MySQL connections which go down: only after the connection is up are we able to obtain its file descriptor to asynchronously poll on. So if connect to DB_HOST:3306 hangs, so will OpenSIPS. Regards, [1]: https://curl.haxx.se/libcurl/c/curl_multi_fdset.html Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 25.06.2019 18:41, Ben Newlin wrote: but I guess my question would be why isn’t the entire operation run in async? Why must the connect be performed in the current process and only the transfer be in another process? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dan at ag-projects.com Wed Jun 26 11:16:55 2019 From: dan at ag-projects.com (Dan Pascu) Date: Wed, 26 Jun 2019 18:16:55 +0300 Subject: [OpenSIPS-Users] Call_control and JSON-RPC In-Reply-To: References: Message-ID: On 26 Jun 2019, at 15:11, Efelin Novak wrote: > Hi, > > I'm using a Kamailio version that does not support MI interface anymore. Call_control module works nice in all situations expect when it wants to kill the call (credit is gone). Is the Call_control module capable of using JSON-RPC instead of MI command? > > When I change class ManagementInterface() so that the RPC command is not sent and I only call os.system(command to kill a call using JSON-RPC), I get a Error messages like this: > > kamailio[19687]: ERROR: call_control [call_control.c:839]: send_command(): did timeout waiting for an answer > > The call is killed but I'm afraid that such error might cause errors in future (e.g.: memory leaking). > > Is there any workaround? > Is it possible the call_control ends the call in a different way than MI interface? It is possible if you modify the code yourself to do it in whatever way you want. The stock call-control only uses the opensips MI interface and there are no plans to support anything else at the moment. > Can I use os.system hack? Can I ignore these errors or I can get rid of them somehow? > > Kind regards > > Kamailio and Call-control are at newest version. > > Efelin > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Dan From k.galinurov at gmail.com Wed Jun 26 11:23:40 2019 From: k.galinurov at gmail.com (Kirill Galinurov) Date: Wed, 26 Jun 2019 18:23:40 +0300 Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi reload_routes In-Reply-To: References: <3cfae2bb-9271-4582-9bea-a77d3c74b4c0@opensips.org> <94261deb-6d55-4d33-02e0-761ce7ee3882@opensips.org> Message-ID: Do you need any additional information or may be tests? вт, 25 июн. 2019 г., 19:32 Bogdan-Andrei Iancu : > Still, whatever syntax (with errors) you have in the cfg, the reload > should not crash :(... my offer of trying to reproduce it with your script > is still available. > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/25/2019 07:30 PM, Kirill Galinurov wrote: > > Bogdan I am very stupped... I am sorry... But I am found problem... > I use uac_replace_from("$avp(fU)","sip:$avp(fU)@{{anycast_ip}}"); > To template my config. > And when I comment this line all became good. > I guess ... I should not use templating in routes... > > вт, 25 июн. 2019 г. в 19:11, Bogdan-Andrei Iancu : > >> Kirill, >> >> Could you share (off-list, privately) your script with me to see if I can >> reproduce the crash ? >> >> Regards, >> >> Bogdan-Andrei Iancu >> >> OpenSIPS Founder and Developer >> https://www.opensips-solutions.com >> OpenSIPS Summit 2019 >> https://www.opensips.org/events/Summit-2019Amsterdam/ >> >> On 06/25/2019 07:10 PM, Kirill Galinurov wrote: >> >> I am very sorry Bogdan. But I have no any useful information for you. I >> can try to rewrite my config step by step... >> >> >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Wed Jun 26 11:40:17 2019 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Wed, 26 Jun 2019 18:40:17 +0300 Subject: [OpenSIPS-Users] Opensips 3.0 segfault on opensips-cli -x mi reload_routes In-Reply-To: References: <3cfae2bb-9271-4582-9bea-a77d3c74b4c0@opensips.org> <94261deb-6d55-4d33-02e0-761ce7ee3882@opensips.org> Message-ID: Hey Kirill, Not yet, sorry, busy day :(, but I will !! Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com OpenSIPS Summit 2019 https://www.opensips.org/events/Summit-2019Amsterdam/ On 06/26/2019 06:23 PM, Kirill Galinurov wrote: > Do you need any additional information or may be tests? > > вт, 25 июн. 2019 г., 19:32 Bogdan-Andrei Iancu >: > > Still, whatever syntax (with errors) you have in the cfg, the > reload should not crash :(... my offer of trying to reproduce it > with your script is still available. > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 06/25/2019 07:30 PM, Kirill Galinurov wrote: >> Bogdan I am very stupped... I am sorry... But I am found problem... >> I use uac_replace_from("$avp(fU)","sip:$avp(fU)@{{anycast_ip}}"); >> To template my config. >> And when I comment this line all became good. >> I guess ... I should not use templating in routes... >> >> вт, 25 июн. 2019 г. в 19:11, Bogdan-Andrei Iancu >> >: >> >> Kirill, >> >> Could you share (off-list, privately) your script with me to >> see if I can reproduce the crash ? >> >> Regards, >> >> Bogdan-Andrei Iancu >> >> OpenSIPS Founder and Developer >> https://www.opensips-solutions.com >> OpenSIPS Summit 2019 >> https://www.opensips.org/events/Summit-2019Amsterdam/ >> >> On 06/25/2019 07:10 PM, Kirill Galinurov wrote: >>> I am very sorry Bogdan. But I have no any useful information >>> for you. I can try to rewrite my config step by step... >>> >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From social at bohboh.info Wed Jun 26 18:10:23 2019 From: social at bohboh.info (Social Boh) Date: Wed, 26 Jun 2019 17:10:23 -0500 Subject: [OpenSIPS-Users] Federated User Location Cluster Message-ID: <11bbd0ec-a990-c16c-8075-22509ceabdc4@bohboh.info> Hello list, I really don't understood how this configuration work. I would like to configure two OpenSIPs instances to share data about registered users but I can't because when from extension 1000 registered on first Opensips call extension 1001 Registered on the second OpenSIPs, OpenSIPs search in the MongoDB a AOR with the same IP of the first OpenSIPs; this because use_domain parameter of usrloc module have to be = 1 So, How have I to use this configuration? balancing DNS records for the same domain? Thank you Regards -- --- I'm SoCIaL, MayBe From spanda at 3clogic.com Thu Jun 27 02:02:50 2019 From: spanda at 3clogic.com (Sasmita Panda) Date: Thu, 27 Jun 2019 11:32:50 +0530 Subject: [OpenSIPS-Users] I need some help in websocket connection error . In-Reply-To: <3cd8b1dd-d450-7798-7f0c-d9f639481fab@opensips.org> References: <3cd8b1dd-d450-7798-7f0c-d9f639481fab@opensips.org> Message-ID: Hi, SSL miss configuration in client side or in opensips side . I think I have done the configuration right . listen=wss:192.168.143.20:443 loadmodule "tls_mgm.so" modparam("tls_mgm", "tls_method", "tlsv1_2") modparam("tls_mgm", "verify_cert", "0") modparam("tls_mgm", "require_cert", "0") modparam("tls_mgm", "certificate", "/usr/local/etc/opensips/tls/3ccloudwebrtc2019.crt") modparam("tls_mgm", "private_key", "/usr/local/etc/opensips/tls/3ccloud.key") modparam("tls_mgm", "ca_list", "/usr/local/etc/opensips/tls/rootCA/cacert.pem") loadmodule "proto_wss.so" modparam("proto_wss", "wss_port", 443) This is for wss . Is there anything I am missing in configuration ? *Thanks & Regards* *Sasmita Panda* *Senior Network Testing and Software Engineer* *3CLogic , ph:07827611765* On Wed, Jun 26, 2019 at 8:10 PM Răzvan Crainea wrote: > TBH, all I can see in the logs you sent is that a connection was > terminated (without even being started), and a connection that was > started, but closed by the client. So in order to understand what's > happening, you need to understand why the client is closing the > connection. Check logs, documentation, anything, but this doesn't seem > to be related to OpenSIPS, it looks like some SSL misconfiguration. > > Best regards, > Răzvan > > On 6/26/19 4:24 PM, Sasmita Panda wrote: > > Is there any update on this issue . How I can solve this error message > > from my opensips logs . > > > > > > */Thanks & Regards/* > > /Sasmita Panda/ > > /Senior Network Testing and Software Engineer/ > > /3CLogic , ph:07827611765/ > > > > > > On Tue, Jun 25, 2019 at 3:48 PM Sasmita Panda > > wrote: > > > > I have tried to take ssldump in the webrtc server in run time . > > > > New TCP connection #19: 192.168.1.y(48530) <-> 192.168.0.x(443) > > 19 0.0011 (0.0011) C>S TCP FIN > > 19 0.0013 (0.0001) S>C TCP FIN > > > > New TCP connection #20: 192.168.0.y(52975) <-> 192.168.0.x(443) > > 20 1 0.0006 (0.0006) C>S Handshake ClientHello > > 20 2 0.0008 (0.0002) S>C Handshake ServerHello > > 20 3 0.0008 (0.0000) S>C Handshake Certificate > > 20 4 0.0008 (0.0000) S>C Handshake ServerHelloDone > > 20 5 0.0020 (0.0011) C>S Handshake ClientKeyExchange > > 20 6 0.0020 (0.0000) C>S ChangeCipherSpec > > 20 7 0.0020 (0.0000) C>S Handshake > > 20 8 0.0036 (0.0015) S>C Handshake20 9 0.0036 (0.0000) S>C > > ChangeCipherSpec > > 20 10 0.0036 (0.0000) S>C Handshake > > 20 11 0.0042 (0.0006) C>S Alert > > 20 0.0042 (0.0000) C>S TCP FIN > > 20 0.0043 (0.0000) S>C TCP FIN > > > > The portion I marked in red whenever appear there is error in > > opensips logs . For below portion the connection was accepted . > > > > I am not even getting any error in my browser side . How I will > > debug this ? please help . > > > > */Thanks & Regards/* > > /Sasmita Panda/ > > /Senior Network Testing and Software Engineer/ > > /3CLogic , ph:07827611765/ > > > > > > On Fri, Jun 14, 2019 at 2:51 PM Callum Guy > > wrote: > > > > You might find that a tcpdump is the only way to get to grips > > with the underlying issue. > > > > Having said that I wonder if there is any chance that the > > connection isn't accepting simply due to a cipher > > incompatibility. Are you setting a cipher list that you know > > your clients accept? Maybe try: > > > > modparam("tls_mgm", "ciphers_list", > > > "AES256-GCM-SHA384,AES256-SHA256,AES256-SHA,CAMELLIA256-SHA,AES128-SHA,CAMELLIA128-SHA,RC4-SHA") > > > > > > On Fri, 14 Jun 2019 at 09:17, Sasmita Panda > > wrote: > > > > I had a dedicated server for 1 Client . When that client > > faces the issue I started looking into the logs . And this > > is what the error I got . > > > > but latter on when I saw other servers which is getting used > > by different client in that logs also same error coming > > everyday . > > > > As a conclusion its happening with everybody . > > > > Below is the configuration . > > > > modparam("tls_mgm", "tls_method", "tlsv1_2") > > modparam("tls_mgm", "verify_cert", "0") > > modparam("tls_mgm", "require_cert", "0") > > modparam("tls_mgm", "certificate", > > "/usr/etc/opensips/tls/3ccloudwebrtc2019.crt") > > modparam("tls_mgm", "private_key", > > "/usr/etc/opensips/tls/3ccloud.key") > > modparam("tls_mgm", "ca_list", > > "/usr/etc/opensips/tls/rootCA/cacert.pem") > > > > > > > > */Thanks & Regards/* > > /Sasmita Panda/ > > /Senior Network Testing and Software Engineer/ > > /3CLogic , ph:07827611765/ > > > > > > On Thu, Jun 13, 2019 at 6:50 PM Răzvan Crainea > > > wrote: > > > > Can you trace the SSL traffic between the two endpoints? > > Perhaps the SSL > > header give you a reason for not accepting the > connection. > > Is this happening only for certain clients, or for > everyone? > > Are you requiring any certificates validation? > > > > Best regards, > > Răzvan > > > > On 6/12/19 3:34 PM, Sasmita Panda wrote: > > > I am using opensips 2.2 > > > version: opensips 2.2.4 (x86_64/linux) > > > > > > I am using the proto_wss and tls_mgm module for > > establishing websocket > > > connection . > > > > > > I am getting bellow error again and again . Whats the > > reson behind this > > > and how can I solve this problem ? > > > > > > > > > Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: > > > INFO:core:probe_max_sock_buff: using snd buffer of > 416 kb > > > Jun 10 00:00:15 localhost /usr/sbin/opensips[1548]: > > > INFO:core:init_sock_keepalive: TCP keepalive enabled > > on socket 96 > > > Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: > > > ERROR:proto_wss:tls_accept: New TLS connection from > > 192.168.160.6:58616 > > > failed to accept > > > Jun 10 00:00:15 localhost /usr/sbin/opensips[1546]: > > > ERROR:proto_wss:wss_read_req: cannot fix read > connection > > > Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: > > > INFO:core:probe_max_sock_buff: using snd buffer of > 416 kb > > > Jun 10 00:00:17 localhost /usr/sbin/opensips[1548]: > > > INFO:core:init_sock_keepalive: TCP keepalive enabled > > on socket 96 > > > Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: > > > ERROR:proto_wss:tls_accept: New TLS connection from > > 192.168.175.59:12918 > > > failed to accept > > > Jun 10 00:00:17 localhost /usr/sbin/opensips[1546]: > > > ERROR:proto_wss:wss_read_req: cannot fix read > connection > > > > > > > > > Please do help . > > > > > > > > > > > > */Thanks & Regards/* > > > /Sasmita Panda/ > > > /Senior 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 > > > > > > > -- > > Răzvan Crainea > > OpenSIPS Core Developer > > http://www.opensips-solutions.com > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org 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 > > > > > > > > *^0333 332 0000 | www.x-on.co.uk | > > _**_^ > > * > > > > X-on is a trading name of Storacall Technology Ltd a limited > > company registered in England and Wales. > > Registered Office : Avaland House, 110 London Road, Apsley, > > Hemel Hempstead, Herts, HP3 9SD. Company Registration No. > 2578478. > > The information in this e-mail is confidential and for use by > > the addressee(s) only. If you are not the intended recipient, > > please notify X-on immediately on +44(0)333 332 0000 and delete > the > > message from your computer. If you are not a named addressee you > > must not use, disclose, disseminate, distribute, copy, print or > > reply to this email. Views or opinions expressed by an individual > > within this email may not necessarily reflect the views of X-on > > or its associated companies. Although X-on routinely screens for > > viruses, addressees should scan this email and any attachments > > for viruses. X-on makes no representation or warranty as to the > > absence of viruses in this email or any attachments. > > > > _______________________________________________ > > 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 > > > > -- > Răzvan Crainea > OpenSIPS Core 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 efelin.novak at gmail.com Thu Jun 27 05:04:25 2019 From: efelin.novak at gmail.com (Efelin Novak) Date: Thu, 27 Jun 2019 11:04:25 +0200 Subject: [OpenSIPS-Users] Call_control and JSON-RPC In-Reply-To: References: Message-ID: Hi Dan, thanks for the clarification. Kind regards Efelin st 26. 6. 2019 o 17:19 Dan Pascu napísal(a): > > On 26 Jun 2019, at 15:11, Efelin Novak wrote: > > > Hi, > > > > I'm using a Kamailio version that does not support MI interface anymore. > Call_control module works nice in all situations expect when it wants to > kill the call (credit is gone). Is the Call_control module capable of using > JSON-RPC instead of MI command? > > > > When I change class ManagementInterface() so that the RPC command is not > sent and I only call os.system(command to kill a call using JSON-RPC), I > get a Error messages like this: > > > > kamailio[19687]: ERROR: call_control [call_control.c:839]: > send_command(): did timeout waiting for an answer > > > > The call is killed but I'm afraid that such error might cause errors in > future (e.g.: memory leaking). > > > > Is there any workaround? > > Is it possible the call_control ends the call in a different way than MI > interface? > > It is possible if you modify the code yourself to do it in whatever way > you want. The stock call-control only uses the opensips MI interface and > there are no plans to support anything else at the moment. > > > Can I use os.system hack? Can I ignore these errors or I can get rid of > them somehow? > > > > Kind regards > > > > Kamailio and Call-control are at newest version. > > > > Efelin > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > -- > Dan > > > > > > _______________________________________________ > 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 Jun 27 05:04:46 2019 From: liviu at opensips.org (Liviu Chircu) Date: Thu, 27 Jun 2019 12:04:46 +0300 Subject: [OpenSIPS-Users] Rest Client Async operation In-Reply-To: References: <6ED95883-2E26-477B-A8DF-6F6C130093AF@genesys.com> <20e603cc-3bd3-c31a-b9d9-fd0c7e3e5542@opensips.org> <4D9686A3-C7F3-4316-B9AF-C938797D6D78@genesys.com> <927a8096-c4a8-7a42-b366-a587cfa73e7a@opensips.org> Message-ID: On 26.06.2019 17:48, Ben Newlin wrote: > > Thanks again for the info. I think what you are saying is that the > async operation is not launching a new process to handle the called > function, but is performing the function in the original worker thread > and only taking advantage of any suspend/resume or polling > functionality already exposed by the underlying function itself. > Just to clear this up:  the underlying functions themselves need not offer any polling functionality, they just need to meet two criteria: (1) be non-blocking; (2) provide a valid fd for the async engine to poll on. Any blocking I/O functionality, be it within libcurl, MySQL, etc. that meets the above can be adapted to work with the async engine available in OpenSIPS 2.1+. > I understand that the practicalities of the implementation in OpenSIPS > may have required this design, but I must re-iterate that these > limitations need to be documented very carefully as they are very > important to understand when designing OpenSIPS scripts with async > functionality and are not described anywhere. I could not find > anywhere in the documentation that indicates that async operations can > potentially still block the original worker thread and block call > processing. The closest is: > > “The current OpenSIPS worker will launch the asynchronous operation, > after which it will continue to process other pending tasks” > > But this provides no elaboration on what it means for the worker to > “launch” the operation, and more importantly it does not indicate that > the launching itself can block, which is the key issue here. > Agreed - will try to find a way to integrate this corner-case into the docs, somehow. > > As I said, this unfortunately makes async processing mostly useless > for us. For both DB and REST queries if only the data transfer is > async then it is only useful when the data being transferred is > extremely large or prone to delays/jitter. Such transfers should be > avoided during realtime processing whether async or not, as they will > still delay the individual call even if not others. For small > payloads, like the single JSON object common in REST responses, it is > the connection itself that is the concern. Once connected, running the > data transfer in async mode represents no real gain. > Then I recommend you stop using rest_client, which currently optimizes system resource usage forsetups where the TCP connect cannot possibly ever hang, and resort to forking a process for eachHTTP request, using a construct such as:     async(exec("curl your_connect_hanging_http_endpoint"), resume_route); Although forking a process for each request is a costly operation which will eat more system resources during normal operation, at least this solution optimizes for the worst case, when the HTTP server is down.  In this latter case, the throughput of your SIP server won't be hindered that much, as the hanging connect will be done asynchronously. Best regards, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From liviu at opensips.org Thu Jun 27 06:14:24 2019 From: liviu at opensips.org (Liviu Chircu) Date: Thu, 27 Jun 2019 13:14:24 +0300 Subject: [OpenSIPS-Users] Rest Client Async operation In-Reply-To: References: <6ED95883-2E26-477B-A8DF-6F6C130093AF@genesys.com> <20e603cc-3bd3-c31a-b9d9-fd0c7e3e5542@opensips.org> <4D9686A3-C7F3-4316-B9AF-C938797D6D78@genesys.com> <927a8096-c4a8-7a42-b366-a587cfa73e7a@opensips.org> Message-ID: <1b6d4537-5342-08a4-4792-8f33f82fdb08@opensips.org> I have updated the async docs [1], so everyone can read more about this limitation, along with a mitigation solution for it. Cheers, [1]: https://www.opensips.org/Documentation/Script-Async-3-0#toc8 Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com From social at bohboh.info Thu Jun 27 09:14:42 2019 From: social at bohboh.info (Social Boh) Date: Thu, 27 Jun 2019 08:14:42 -0500 Subject: [OpenSIPS-Users] Federated User Location Cluster In-Reply-To: <11bbd0ec-a990-c16c-8075-22509ceabdc4@bohboh.info> References: <11bbd0ec-a990-c16c-8075-22509ceabdc4@bohboh.info> Message-ID: Any Light, please? --- I'm SoCIaL, MayBe On 6/26/19 17:10, Social Boh wrote: > Hello list, > > I really don't understood how this configuration work. > > I would like to configure two OpenSIPs instances to share data about > registered users but I can't because when from extension 1000 > registered on first Opensips call extension 1001 Registered on the > second OpenSIPs, OpenSIPs search in the MongoDB a AOR with the same IP > of the first OpenSIPs; this because use_domain parameter of usrloc > module have to be = 1 > > So, How have I to use this configuration? balancing DNS records for > the same domain? > > Thank you > > Regards > From Ben.Newlin at genesys.com Thu Jun 27 09:20:19 2019 From: Ben.Newlin at genesys.com (Ben Newlin) Date: Thu, 27 Jun 2019 13:20:19 +0000 Subject: [OpenSIPS-Users] Rest Client Async operation In-Reply-To: References: <6ED95883-2E26-477B-A8DF-6F6C130093AF@genesys.com> <20e603cc-3bd3-c31a-b9d9-fd0c7e3e5542@opensips.org> <4D9686A3-C7F3-4316-B9AF-C938797D6D78@genesys.com> <927a8096-c4a8-7a42-b366-a587cfa73e7a@opensips.org> Message-ID: <1E2436AA-B53D-4D05-92AE-363A9BF27432@genesys.com> Liviu, Thank you. This makes complete sense now and the documentation updates are excellent. Thanks as well for the workaround suggestion; we will investigate whether it is necessary. You do make a good point in the docs about TCP connection reuse in the workers, which shows my example as a bit of an extreme case. In practical use it is more likely the connection would exist and the transfer would timeout instead, which would be async. Even though the example may be extreme, in the current world of cloud computing having the remote server “disappear” without closing TCP connections is becoming a much more common concern. Cloud instances can and do just disappear and the connections will hang; cloud networks have issues and can leave connections hung as well. We have been wrestling with these issues with the db_postgres and db_virtual modules for some time and have an open ticket for it now. While it is impossible to avoid some service impairment when a necessary remote component is no longer available, having the entire call processing application block on the resource is also not a very good response. We are always looking for better ways to gracefully handle the unexpected. Thanks for the time and quick responses! Ben Newlin From: Users on behalf of Liviu Chircu Reply-To: OpenSIPS users mailling list Date: Thursday, June 27, 2019 at 5:05 AM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Rest Client Async operation On 26.06.2019 17:48, Ben Newlin wrote: Thanks again for the info. I think what you are saying is that the async operation is not launching a new process to handle the called function, but is performing the function in the original worker thread and only taking advantage of any suspend/resume or polling functionality already exposed by the underlying function itself. Just to clear this up: the underlying functions themselves need not offer any polling functionality, they just need to meet two criteria: (1) be non-blocking; (2) provide a valid fd for the async engine to poll on. Any blocking I/O functionality, be it within libcurl, MySQL, etc. that meets the above can be adapted to work with the async engine available in OpenSIPS 2.1+. I understand that the practicalities of the implementation in OpenSIPS may have required this design, but I must re-iterate that these limitations need to be documented very carefully as they are very important to understand when designing OpenSIPS scripts with async functionality and are not described anywhere. I could not find anywhere in the documentation that indicates that async operations can potentially still block the original worker thread and block call processing. The closest is: “The current OpenSIPS worker will launch the asynchronous operation, after which it will continue to process other pending tasks” But this provides no elaboration on what it means for the worker to “launch” the operation, and more importantly it does not indicate that the launching itself can block, which is the key issue here. Agreed - will try to find a way to integrate this corner-case into the docs, somehow. As I said, this unfortunately makes async processing mostly useless for us. For both DB and REST queries if only the data transfer is async then it is only useful when the data being transferred is extremely large or prone to delays/jitter. Such transfers should be avoided during realtime processing whether async or not, as they will still delay the individual call even if not others. For small payloads, like the single JSON object common in REST responses, it is the connection itself that is the concern. Once connected, running the data transfer in async mode represents no real gain. Then I recommend you stop using rest_client, which currently optimizes system resource usage for setups where the TCP connect cannot possibly ever hang, and resort to forking a process for each HTTP request, using a construct such as: async(exec("curl your_connect_hanging_http_endpoint"), resume_route); Although forking a process for each request is a costly operation which will eat more system resources during normal operation, at least this solution optimizes for the worst case, when the HTTP server is down. In this latter case, the throughput of your SIP server won't be hindered that much, as the hanging connect will be done asynchronously. Best regards, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ben.Newlin at genesys.com Thu Jun 27 09:25:06 2019 From: Ben.Newlin at genesys.com (Ben Newlin) Date: Thu, 27 Jun 2019 13:25:06 +0000 Subject: [OpenSIPS-Users] Federated User Location Cluster In-Reply-To: References: <11bbd0ec-a990-c16c-8075-22509ceabdc4@bohboh.info> Message-ID: Social, It seems like what you want is for the registration to ignore the domain. Why do you say that use_domain has to be enabled? It seems like if you turn it off this would work. Alternatively, you could use DNS for the domain instead of IP addresses and have the DNS resolve to both OpenSIPS instances, either with SRV if the registering device supports it or with A records. You would not be able to control which specific server each device would register to, but in the long run they should be balanced across both nodes. Lastly, I believe the usrloc and registration modules have support for the new clustering functionality. I have not used it personally, but I believe it has mechanisms to resolve issues like this. Ben Newlin On 6/27/19, 9:16 AM, "Users on behalf of Social Boh" wrote: Any Light, please? --- I'm SoCIaL, MayBe On 6/26/19 17:10, Social Boh wrote: > Hello list, > > I really don't understood how this configuration work. > > I would like to configure two OpenSIPs instances to share data about > registered users but I can't because when from extension 1000 > registered on first Opensips call extension 1001 Registered on the > second OpenSIPs, OpenSIPs search in the MongoDB a AOR with the same IP > of the first OpenSIPs; this because use_domain parameter of usrloc > module have to be = 1 > > So, How have I to use this configuration? balancing DNS records for > the same domain? > > Thank you > > Regards > _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users From social at bohboh.info Thu Jun 27 09:35:22 2019 From: social at bohboh.info (Social Boh) Date: Thu, 27 Jun 2019 08:35:22 -0500 Subject: [OpenSIPS-Users] Federated User Location Cluster In-Reply-To: References: <11bbd0ec-a990-c16c-8075-22509ceabdc4@bohboh.info> Message-ID: <25248737-ddd8-d577-4346-65615f880582@bohboh.info> Ben, justly I'm trying to using clustering functionality bud I don't understood completely the registration part. On the tutorial (1) appear a domain but I don't understand how the devices choose in which OpenSIPs instance register and how I have to add user on the subscriber table of each OpenSIPs. Regards. 1) https://opensips.org/Documentation/Tutorials-Distributed-User-Location-Federation --- I'm SoCIaL, MayBe On 6/27/19 08:25, Ben Newlin wrote: > Social, > > It seems like what you want is for the registration to ignore the domain. Why do you say that use_domain has to be enabled? It seems like if you turn it off this would work. > > Alternatively, you could use DNS for the domain instead of IP addresses and have the DNS resolve to both OpenSIPS instances, either with SRV if the registering device supports it or with A records. You would not be able to control which specific server each device would register to, but in the long run they should be balanced across both nodes. > > Lastly, I believe the usrloc and registration modules have support for the new clustering functionality. I have not used it personally, but I believe it has mechanisms to resolve issues like this. > > Ben Newlin > > On 6/27/19, 9:16 AM, "Users on behalf of Social Boh" wrote: > > Any Light, please? > > --- > I'm SoCIaL, MayBe > > On 6/26/19 17:10, Social Boh wrote: > > Hello list, > > > > I really don't understood how this configuration work. > > > > I would like to configure two OpenSIPs instances to share data about > > registered users but I can't because when from extension 1000 > > registered on first Opensips call extension 1001 Registered on the > > second OpenSIPs, OpenSIPs search in the MongoDB a AOR with the same IP > > of the first OpenSIPs; this because use_domain parameter of usrloc > > module have to be = 1 > > > > So, How have I to use this configuration? balancing DNS records for > > the same domain? > > > > Thank you > > > > 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 > From liviu at opensips.org Thu Jun 27 09:42:45 2019 From: liviu at opensips.org (Liviu Chircu) Date: Thu, 27 Jun 2019 16:42:45 +0300 Subject: [OpenSIPS-Users] Federated User Location Cluster In-Reply-To: <11bbd0ec-a990-c16c-8075-22509ceabdc4@bohboh.info> References: <11bbd0ec-a990-c16c-8075-22509ceabdc4@bohboh.info> Message-ID: <1c51d468-221a-471a-1560-10fd2b7891a6@opensips.org> Hi Social, From what I understand, you are registering your devices to 1000 at IP_A and 1001 at IP_B, respectively.  If this is the case, please have them register to 1000 at opensips-cluster and 1001 at opensips-cluster, and point their "Outbound Proxy" settings to IP_A and IP_B, respectively. Hope this helps.  If you haven't read the tutorial [1], I strongly suggest you do so :) Cheers, [1]: https://opensips.org/Documentation/Tutorials-Distributed-User-Location-Federation Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 27.06.2019 01:10, Social Boh wrote: > Hello list, > > I really don't understood how this configuration work. > > I would like to configure two OpenSIPs instances to share data about > registered users but I can't because when from extension 1000 > registered on first Opensips call extension 1001 Registered on the > second OpenSIPs, OpenSIPs search in the MongoDB a AOR with the same IP > of the first OpenSIPs; this because use_domain parameter of usrloc > module have to be = 1 > > So, How have I to use this configuration? balancing DNS records for > the same domain? > > Thank you > > Regards > From social at bohboh.info Thu Jun 27 10:05:26 2019 From: social at bohboh.info (Social Boh) Date: Thu, 27 Jun 2019 09:05:26 -0500 Subject: [OpenSIPS-Users] Federated User Location Cluster In-Reply-To: <1c51d468-221a-471a-1560-10fd2b7891a6@opensips.org> References: <11bbd0ec-a990-c16c-8075-22509ceabdc4@bohboh.info> <1c51d468-221a-471a-1560-10fd2b7891a6@opensips.org> Message-ID: Hi Liviu, I read the tutorial but I don't understood completely how this architecture work. I Have two OpenSIPs instances, each one with his IP. I add user 1000 and user 1001 on both instances so the user can choose which OpenSIPs use to register. How USRLOC use_domain parameter is obligatory on federated cluster, each user can be reached only using user at OpenSIPsIP so if I call from user 1000 (registered on first OpenSIPs), user 1001 registered on the second OpenSIPs, the call fail because the IP present in the AOR is different. With your solution I have to create opensips-cluster domain and configure two A record with two OpenSIPs Public IP; then create the users using this domain and configure the devices with the outbound proxy parameter, right? is it the only solution to achieve federated cluster location? Thank you Regards --- I'm SoCIaL, MayBe On 6/27/19 08:42, Liviu Chircu wrote: > Hi Social, > > From what I understand, you are registering your devices to 1000 at IP_A > and 1001 at IP_B, > respectively.  If this is the case, please have them register to > 1000 at opensips-cluster and > 1001 at opensips-cluster, and point their "Outbound Proxy" settings to > IP_A and IP_B, respectively. > > Hope this helps.  If you haven't read the tutorial [1], I strongly > suggest you do so :) > > Cheers, > > [1]: > https://opensips.org/Documentation/Tutorials-Distributed-User-Location-Federation > > Liviu Chircu > OpenSIPS Developer > http://www.opensips-solutions.com > > On 27.06.2019 01:10, Social Boh wrote: >> Hello list, >> >> I really don't understood how this configuration work. >> >> I would like to configure two OpenSIPs instances to share data about >> registered users but I can't because when from extension 1000 >> registered on first Opensips call extension 1001 Registered on the >> second OpenSIPs, OpenSIPs search in the MongoDB a AOR with the same >> IP of the first OpenSIPs; this because use_domain parameter of usrloc >> module have to be = 1 >> >> So, How have I to use this configuration? balancing DNS records for >> the same domain? >> >> Thank you >> >> Regards >> > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > From liviu at opensips.org Thu Jun 27 10:59:18 2019 From: liviu at opensips.org (Liviu Chircu) Date: Thu, 27 Jun 2019 17:59:18 +0300 Subject: [OpenSIPS-Users] Federated User Location Cluster In-Reply-To: References: <11bbd0ec-a990-c16c-8075-22509ceabdc4@bohboh.info> <1c51d468-221a-471a-1560-10fd2b7891a6@opensips.org> Message-ID: <598b3c26-ca6d-2f78-36ad-d9f8f875d177@opensips.org> You are overcomplicating this.  There are two ways to get it working: 1. just use a dummy "opensips-cluster" domain + outbound proxy settings on your UACs.  This way,    the domain doesn't even have to be resolvable.  As long as OpenSIPS detects it as being a    local domain (either through the "alias=" setting, or the "domain" module table), the setup    will simply work. 2. you take the time to create an actual DNS record for your platform and provision both IPs into it    using the policy of your choosing: round-robin, weight-based, geo-DNS, etc.  This will not    require any "outbound proxy" setting on the UACs, as they will be able to resolve the domain. Best regards, Liviu Chircu OpenSIPS Developer http://www.opensips-solutions.com On 27.06.2019 17:05, Social Boh wrote: > With your solution I have to create opensips-cluster domain and > configure two A record with two OpenSIPs Public IP; then create the > users using this domain and configure the devices with the outbound > proxy parameter, right? From goup2010 at gmail.com Thu Jun 27 16:36:16 2019 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Thu, 27 Jun 2019 23:36:16 +0300 Subject: [OpenSIPS-Users] How to change media protocol? Message-ID: Hello, I have OpenSips + rtpengine. Opensips receive INVITE with Media Protocol: RTP/SAVP How to setup Opensips to forward INVITE to ITSP with Media Protocol: RTP/AVP. Like this scheme: INVITE with Media Protocol: RTP/SAVP --> (OpenSips +rtpengine) ---->INVITE with Media Protocol: RTP/AVP ---> ITSP Best regards, Dragomir -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob.dyck at telus.net Thu Jun 27 18:21:59 2019 From: rob.dyck at telus.net (rob.dyck at telus.net) Date: Thu, 27 Jun 2019 16:21:59 -0600 (MDT) Subject: [OpenSIPS-Users] Feature request - pseudo-variable for destination IP address Message-ID: <1084479194.59156276.1561674119097.JavaMail.zimbra@mailid.telus.net> I was looking for something similar to the $si PV but for the destination IP address. Either it doesn't exist or I am blind. I can't find things in the refrigerator either. The motivation. I have a working instance of Opensips with a basic residential configuration. I extended it to allow calling UAs on the LAN from the outside. It is a typical residential LAN without a fixed IP address. Dynamic DNS is working for me. I read the tutorial about Opensips behind NAT. Following the recommendations there I was able to setup rtpproxy, the advertised address and an alias for my Opensips. Initial testing using a softphone on a laptop using either WiFi or a mobile phone tethered to the laptop worked well. However it seems that some UAs will not accept a domain name in the SDP connection. The UAs that failed could be made to work by coding in an IP address. This is not a satisfactory solution because the router's address may chaange. There is probably some convoluted way to import the needed address into the script. A pseudo-variable representing the destination IP address of the received INVITE or 200 OK could then be passed as the advertised address to the rtpproxy module. Thank you for having a look. Rob From osas at voipembedded.com Thu Jun 27 18:31:34 2019 From: osas at voipembedded.com (Ovidiu Sas) Date: Thu, 27 Jun 2019 18:31:34 -0400 Subject: [OpenSIPS-Users] Feature request - pseudo-variable for destination IP address In-Reply-To: <1084479194.59156276.1561674119097.JavaMail.zimbra@mailid.telus.net> References: <1084479194.59156276.1561674119097.JavaMail.zimbra@mailid.telus.net> Message-ID: Check out the $Ri pvar: https://www.opensips.org/Documentation/Script-CoreVar-3-0#toc78 -ovidiu On Thu, Jun 27, 2019 at 6:23 PM rob.dyck at telus.net wrote: > > I was looking for something similar to the $si PV but for the destination IP address. Either it doesn't exist or I am blind. I can't find things in the refrigerator either. > > The motivation. > > I have a working instance of Opensips with a basic residential configuration. I extended it to allow calling UAs on the LAN from the outside. It is a typical residential LAN without a fixed IP address. Dynamic DNS is working for me. I read the tutorial about Opensips behind NAT. Following the recommendations there I was able to setup rtpproxy, the advertised address and an alias for my Opensips. Initial testing using a softphone on a laptop using either WiFi or a mobile phone tethered to the laptop worked well. However it seems that some UAs will not accept a domain name in the SDP connection. The UAs that failed could be made to work by coding in an IP address. This is not a satisfactory solution because the router's address may chaange. There is probably some convoluted way to import the needed address into the script. A pseudo-variable representing the destination IP address of the received INVITE or 200 OK could then be passed as the advertised address to the rtpproxy module. > > Thank you for having a look. > Rob > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- VoIP Embedded, Inc. http://www.voipembedded.com From rob.dyck at telus.net Thu Jun 27 18:35:37 2019 From: rob.dyck at telus.net (rob.dyck at telus.net) Date: Thu, 27 Jun 2019 16:35:37 -0600 (MDT) Subject: [OpenSIPS-Users] Feature request - pseudo-variable for destination IP address In-Reply-To: <1084479194.59156276.1561674119097.JavaMail.zimbra@mailid.telus.net> References: <1084479194.59156276.1561674119097.JavaMail.zimbra@mailid.telus.net> Message-ID: <1061883766.59177749.1561674937246.JavaMail.zimbra@mailid.telus.net> On second thought it probably isn't poosible to do in any direct way because the information is lost in the router. The only possible way is a DNS query. ----- Original Message ----- From: "rob dyck" To: users at lists.opensips.org Sent: Thursday, June 27, 2019 3:21:59 PM Subject: Feature request - pseudo-variable for destination IP address I was looking for something similar to the $si PV but for the destination IP address. Either it doesn't exist or I am blind. I can't find things in the refrigerator either. The motivation. I have a working instance of Opensips with a basic residential configuration. I extended it to allow calling UAs on the LAN from the outside. It is a typical residential LAN without a fixed IP address. Dynamic DNS is working for me. I read the tutorial about Opensips behind NAT. Following the recommendations there I was able to setup rtpproxy, the advertised address and an alias for my Opensips. Initial testing using a softphone on a laptop using either WiFi or a mobile phone tethered to the laptop worked well. However it seems that some UAs will not accept a domain name in the SDP connection. The UAs that failed could be made to work by coding in an IP address. This is not a satisfactory solution because the router's address may chaange. There is probably some convoluted way to import the needed address into the script. A pseudo-variable representing the destination IP address of the received INVITE or 200 OK could then be passed as the advertised address to the rtpproxy module. Thank you for having a look. Rob From igor.pavlov1987 at gmail.com Fri Jun 28 03:46:28 2019 From: igor.pavlov1987 at gmail.com (Igor Pavlov) Date: Fri, 28 Jun 2019 11:46:28 +0400 Subject: [OpenSIPS-Users] create_dialog with Load Balancer module Message-ID: <521925db-457a-5d21-f601-43b8dd127a48@gmail.com> Hi all, I'm a little bit confused with using 'dialog' and 'load balancer' modules. Tutorial says that load_balance() will automatically create the dialog state, in this case can I use create_dialog( ) or it's redundant? If yes, what should be called firstly - load_balance() and if it return true call create_dialog() or vice versa? I'm also using dialog profiling and sharing. -- -- Kind regards, Igor Pavlov From johan at democon.be Fri Jun 28 03:49:39 2019 From: johan at democon.be (johan de clercq) Date: Fri, 28 Jun 2019 09:49:39 +0200 Subject: [OpenSIPS-Users] How to change media protocol? In-Reply-To: References: Message-ID: <004401d52d86$0a3041e0$1e90c5a0$@democon.be> Change ruri to transport:udp. Start the params that you give to rtpengine_offer or answer with RTP/AVP or RTP/SAVP accordingly. From: Users On Behalf Of Dragomir Haralambiev Sent: Thursday, June 27, 2019 10:36 PM To: OpenSIPS users mailling list Subject: [OpenSIPS-Users] How to change media protocol? Hello, I have OpenSips + rtpengine. Opensips receive INVITE with Media Protocol: RTP/SAVP How to setup Opensips to forward INVITE to ITSP with Media Protocol: RTP/AVP. Like this scheme: INVITE with Media Protocol: RTP/SAVP --> (OpenSips +rtpengine) ---->INVITE with Media Protocol: RTP/AVP ---> ITSP Best regards, Dragomir -------------- next part -------------- An HTML attachment was scrubbed... URL: From johan at democon.be Fri Jun 28 03:51:12 2019 From: johan at democon.be (johan de clercq) Date: Fri, 28 Jun 2019 09:51:12 +0200 Subject: [OpenSIPS-Users] create_dialog with Load Balancer module In-Reply-To: <521925db-457a-5d21-f601-43b8dd127a48@gmail.com> References: <521925db-457a-5d21-f601-43b8dd127a48@gmail.com> Message-ID: <004901d52d86$421e3080$c65a9180$@democon.be> You should call create dialog first (as you do stuff with profiles). If the dialog exist, the value of it's profile will not be changed by calling the loadbalancer. -----Original Message----- From: Users On Behalf Of Igor Pavlov Sent: Friday, June 28, 2019 9:46 AM To: OpenSIPS users mailling list Subject: [OpenSIPS-Users] create_dialog with Load Balancer module Hi all, I'm a little bit confused with using 'dialog' and 'load balancer' modules. Tutorial says that load_balance() will automatically create the dialog state, in this case can I use create_dialog( ) or it's redundant? If yes, what should be called firstly - load_balance() and if it return true call create_dialog() or vice versa? I'm also using dialog profiling and sharing. -- -- Kind regards, Igor Pavlov _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users From razvan at opensips.org Fri Jun 28 04:01:35 2019 From: razvan at opensips.org (=?UTF-8?Q?R=c4=83zvan_Crainea?=) Date: Fri, 28 Jun 2019 11:01:35 +0300 Subject: [OpenSIPS-Users] I need some help in websocket connection error . In-Reply-To: References: <3cd8b1dd-d450-7798-7f0c-d9f639481fab@opensips.org> Message-ID: <0455befb-77af-3c0f-6dc7-b9282646d7a2@opensips.org> Hi, Sasmita! I see that you require TLSv1.2 authentication method - are you sure your clients do support this version? A similar problem can be with the ciphers, are you sure your clients support the whitelisted ciphers? As you do not enforce anything, this might be true, but this is something you should double-check. Besides that, I don't have any other ideas. Best regards, Răzvan On 6/27/19 9:02 AM, Sasmita Panda wrote: > Hi, > > SSL miss configuration in client side or in opensips side . I think I > have done the configuration right . > > listen=wss:192.168.143.20:443 > loadmodule "tls_mgm.so" > modparam("tls_mgm", "tls_method", "tlsv1_2") > modparam("tls_mgm", "verify_cert", "0") > modparam("tls_mgm", "require_cert", "0") > modparam("tls_mgm", "certificate", > "/usr/local/etc/opensips/tls/3ccloudwebrtc2019.crt") > modparam("tls_mgm", "private_key", > "/usr/local/etc/opensips/tls/3ccloud.key") > modparam("tls_mgm", "ca_list", > "/usr/local/etc/opensips/tls/rootCA/cacert.pem") > loadmodule "proto_wss.so" > modparam("proto_wss", "wss_port", 443) > > This is for wss . Is there anything I am missing in configuration ? > > > */Thanks & Regards/* > /Sasmita Panda/ > /Senior Network Testing and Software Engineer/ > /3CLogic , ph:07827611765/ > > > On Wed, Jun 26, 2019 at 8:10 PM Răzvan Crainea > wrote: > > TBH, all I can see in the logs you sent is that a connection was > terminated (without even being started), and a connection that was > started, but closed by the client. So in order to understand what's > happening, you need to understand why the client is closing the > connection. Check logs, documentation, anything, but this doesn't seem > to be related to OpenSIPS, it looks like some SSL misconfiguration. > > Best regards, > Răzvan > > On 6/26/19 4:24 PM, Sasmita Panda wrote: > > Is there any update on this issue . How I can solve this error > message > > from my opensips logs . > > > > > > */Thanks & Regards/* > > /Sasmita Panda/ > > /Senior Network Testing and Software Engineer/ > > /3CLogic , ph:07827611765/ > > > > > > On Tue, Jun 25, 2019 at 3:48 PM Sasmita Panda > > >> wrote: > > > >     I have tried to take ssldump in the webrtc server in run time . > > > >     New TCP connection #19: 192.168.1.y(48530) <-> 192.168.0.x(443) > >     19    0.0011 (0.0011)  C>S  TCP FIN > >     19    0.0013 (0.0001)  S>C  TCP FIN > > > >     New TCP connection #20: 192.168.0.y(52975) <-> 192.168.0.x(443) > >     20 1  0.0006 (0.0006)  C>S  Handshake      ClientHello > >     20 2  0.0008 (0.0002)  S>C  Handshake      ServerHello > >     20 3  0.0008 (0.0000)  S>C  Handshake      Certificate > >     20 4  0.0008 (0.0000)  S>C  Handshake      ServerHelloDone > >     20 5  0.0020 (0.0011)  C>S  Handshake      ClientKeyExchange > >     20 6  0.0020 (0.0000)  C>S  ChangeCipherSpec > >     20 7  0.0020 (0.0000)  C>S  Handshake > >     20 8  0.0036 (0.0015)  S>C  Handshake20 9  0.0036 (0.0000)  S>C > >       ChangeCipherSpec > >     20 10 0.0036 (0.0000)  S>C  Handshake > >     20 11 0.0042 (0.0006)  C>S  Alert > >     20    0.0042 (0.0000)  C>S  TCP FIN > >     20    0.0043 (0.0000)  S>C  TCP FIN > > > >     The portion I marked in red whenever appear there is error in > >     opensips logs  . For below portion the connection was accepted  . > > > >     I am not even getting any error  in my browser side .  How I will > >     debug this ? please help . > > > >     */Thanks & Regards/* > >     /Sasmita Panda/ > >     /Senior Network Testing and Software Engineer/ > >     /3CLogic , ph:07827611765/ > > > > > >     On Fri, Jun 14, 2019 at 2:51 PM Callum Guy > > >      >> wrote: > > > >         You might find that a tcpdump is the only way to get to grips > >         with the underlying issue. > > > >         Having said that I wonder if there is any chance that the > >         connection isn't accepting simply due to a cipher > >         incompatibility. Are you setting a cipher list that you know > >         your clients accept? Maybe try: > > > >         modparam("tls_mgm", "ciphers_list", > > >  "AES256-GCM-SHA384,AES256-SHA256,AES256-SHA,CAMELLIA256-SHA,AES128-SHA,CAMELLIA128-SHA,RC4-SHA") > > > > > >         On Fri, 14 Jun 2019 at 09:17, Sasmita Panda > > >         >> > wrote: > > > >             I had a dedicated server for 1 Client . When that client > >             faces the issue I started looking into the logs . And > this > >             is what the error I got . > > > >             but latter on when I saw other servers which is > getting used > >             by different client in that logs also same error coming > >             everyday . > > > >             As a conclusion its happening with everybody . > > > >             Below is the configuration . > > > >             modparam("tls_mgm", "tls_method", "tlsv1_2") > >             modparam("tls_mgm", "verify_cert", "0") > >             modparam("tls_mgm", "require_cert", "0") > >             modparam("tls_mgm", "certificate", > >             "/usr/etc/opensips/tls/3ccloudwebrtc2019.crt") > >             modparam("tls_mgm", "private_key", > >             "/usr/etc/opensips/tls/3ccloud.key") > >             modparam("tls_mgm", "ca_list", > >             "/usr/etc/opensips/tls/rootCA/cacert.pem") > > > > > > > >             */Thanks & Regards/* > >             /Sasmita Panda/ > >             /Senior Network Testing and Software Engineer/ > >             /3CLogic , ph:07827611765/ > > > > > >             On Thu, Jun 13, 2019 at 6:50 PM Răzvan Crainea > >              > >> wrote: > > > >                 Can you trace the SSL traffic between the two > endpoints? > >                 Perhaps the SSL > >                 header give you a reason for not accepting the > connection. > >                 Is this happening only for certain clients, or > for everyone? > >                 Are you requiring any certificates validation? > > > >                 Best regards, > >                 Răzvan > > > >                 On 6/12/19 3:34 PM, Sasmita Panda wrote: > >                  > I am using opensips 2.2 > >                  >   version: opensips 2.2.4 (x86_64/linux) > >                  > > >                  > I am using the proto_wss and tls_mgm module for > >                 establishing websocket > >                  > connection . > >                  > > >                  > I am getting bellow error again and again . > Whats the > >                 reson behind this > >                  > and how can I solve this problem ? > >                  > > >                  > > >                  > Jun 10 00:00:15 localhost > /usr/sbin/opensips[1548]: > >                  > INFO:core:probe_max_sock_buff: using snd > buffer of 416 kb > >                  > Jun 10 00:00:15 localhost > /usr/sbin/opensips[1548]: > >                  > INFO:core:init_sock_keepalive: TCP keepalive > enabled > >                 on socket 96 > >                  > Jun 10 00:00:15 localhost > /usr/sbin/opensips[1546]: > >                  > ERROR:proto_wss:tls_accept: New TLS connection > from > > 192.168.160.6:58616 > > >                  > failed to accept > >                  > Jun 10 00:00:15 localhost > /usr/sbin/opensips[1546]: > >                  > ERROR:proto_wss:wss_read_req: cannot fix read > connection > >                  > Jun 10 00:00:17 localhost > /usr/sbin/opensips[1548]: > >                  > INFO:core:probe_max_sock_buff: using snd > buffer of 416 kb > >                  > Jun 10 00:00:17 localhost > /usr/sbin/opensips[1548]: > >                  > INFO:core:init_sock_keepalive: TCP keepalive > enabled > >                 on socket 96 > >                  > Jun 10 00:00:17 localhost > /usr/sbin/opensips[1546]: > >                  > ERROR:proto_wss:tls_accept: New TLS connection > from > > 192.168.175.59:12918 > > >                  > failed to accept > >                  > Jun 10 00:00:17 localhost > /usr/sbin/opensips[1546]: > >                  > ERROR:proto_wss:wss_read_req: cannot fix read > connection > >                  > > >                  > > >                  > Please do help . > >                  > > >                  > > >                  > > >                  > */Thanks & Regards/* > >                  > /Sasmita Panda/ > >                  > /Senior 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 > >                  > > > > >                 -- > >                 Răzvan Crainea > >                 OpenSIPS Core 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 > > > > > > > >         *^0333 332 0000  | www.x-on.co.uk >   | > >         _**_^ > >          > * > > > >         X-on is a trading name of Storacall Technology Ltd a limited > >         company registered in England and Wales. > >         Registered Office : Avaland House, 110 London Road, Apsley, > >         Hemel Hempstead, Herts, HP3 9SD. Company Registration No. > 2578478. > >         The information in this e-mail is confidential and for use by > >         the addressee(s) only. If you are not the intended recipient, > >         please notify X-on immediately on +44(0)333 332 0000 and > delete the > >         message from your computer. If you are not a named > addressee you > >         must not use, disclose, disseminate, distribute, copy, > print or > >         reply to this email. Views or opinions expressed by an > individual > >         within this email may not necessarily reflect the views > of X-on > >         or its associated companies. Although X-on routinely > screens for > >         viruses, addressees should scan this email and any > attachments > >         for viruses. X-on makes no representation or warranty as > to the > >         absence of viruses in this email or any attachments. > > > >         _______________________________________________ > >         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 > > > > -- > Răzvan Crainea > OpenSIPS Core 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 > -- Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com From goup2010 at gmail.com Fri Jun 28 07:43:56 2019 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Fri, 28 Jun 2019 14:43:56 +0300 Subject: [OpenSIPS-Users] How to change media protocol? In-Reply-To: <004401d52d86$0a3041e0$1e90c5a0$@democon.be> References: <004401d52d86$0a3041e0$1e90c5a0$@democon.be> Message-ID: Hi, Thanks for your reply. Yes I use rtpengine_offer like this: rtpengine_offer("RTP/AVP/SAVP replace-session-connection replace-origin ICE=remove") In this case Opensips + Rtpengine send INVITE to ITSP with Media Protocol: RTP/SAVP, But ITSP not supported RTP/SAVP (they supported only RTP/AVP). I'm looking for a way to setup Opensips to change Media Protocol from RTP/SAVP to RTP/AVP. It means converting encrypted media to normal. Best regards, Dragomir На пт, 28.06.2019 г. в 10:52 ч. johan de clercq написа: > Change ruri to transport:udp. > > > > Start the params that you give to rtpengine_offer or answer with RTP/AVP > or RTP/SAVP accordingly. > > > > *From:* Users *On Behalf Of *Dragomir > Haralambiev > *Sent:* Thursday, June 27, 2019 10:36 PM > *To:* OpenSIPS users mailling list > *Subject:* [OpenSIPS-Users] How to change media protocol? > > > > Hello, > > I have OpenSips + rtpengine. > Opensips receive INVITE with Media Protocol: RTP/SAVP > How to setup Opensips to forward INVITE to ITSP with Media Protocol: > RTP/AVP. Like this scheme: > > > INVITE with Media Protocol: RTP/SAVP --> (OpenSips +rtpengine) ---->INVITE > with Media Protocol: RTP/AVP ---> ITSP > > > > 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 Johan at democon.be Fri Jun 28 09:33:05 2019 From: Johan at democon.be (Johan De Clercq) Date: Fri, 28 Jun 2019 15:33:05 +0200 Subject: [OpenSIPS-Users] How to change media protocol? In-Reply-To: References: <004401d52d86$0a3041e0$1e90c5a0$@democon.be> Message-ID: See earlier response. On Fri, 28 Jun 2019, 13:46 Dragomir Haralambiev, wrote: > Hi, > > Thanks for your reply. > > Yes I use rtpengine_offer like this: > rtpengine_offer("RTP/AVP/SAVP replace-session-connection replace-origin > ICE=remove") > > In this case Opensips + Rtpengine send INVITE to ITSP with Media > Protocol: RTP/SAVP, > But ITSP not supported RTP/SAVP (they supported only RTP/AVP). > > I'm looking for a way to setup Opensips to change Media Protocol from > RTP/SAVP to RTP/AVP. > It means converting encrypted media to normal. > > Best regards, > Dragomir > > > На пт, 28.06.2019 г. в 10:52 ч. johan de clercq написа: > >> Change ruri to transport:udp. >> >> >> >> Start the params that you give to rtpengine_offer or answer with RTP/AVP >> or RTP/SAVP accordingly. >> >> >> >> *From:* Users *On Behalf Of *Dragomir >> Haralambiev >> *Sent:* Thursday, June 27, 2019 10:36 PM >> *To:* OpenSIPS users mailling list >> *Subject:* [OpenSIPS-Users] How to change media protocol? >> >> >> >> Hello, >> >> I have OpenSips + rtpengine. >> Opensips receive INVITE with Media Protocol: RTP/SAVP >> How to setup Opensips to forward INVITE to ITSP with Media Protocol: >> RTP/AVP. Like this scheme: >> >> >> INVITE with Media Protocol: RTP/SAVP --> (OpenSips +rtpengine) >> ---->INVITE with Media Protocol: RTP/AVP ---> ITSP >> >> >> >> 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Johan at democon.be Fri Jun 28 09:34:35 2019 From: Johan at democon.be (Johan De Clercq) Date: Fri, 28 Jun 2019 15:34:35 +0200 Subject: [OpenSIPS-Users] How to change media protocol? In-Reply-To: References: <004401d52d86$0a3041e0$1e90c5a0$@democon.be> Message-ID: If goes to provider: rtp/avp Else rtp/savp So put your parameters in a var before calling rtpengine On Fri, 28 Jun 2019, 13:46 Dragomir Haralambiev, wrote: > Hi, > > Thanks for your reply. > > Yes I use rtpengine_offer like this: > rtpengine_offer("RTP/AVP/SAVP replace-session-connection replace-origin > ICE=remove") > > In this case Opensips + Rtpengine send INVITE to ITSP with Media > Protocol: RTP/SAVP, > But ITSP not supported RTP/SAVP (they supported only RTP/AVP). > > I'm looking for a way to setup Opensips to change Media Protocol from > RTP/SAVP to RTP/AVP. > It means converting encrypted media to normal. > > Best regards, > Dragomir > > > На пт, 28.06.2019 г. в 10:52 ч. johan de clercq написа: > >> Change ruri to transport:udp. >> >> >> >> Start the params that you give to rtpengine_offer or answer with RTP/AVP >> or RTP/SAVP accordingly. >> >> >> >> *From:* Users *On Behalf Of *Dragomir >> Haralambiev >> *Sent:* Thursday, June 27, 2019 10:36 PM >> *To:* OpenSIPS users mailling list >> *Subject:* [OpenSIPS-Users] How to change media protocol? >> >> >> >> Hello, >> >> I have OpenSips + rtpengine. >> Opensips receive INVITE with Media Protocol: RTP/SAVP >> How to setup Opensips to forward INVITE to ITSP with Media Protocol: >> RTP/AVP. Like this scheme: >> >> >> INVITE with Media Protocol: RTP/SAVP --> (OpenSips +rtpengine) >> ---->INVITE with Media Protocol: RTP/AVP ---> ITSP >> >> >> >> 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From goup2010 at gmail.com Fri Jun 28 09:42:53 2019 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Fri, 28 Jun 2019 16:42:53 +0300 Subject: [OpenSIPS-Users] How to change media protocol? In-Reply-To: References: <004401d52d86$0a3041e0$1e90c5a0$@democon.be> Message-ID: Hi, I do this but Opensips +rtpengine not converting encrypted media to normal. if (isflagset(SRC_WS) && isbflagset(DST_WS)) { $var(rtpengine_flags) = "ICE=force-relay DTLS=passive"; } else if (isflagset(SRC_WS) && !isbflagset(DST_WS)) { $var(rtpengine_flags) = "RTP/AVP replace-session-connection replace-origin ICE=remove"; } else if (!isflagset(SRC_WS) && isbflagset(DST_WS)) { $var(rtpengine_flags) = "UDP/TLS/RTP/SAVPF ICE=force"; } else if (!isflagset(SRC_WS) && !isbflagset(DST_WS)) { $var(rtpengine_flags) = "RTP/AVP/SAVP replace-session-connection replace-origin ICE=remove"; } rtpengine_offer("$var(rtpengine_flags)"); На пт, 28.06.2019 г. в 16:38 ч. Johan De Clercq написа: > If goes to provider: rtp/avp > Else rtp/savp > > So put your parameters in a var before calling rtpengine > > On Fri, 28 Jun 2019, 13:46 Dragomir Haralambiev, > wrote: > >> Hi, >> >> Thanks for your reply. >> >> Yes I use rtpengine_offer like this: >> rtpengine_offer("RTP/AVP/SAVP replace-session-connection replace-origin >> ICE=remove") >> >> In this case Opensips + Rtpengine send INVITE to ITSP with Media >> Protocol: RTP/SAVP, >> But ITSP not supported RTP/SAVP (they supported only RTP/AVP). >> >> I'm looking for a way to setup Opensips to change Media Protocol from >> RTP/SAVP to RTP/AVP. >> It means converting encrypted media to normal. >> >> Best regards, >> Dragomir >> >> >> На пт, 28.06.2019 г. в 10:52 ч. johan de clercq >> написа: >> >>> Change ruri to transport:udp. >>> >>> >>> >>> Start the params that you give to rtpengine_offer or answer with RTP/AVP >>> or RTP/SAVP accordingly. >>> >>> >>> >>> *From:* Users *On Behalf Of *Dragomir >>> Haralambiev >>> *Sent:* Thursday, June 27, 2019 10:36 PM >>> *To:* OpenSIPS users mailling list >>> *Subject:* [OpenSIPS-Users] How to change media protocol? >>> >>> >>> >>> Hello, >>> >>> I have OpenSips + rtpengine. >>> Opensips receive INVITE with Media Protocol: RTP/SAVP >>> How to setup Opensips to forward INVITE to ITSP with Media Protocol: >>> RTP/AVP. Like this scheme: >>> >>> >>> INVITE with Media Protocol: RTP/SAVP --> (OpenSips +rtpengine) >>> ---->INVITE with Media Protocol: RTP/AVP ---> ITSP >>> >>> >>> >>> 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 rob.dyck at telus.net Fri Jun 28 10:14:31 2019 From: rob.dyck at telus.net (rob.dyck at telus.net) Date: Fri, 28 Jun 2019 08:14:31 -0600 (MDT) Subject: [OpenSIPS-Users] Feature request - pseudo-variable for destination IP address In-Reply-To: References: <1084479194.59156276.1561674119097.JavaMail.zimbra@mailid.telus.net> Message-ID: <1464802737.63108382.1561731271217.JavaMail.zimbra@mailid.telus.net> Unfortunately the address of the interface where the request was receeived is private. I am using 1 to 1 NAT. ----- Original Message ----- From: "Ovidiu Sas" To: "OpenSIPS users mailling list" Sent: Thursday, June 27, 2019 3:31:34 PM Subject: Re: [OpenSIPS-Users] Feature request - pseudo-variable for destination IP address Check out the $Ri pvar: https://www.opensips.org/Documentation/Script-CoreVar-3-0#toc78 -ovidiu On Thu, Jun 27, 2019 at 6:23 PM rob.dyck at telus.net wrote: > > I was looking for something similar to the $si PV but for the destination IP address. Either it doesn't exist or I am blind. I can't find things in the refrigerator either. > > The motivation. > > I have a working instance of Opensips with a basic residential configuration. I extended it to allow calling UAs on the LAN from the outside. It is a typical residential LAN without a fixed IP address. Dynamic DNS is working for me. I read the tutorial about Opensips behind NAT. Following the recommendations there I was able to setup rtpproxy, the advertised address and an alias for my Opensips. Initial testing using a softphone on a laptop using either WiFi or a mobile phone tethered to the laptop worked well. However it seems that some UAs will not accept a domain name in the SDP connection. The UAs that failed could be made to work by coding in an IP address. This is not a satisfactory solution because the router's address may chaange. There is probably some convoluted way to import the needed address into the script. A pseudo-variable representing the destination IP address of the received INVITE or 200 OK could then be passed as the advertised address to the rtpproxy module. > > Thank you for having a look. > Rob > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- VoIP Embedded, Inc. http://www.voipembedded.com _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users From Johan at democon.be Fri Jun 28 10:43:54 2019 From: Johan at democon.be (Johan De Clercq) Date: Fri, 28 Jun 2019 16:43:54 +0200 Subject: [OpenSIPS-Users] How to change media protocol? In-Reply-To: References: <004401d52d86$0a3041e0$1e90c5a0$@democon.be> Message-ID: Drop the webrtc part and you will be fine On Fri, 28 Jun 2019, 15:45 Dragomir Haralambiev, wrote: > Hi, > > I do this but Opensips +rtpengine not converting encrypted media to normal. > > if (isflagset(SRC_WS) && isbflagset(DST_WS)) { > $var(rtpengine_flags) = "ICE=force-relay DTLS=passive"; > } else if (isflagset(SRC_WS) && !isbflagset(DST_WS)) { > $var(rtpengine_flags) = "RTP/AVP replace-session-connection > replace-origin ICE=remove"; > } else if (!isflagset(SRC_WS) && isbflagset(DST_WS)) { > $var(rtpengine_flags) = "UDP/TLS/RTP/SAVPF ICE=force"; > } else if (!isflagset(SRC_WS) && !isbflagset(DST_WS)) { > $var(rtpengine_flags) = "RTP/AVP/SAVP replace-session-connection > replace-origin ICE=remove"; > } > > rtpengine_offer("$var(rtpengine_flags)"); > > На пт, 28.06.2019 г. в 16:38 ч. Johan De Clercq написа: > >> If goes to provider: rtp/avp >> Else rtp/savp >> >> So put your parameters in a var before calling rtpengine >> >> On Fri, 28 Jun 2019, 13:46 Dragomir Haralambiev, >> wrote: >> >>> Hi, >>> >>> Thanks for your reply. >>> >>> Yes I use rtpengine_offer like this: >>> rtpengine_offer("RTP/AVP/SAVP replace-session-connection replace-origin >>> ICE=remove") >>> >>> In this case Opensips + Rtpengine send INVITE to ITSP with Media >>> Protocol: RTP/SAVP, >>> But ITSP not supported RTP/SAVP (they supported only RTP/AVP). >>> >>> I'm looking for a way to setup Opensips to change Media Protocol from >>> RTP/SAVP to RTP/AVP. >>> It means converting encrypted media to normal. >>> >>> Best regards, >>> Dragomir >>> >>> >>> На пт, 28.06.2019 г. в 10:52 ч. johan de clercq >>> написа: >>> >>>> Change ruri to transport:udp. >>>> >>>> >>>> >>>> Start the params that you give to rtpengine_offer or answer with >>>> RTP/AVP or RTP/SAVP accordingly. >>>> >>>> >>>> >>>> *From:* Users *On Behalf Of *Dragomir >>>> Haralambiev >>>> *Sent:* Thursday, June 27, 2019 10:36 PM >>>> *To:* OpenSIPS users mailling list >>>> *Subject:* [OpenSIPS-Users] How to change media protocol? >>>> >>>> >>>> >>>> Hello, >>>> >>>> I have OpenSips + rtpengine. >>>> Opensips receive INVITE with Media Protocol: RTP/SAVP >>>> How to setup Opensips to forward INVITE to ITSP with Media Protocol: >>>> RTP/AVP. Like this scheme: >>>> >>>> >>>> INVITE with Media Protocol: RTP/SAVP --> (OpenSips +rtpengine) >>>> ---->INVITE with Media Protocol: RTP/AVP ---> ITSP >>>> >>>> >>>> >>>> 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 >> > _______________________________________________ > 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 Jun 28 10:52:22 2019 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Fri, 28 Jun 2019 17:52:22 +0300 Subject: [OpenSIPS-Users] How to change media protocol? In-Reply-To: References: <004401d52d86$0a3041e0$1e90c5a0$@democon.be> Message-ID: ....... } else if (!isflagset(SRC_WS) && !isbflagset(DST_WS)) { $var(rtpengine_flags) = "RTP/AVP/SAVP replace-session-connection replace-origin ICE=remove"; } in this case: $var(rtpengine_flags) = "RTP/AVP/SAVP replace-session-connection replace-origin ICE=remove"; rtpengine_offer("$var(rtpengine_flags)"); This is no working. Opensips received RTP/SAVP and forrward RTP/SAVP. I like to received RTP/SAVP and forrward RTP/AVP. На пт, 28.06.2019 г. в 17:47 ч. Johan De Clercq написа: > Drop the webrtc part and you will be fine > > On Fri, 28 Jun 2019, 15:45 Dragomir Haralambiev, > wrote: > >> Hi, >> >> I do this but Opensips +rtpengine not converting encrypted media to >> normal. >> >> if (isflagset(SRC_WS) && isbflagset(DST_WS)) { >> $var(rtpengine_flags) = "ICE=force-relay DTLS=passive"; >> } else if (isflagset(SRC_WS) && !isbflagset(DST_WS)) { >> $var(rtpengine_flags) = "RTP/AVP replace-session-connection >> replace-origin ICE=remove"; >> } else if (!isflagset(SRC_WS) && isbflagset(DST_WS)) { >> $var(rtpengine_flags) = "UDP/TLS/RTP/SAVPF ICE=force"; >> } else if (!isflagset(SRC_WS) && !isbflagset(DST_WS)) { >> $var(rtpengine_flags) = "RTP/AVP/SAVP replace-session-connection >> replace-origin ICE=remove"; >> } >> >> rtpengine_offer("$var(rtpengine_flags)"); >> >> На пт, 28.06.2019 г. в 16:38 ч. Johan De Clercq >> написа: >> >>> If goes to provider: rtp/avp >>> Else rtp/savp >>> >>> So put your parameters in a var before calling rtpengine >>> >>> On Fri, 28 Jun 2019, 13:46 Dragomir Haralambiev, >>> wrote: >>> >>>> Hi, >>>> >>>> Thanks for your reply. >>>> >>>> Yes I use rtpengine_offer like this: >>>> rtpengine_offer("RTP/AVP/SAVP replace-session-connection replace-origin >>>> ICE=remove") >>>> >>>> In this case Opensips + Rtpengine send INVITE to ITSP with Media >>>> Protocol: RTP/SAVP, >>>> But ITSP not supported RTP/SAVP (they supported only RTP/AVP). >>>> >>>> I'm looking for a way to setup Opensips to change Media Protocol from >>>> RTP/SAVP to RTP/AVP. >>>> It means converting encrypted media to normal. >>>> >>>> Best regards, >>>> Dragomir >>>> >>>> >>>> На пт, 28.06.2019 г. в 10:52 ч. johan de clercq >>>> написа: >>>> >>>>> Change ruri to transport:udp. >>>>> >>>>> >>>>> >>>>> Start the params that you give to rtpengine_offer or answer with >>>>> RTP/AVP or RTP/SAVP accordingly. >>>>> >>>>> >>>>> >>>>> *From:* Users *On Behalf Of *Dragomir >>>>> Haralambiev >>>>> *Sent:* Thursday, June 27, 2019 10:36 PM >>>>> *To:* OpenSIPS users mailling list >>>>> *Subject:* [OpenSIPS-Users] How to change media protocol? >>>>> >>>>> >>>>> >>>>> Hello, >>>>> >>>>> I have OpenSips + rtpengine. >>>>> Opensips receive INVITE with Media Protocol: RTP/SAVP >>>>> How to setup Opensips to forward INVITE to ITSP with Media Protocol: >>>>> RTP/AVP. Like this scheme: >>>>> >>>>> >>>>> INVITE with Media Protocol: RTP/SAVP --> (OpenSips +rtpengine) >>>>> ---->INVITE with Media Protocol: RTP/AVP ---> ITSP >>>>> >>>>> >>>>> >>>>> 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 >>> >> _______________________________________________ >> 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 Ben.Newlin at genesys.com Fri Jun 28 11:38:01 2019 From: Ben.Newlin at genesys.com (Ben Newlin) Date: Fri, 28 Jun 2019 15:38:01 +0000 Subject: [OpenSIPS-Users] Feature request - pseudo-variable for destination IP address Message-ID: <9D325F82-E29F-4E7A-98F7-40E229D7486E@genesys.com> As far as I know, the equivalent variable to $si on the destination side is either $dd, which may not always be set, or $rd. Those are not guaranteed to be IP addresses, however. If DNS is being used, I don't believe OpenSIPS provides the results of the DNS lookup to the script in any variable, so I don't think there is a way to find the actual IP aside from doing your own DNS lookup (or possibly using the dns_cache module and snooping the cache, but I have had issues with this module in the past.) Ben Newlin On 6/28/19, 10:16 AM, "Users on behalf of rob.dyck at telus.net" wrote: Unfortunately the address of the interface where the request was receeived is private. I am using 1 to 1 NAT. ----- Original Message ----- From: "Ovidiu Sas" To: "OpenSIPS users mailling list" Sent: Thursday, June 27, 2019 3:31:34 PM Subject: Re: [OpenSIPS-Users] Feature request - pseudo-variable for destination IP address Check out the $Ri pvar: https://www.opensips.org/Documentation/Script-CoreVar-3-0#toc78 -ovidiu On Thu, Jun 27, 2019 at 6:23 PM rob.dyck at telus.net wrote: > > I was looking for something similar to the $si PV but for the destination IP address. Either it doesn't exist or I am blind. I can't find things in the refrigerator either. > > The motivation. > > I have a working instance of Opensips with a basic residential configuration. I extended it to allow calling UAs on the LAN from the outside. It is a typical residential LAN without a fixed IP address. Dynamic DNS is working for me. I read the tutorial about Opensips behind NAT. Following the recommendations there I was able to setup rtpproxy, the advertised address and an alias for my Opensips. Initial testing using a softphone on a laptop using either WiFi or a mobile phone tethered to the laptop worked well. However it seems that some UAs will not accept a domain name in the SDP connection. The UAs that failed could be made to work by coding in an IP address. This is not a satisfactory solution because the router's address may chaange. There is probably some convoluted way to import the needed address into the script. A pseudo-variable representing the destination IP address of the received INVITE or 200 OK could then be passed as the advertised address to the rtpproxy module. > > Thank you for having a look. > Rob > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- VoIP Embedded, Inc. http://www.voipembedded.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 From yuri.ritvin at gmail.com Fri Jun 28 12:21:17 2019 From: yuri.ritvin at gmail.com (Yuri Ritvin) Date: Fri, 28 Jun 2019 12:21:17 -0400 Subject: [OpenSIPS-Users] Users Digest, Vol 131, Issue 82 In-Reply-To: References: Message-ID: You may try this: https://www.opensips.org/Documentation/Script-Tran-2-4#ip.resolve On Fri, Jun 28, 2019 at 12:00 PM 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. Re: Feature request - pseudo-variable for destination IP > address (Ben Newlin) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 28 Jun 2019 15:38:01 +0000 > From: Ben Newlin > To: OpenSIPS users mailling list > Subject: Re: [OpenSIPS-Users] Feature request - pseudo-variable for > destination IP address > Message-ID: <9D325F82-E29F-4E7A-98F7-40E229D7486E at genesys.com> > Content-Type: text/plain; charset=UTF-8 > > As far as I know, the equivalent variable to $si on the destination side > is either $dd, which may not always be set, or $rd. Those are not > guaranteed to be IP addresses, however. If DNS is being used, I don't > believe OpenSIPS provides the results of the DNS lookup to the script in > any variable, so I don't think there is a way to find the actual IP aside > from doing your own DNS lookup (or possibly using the dns_cache module and > snooping the cache, but I have had issues with this module in the past.) > > Ben Newlin > > On 6/28/19, 10:16 AM, "Users on behalf of rob.dyck at telus.net" < > users-bounces at lists.opensips.org on behalf of rob.dyck at telus.net> wrote: > > Unfortunately the address of the interface where the request was > receeived is private. I am using 1 to 1 NAT. > > ----- Original Message ----- > From: "Ovidiu Sas" > To: "OpenSIPS users mailling list" > Sent: Thursday, June 27, 2019 3:31:34 PM > Subject: Re: [OpenSIPS-Users] Feature request - pseudo-variable for > destination IP address > > Check out the $Ri pvar: > https://www.opensips.org/Documentation/Script-CoreVar-3-0#toc78 > > -ovidiu > > On Thu, Jun 27, 2019 at 6:23 PM rob.dyck at telus.net > wrote: > > > > I was looking for something similar to the $si PV but for the > destination IP address. Either it doesn't exist or I am blind. I can't find > things in the refrigerator either. > > > > The motivation. > > > > I have a working instance of Opensips with a basic residential > configuration. I extended it to allow calling UAs on the LAN from the > outside. It is a typical residential LAN without a fixed IP address. > Dynamic DNS is working for me. I read the tutorial about Opensips behind > NAT. Following the recommendations there I was able to setup rtpproxy, the > advertised address and an alias for my Opensips. Initial testing using a > softphone on a laptop using either WiFi or a mobile phone tethered to the > laptop worked well. However it seems that some UAs will not accept a domain > name in the SDP connection. The UAs that failed could be made to work by > coding in an IP address. This is not a satisfactory solution because the > router's address may chaange. There is probably some convoluted way to > import the needed address into the script. A pseudo-variable representing > the destination IP address of the received INVITE or 200 OK could then be > passed as the advertised address to the rtpproxy module. > > > > Thank you for having a look. > > Rob > > > > _______________________________________________ > > Users mailing list > > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > -- > VoIP Embedded, Inc. > http://www.voipembedded.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 > > > > > ------------------------------ > > 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 131, Issue 82 > ************************************** > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob.dyck at telus.net Fri Jun 28 19:23:02 2019 From: rob.dyck at telus.net (Robert Dyck) Date: Fri, 28 Jun 2019 16:23:02 -0700 Subject: [OpenSIPS-Users] Feature request - pseudo-variable for destination IP address In-Reply-To: <1061883766.59177749.1561674937246.JavaMail.zimbra@mailid.telus.net> References: <1084479194.59156276.1561674119097.JavaMail.zimbra@mailid.telus.net> <1061883766.59177749.1561674937246.JavaMail.zimbra@mailid.telus.net> Message-ID: <9524250.tynBcp5C2U@blacky.mylan> Thank you Yuri Ritvin {ip.resolve} transform works for me. The example given in the documentation is misleading. You can't use a literal string. You need to put into a var of some sort and then transform it. On Thursday, June 27, 2019 3:35:37 P.M. PDT rob.dyck at telus.net wrote: > On second thought it probably isn't poosible to do in any direct way because > the information is lost in the router. The only possible way is a DNS > query. > > ----- Original Message ----- > From: "rob dyck" > To: users at lists.opensips.org > Sent: Thursday, June 27, 2019 3:21:59 PM > Subject: Feature request - pseudo-variable for destination IP address > > I was looking for something similar to the $si PV but for the destination IP > address. Either it doesn't exist or I am blind. I can't find things in the > refrigerator either. > > The motivation. > > I have a working instance of Opensips with a basic residential > configuration. I extended it to allow calling UAs on the LAN from the > outside. It is a typical residential LAN without a fixed IP address. > Dynamic DNS is working for me. I read the tutorial about Opensips behind > NAT. Following the recommendations there I was able to setup rtpproxy, the > advertised address and an alias for my Opensips. Initial testing using a > softphone on a laptop using either WiFi or a mobile phone tethered to the > laptop worked well. However it seems that some UAs will not accept a domain > name in the SDP connection. The UAs that failed could be made to work by > coding in an IP address. This is not a satisfactory solution because the > router's address may chaange. There is probably some convoluted way to > import the needed address into the script. A pseudo-variable representing > the destination IP address of the received INVITE or 200 OK could then be > passed as the advertised address to the rtpproxy module. > > Thank you for having a look. > Rob > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From goup2010 at gmail.com Sun Jun 30 03:43:03 2019 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Sun, 30 Jun 2019 10:43:03 +0300 Subject: [OpenSIPS-Users] rtpengine_offer error Message-ID: Hello, >From rtpengine_offer manual I see: RTP/AVP, RTP/SAVP, RTP/AVPF, RTP/SAVPF - these serve as an alternative, more explicit way to select between the different RTP protocols and profiles supported by the RTP proxy. For example, giving the flag “RTP/SAVPF” has the same effect as giving the two flags “SRTP AVPF”. When use this: rtpengine_offer("RTP/AVP,RTP/SAVP replace-session-connection replace-origin ICE=remove"); I receive follow error: ERROR:rtpengine:parse_flags: error processing flag `RTP/AVP,RTP/SAVP': unknown flag Where is problem? Best regards, Dragomir -------------- next part -------------- An HTML attachment was scrubbed... URL: From olle at zaark.com Sun Jun 30 03:50:33 2019 From: olle at zaark.com (Olle Frimanson) Date: Sun, 30 Jun 2019 09:50:33 +0200 Subject: [OpenSIPS-Users] rtpengine_offer error In-Reply-To: References: Message-ID: <420DE8DA-53EA-413B-819E-51886A22A7D0@zaark.com> Try replace comma with space rtp/avp rtp/save I’m not sure of you can offer both at the same time Br Olle Skickat från min iPhone > 30 juni 2019 kl. 09:43 skrev Dragomir Haralambiev : > > Hello, > > From rtpengine_offer manual I see: > > RTP/AVP, RTP/SAVP, RTP/AVPF, RTP/SAVPF - these serve as an alternative, more explicit way to select between the different RTP protocols and profiles supported by the RTP proxy. For example, giving the flag “RTP/SAVPF” has the same effect as giving the two flags “SRTP AVPF”. > > When use this: > rtpengine_offer("RTP/AVP,RTP/SAVP replace-session-connection replace-origin ICE=remove"); > > I receive follow error: > ERROR:rtpengine:parse_flags: error processing flag `RTP/AVP,RTP/SAVP': unknown flag > > Where is problem? > > Best regards, > Dragomir > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From goup2010 at gmail.com Sun Jun 30 04:00:46 2019 From: goup2010 at gmail.com (Dragomir Haralambiev) Date: Sun, 30 Jun 2019 11:00:46 +0300 Subject: [OpenSIPS-Users] rtpengine_offer error In-Reply-To: <420DE8DA-53EA-413B-819E-51886A22A7D0@zaark.com> References: <420DE8DA-53EA-413B-819E-51886A22A7D0@zaark.com> Message-ID: When use comma Opensips get second one. На нд, 30.06.2019 г. в 10:53 ч. Olle Frimanson написа: > Try replace comma with space > rtp/avp rtp/save > I’m not sure of you can offer both at the same time > > Br Olle > > Skickat från min iPhone > > > 30 juni 2019 kl. 09:43 skrev Dragomir Haralambiev : > > > > Hello, > > > > From rtpengine_offer manual I see: > > > > RTP/AVP, RTP/SAVP, RTP/AVPF, RTP/SAVPF - these serve as an alternative, > more explicit way to select between the different RTP protocols and > profiles supported by the RTP proxy. For example, giving the flag > “RTP/SAVPF” has the same effect as giving the two flags “SRTP AVPF”. > > > > When use this: > > rtpengine_offer("RTP/AVP,RTP/SAVP replace-session-connection > replace-origin ICE=remove"); > > > > I receive follow error: > > ERROR:rtpengine:parse_flags: error processing flag `RTP/AVP,RTP/SAVP': > unknown flag > > > > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From virendra at cloud-connect.in Wed Jun 26 07:05:13 2019 From: virendra at cloud-connect.in (Virendra Bhati) Date: Wed, 26 Jun 2019 16:35:13 +0530 Subject: [OpenSIPS-Users] OpenSIPs 3.0 Crash issue Message-ID: Dear Team, We have setup Opensips 3.0 stable version for stress testing. We are invoking calls from SIPp to Opensips. We noticed after 600 CC with 10 CPS Opensips crash. I have attached files for more details of DUMP. Below is the call flow (Leg A) SIPp (UAC)---> OpenSIPs(5070) ---> Freeswitch(5060) (Leg B) Freeswitch(5060) --> OpenSIPs(5070) ---> SIPp (UAS) OpenSIPs and Freeswitch is running on same machine with different ports. As per our initial understanding it seems there is an issue with Memory. Please help me on it, -- Regards Virendra Bhati -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: Inside INVITE Call si=192.168.1.25 , sp=5080 , oP=udp ,avp=2 Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: call FS Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: NOW rd=192.168.1.98 , rp=5060 , rP=udp, ru=sip:1046 at 192.168.1.98:5060 du=sip:192.168.1.98:5060 Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: new branch at sip:1046 at 192.168.1.98:5060 Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: inside =====> Handle_nat Reply Status:200 and User Agent: Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24815]: inside =====> Handle_nat Reply Status:200 and User Agent: FreeSWITCH-mod_sofia/1.8.5~64bit Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: Called [ACK] with [-2] Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: Called [ACK] with [-2] Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: inside =====> Handle_nat Reply Status:200 and User Agent: FreeSWITCH-mod_sofia/1.8.5~64bit Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: ERROR:core:fm_malloc: not enough free shm memory (357200 bytes left, need 6712), please increase the "-m" command line parameter! Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: INFO:core:fm_malloc: attempting defragmentation... Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: INFO:core:fm_malloc: unable to alloc a big enough fragment! Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: ERROR:tm:t_uac: short of cell shmem Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: ERROR:pua:send_publish_int: failed to send PUBLISH Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: ERROR:pua_dialoginfo:dialog_publish: sending publish failed for pres_uri [sip:1740 at 192.168.1.98:5061] to server [sip:192.168.1.25:5070] Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: ERROR:core:fm_malloc: not enough free shm memory (356864 bytes left, need 6712), please increase the "-m" command line parameter! Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: INFO:core:fm_malloc: attempting defragmentation... Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: INFO:core:fm_malloc: unable to alloc a big enough fragment! Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: ERROR:tm:t_uac: short of cell shmem Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: ERROR:pua:send_publish_int: failed to send PUBLISH Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: ERROR:pua_dialoginfo:dialog_publish: sending publish failed for pres_uri [sip:1240 at 192.168.1.25:5070] to server [sip:192.168.1.25:5070] Jun 26 14:31:13 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: Called [ACK] with [-2] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: inside =====> Handle_nat Reply Status:500 and User Agent: FreeSWITCH-mod_sofia/1.8.5~64bit Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24815]: inside =====> Handle_nat Reply Status:500 and User Agent: FreeSWITCH-mod_sofia/1.8.5~64bit Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24815]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24811]: inside =====> Handle_nat Reply Status:200 and User Agent: FreeSWITCH-mod_sofia/1.8.5~64bit Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: ERROR:core:fm_malloc: not enough free shm memory (349984 bytes left, need 6712), please increase the "-m" command line parameter! Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: INFO:core:fm_malloc: attempting defragmentation... Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: INFO:core:fm_malloc: unable to alloc a big enough fragment! Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: ERROR:tm:new_t: out of mem Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: ERROR:tm:t_newtran: new_t failed Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: inside =====> Handle_nat Reply Status:500 and User Agent: FreeSWITCH-mod_sofia/1.8.5~64bit Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24809]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24809]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24815]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24814]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24814]: message repeated 2 times: [ Called [BYE] with [-1]] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: inside =====> Handle_nat Reply Status:100 and User Agent: FreeSWITCH-mod_sofia/1.8.5~64bit Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24809]: Get group is 2 and AVP group 2 Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24809]: Inside INVITE Call rd=192.168.1.25 , rp=5070 , rP=udp, ru=sip:1051 at 192.168.1.25:5070 du= Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24809]: Inside INVITE Call si=192.168.1.25 , sp=5080 , oP=udp ,avp=2 Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24809]: call FS Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24809]: NOW rd=192.168.1.98 , rp=5060 , rP=udp, ru=sip:1051 at 192.168.1.98:5060 du=sip:192.168.1.98:5060 Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24809]: ERROR:core:fm_malloc: not enough free shm memory (345696 bytes left, need 6712), please increase the "-m" command line parameter! Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24809]: INFO:core:fm_malloc: attempting defragmentation... Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24809]: INFO:core:fm_malloc: unable to alloc a big enough fragment! Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24809]: ERROR:tm:new_t: out of mem Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24809]: ERROR:tm:t_newtran: new_t failed Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24811]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24808]: WARNING:core:timer_ticker: timer task already scheduled 540050 ms ago (now 660370 ms), delaying execution Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: inside =====> Handle_nat Reply Status:487 and User Agent: FreeSWITCH-mod_sofia/1.8.5~64bit Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: inside =====> Handle_nat Reply Status:487 and User Agent: FreeSWITCH-mod_sofia/1.8.5~64bit Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24818]: CRITICAL:core:sig_usr: segfault in process pid: 24818, id: 14 Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24810]: message repeated 2 times: [ Called [BYE] with [-1]] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24812]: inside =====> Handle_nat Reply Status:200 and User Agent: FreeSWITCH-mod_sofia/1.8.5~64bit Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24813]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24811]: inside =====> Handle_nat Reply Status:100 and User Agent: FreeSWITCH-mod_sofia/1.8.5~64bit Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24811]: Called [BYE] with [-1] Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24808]: WARNING:core:utimer_ticker: utimer task already scheduled 100 ms ago (now 660570 ms), delaying execution Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:core:handle_sigs: child process 24818 exited by a signal 11 Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:core:handle_sigs: core was generated Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:core:handle_sigs: terminating due to SIGCHLD Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24808]: INFO:core:sig_usr: signal 15 received Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24805]: INFO:core:sig_usr: signal 15 received Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24807]: INFO:core:sig_usr: signal 15 received Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:core:shutdown_opensips: process 1(24805) [MI FIFO] terminated, still waiting for 16 more Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:core:shutdown_opensips: process 2(24806) [FS Manager] terminated, still waiting for 15 more Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:core:shutdown_opensips: process 16(24820) [TCP receiver] terminated, still waiting for 14 more Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:core:shutdown_opensips: process 3(24807) [time_keeper] terminated, still waiting for 13 more Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:core:shutdown_opensips: process 4(24808) [timer] terminated, still waiting for 12 more Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:core:shutdown_opensips: process 19(24824) [TCP main] terminated, still waiting for 11 more Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:core:shutdown_opensips: process 17(24821) [Timer handler] terminated, still waiting for 10 more Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:core:shutdown_opensips: process 7(24811) [SIP receiver udp:192.168.1.25:5070] terminated, still waiting for 9 more Jun 26 14:31:14 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:core:shutdown_opensips: process 18(24822) [Timer handler] terminated, still waiting for 8 more Jun 26 14:31:19 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:core:cleanup: cleanup Jun 26 14:31:19 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:db_mysql:switch_state_to_disconnected: disconnect event for 0x7f7525cf4550 Jun 26 14:31:19 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:db_mysql:reset_all_statements: resetting all statements on connection: (0x7f7525cf5198) 0x7f7525cf4550 Jun 26 14:31:19 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: INFO:db_mysql:connect_with_retry: re-connected successful for 0x7f7525cf4550 Jun 26 14:31:44 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: NOTICE:presence:destroy: destroy module ... Jun 26 14:31:55 cloudconnect-PowerEdge-T30 /usr/local/sbin/opensips[24804]: CRITICAL:core:fm_free: freeing already freed shm pointer (0x7f752506e138), first free: (null): #001(0) - aborting! -------------- next part -------------- A non-text attachment was scrubbed... Name: opensips_BT_FULL Type: application/octet-stream Size: 17626 bytes Desc: not available URL: From spanda at 3clogic.com Fri Jun 28 05:09:53 2019 From: spanda at 3clogic.com (Sasmita Panda) Date: Fri, 28 Jun 2019 14:39:53 +0530 Subject: [OpenSIPS-Users] I need some help in websocket connection error . In-Reply-To: <0455befb-77af-3c0f-6dc7-b9282646d7a2@opensips.org> References: <3cd8b1dd-d450-7798-7f0c-d9f639481fab@opensips.org> <0455befb-77af-3c0f-6dc7-b9282646d7a2@opensips.org> Message-ID: I am sure the client supports TLSv1.2 version . That was confirmed . I am not sure about the ciphers . I have to ask them . modparam("tls_mgm", "ciphers_list", "AES256-GCM-SHA384,AES256- SHA256,AES256-SHA,CAMELLIA256-SHA,AES128-SHA,CAMELLIA128-SHA,RC4-SHA") Is this the list of whitelisted ciphers ? *Thanks & Regards* *Sasmita Panda* *Senior Network Testing and Software Engineer* *3CLogic , ph:07827611765* On Fri, Jun 28, 2019 at 1:33 PM Răzvan Crainea wrote: > Hi, Sasmita! > > I see that you require TLSv1.2 authentication method - are you sure your > clients do support this version? A similar problem can be with the > ciphers, are you sure your clients support the whitelisted ciphers? As > you do not enforce anything, this might be true, but this is something > you should double-check. Besides that, I don't have any other ideas. > > Best regards, > Răzvan > > On 6/27/19 9:02 AM, Sasmita Panda wrote: > > Hi, > > > > SSL miss configuration in client side or in opensips side . I think I > > have done the configuration right . > > > > listen=wss:192.168.143.20:443 > > loadmodule "tls_mgm.so" > > modparam("tls_mgm", "tls_method", "tlsv1_2") > > modparam("tls_mgm", "verify_cert", "0") > > modparam("tls_mgm", "require_cert", "0") > > modparam("tls_mgm", "certificate", > > "/usr/local/etc/opensips/tls/3ccloudwebrtc2019.crt") > > modparam("tls_mgm", "private_key", > > "/usr/local/etc/opensips/tls/3ccloud.key") > > modparam("tls_mgm", "ca_list", > > "/usr/local/etc/opensips/tls/rootCA/cacert.pem") > > loadmodule "proto_wss.so" > > modparam("proto_wss", "wss_port", 443) > > > > This is for wss . Is there anything I am missing in configuration ? > > > > > > */Thanks & Regards/* > > /Sasmita Panda/ > > /Senior Network Testing and Software Engineer/ > > /3CLogic , ph:07827611765/ > > > > > > On Wed, Jun 26, 2019 at 8:10 PM Răzvan Crainea > > wrote: > > > > TBH, all I can see in the logs you sent is that a connection was > > terminated (without even being started), and a connection that was > > started, but closed by the client. So in order to understand what's > > happening, you need to understand why the client is closing the > > connection. Check logs, documentation, anything, but this doesn't > seem > > to be related to OpenSIPS, it looks like some SSL misconfiguration. > > > > Best regards, > > Răzvan > > > > On 6/26/19 4:24 PM, Sasmita Panda wrote: > > > Is there any update on this issue . How I can solve this error > > message > > > from my opensips logs . > > > > > > > > > */Thanks & Regards/* > > > /Sasmita Panda/ > > > /Senior Network Testing and Software Engineer/ > > > /3CLogic , ph:07827611765/ > > > > > > > > > On Tue, Jun 25, 2019 at 3:48 PM Sasmita Panda > > > > >> wrote: > > > > > > I have tried to take ssldump in the webrtc server in run time > . > > > > > > New TCP connection #19: 192.168.1.y(48530) <-> > 192.168.0.x(443) > > > 19 0.0011 (0.0011) C>S TCP FIN > > > 19 0.0013 (0.0001) S>C TCP FIN > > > > > > New TCP connection #20: 192.168.0.y(52975) <-> > 192.168.0.x(443) > > > 20 1 0.0006 (0.0006) C>S Handshake ClientHello > > > 20 2 0.0008 (0.0002) S>C Handshake ServerHello > > > 20 3 0.0008 (0.0000) S>C Handshake Certificate > > > 20 4 0.0008 (0.0000) S>C Handshake ServerHelloDone > > > 20 5 0.0020 (0.0011) C>S Handshake ClientKeyExchange > > > 20 6 0.0020 (0.0000) C>S ChangeCipherSpec > > > 20 7 0.0020 (0.0000) C>S Handshake > > > 20 8 0.0036 (0.0015) S>C Handshake20 9 0.0036 (0.0000) > S>C > > > ChangeCipherSpec > > > 20 10 0.0036 (0.0000) S>C Handshake > > > 20 11 0.0042 (0.0006) C>S Alert > > > 20 0.0042 (0.0000) C>S TCP FIN > > > 20 0.0043 (0.0000) S>C TCP FIN > > > > > > The portion I marked in red whenever appear there is error in > > > opensips logs . For below portion the connection was > accepted . > > > > > > I am not even getting any error in my browser side . How I > will > > > debug this ? please help . > > > > > > */Thanks & Regards/* > > > /Sasmita Panda/ > > > /Senior Network Testing and Software Engineer/ > > > /3CLogic , ph:07827611765/ > > > > > > > > > On Fri, Jun 14, 2019 at 2:51 PM Callum Guy > > > > > > >> wrote: > > > > > > You might find that a tcpdump is the only way to get to > grips > > > with the underlying issue. > > > > > > Having said that I wonder if there is any chance that the > > > connection isn't accepting simply due to a cipher > > > incompatibility. Are you setting a cipher list that you > know > > > your clients accept? Maybe try: > > > > > > modparam("tls_mgm", "ciphers_list", > > > > > > "AES256-GCM-SHA384,AES256-SHA256,AES256-SHA,CAMELLIA256-SHA,AES128-SHA,CAMELLIA128-SHA,RC4-SHA") > > > > > > > > > On Fri, 14 Jun 2019 at 09:17, Sasmita Panda > > > > > >> > > wrote: > > > > > > I had a dedicated server for 1 Client . When that > client > > > faces the issue I started looking into the logs . And > > this > > > is what the error I got . > > > > > > but latter on when I saw other servers which is > > getting used > > > by different client in that logs also same error > coming > > > everyday . > > > > > > As a conclusion its happening with everybody . > > > > > > Below is the configuration . > > > > > > modparam("tls_mgm", "tls_method", "tlsv1_2") > > > modparam("tls_mgm", "verify_cert", "0") > > > modparam("tls_mgm", "require_cert", "0") > > > modparam("tls_mgm", "certificate", > > > "/usr/etc/opensips/tls/3ccloudwebrtc2019.crt") > > > modparam("tls_mgm", "private_key", > > > "/usr/etc/opensips/tls/3ccloud.key") > > > modparam("tls_mgm", "ca_list", > > > "/usr/etc/opensips/tls/rootCA/cacert.pem") > > > > > > > > > > > > */Thanks & Regards/* > > > /Sasmita Panda/ > > > /Senior Network Testing and Software Engineer/ > > > /3CLogic , ph:07827611765/ > > > > > > > > > On Thu, Jun 13, 2019 at 6:50 PM Răzvan Crainea > > > > > >> wrote: > > > > > > Can you trace the SSL traffic between the two > > endpoints? > > > Perhaps the SSL > > > header give you a reason for not accepting the > > connection. > > > Is this happening only for certain clients, or > > for everyone? > > > Are you requiring any certificates validation? > > > > > > Best regards, > > > Răzvan > > > > > > On 6/12/19 3:34 PM, Sasmita Panda wrote: > > > > I am using opensips 2.2 > > > > version: opensips 2.2.4 (x86_64/linux) > > > > > > > > I am using the proto_wss and tls_mgm module for > > > establishing websocket > > > > connection . > > > > > > > > I am getting bellow error again and again . > > Whats the > > > reson behind this > > > > and how can I solve this problem ? > > > > > > > > > > > > Jun 10 00:00:15 localhost > > /usr/sbin/opensips[1548]: > > > > INFO:core:probe_max_sock_buff: using snd > > buffer of 416 kb > > > > Jun 10 00:00:15 localhost > > /usr/sbin/opensips[1548]: > > > > INFO:core:init_sock_keepalive: TCP keepalive > > enabled > > > on socket 96 > > > > Jun 10 00:00:15 localhost > > /usr/sbin/opensips[1546]: > > > > ERROR:proto_wss:tls_accept: New TLS connection > > from > > > 192.168.160.6:58616 > > > > > > failed to accept > > > > Jun 10 00:00:15 localhost > > /usr/sbin/opensips[1546]: > > > > ERROR:proto_wss:wss_read_req: cannot fix read > > connection > > > > Jun 10 00:00:17 localhost > > /usr/sbin/opensips[1548]: > > > > INFO:core:probe_max_sock_buff: using snd > > buffer of 416 kb > > > > Jun 10 00:00:17 localhost > > /usr/sbin/opensips[1548]: > > > > INFO:core:init_sock_keepalive: TCP keepalive > > enabled > > > on socket 96 > > > > Jun 10 00:00:17 localhost > > /usr/sbin/opensips[1546]: > > > > ERROR:proto_wss:tls_accept: New TLS connection > > from > > > 192.168.175.59:12918 > > > > > > failed to accept > > > > Jun 10 00:00:17 localhost > > /usr/sbin/opensips[1546]: > > > > ERROR:proto_wss:wss_read_req: cannot fix read > > connection > > > > > > > > > > > > Please do help . > > > > > > > > > > > > > > > > */Thanks & Regards/* > > > > /Sasmita Panda/ > > > > /Senior 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 > > > > > > > > > > -- > > > Răzvan Crainea > > > OpenSIPS Core 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 > > > > > > > > > > > > *^0333 332 0000 | www.x-on.co.uk > > | > > > _**_^ > > > > > * > > > > > > X-on is a trading name of Storacall Technology Ltd a > limited > > > company registered in England and Wales. > > > Registered Office : Avaland House, 110 London Road, > Apsley, > > > Hemel Hempstead, Herts, HP3 9SD. Company Registration No. > > 2578478. > > > The information in this e-mail is confidential and for > use by > > > the addressee(s) only. If you are not the intended > recipient, > > > please notify X-on immediately on +44(0)333 332 0000 and > > delete the > > > message from your computer. If you are not a named > > addressee you > > > must not use, disclose, disseminate, distribute, copy, > > print or > > > reply to this email. Views or opinions expressed by an > > individual > > > within this email may not necessarily reflect the views > > of X-on > > > or its associated companies. Although X-on routinely > > screens for > > > viruses, addressees should scan this email and any > > attachments > > > for viruses. X-on makes no representation or warranty as > > to the > > > absence of viruses in this email or any attachments. > > > > > > _______________________________________________ > > > 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 > > > > > > > -- > > Răzvan Crainea > > OpenSIPS Core 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 > > > > -- > Răzvan Crainea > OpenSIPS Core 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 Phil.Whitener at genesys.com Fri Jun 28 12:40:21 2019 From: Phil.Whitener at genesys.com (Phil Whitener) Date: Fri, 28 Jun 2019 16:40:21 +0000 Subject: [OpenSIPS-Users] OpenSIPs with mutual TLS and client CA lists Message-ID: I have looked into using OpenSIPS with optional mutual TLS. In short, using verify_cert=1 & require_cert=0. In this case, the OpenSIPs acting as a server sends the TLS "Certificate Request" during the handshake and based on the response the OpenSIPs server decides whether to continue (as either server-only TLS or mutual TLS) or terminate the connection. I have experienced more failures than expected as some remote endpoints are attempting to satisfy the certificate request by sending any potential certificate that meets the requested criteria. During the "Certificate Request" there is an optional parameter allowing the trusted certificate authority distinguished name to be provided in the request. This is defined in OpenSSL's SSL_CTX_set_client_CA_list. Without this directive defined the remote client may choose to send a client certificate that meets the only defined parameter (Certificate types); however, in many cases OpenSIPs may reject the client selected certificate. It does not appear that OpenSIPs controls this optional parameter. I may have missed this definition in OpenSIPs. This may be a potential feature request. If it has been omitted, I feel that when OpenSIPs is acting as a TLS server, the existing parameter CA_LIST could be defined in the server domain to provide a set of trusted certificate authorities to pass along as the Certificate Request distinguished name. In this case the remote client peer that is not able to satisfy the scoped Certificate Request can then choose to proceed without mutual authentication and continue the handshake without offering a client certificate. RFC5246 7.4.6 Client Certificate https://tools.ietf.org/html/rfc5246#section-7.4.6 TLSv1 Record Layer: Handshake Protocol: Multiple Handshake Messages Content Type: Handshake (22) Version: TLS 1.0 (0x0301) Length: 14 Handshake Protocol: Certificate Request Handshake Type: Certificate Request (13) Length: 6 Certificate types count: 3 Certificate types (3 types) Certificate type: RSA Sign (1) Certificate type: DSS Sign (2) Certificate type: ECDSA Sign (64) Distinguished Names Length: 0 Handshake Protocol: Server Hello Done Handshake Type: Server Hello Done (14) Length: 0 OpenSSL SSL_CTX_set_client_CA_list https://www.openssl.org/docs/man1.0.2/man3/SSL_CTX_set_client_CA_list.html Thank you for your review, Phil Whitener phil.whitener at genesys.com -------------- next part -------------- An HTML attachment was scrubbed... URL: