From callum.guy at x-on.co.uk Tue Aug 1 13:23:07 2023 From: callum.guy at x-on.co.uk (Callum Guy) Date: Tue, 1 Aug 2023 14:23:07 +0100 Subject: [OpenSIPS-Users] Dialog contact not updating until answer Message-ID: Hi All, I've observed a behaviour (OpenSIPs 3.2.4) where the contact stored against an active dialog is not populated until the call is answered. Using opensips-cli dlg_list I see the following: Ringing - https://gist.github.com/spacetourist/2502f6b76a95bb2f500fda5291e1c93b Answered - https://gist.github.com/spacetourist/81b9e19de14a04aeff7f1f7b8965e2e5 During ringing we have: - "state": 2 - CALLEES > "callee_contact": "", Once answered we have: - "state": 4 - CALLEES > "callee_contact": "sip:b2o80qss at 77.95.114.132:45656;transport=ws", This is problematic for me as I'm working on a system to prevent duplicate registrations from an AoR (sip:6190051 at sk-1.rtc.sip.net) whilst preventing other instances from overruling and taking ownership of the session by blocking registrations from separate contacts when a call is ongoing. The exact scenario where I'm currently seeing errors is when an active contact (i.e. sip:b2o80qss at 77.95.114.132:45656;transport=ws) issues a re-REGISTER during call setup. I use get_dialogs_by_profile() in OpenSIPs to track sessions against the AoR and loop through any active dialogs associated whenever a call or registration comes in. Using this approach has allowed me to block other devices from creating a second registration however the lookup is currently failing during the ringing part of the session as the contact cannot be checked. Is there a reason why callee_contact cannot be updated immediately when the session begins? Is this to accommodate branching or similar? I'll review alternative approaches whilst awaiting a reply however it would be great if there was a path for me to solve this issue with my current approach! Thanks, Callum P.S. if this makes more sense as a Github issue then please let me know, I'm not sure where is best to ask! -- *0333 332 0000  |  x-on.co.uk   |   **      **  |  **Practice Index Reviews * *Our new office address: 22 Riduna Park, Melton IP12 1QT.* X-on is a trading name of X-on Health Ltd a limited company registered in England and Wales. Registered Office : Glebe Farm, Down Street, Dummer, Basingstoke, Hampshire, England RG25 2AD. 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. From razvan at opensips.org Tue Aug 1 13:32:53 2023 From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=) Date: Tue, 1 Aug 2023 16:32:53 +0300 Subject: [OpenSIPS-Users] Issue with stir and shaken crl_list In-Reply-To: <6B3CB7FE-F20C-431F-A14B-20838691A0FA@free.fr> References: <657BF0AB-6533-4F70-A6D7-67A004437B6C@free.fr> <6B3CB7FE-F20C-431F-A14B-20838691A0FA@free.fr> Message-ID: <93268186-cfc5-090c-0b79-85311cff4b25@opensips.org> Hi, Alain! You are actually right, it looks like the crl_list and ca_dir cannot be dynamic :(. Could you please open a feature request for this, so we can keep them right, perhaps change them to a tls_mgm domain? Best regards, Răzvan Crainea OpenSIPS Core Developer / SIPhub CTO http://www.opensips-solutions.com / https://www.siphub.com On 7/28/23 16:45, Alain Bieuzent wrote: > sorry I wrote nonsense (again...) > In the French implementation of STIR/SHAKEN we must download certificate updates every day (only for crl_list). > In stir_shaken module documentation , there is no explanation how to put crl_list in db. > > Regards > > > Le 28/07/2023 15:39, « Users au nom de Alain Bieuzent » au nom de alain.bieuzent at free.fr > a écrit : > > > Hi Razvan, > > > I work on the same project as Mickael and we don't understand how the tls_mgm can help us in this case. > In the French implementation of STIR/SHAKEN we must download certificate updates every day (ca_list and crl_list). > How can these updates be considered in real time? > > > Regards > > > Le 27/07/2023 12:38, « Users au nom de Răzvan Crainea » > au nom de razvan at opensips.org >> a écrit : > > > > > Hi, Mickael! > > > > > The only way is to store certificates in database and reload the tls_mgm > module (using tls_reload). > > > > > Best regards, > > > > > Răzvan Crainea > OpenSIPS Core Developer / SIPhub CTO > http://www.opensips-solutions.com / https://www.siphub.com > > > > > On 7/26/23 16:38, Mickael Hubert wrote: >> Hi Razvan, >> another question about crl_list, when crl list changed, what is the best >> way to reload this list in OpenSIPS memory ? restart it ? or another way ? >> I know the crl_list can change each day, so if I have to restart >> opensips each day, it's not very practical. >> >> thanks in advance >> >> Le mar. 25 juil. 2023 à 14:47, Mickael Hubert > >> >>> a écrit : >> >> Hi Razvan, >> Thanks a lot. >> I loaded the CRL for CA and certs and opensips start correctly ;) >> >> Have a good day ! >> >> Le lun. 24 juil. 2023 à 16:07, Răzvan Crainea > >> >>> a écrit : >> >> Hi, Mickael! >> >> I don't have much experience with this, but a first search would >> point >> to this [1] answer, which seems reasonable to me: you need to >> provide >> the CRL of the entire path, not only of your intermediate cert. >> Did you >> try that? >> >> [1] https://stackoverflow.com/a/47398918 >> >> >> Best regards, >> >> Răzvan Crainea >> OpenSIPS Core Developer >> http://www.opensips-solutions.com >> >> >> On 7/19/23 15:47, Mickael Hubert wrote: >>> Hi all, >>> I'm working on stir and shaken, and I want to include all >> revoked >>> certificates. >>> I my list in DER format, I use this command to transform it >> to PEM format: >>> openssl crl -in man_crl.der -inform DER -outform PEM -out crl.pem >>> >>> there is no erreur, I can read pem format (crl.pem): >>> -----BEGIN X509 CRL----- >>> .... >>> -----END X509 CRL----- >>> >>> I configured opensips with this: >>> modparam("stir_shaken", "crl_list", >> "/etc/opensips/stir-shaken-ca/crl.pem") >>> >>> but I have an error: >>> ul 19 12:39:07 [12] INFO:stir_shaken:verify_callback: >> certificate >>> validation failed: unable to get certificate CRL >>> Jul 19 12:39:07 [12] INFO:stir_shaken:w_stir_verify: Invalid >> certificate >>> >>> Can you tell me, what is exactly the correct format please ? >>> >>> Thanks in advance ! >>> ++ >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org > >> >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org > >> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org > >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From alain.bieuzent at free.fr Tue Aug 1 14:04:15 2023 From: alain.bieuzent at free.fr (Alain Bieuzent) Date: Tue, 01 Aug 2023 16:04:15 +0200 Subject: [OpenSIPS-Users] Issue with stir and shaken crl_list In-Reply-To: <93268186-cfc5-090c-0b79-85311cff4b25@opensips.org> References: <657BF0AB-6533-4F70-A6D7-67A004437B6C@free.fr> <6B3CB7FE-F20C-431F-A14B-20838691A0FA@free.fr> <93268186-cfc5-090c-0b79-85311cff4b25@opensips.org> Message-ID: <34CF2799-B0A9-423E-9AFC-3034B6519B92@free.fr> Thaks Razvan, it's done Le 01/08/2023 15:35, « Users au nom de Răzvan Crainea » au nom de razvan at opensips.org > a écrit : Hi, Alain! You are actually right, it looks like the crl_list and ca_dir cannot be dynamic :(. Could you please open a feature request for this, so we can keep them right, perhaps change them to a tls_mgm domain? Best regards, Răzvan Crainea OpenSIPS Core Developer / SIPhub CTO http://www.opensips-solutions.com / https://www.siphub.com On 7/28/23 16:45, Alain Bieuzent wrote: > sorry I wrote nonsense (again...) > In the French implementation of STIR/SHAKEN we must download certificate updates every day (only for crl_list). > In stir_shaken module documentation , there is no explanation how to put crl_list in db. > > Regards > > > Le 28/07/2023 15:39, « Users au nom de Alain Bieuzent » > au nom de alain.bieuzent at free.fr >> a écrit : > > > Hi Razvan, > > > I work on the same project as Mickael and we don't understand how the tls_mgm can help us in this case. > In the French implementation of STIR/SHAKEN we must download certificate updates every day (ca_list and crl_list). > How can these updates be considered in real time? > > > Regards > > > Le 27/07/2023 12:38, « Users au nom de Răzvan Crainea » > >> au nom de razvan at opensips.org > >>> a écrit : > > > > > Hi, Mickael! > > > > > The only way is to store certificates in database and reload the tls_mgm > module (using tls_reload). > > > > > Best regards, > > > > > Răzvan Crainea > OpenSIPS Core Developer / SIPhub CTO > http://www.opensips-solutions.com / https://www.siphub.com > > > > > On 7/26/23 16:38, Mickael Hubert wrote: >> Hi Razvan, >> another question about crl_list, when crl list changed, what is the best >> way to reload this list in OpenSIPS memory ? restart it ? or another way ? >> I know the crl_list can change each day, so if I have to restart >> opensips each day, it's not very practical. >> >> thanks in advance >> >> Le mar. 25 juil. 2023 à 14:47, Mickael Hubert > >> >> > >>>> a écrit : >> >> Hi Razvan, >> Thanks a lot. >> I loaded the CRL for CA and certs and opensips start correctly ;) >> >> Have a good day ! >> >> Le lun. 24 juil. 2023 à 16:07, Răzvan Crainea > >> >> > >>>> a écrit : >> >> Hi, Mickael! >> >> I don't have much experience with this, but a first search would >> point >> to this [1] answer, which seems reasonable to me: you need to >> provide >> the CRL of the entire path, not only of your intermediate cert. >> Did you >> try that? >> >> [1] https://stackoverflow.com/a/47398918 >> >> >> Best regards, >> >> Răzvan Crainea >> OpenSIPS Core Developer >> http://www.opensips-solutions.com >> >> >> On 7/19/23 15:47, Mickael Hubert wrote: >>> Hi all, >>> I'm working on stir and shaken, and I want to include all >> revoked >>> certificates. >>> I my list in DER format, I use this command to transform it >> to PEM format: >>> openssl crl -in man_crl.der -inform DER -outform PEM -out crl.pem >>> >>> there is no erreur, I can read pem format (crl.pem): >>> -----BEGIN X509 CRL----- >>> .... >>> -----END X509 CRL----- >>> >>> I configured opensips with this: >>> modparam("stir_shaken", "crl_list", >> "/etc/opensips/stir-shaken-ca/crl.pem") >>> >>> but I have an error: >>> ul 19 12:39:07 [12] INFO:stir_shaken:verify_callback: >> certificate >>> validation failed: unable to get certificate CRL >>> Jul 19 12:39:07 [12] INFO:stir_shaken:w_stir_verify: Invalid >> certificate >>> >>> Can you tell me, what is exactly the correct format please ? >>> >>> Thanks in advance ! >>> ++ >>> >>> _______________________________________________ >>> Users mailing list >>> Users at lists.opensips.org > >> > >>> >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org > >> > >>> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org > >> >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > >> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list Users at lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users From tahir at ictinnovations.com Thu Aug 3 10:14:46 2023 From: tahir at ictinnovations.com (Tahir Almas Dhesi) Date: Thu, 3 Aug 2023 15:14:46 +0500 Subject: [OpenSIPS-Users] error on reload button Message-ID: Sending MI command: address_reload I receive following error whenever reload button is pressed at system = > addresses, please help Sending to *json:127.0.0.1:8888/mi * : Failed to connect to 127.0.0.1 port 8888: Connection refused *regards* *Tahir Almas* Managing Partner ICT Innovations http://www.ictinnovations.com Leveraging open source in ICT -------------- next part -------------- An HTML attachment was scrubbed... URL: From tahir at ictinnovations.com Thu Aug 3 10:25:52 2023 From: tahir at ictinnovations.com (Tahir Almas Dhesi) Date: Thu, 3 Aug 2023 15:25:52 +0500 Subject: [OpenSIPS-Users] Opensips CP Permissions "RELOAD on SERVER" produces error In-Reply-To: <495b5d7f-88be-6da2-88f2-1a5560b996c8@opensips.org> References: <035001d8c850$9be03290$d3a097b0$@gmail.com> <495b5d7f-88be-6da2-88f2-1a5560b996c8@opensips.org> Message-ID: My installation is not listening on port 8888, what modification i need to do ? regards *Tahir Almas* Managing Partner ICT Innovations http://www.ictinnovations.com Leveraging open source in ICT On Tue, Sep 20, 2022 at 5:06 PM Bogdan-Andrei Iancu wrote: > Hi, > > Is your opensips listening on the 8888 port? > netstat -tlnp | grep opensips > > Do you see any errors in the opensips logs when running doing the reload ? > > Do you see any communication on the 8888 port when doing the reload? > ngrep -qtd any port 8888 > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 27-30 Sept 2022, Athens > https://www.opensips.org/events/Summit-2022Athens/ > > On 9/14/22 6:42 PM, mtck01 wrote: > > Thank you, I managed to load the ‘permissions module’, and no more error, > but nothing happens, just stuck on “Sending to json:127.0.0.1:8888/mi :” > without error or successful confirmation. > > > > Regards, > > Martin > > > > _______________________________________________ > Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rvg at rvgeerligs.nl Thu Aug 3 16:15:36 2023 From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl) Date: Thu, 03 Aug 2023 16:15:36 +0000 Subject: [OpenSIPS-Users] opensips v 3.3 to 3.4 on Oracle cloud ARM Message-ID: Hi , I compiled v 3.3 all is working. Compiled 3.4 and I get the errors below. I looked at the source 3.4, also at the source in version 3.3.5 (nathelper and nattraversal) but I could not simply replace the 3.4 source with the 3.3 source. This looks like a compiler setting or a programm issue. Please advice, Ronald Geerligs --- error from logfile: DBG:core:trace_prot_bind: has no bind api function 2023-08-03T12:20:09.298662+00:00 xsp2 /usr/local/sbin/opensips[52802]: DBG:core:init_xlog: failed to load trace protocol! 2023-08-03T12:20:09.298686+00:00 xsp2 /usr/local/sbin/opensips[52802]: DBG:core:count_module_procs: modules require 1 extra processes 2023-08-03T12:20:09.298712+00:00 xsp2 /usr/local/sbin/opensips[52802]: DBG:core:init_pkg_stats: setting stats for 18 processes 2023-08-03T12:20:09.298741+00:00 xsp2 /usr/local/sbin/opensips[52802]: DBG:core:fix_actions: fixing force_rport, /etc/opensips/opensips34.cfg:169 2023-08-03T12:20:09.298769+00:00 xsp2 /usr/local/sbin/opensips[52802]: DBG:core:fix_actions: fixing nat_uac_test, /etc/opensips/opensips34.cfg:170 2023-08-03T12:20:09.298796+00:00 xsp2 /usr/local/sbin/opensips[52802]: ERROR:core:fix_cmd: Param [1] expected to be a string or variable 2023-08-03T12:20:09.298826+00:00 xsp2 /usr/local/sbin/opensips[52802]: ERROR:core:fix_actions: Failed to fix command 2023-08-03T12:20:09.298851+00:00 xsp2 /usr/local/sbin/opensips[52802]: ERROR:core:fix_actions: fixing failed (code=-6) at /etc/opensips/opensips34.cfg:170 2023-08-03T12:20:09.298879+00:00 xsp2 /usr/local/sbin/opensips[52802]: CRITICAL:core:fix_expr: fix_actions error 2023-08-03T12:20:09.298905+00:00 xsp2 /usr/local/sbin/opensips[52802]: ERROR:core:main: failed to fix configuration with err code -6 2023-08-03T12:20:09.298936+00:00 xsp2 /usr/local/sbin/opensips[52802]: INFO:core:cleanup: cleanup 2023-08-03T12:20:09.298962+00:00 xsp2 /usr/local/sbin/opensips[52802]: DBG:presence_xml:destroy: start 2023-08-03T12:20:09.298991+00:00 xsp2 /usr/local/sbin/opensips[52802]: NOTICE:presence:destroy: destroy module ... -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Fri Aug 4 06:48:55 2023 From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=) Date: Fri, 4 Aug 2023 09:48:55 +0300 Subject: [OpenSIPS-Users] opensips v 3.3 to 3.4 on Oracle cloud ARM In-Reply-To: References: Message-ID: Hi, Ronald! Usage of nat_uac_test has been changed between 3.3 and 3.4 [1]. Did you update your function according to the 3.4 syntax? Can you paste the snippet you are using? [1] https://www.opensips.org/Documentation/Migration-3-3-0-to-3-4-0 Best regards, Răzvan Crainea OpenSIPS Core Developer / SIPhub CTO http://www.opensips-solutions.com / https://www.siphub.com On 8/3/23 19:15, rvg at rvgeerligs.nl wrote: > Hi , > > I compiled v 3.3 all is working. Compiled 3.4 and I get the errors below. > > I looked at the source 3.4, also at the source in version 3.3.5 > (nathelper and nattraversal) but I could not simply replace the 3.4 > source with the 3.3 source. > > This looks like a compiler setting or a programm issue. > > Please advice, > > > Ronald Geerligs > > > --- > error from logfile: > > DBG:core:trace_prot_bind: has no bind api function > > > 2023-08-03T12:20:09.298662+00:00 xsp2 /usr/local/sbin/opensips[52802]: > DBG:core:init_xlog: failed to load trace protocol! > > > 2023-08-03T12:20:09.298686+00:00 xsp2 /usr/local/sbin/opensips[52802]: > DBG:core:count_module_procs: modules require 1 extra processes > > > 2023-08-03T12:20:09.298712+00:00 xsp2 /usr/local/sbin/opensips[52802]: > DBG:core:init_pkg_stats: setting stats for 18 processes > > > 2023-08-03T12:20:09.298741+00:00 xsp2 /usr/local/sbin/opensips[52802]: > DBG:core:fix_actions: fixing force_rport, /etc/opensips/opensips34.cfg:169 > > > 2023-08-03T12:20:09.298769+00:00 xsp2 /usr/local/sbin/opensips[52802]: > DBG:core:fix_actions: fixing nat_uac_test, /etc/opensips/opensips34.cfg:170 > > > 2023-08-03T12:20:09.298796+00:00 xsp2 /usr/local/sbin/opensips[52802]: > ERROR:core:fix_cmd: Param [1] expected to be a string or variable > > > 2023-08-03T12:20:09.298826+00:00 xsp2 /usr/local/sbin/opensips[52802]: > ERROR:core:fix_actions: Failed to fix command > > > 2023-08-03T12:20:09.298851+00:00 xsp2 /usr/local/sbin/opensips[52802]: > ERROR:core:fix_actions: fixing failed (code=-6) at > /etc/opensips/opensips34.cfg:170 > > > 2023-08-03T12:20:09.298879+00:00 xsp2 /usr/local/sbin/opensips[52802]: > CRITICAL:core:fix_expr: fix_actions error > > > 2023-08-03T12:20:09.298905+00:00 xsp2 /usr/local/sbin/opensips[52802]: > ERROR:core:main: failed to fix configuration with err code -6 > > > 2023-08-03T12:20:09.298936+00:00 xsp2 /usr/local/sbin/opensips[52802]: > INFO:core:cleanup: cleanup > > > 2023-08-03T12:20:09.298962+00:00 xsp2 /usr/local/sbin/opensips[52802]: > DBG:presence_xml:destroy: start > > > 2023-08-03T12:20:09.298991+00:00 xsp2 /usr/local/sbin/opensips[52802]: > NOTICE:presence:destroy: destroy module ... > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From rvg at rvgeerligs.nl Fri Aug 4 09:13:44 2023 From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl) Date: Fri, 04 Aug 2023 09:13:44 +0000 Subject: [OpenSIPS-Users] opensips v 3.3 to 3.4 on Oracle cloud ARM In-Reply-To: References: Message-ID: <03d198cebdcb82cd766eee59008bf915ae0adf71@rvgeerligs.nl> Hi Răzvan, The error happens at the if (nat_uac_test(23)), fix_nated_register(); This part of the 3.4 cfg file is the same as in the 3.3 cfg file. It was generated with osipsconfig in the 3.4 sbin directory, after compilation. I did not do anything with the nathelper or nat_traversal .c files. Regards, Ronald Geerligs --- from cfg file: # initial NAT handling; detect if the request comes from behind a NAT # and apply contact fixing force_rport(); if (nat_uac_test(23)) { if (is_method("REGISTER")) { fix_nated_register(); setbflag("NAT"); } else { fix_nated_contact(); setflag("NAT"); } } August 4, 2023 at 9:48 AM, "Răzvan Crainea" wrote: > > Hi, Ronald! > > Usage of nat_uac_test has been changed between 3.3 and 3.4 [1]. Did you > update your function according to the 3.4 syntax? Can you paste the > snippet you are using? > > [1] https://www.opensips.org/Documentation/Migration-3-3-0-to-3-4-0 > > Best regards, > > Răzvan Crainea > OpenSIPS Core Developer / SIPhub CTO > http://www.opensips-solutions.com/ / https://www.siphub.com/ > > On 8/3/23 19:15, rvg at rvgeerligs.nl wrote: > > > > > Hi , > > > > I compiled v 3.3 all is working. Compiled 3.4 and I get the errors below. > > > > I looked at the source 3.4, also at the source in version 3.3.5 > > (nathelper and nattraversal) but I could not simply replace the 3.4 > > source with the 3.3 source. > > > > This looks like a compiler setting or a programm issue. > > > > Please advice, > > > > > > Ronald Geerligs > > > > > > --- > > error from logfile: > > > > DBG:core:trace_prot_bind: has no bind api function > > > > > > 2023-08-03T12:20:09.298662+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:init_xlog: failed to load trace protocol! > > > > > > 2023-08-03T12:20:09.298686+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:count_module_procs: modules require 1 extra processes > > > > > > 2023-08-03T12:20:09.298712+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:init_pkg_stats: setting stats for 18 processes > > > > > > 2023-08-03T12:20:09.298741+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:fix_actions: fixing force_rport, /etc/opensips/opensips34.cfg:169 > > > > > > 2023-08-03T12:20:09.298769+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:fix_actions: fixing nat_uac_test, /etc/opensips/opensips34.cfg:170 > > > > > > 2023-08-03T12:20:09.298796+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_cmd: Param [1] expected to be a string or variable > > > > > > 2023-08-03T12:20:09.298826+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_actions: Failed to fix command > > > > > > 2023-08-03T12:20:09.298851+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_actions: fixing failed (code=-6) at > > /etc/opensips/opensips34.cfg:170 > > > > > > 2023-08-03T12:20:09.298879+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > CRITICAL:core:fix_expr: fix_actions error > > > > > > 2023-08-03T12:20:09.298905+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:main: failed to fix configuration with err code -6 > > > > > > 2023-08-03T12:20:09.298936+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > INFO:core:cleanup: cleanup > > > > > > 2023-08-03T12:20:09.298962+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:presence_xml:destroy: start > > > > > > 2023-08-03T12:20:09.298991+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > NOTICE:presence:destroy: destroy 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 rvg at rvgeerligs.nl Fri Aug 4 09:40:05 2023 From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl) Date: Fri, 04 Aug 2023 09:40:05 +0000 Subject: [OpenSIPS-Users] opensips v 3.3 to 3.4 on Oracle cloud ARM In-Reply-To: References: Message-ID: Hi. cfg file attached and init.d/opensips34 attached. Regards, Ronald Geerligs August 4, 2023 at 9:48 AM, "Răzvan Crainea" wrote: > > Hi, Ronald! > > Usage of nat_uac_test has been changed between 3.3 and 3.4 [1]. Did you > update your function according to the 3.4 syntax? Can you paste the > snippet you are using? > > [1] https://www.opensips.org/Documentation/Migration-3-3-0-to-3-4-0 > > Best regards, > > Răzvan Crainea > OpenSIPS Core Developer / SIPhub CTO > http://www.opensips-solutions.com/ / https://www.siphub.com/ > > On 8/3/23 19:15, rvg at rvgeerligs.nl wrote: > > > > > Hi , > > > > I compiled v 3.3 all is working. Compiled 3.4 and I get the errors below. > > > > I looked at the source 3.4, also at the source in version 3.3.5 > > (nathelper and nattraversal) but I could not simply replace the 3.4 > > source with the 3.3 source. > > > > This looks like a compiler setting or a programm issue. > > > > Please advice, > > > > > > Ronald Geerligs > > > > > > --- > > error from logfile: > > > > DBG:core:trace_prot_bind: has no bind api function > > > > > > 2023-08-03T12:20:09.298662+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:init_xlog: failed to load trace protocol! > > > > > > 2023-08-03T12:20:09.298686+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:count_module_procs: modules require 1 extra processes > > > > > > 2023-08-03T12:20:09.298712+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:init_pkg_stats: setting stats for 18 processes > > > > > > 2023-08-03T12:20:09.298741+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:fix_actions: fixing force_rport, /etc/opensips/opensips34.cfg:169 > > > > > > 2023-08-03T12:20:09.298769+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:fix_actions: fixing nat_uac_test, /etc/opensips/opensips34.cfg:170 > > > > > > 2023-08-03T12:20:09.298796+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_cmd: Param [1] expected to be a string or variable > > > > > > 2023-08-03T12:20:09.298826+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_actions: Failed to fix command > > > > > > 2023-08-03T12:20:09.298851+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_actions: fixing failed (code=-6) at > > /etc/opensips/opensips34.cfg:170 > > > > > > 2023-08-03T12:20:09.298879+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > CRITICAL:core:fix_expr: fix_actions error > > > > > > 2023-08-03T12:20:09.298905+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:main: failed to fix configuration with err code -6 > > > > > > 2023-08-03T12:20:09.298936+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > INFO:core:cleanup: cleanup > > > > > > 2023-08-03T12:20:09.298962+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:presence_xml:destroy: start > > > > > > 2023-08-03T12:20:09.298991+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > NOTICE:presence:destroy: destroy 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: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: opensips34.cfg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: opensips34 Type: text/x-shellscript Size: 4537 bytes Desc: not available URL: From razvan at opensips.org Fri Aug 4 10:06:50 2023 From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=) Date: Fri, 4 Aug 2023 13:06:50 +0300 Subject: [OpenSIPS-Users] opensips v 3.3 to 3.4 on Oracle cloud ARM In-Reply-To: References: Message-ID: <1a138e52-69f0-2fbe-089b-322ee1d141fb@opensips.org> The migration document[1] clearly states to "Check the module docs for the flags parameters of the fix_nated_sdp() and nat_uac_test() functions for the mapping between the old and new flag names." Did you do that? You might have missed the fact that the nat_uac_test() function no longer receives arguments as integers, they have to be strings. Please check the 3.4 documentation[2]. [2] https://opensips.org/docs/modules/3.4.x/nathelper.html#func_nat_uac_test PS: please do not attach files in a mailing list message Best regards, Răzvan Crainea OpenSIPS Core Developer / SIPhub CTO http://www.opensips-solutions.com / https://www.siphub.com On 8/4/23 12:40, rvg at rvgeerligs.nl wrote: > Hi. > > cfg file attached and init.d/opensips34 attached. > > Regards, > > Ronald Geerligs > > > > August 4, 2023 at 9:48 AM, "Răzvan Crainea" > wrote: > > Hi, Ronald! > > Usage of nat_uac_test has been changed between 3.3 and 3.4 [1]. Did you > update your function according to the 3.4 syntax? Can you paste the > snippet you are using? > > [1] https://www.opensips.org/Documentation/Migration-3-3-0-to-3-4-0 > > > Best regards, > > Răzvan Crainea > OpenSIPS Core Developer / SIPhub CTO > http://www.opensips-solutions.com/ > / https://www.siphub.com/ > > > On 8/3/23 19:15, rvg at rvgeerligs.nl wrote: > > Hi , > I compiled v 3.3 all is working. Compiled 3.4 and I get the > errors below. > I looked at the source 3.4, also at the source in version 3.3.5 > (nathelper and nattraversal) but I could not simply replace the 3.4 > source with the 3.3 source. > This looks like a compiler setting or a programm issue. > Please advice, > Ronald Geerligs > --- > error from logfile: > DBG:core:trace_prot_bind: has no bind api function > 2023-08-03T12:20:09.298662+00:00 xsp2 > /usr/local/sbin/opensips[52802]: > DBG:core:init_xlog: failed to load trace protocol! > 2023-08-03T12:20:09.298686+00:00 xsp2 > /usr/local/sbin/opensips[52802]: > DBG:core:count_module_procs: modules require 1 extra processes > 2023-08-03T12:20:09.298712+00:00 xsp2 > /usr/local/sbin/opensips[52802]: > DBG:core:init_pkg_stats: setting stats for 18 processes > 2023-08-03T12:20:09.298741+00:00 xsp2 > /usr/local/sbin/opensips[52802]: > DBG:core:fix_actions: fixing force_rport, > /etc/opensips/opensips34.cfg:169 > 2023-08-03T12:20:09.298769+00:00 xsp2 > /usr/local/sbin/opensips[52802]: > DBG:core:fix_actions: fixing nat_uac_test, > /etc/opensips/opensips34.cfg:170 > 2023-08-03T12:20:09.298796+00:00 xsp2 > /usr/local/sbin/opensips[52802]: > ERROR:core:fix_cmd: Param [1] expected to be a string or variable > 2023-08-03T12:20:09.298826+00:00 xsp2 > /usr/local/sbin/opensips[52802]: > ERROR:core:fix_actions: Failed to fix command > 2023-08-03T12:20:09.298851+00:00 xsp2 > /usr/local/sbin/opensips[52802]: > ERROR:core:fix_actions: fixing failed (code=-6) at > /etc/opensips/opensips34.cfg:170 > 2023-08-03T12:20:09.298879+00:00 xsp2 > /usr/local/sbin/opensips[52802]: > CRITICAL:core:fix_expr: fix_actions error > 2023-08-03T12:20:09.298905+00:00 xsp2 > /usr/local/sbin/opensips[52802]: > ERROR:core:main: failed to fix configuration with err code -6 > 2023-08-03T12:20:09.298936+00:00 xsp2 > /usr/local/sbin/opensips[52802]: > INFO:core:cleanup: cleanup > 2023-08-03T12:20:09.298962+00:00 xsp2 > /usr/local/sbin/opensips[52802]: > DBG:presence_xml:destroy: start > 2023-08-03T12:20:09.298991+00:00 xsp2 > /usr/local/sbin/opensips[52802]: > NOTICE:presence:destroy: destroy 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 > > > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From rvg at rvgeerligs.nl Fri Aug 4 11:48:55 2023 From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl) Date: Fri, 04 Aug 2023 11:48:55 +0000 Subject: [OpenSIPS-Users] opensips v 3.3 to 3.4 on Oracle cloud ARM In-Reply-To: <1a138e52-69f0-2fbe-089b-322ee1d141fb@opensips.org> References: <1a138e52-69f0-2fbe-089b-322ee1d141fb@opensips.org> Message-ID: <91d6cb239b68b874820d734f0587aabff969517c@rvgeerligs.nl> Hi, I took a look at it but I did not do anything with it. I read through the xml nathelper_admin.xml but there the same flags as in the doc. In that case  nat_uac_test(23)  should use flag 23 and I can't find what flag that is. It says that a CSV file can be provided? if the call was nat_uac_test(4), it would now be nat_uac_test(*private-via*) ?? Where could I obtain this CSV? Regards, Ronald Geerligs # initial NAT handling; detect if the request comes from behind a NAT # and apply contact fixing force_rport(); if (nat_uac_test(23)) { if (is_method("REGISTER")) { fix_nated_register(); setbflag("NAT"); } else { fix_nated_contact(); setflag("NAT"); } } August 4, 2023 at 1:06 PM, "Răzvan Crainea" wrote: > > The migration document[1] clearly states to "Check the module docs for > the flags parameters of the fix_nated_sdp() and nat_uac_test() functions > for the mapping between the old and new flag names." Did you do that? > You might have missed the fact that the nat_uac_test() function no > longer receives arguments as integers, they have to be strings. Please > check the 3.4 documentation[2]. > > [2] https://opensips.org/docs/modules/3.4.x/nathelper.html#func_nat_uac_test > > PS: please do not attach files in a mailing list message > > Best regards, > > Răzvan Crainea > OpenSIPS Core Developer / SIPhub CTO > http://www.opensips-solutions.com/ / https://www.siphub.com/ > > On 8/4/23 12:40, rvg at rvgeerligs.nl wrote: > > > > > Hi. > > > > cfg file attached and init.d/opensips34 attached. > > > > Regards, > > > > Ronald Geerligs > > > > > > > > August 4, 2023 at 9:48 AM, "Răzvan Crainea" > > wrote: > > > > Hi, Ronald! > > > > Usage of nat_uac_test has been changed between 3.3 and 3.4 [1]. Did you > > update your function according to the 3.4 syntax? Can you paste the > > snippet you are using? > > > > [1] https://www.opensips.org/Documentation/Migration-3-3-0-to-3-4-0 > > > > > > Best regards, > > > > Răzvan Crainea > > OpenSIPS Core Developer / SIPhub CTO > > http://www.opensips-solutions.com/ > > / https://www.siphub.com/ > > > > > > On 8/3/23 19:15, rvg at rvgeerligs.nl wrote: > > > > Hi , > > I compiled v 3.3 all is working. Compiled 3.4 and I get the > > errors below. > > I looked at the source 3.4, also at the source in version 3.3.5 > > (nathelper and nattraversal) but I could not simply replace the 3.4 > > source with the 3.3 source. > > This looks like a compiler setting or a programm issue. > > Please advice, > > Ronald Geerligs > > --- > > error from logfile: > > DBG:core:trace_prot_bind: has no bind api function > > 2023-08-03T12:20:09.298662+00:00 xsp2 > > /usr/local/sbin/opensips[52802]: > > DBG:core:init_xlog: failed to load trace protocol! > > 2023-08-03T12:20:09.298686+00:00 xsp2 > > /usr/local/sbin/opensips[52802]: > > DBG:core:count_module_procs: modules require 1 extra processes > > 2023-08-03T12:20:09.298712+00:00 xsp2 > > /usr/local/sbin/opensips[52802]: > > DBG:core:init_pkg_stats: setting stats for 18 processes > > 2023-08-03T12:20:09.298741+00:00 xsp2 > > /usr/local/sbin/opensips[52802]: > > DBG:core:fix_actions: fixing force_rport, > > /etc/opensips/opensips34.cfg:169 > > 2023-08-03T12:20:09.298769+00:00 xsp2 > > /usr/local/sbin/opensips[52802]: > > DBG:core:fix_actions: fixing nat_uac_test, > > /etc/opensips/opensips34.cfg:170 > > 2023-08-03T12:20:09.298796+00:00 xsp2 > > /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_cmd: Param [1] expected to be a string or variable > > 2023-08-03T12:20:09.298826+00:00 xsp2 > > /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_actions: Failed to fix command > > 2023-08-03T12:20:09.298851+00:00 xsp2 > > /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_actions: fixing failed (code=-6) at > > /etc/opensips/opensips34.cfg:170 > > 2023-08-03T12:20:09.298879+00:00 xsp2 > > /usr/local/sbin/opensips[52802]: > > CRITICAL:core:fix_expr: fix_actions error > > 2023-08-03T12:20:09.298905+00:00 xsp2 > > /usr/local/sbin/opensips[52802]: > > ERROR:core:main: failed to fix configuration with err code -6 > > 2023-08-03T12:20:09.298936+00:00 xsp2 > > /usr/local/sbin/opensips[52802]: > > INFO:core:cleanup: cleanup > > 2023-08-03T12:20:09.298962+00:00 xsp2 > > /usr/local/sbin/opensips[52802]: > > DBG:presence_xml:destroy: start > > 2023-08-03T12:20:09.298991+00:00 xsp2 > > /usr/local/sbin/opensips[52802]: > > NOTICE:presence:destroy: destroy 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 > > > > > > > > > > _______________________________________________ > > 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 rvg at rvgeerligs.nl Fri Aug 4 12:43:48 2023 From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl) Date: Fri, 04 Aug 2023 12:43:48 +0000 Subject: [OpenSIPS-Users] opensips v 3.3 to 3.4 on Oracle cloud ARM In-Reply-To: References: Message-ID: <66b56d4ff739d368064a8932f0e2d61286d2fc6c@rvgeerligs.nl> Hi, I chose the equivalent of 32 "*diff-ip-src-contact*" and "*private-contact*" later on in the script and it started working! Thx all for the help. Regards, Ronald Geerligs August 4, 2023 at 9:48 AM, "Răzvan Crainea" wrote: > > Hi, Ronald! > > Usage of nat_uac_test has been changed between 3.3 and 3.4 [1]. Did you > update your function according to the 3.4 syntax? Can you paste the > snippet you are using? > > [1] https://www.opensips.org/Documentation/Migration-3-3-0-to-3-4-0 > > Best regards, > > Răzvan Crainea > OpenSIPS Core Developer / SIPhub CTO > http://www.opensips-solutions.com/ / https://www.siphub.com/ > > On 8/3/23 19:15, rvg at rvgeerligs.nl wrote: > > > > > Hi , > > > > I compiled v 3.3 all is working. Compiled 3.4 and I get the errors below. > > > > I looked at the source 3.4, also at the source in version 3.3.5 > > (nathelper and nattraversal) but I could not simply replace the 3.4 > > source with the 3.3 source. > > > > This looks like a compiler setting or a programm issue. > > > > Please advice, > > > > > > Ronald Geerligs > > > > > > --- > > error from logfile: > > > > DBG:core:trace_prot_bind: has no bind api function > > > > > > 2023-08-03T12:20:09.298662+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:init_xlog: failed to load trace protocol! > > > > > > 2023-08-03T12:20:09.298686+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:count_module_procs: modules require 1 extra processes > > > > > > 2023-08-03T12:20:09.298712+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:init_pkg_stats: setting stats for 18 processes > > > > > > 2023-08-03T12:20:09.298741+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:fix_actions: fixing force_rport, /etc/opensips/opensips34.cfg:169 > > > > > > 2023-08-03T12:20:09.298769+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:core:fix_actions: fixing nat_uac_test, /etc/opensips/opensips34.cfg:170 > > > > > > 2023-08-03T12:20:09.298796+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_cmd: Param [1] expected to be a string or variable > > > > > > 2023-08-03T12:20:09.298826+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_actions: Failed to fix command > > > > > > 2023-08-03T12:20:09.298851+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:fix_actions: fixing failed (code=-6) at > > /etc/opensips/opensips34.cfg:170 > > > > > > 2023-08-03T12:20:09.298879+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > CRITICAL:core:fix_expr: fix_actions error > > > > > > 2023-08-03T12:20:09.298905+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > ERROR:core:main: failed to fix configuration with err code -6 > > > > > > 2023-08-03T12:20:09.298936+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > INFO:core:cleanup: cleanup > > > > > > 2023-08-03T12:20:09.298962+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > DBG:presence_xml:destroy: start > > > > > > 2023-08-03T12:20:09.298991+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > NOTICE:presence:destroy: destroy 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 rvg at rvgeerligs.nl Fri Aug 4 14:34:21 2023 From: rvg at rvgeerligs.nl (rvg at rvgeerligs.nl) Date: Fri, 04 Aug 2023 14:34:21 +0000 Subject: [OpenSIPS-Users] opensips v 3.3 to 3.4 on Oracle cloud ARM In-Reply-To: References: Message-ID: changed user and passwd August 4, 2023 at 12:40 PM, rvg at rvgeerligs.nl wrote: > > Hi. > > cfg file attached and init.d/opensips34 attached. > > Regards, > > Ronald Geerligs > > August 4, 2023 at 9:48 AM, "Răzvan Crainea" wrote: > > > > > Hi, Ronald! > > > > Usage of nat_uac_test has been changed between 3.3 and 3.4 [1]. Did you > > update your function according to the 3.4 syntax? Can you paste the > > snippet you are using? > > > > [1] https://www.opensips.org/Documentation/Migration-3-3-0-to-3-4-0 > > > > Best regards, > > > > Răzvan Crainea > > OpenSIPS Core Developer / SIPhub CTO > > http://www.opensips-solutions.com/ / https://www.siphub.com/ > > > > On 8/3/23 19:15, rvg at rvgeerligs.nl wrote: > > > > > > > > Hi , > > > > > > I compiled v 3.3 all is working. Compiled 3.4 and I get the errors below. > > > > > > I looked at the source 3.4, also at the source in version 3.3.5 > > > (nathelper and nattraversal) but I could not simply replace the 3.4 > > > source with the 3.3 source. > > > > > > This looks like a compiler setting or a programm issue. > > > > > > Please advice, > > > > > > > > > Ronald Geerligs > > > > > > > > > --- > > > error from logfile: > > > > > > DBG:core:trace_prot_bind: has no bind api function > > > > > > > > > 2023-08-03T12:20:09.298662+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > DBG:core:init_xlog: failed to load trace protocol! > > > > > > > > > 2023-08-03T12:20:09.298686+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > DBG:core:count_module_procs: modules require 1 extra processes > > > > > > > > > 2023-08-03T12:20:09.298712+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > DBG:core:init_pkg_stats: setting stats for 18 processes > > > > > > > > > 2023-08-03T12:20:09.298741+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > DBG:core:fix_actions: fixing force_rport, /etc/opensips/opensips34.cfg:169 > > > > > > > > > 2023-08-03T12:20:09.298769+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > DBG:core:fix_actions: fixing nat_uac_test, /etc/opensips/opensips34.cfg:170 > > > > > > > > > 2023-08-03T12:20:09.298796+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > ERROR:core:fix_cmd: Param [1] expected to be a string or variable > > > > > > > > > 2023-08-03T12:20:09.298826+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > ERROR:core:fix_actions: Failed to fix command > > > > > > > > > 2023-08-03T12:20:09.298851+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > ERROR:core:fix_actions: fixing failed (code=-6) at > > > /etc/opensips/opensips34.cfg:170 > > > > > > > > > 2023-08-03T12:20:09.298879+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > CRITICAL:core:fix_expr: fix_actions error > > > > > > > > > 2023-08-03T12:20:09.298905+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > ERROR:core:main: failed to fix configuration with err code -6 > > > > > > > > > 2023-08-03T12:20:09.298936+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > INFO:core:cleanup: cleanup > > > > > > > > > 2023-08-03T12:20:09.298962+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > DBG:presence_xml:destroy: start > > > > > > > > > 2023-08-03T12:20:09.298991+00:00 xsp2 /usr/local/sbin/opensips[52802]: > > > NOTICE:presence:destroy: destroy 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 tahir at ictinnovations.com Fri Aug 4 17:05:28 2023 From: tahir at ictinnovations.com (Tahir Almas Dhesi) Date: Fri, 4 Aug 2023 22:05:28 +0500 Subject: [OpenSIPS-Users] Opensips CP Permissions "RELOAD on SERVER" produces error In-Reply-To: References: <035001d8c850$9be03290$d3a097b0$@gmail.com> <495b5d7f-88be-6da2-88f2-1a5560b996c8@opensips.org> Message-ID: It get fixed actually permission.so module was missing in configuration file regards *Tahir Almas* Managing Partner ICT Innovations http://www.ictinnovations.com Leveraging open source in ICT On Thu, Aug 3, 2023 at 3:25 PM Tahir Almas Dhesi wrote: > My installation is not listening on port 8888, what modification i need to > do ? > > regards > *Tahir Almas* > > Managing Partner > ICT Innovations > http://www.ictinnovations.com > Leveraging open source in ICT > > > On Tue, Sep 20, 2022 at 5:06 PM Bogdan-Andrei Iancu > wrote: > >> Hi, >> >> Is your opensips listening on the 8888 port? >> netstat -tlnp | grep opensips >> >> Do you see any errors in the opensips logs when running doing the reload ? >> >> Do you see any communication on the 8888 port when doing the reload? >> ngrep -qtd any port 8888 >> >> Regards, >> >> Bogdan-Andrei Iancu >> >> OpenSIPS Founder and Developer >> https://www.opensips-solutions.com >> OpenSIPS Summit 27-30 Sept 2022, Athens >> https://www.opensips.org/events/Summit-2022Athens/ >> >> On 9/14/22 6:42 PM, mtck01 wrote: >> >> Thank you, I managed to load the ‘permissions module’, and no more error, >> but nothing happens, just stuck on “Sending to json:127.0.0.1:8888/mi :” >> without error or successful confirmation. >> >> >> >> Regards, >> >> Martin >> >> >> >> _______________________________________________ >> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> >> _______________________________________________ >> Users mailing list >> Users at lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tahir at ictinnovations.com Fri Aug 4 17:06:19 2023 From: tahir at ictinnovations.com (Tahir Almas Dhesi) Date: Fri, 4 Aug 2023 22:06:19 +0500 Subject: [OpenSIPS-Users] error on reload button In-Reply-To: References: Message-ID: It get fixed, actually permission module was missing in opensips configuration file regards *Tahir Almas* Managing Partner ICT Innovations http://www.ictinnovations.com Leveraging open source in ICT On Thu, Aug 3, 2023 at 3:14 PM Tahir Almas Dhesi wrote: > Sending MI command: address_reload > > I receive following error whenever reload button is pressed at system = > > addresses, please help > > Sending to *json:127.0.0.1:8888/mi * : > Failed to connect to 127.0.0.1 port 8888: Connection refused > > > > *regards* > *Tahir Almas* > > Managing Partner > ICT Innovations > http://www.ictinnovations.com > Leveraging open source in ICT > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bogdan at opensips.org Mon Aug 7 07:01:48 2023 From: bogdan at opensips.org (Bogdan-Andrei Iancu) Date: Mon, 7 Aug 2023 10:01:48 +0300 Subject: [OpenSIPS-Users] Dialog contact not updating until answer In-Reply-To: References: Message-ID: Hi Callum, The callee contact is learned only when the call is established (so , at 200 OK). During the ringing state, a call may have several in-progress/ringing branches to different callee end-points, each with its own contact. Only when the call is answered you will get ONE of the branches actually established , so you will have the final contact from the callee end-point. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer https://www.opensips-solutions.com https://www.siphub.com On 8/1/23 4:23 PM, Callum Guy wrote: > Hi All, > > I've observed a behaviour (OpenSIPs 3.2.4) where the contact stored > against an active dialog is not populated until the call is answered. > > Using opensips-cli dlg_list I see the following: > > Ringing - https://gist.github.com/spacetourist/2502f6b76a95bb2f500fda5291e1c93b > Answered - https://gist.github.com/spacetourist/81b9e19de14a04aeff7f1f7b8965e2e5 > > During ringing we have: > - "state": 2 > - CALLEES > "callee_contact": "", > > Once answered we have: > - "state": 4 > - CALLEES > "callee_contact": "sip:b2o80qss at 77.95.114.132:45656;transport=ws", > > This is problematic for me as I'm working on a system to prevent > duplicate registrations from an AoR (sip:6190051 at sk-1.rtc.sip.net) > whilst preventing other instances from overruling and taking ownership > of the session by blocking registrations from separate contacts when a > call is ongoing. > > The exact scenario where I'm currently seeing errors is when an active > contact (i.e. sip:b2o80qss at 77.95.114.132:45656;transport=ws) issues a > re-REGISTER during call setup. I use get_dialogs_by_profile() in > OpenSIPs to track sessions against the AoR and loop through any active > dialogs associated whenever a call or registration comes in. Using > this approach has allowed me to block other devices from creating a > second registration however the lookup is currently failing during the > ringing part of the session as the contact cannot be checked. > > Is there a reason why callee_contact cannot be updated immediately > when the session begins? Is this to accommodate branching or similar? > I'll review alternative approaches whilst awaiting a reply however it > would be great if there was a path for me to solve this issue with my > current approach! > > Thanks, > > Callum > > P.S. if this makes more sense as a Github issue then please let me > know, I'm not sure where is best to ask! > From wadii at evenmedia.fr Mon Aug 7 07:28:01 2023 From: wadii at evenmedia.fr (Wadii ELMAJDI | Evenmedia) Date: Mon, 7 Aug 2023 07:28:01 +0000 Subject: [OpenSIPS-Users] Issue with CRL Validation in French STIR/SHAKEN Implementation Message-ID: Hello I have run into a problem with the STIR/SHAKEN verification process. In the French implementation of StirShaken, the CRL of the operator certificates is signed with a certificate that is different from the one used to sign providers certificates. and in such case, OpenSSL does not allow in one command to validate the entire certification chain. Also, OPENSIPS stirshaken module's stir_shaken_verify function fails to validate providers certificate (with CRL Loaded) Error : certificate validation failed: unable to get certificate CRL For now, following the guidelines suggested by the French authority handling STIR/SHAKEN, we are planning to implement a two-step approach to check CRL before stir_shaken_verify kicks in (w/o CRL loaded) First, we verify the certification chain of the provider's certificate, plus making sure CA's certificates are not revoked. We do this using a command like: openssl verify -CAfile /etc/opensips/example_certs/ca_list.pem -untrusted /etc/opensips/example_certs/example_pa.pem -extended_crl -crl_check_all -CRLfile /etc/opensips/example_certs/crl_list.pem /etc/opensips/example_certs/ProviderCertificate.cer Where example_pa.pem is the certificate used to sign CRL of providers certificates, and crl_list : the concatenation of both providers and CA's CRLs in PEM format. The second step involves a separate check to verify if the provider's certificate is revoked : openssl crl -in /etc/opensips/example_certs/crl_list.pem -noout -text | grep $(openssl x509 -in /etc/opensips/example_certs/ProviderCertificate.cer -noout -serial | cut -d '=' -f 2) This will add an extra processing time due to a double certification validation (ran by both by openssl and stir_shaken_verify) + reading crls from disk. Given this situation, it would be highly beneficial if Opensips could accommodate cases where revocation lists are signed with a different certificate. This would not only simplify the verification process but also improve compatibility for similar future scenarios (like a complex certificate hierarchy) Suggestion : Consider adding an exported parameter, such as : modparam("stir_shaken", "crl_signing_certs", "/stir_certs/crl_signing_certs.pem") This parameter would allow users to specify a list of separate certificates used to sign the CRLs, in cases where the CRLs and the provider certificates are not signed by the same certificate. -------------- next part -------------- An HTML attachment was scrubbed... URL: From amel.guesmi at sofrecom.com Mon Aug 7 09:53:54 2023 From: amel.guesmi at sofrecom.com (amel.guesmi at sofrecom.com) Date: Mon, 7 Aug 2023 09:53:54 +0000 Subject: [OpenSIPS-Users] B2BUA - REFER- detect 200 OK to send notify In-Reply-To: <0185ced03c8b496490c5390a82f87719@orange.com> References: <0185ced03c8b496490c5390a82f87719@orange.com> Message-ID: <5fd9f02607c74328893495b2851587b9@orange.com> Hello all, Sorry for sending this question several times, hope i get some help this time 😊 We are trying to implement the « REFER » method in opensips 3.3. we used this documentation : openSIPS | Documentation / Tutorials-B2BUA When we detect a REFER method, we are excuting those functions : b2b_send_reply(202, "Accepted"); # Example: Send NOTIFY request $var(destination) = $hdr(Refer-From); $var(message_body) = "This is the message body of the NOTIFY"; send_request("NOTIFY", $var(destination), $hdr(Refer-To), $var(message_body)); # create the client entity corresponding to # the user specified in the 'Refer-To' header b2b_client_new("referee", $hdr(Refer-To)); # bridge the referrer's peer with the referee b2b_bridge("peer", "referee"); #b2b_end_dlg_leg(); With that scenario, we succeeded in transfering a call after the REFER and we are tryning now to implement that process with « Notify » after the REFER (see the flow in the following link). REFER_-_User_docs_2.width-800.png (720×540) (twilio.com) For this, when we open the new client session, we don’t end the session with the one sending the REFER and we need to detect when the call is accepted by the Callee (200 OK) when we are using that function : b2b_client_new("referee", $hdr(Refer-To)); How can we detect the 200 OK in that B2B mode in order to send the NOTIFY before ending the session with Alice. Thank you very much BR, Amel Orange Restricted -------------- next part -------------- An HTML attachment was scrubbed... URL: From JPyle at fusionconnect.com Tue Aug 8 14:17:19 2023 From: JPyle at fusionconnect.com (Pyle, Jeff) Date: Tue, 8 Aug 2023 14:17:19 +0000 Subject: [OpenSIPS-Users] handing To URI params with uac_replace_to() Message-ID: Hello, This is on OpenSIPS 3.2.13 I am running uac_replace_to() in branch_route, with restore_mode on 'auto'. It works as expected...almost. The b-leg attaches To URI params in addition to the tag on its replies. I would like to strip these params before relaying back to the a-leg. Is that possible? Then, of course, the tags would be restored when sending messages back towards the b-leg, as a function of the 'auto' mode. Regards, Jeff This message is subject to Fusion Connect, Inc.'s email communication policy: www.fusionconnect.com/email-policy -------------- next part -------------- An HTML attachment was scrubbed... URL: From mickael at winlux.fr Thu Aug 10 09:45:52 2023 From: mickael at winlux.fr (Mickael Hubert) Date: Thu, 10 Aug 2023 11:45:52 +0200 Subject: [OpenSIPS-Users] Issue with CRL Validation in French STIR/SHAKEN Implementation In-Reply-To: References: Message-ID: Hi all, Thanks Wadii for your help (in private ;) ) I developed a solution to check CRL in an external process (python script scheduled by AWX). My python script (download only in memory, not on disk) *For CA certificates:* - Download CA et intermediate certs - Download PA cert (pa cert is used to sign CRL) - Download CA CRL - Check if CA or intermediate cert are revoked - I use ansible (AWX) to write CA et intermediate certs into opensips disk - Ansible restart opensips only if CA or intermediate cert change *For provider certificate (BPCO):* - Download provider certificates that are in tar.gz (only in memory) - Uncompress tar.gz and create a dict with data (cert data, cert id, provider id) - Download CRL for provider certificates - Check all provider certificates signatures (not necessary, because opensips can do that for each call) - Check if cert is revoked - Extract metadata and add them to dict - Ansible parses this dict and push each line in mysql cache DB (sql_cacher module) Ex of dict: { "126881e75888888": { "provider_code": "PROV00", "cert_data": "-----BEGIN CERTIFICATE-----.........\n-----END CERTIFICATE-----\n", "not_before": "20230815220000Z", "not_after": "20240814215959Z", "has_expired": false, "valid": false, "revoked": true, "revoked_date": "20230809151920Z" } } Thanks to that, when call is processed by opensips, it gets in its cache the correct data, if revoked == true, force $rc = -7 ( https://github.com/OpenSIPS/sipssert-opensips-tests/blob/1313d03b6ecd1972f9d2facf69116c418fb40399/stir-shaken/04.verify-200/stir_shaken_verify.cfg#L135) to send a correct error code 437 Unsupported Credential) Maybe that can help my french friends voip providers ;) Have a good day Le lun. 7 août 2023 à 09:29, Wadii ELMAJDI | Evenmedia a écrit : > Hello > > > > I have run into a problem with the STIR/SHAKEN verification process. > > In the French implementation of StirShaken, the CRL of the operator > certificates is signed with a certificate that is different from the one > used to sign providers certificates. > and in such case, OpenSSL does not allow in one command to validate the > entire certification chain. > > Also, OPENSIPS stirshaken module's stir_shaken_verify function fails to > validate providers certificate (with CRL Loaded) > > > > Error : certificate validation failed: unable to get certificate CRL > > > > For now, following the guidelines suggested by the French authority > handling STIR/SHAKEN, we are planning to implement a two-step approach to > check CRL before stir_shaken_verify kicks in (w/o CRL loaded) > > First, we verify the certification chain of the provider's certificate, > plus making sure CA’s certificates are not revoked. We do this using a > command like: > > > > openssl verify -CAfile /etc/opensips/example_certs/ca_list.pem -untrusted > /etc/opensips/example_certs/example_pa.pem -extended_crl -crl_check_all > -CRLfile /etc/opensips/example_certs/crl_list.pem > /etc/opensips/example_certs/ProviderCertificate.cer > > > > Where example_pa.pem is the certificate used to sign CRL of providers > certificates, and crl_list : the concatenation of both providers and CA’s > CRLs in PEM format. > > The second step involves a separate check to verify if the provider’s > certificate is revoked : > > > > openssl crl -in /etc/opensips/example_certs/crl_list.pem -noout -text | > grep $(openssl x509 -in /etc/opensips/example_certs/ProviderCertificate.cer > -noout -serial | cut -d '=' -f 2) > > > > This will add an extra processing time due to a double certification > validation (ran by both by openssl and stir_shaken_verify) + reading crls > from disk. > > > > Given this situation, it would be highly beneficial if Opensips could > accommodate cases where revocation lists are signed with a different > certificate. This would not only simplify the verification process but also > improve compatibility for similar future scenarios (like a complex > certificate hierarchy) > > > > Suggestion : > > > > Consider adding an exported parameter, such as : > > modparam("stir_shaken", "crl_signing_certs", > "/stir_certs/crl_signing_certs.pem") > > > > This parameter would allow users to specify a list of separate > certificates used to sign the CRLs, in cases where the CRLs and the > provider certificates are not signed by the same certificate. > _______________________________________________ > 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 amel.guesmi at sofrecom.com Thu Aug 10 13:26:39 2023 From: amel.guesmi at sofrecom.com (amel.guesmi at sofrecom.com) Date: Thu, 10 Aug 2023 13:26:39 +0000 Subject: [OpenSIPS-Users] B2BUA - REFER- detect 200 OK to send notify In-Reply-To: <5fd9f02607c74328893495b2851587b9@orange.com> References: <0185ced03c8b496490c5390a82f87719@orange.com> <5fd9f02607c74328893495b2851587b9@orange.com> Message-ID: Could anyone help us to move forward in this subject please ? If more clarification or details need , please let me know Thank you very much De : GUESMI Amel SOFRECOM Envoyé : lundi 7 août 2023 10:54 À : 'users at lists.opensips.org' Cc : DL FT-FR Sbc TEAM Objet : B2BUA - REFER- detect 200 OK to send notify Hello all, Sorry for sending this question several times, hope i get some help this time 😊 We are trying to implement the « REFER » method in opensips 3.3. we used this documentation : openSIPS | Documentation / Tutorials-B2BUA When we detect a REFER method, we are excuting those functions : b2b_send_reply(202, "Accepted"); # Example: Send NOTIFY request $var(destination) = $hdr(Refer-From); $var(message_body) = "This is the message body of the NOTIFY"; send_request("NOTIFY", $var(destination), $hdr(Refer-To), $var(message_body)); # create the client entity corresponding to # the user specified in the 'Refer-To' header b2b_client_new("referee", $hdr(Refer-To)); # bridge the referrer's peer with the referee b2b_bridge("peer", "referee"); #b2b_end_dlg_leg(); With that scenario, we succeeded in transfering a call after the REFER and we are tryning now to implement that process with « Notify » after the REFER (see the flow in the following link). REFER_-_User_docs_2.width-800.png (720×540) (twilio.com) For this, when we open the new client session, we don’t end the session with the one sending the REFER and we need to detect when the call is accepted by the Callee (200 OK) when we are using that function : b2b_client_new("referee", $hdr(Refer-To)); How can we detect the 200 OK in that B2B mode in order to send the NOTIFY before ending the session with Alice. Thank you very much BR, Amel Orange Restricted -------------- next part -------------- An HTML attachment was scrubbed... URL: From amel.guesmi at sofrecom.com Fri Aug 11 11:19:30 2023 From: amel.guesmi at sofrecom.com (amel.guesmi at sofrecom.com) Date: Fri, 11 Aug 2023 11:19:30 +0000 Subject: [OpenSIPS-Users] Change contact - B2B in opensips with docker bridge network mode Message-ID: <2ea5ec2fc2fe4f888a5047c7da28956f@orange.com> Hello dear opensips community, We are trying to implement the B2B with TLS, we have opensips installed in docker, with netwrok bridge mode. We are facing a problem with private Docker interface : the < contact > in the invite is sent with the private docker adresse not the adress of the host machine. We want a solution to change the < contact > field in the INVITE because we can't receive the ACK from the callee when the contact of opensips is a docker private adress. This is an example of an INVITE with the the public adress and the container private adress : INVITE sip:+Number;tgrp=xxxxxx at Y.Y.Y.Y:5061;user=phone;transport=udp SIP/2.0 Via: SIP/2.0/UDP Public_Host_adress:5060;branch=z9hG4bKa547.ede09bf3.0 To: .... Contact: Hope my request is clear Thank you very much BR, Amel -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Mon Aug 14 10:48:24 2023 From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=) Date: Mon, 14 Aug 2023 13:48:24 +0300 Subject: [OpenSIPS-Users] Change contact - B2B in opensips with docker bridge network mode In-Reply-To: <2ea5ec2fc2fe4f888a5047c7da28956f@orange.com> References: <2ea5ec2fc2fe4f888a5047c7da28956f@orange.com> Message-ID: Hi, Amel! Change the advertised address of your socket[1] using the ` AS PUBLIC_IP:PUBLIC_PORT` token. [1] https://www.opensips.org/Documentation/Script-CoreParameters-3-2#toc67 Best regards, Răzvan Crainea OpenSIPS Core Developer / SIPhub CTO http://www.opensips-solutions.com / https://www.siphub.com On 8/11/23 14:19, amel.guesmi at sofrecom.com wrote: > Hello dear opensips community, > > We are trying to implement the *B2B* with *TLS*, we have opensips > installed in *docker*, with *netwrok bridge mode*. > > We are facing a problem with *private Docker interface* : > the« contact »in the invite is sent with the private docker adresse not > the adress of the host machine. > > We want a solution to change the « contact »field in the INVITEbecause > we can't receive the ACKfrom the callee when the contact of opensips is > a docker private adress. > > This is an example of an INVITE with the  the public adress and  the > container private adress : > > INVITE sip:+Number;tgrp=xxxxxx at Y.Y.Y.Y:5061;user=phone;transport=udp > SIP/2.0 > > Via: SIP/2.0/UDP *Public_Host_adress*:5060;branch=z9hG4bKa547.ede09bf3.0 > > To: > > .... > > Contact: <*sip:Private_Container_adress*> > > Hope my request is clear > > Thank you very much > > BR, Amel > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From devang.dhandhalya at ecosmob.com Mon Aug 14 10:51:17 2023 From: devang.dhandhalya at ecosmob.com (Devang Dhandhalya) Date: Mon, 14 Aug 2023 16:21:17 +0530 Subject: [OpenSIPS-Users] Caller not able to hear Audio file Message-ID: Hello All I am facing the problem that when I make a call, I am not able to hear the audio file on my softphone(zoiper3&5, microsip) which is playing from opensips using rtpengine module, but when i capture the that call sip trace and load that pcap in wireshark i am able to hear audio file music. Here is the code snippet: rtpengine_offer(); append_to_reply("Content-Type: application/sdp\r\n"); $var(body) = $(rb{re.subst,/(IP4.).*/\1127.0.0.1/g}); t_reply_with_body(183, "Session Progress", $var(body)); rtpengine_play_media("file=/home/file_example_WAV_2MG_G711.org_1.wav"); opensips version: 3.2.5 I am using a Standard wave audio file with 8KHz, 16bit mono, I used other formats (i.e.mp3) as well but still in softphones I am not able to Hear voice but in wireshark I am able to hear mp3 file voice. I would appreciate it if someone has an idea what to do. Please feel free to ask if you think I have forgotten to describe something that might be important or something is unclear in what I have written. Regards Devang Dhandhalya -- *Disclaimer* In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis of any of the information contained in this email is hereby excluded. *Confidentiality* This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error. *Caution for viruses, malware etc.* This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware, interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems.  -------------- next part -------------- An HTML attachment was scrubbed... URL: From trumpetguy900s at gmail.com Fri Aug 18 02:49:59 2023 From: trumpetguy900s at gmail.com (trumpetguy) Date: Thu, 17 Aug 2023 19:49:59 -0700 Subject: [OpenSIPS-Users] opensips-cli errors Message-ID: Greetings - I recently installed Opensips v3.3 on a CentOS Linux physical server via yum. When I attempt to create the Opensips databases using opensips-cli, I am constantly getting errors and the databases are not created. I have provided the screen output from running "opensips-cli -f /etc/opensips/opensips-cli.cfg -x database create" below: # opensips-cli -f /etc/opensips/opensips-cli.cfg -x database create DEBUG: Loaded module 'database' DEBUG: running in non-interactive mode database create [] DEBUG: running command 'create' '[]' DEBUG: db_name: 'opensips' Password for admin MySQL user (root): DEBUG: read password: '' DEBUG: admin DB URL: 'mysql://root:@localhost' DEBUG: DB URL: 'mysql://opensips:opensipsrw at localhost' DEBUG: connecting to mysql://root:@localhost Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 1122, in _do_get return self._pool.get(wait, self._timeout) File "/usr/lib64/python3.6/site-packages/sqlalchemy/util/queue.py", line 145, in get raise Empty sqlalchemy.util.queue.Empty During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib64/python3.6/site-packages/sqlalchemy/engine/base.py", line 2141, in _wrap_pool_connect return fn() File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 328, in unique_connection return _ConnectionFairy._checkout(self) File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 766, in _checkout fairy = _ConnectionRecord.checkout(pool) File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 516, in checkout rec = pool._do_get() File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 1138, in _do_get self._dec_overflow() File "/usr/lib64/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 60, in __exit__ compat.reraise(exc_type, exc_value, exc_tb) File "/usr/lib64/python3.6/site-packages/sqlalchemy/util/compat.py", line 186, in reraise raise value File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 1135, in _do_get return self._create_connection() File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 333, in _create_connection return _ConnectionRecord(self) File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 461, in __init__ self.__connect(first_connect_check=True) File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 661, in __connect exec_once(self.connection, self) File "/usr/lib64/python3.6/site-packages/sqlalchemy/event/attr.py", line 246, in exec_once self(*args, **kw) File "/usr/lib64/python3.6/site-packages/sqlalchemy/event/attr.py", line 256, in __call__ fn(*args, **kw) File "/usr/lib64/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 1321, in go return once_fn(*arg, **kw) File "/usr/lib64/python3.6/site-packages/sqlalchemy/engine/strategies.py", line 181, in first_connect dialect.initialize(c) File "/usr/lib64/python3.6/site-packages/sqlalchemy/dialects/mysql/base.py", line 1632, in initialize default.DefaultDialect.initialize(self, connection) File "/usr/lib64/python3.6/site-packages/sqlalchemy/engine/default.py", line 249, in initialize self.get_isolation_level(connection.connection) File "/usr/lib64/python3.6/site-packages/sqlalchemy/dialects/mysql/base.py", line 1496, in get_isolation_level cursor.execute('SELECT @@tx_isolation') File "/usr/lib64/python3.6/site-packages/MySQLdb/cursors.py", line 255, in execute self.errorhandler(self, exc, value) File "/usr/lib64/python3.6/site-packages/MySQLdb/connections.py", line 50, in defaulterrorhandler raise errorvalue File "/usr/lib64/python3.6/site-packages/MySQLdb/cursors.py", line 252, in execute res = self._query(query) File "/usr/lib64/python3.6/site-packages/MySQLdb/cursors.py", line 378, in _query db.query(q) File "/usr/lib64/python3.6/site-packages/MySQLdb/connections.py", line 280, in query _mysql.connection.query(self, query) _mysql_exceptions.OperationalError: (1193, "Unknown system variable 'tx_isolation'") The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/opensipscli/db.py", line 208, in __init__ self.__conn = self.__engine.connect().\ File "/usr/lib64/python3.6/site-packages/sqlalchemy/engine/base.py", line 2085, in connect return self._connection_cls(self, **kwargs) File "/usr/lib64/python3.6/site-packages/sqlalchemy/engine/base.py", line 90, in __init__ if connection is not None else engine.raw_connection() File "/usr/lib64/python3.6/site-packages/sqlalchemy/engine/base.py", line 2171, in raw_connection self.pool.unique_connection, _connection) File "/usr/lib64/python3.6/site-packages/sqlalchemy/engine/base.py", line 2145, in _wrap_pool_connect e, dialect, self) File "/usr/lib64/python3.6/site-packages/sqlalchemy/engine/base.py", line 1456, in _handle_dbapi_exception_noconnection exc_info File "/usr/lib64/python3.6/site-packages/sqlalchemy/util/compat.py", line 202, in raise_from_cause reraise(type(exception), exception, tb=exc_tb, cause=cause) File "/usr/lib64/python3.6/site-packages/sqlalchemy/util/compat.py", line 185, in reraise raise value.with_traceback(tb) File "/usr/lib64/python3.6/site-packages/sqlalchemy/engine/base.py", line 2141, in _wrap_pool_connect return fn() File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 328, in unique_connection return _ConnectionFairy._checkout(self) File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 766, in _checkout fairy = _ConnectionRecord.checkout(pool) File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 516, in checkout rec = pool._do_get() File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 1138, in _do_get self._dec_overflow() File "/usr/lib64/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 60, in __exit__ compat.reraise(exc_type, exc_value, exc_tb) File "/usr/lib64/python3.6/site-packages/sqlalchemy/util/compat.py", line 186, in reraise raise value File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 1135, in _do_get return self._create_connection() File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 333, in _create_connection return _ConnectionRecord(self) File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 461, in __init__ self.__connect(first_connect_check=True) File "/usr/lib64/python3.6/site-packages/sqlalchemy/pool.py", line 661, in __connect exec_once(self.connection, self) File "/usr/lib64/python3.6/site-packages/sqlalchemy/event/attr.py", line 246, in exec_once self(*args, **kw) File "/usr/lib64/python3.6/site-packages/sqlalchemy/event/attr.py", line 256, in __call__ fn(*args, **kw) File "/usr/lib64/python3.6/site-packages/sqlalchemy/util/langhelpers.py", line 1321, in go return once_fn(*arg, **kw) File "/usr/lib64/python3.6/site-packages/sqlalchemy/engine/strategies.py", line 181, in first_connect dialect.initialize(c) File "/usr/lib64/python3.6/site-packages/sqlalchemy/dialects/mysql/base.py", line 1632, in initialize default.DefaultDialect.initialize(self, connection) File "/usr/lib64/python3.6/site-packages/sqlalchemy/engine/default.py", line 249, in initialize self.get_isolation_level(connection.connection) File "/usr/lib64/python3.6/site-packages/sqlalchemy/dialects/mysql/base.py", line 1496, in get_isolation_level cursor.execute('SELECT @@tx_isolation') File "/usr/lib64/python3.6/site-packages/MySQLdb/cursors.py", line 255, in execute self.errorhandler(self, exc, value) File "/usr/lib64/python3.6/site-packages/MySQLdb/connections.py", line 50, in defaulterrorhandler raise errorvalue File "/usr/lib64/python3.6/site-packages/MySQLdb/cursors.py", line 252, in execute res = self._query(query) File "/usr/lib64/python3.6/site-packages/MySQLdb/cursors.py", line 378, in _query db.query(q) File "/usr/lib64/python3.6/site-packages/MySQLdb/connections.py", line 280, in query _mysql.connection.query(self, query) sqlalchemy.exc.OperationalError: (_mysql_exceptions.OperationalError) (1193, "Unknown system variable 'tx_isolation'") During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/bin/opensips-cli", line 9, in run_console() File "/bin/opensips-cli", line 6, in run_console main.main() File "/usr/lib/python3.6/site-packages/opensipscli/main.py", line 78, in main sys.exit(shell.cmdloop()) File "/usr/lib/python3.6/site-packages/opensipscli/cli.py", line 247, in cmdloop ret = self.run_command(module, command, modifiers, params) File "/usr/lib/python3.6/site-packages/opensipscli/cli.py", line 409, in run_command return mod[0].__invoke__(cmd, params, modifiers) File "/usr/lib/python3.6/site-packages/opensipscli/module.py", line 36, in __invoke__ return f(params, modifiers) File "/usr/lib/python3.6/site-packages/opensipscli/modules/database.py", line 598, in do_create db = self.get_db(admin_url if engine != 'sqlite' else db_url, db_name) File "/usr/lib/python3.6/site-packages/opensipscli/modules/database.py", line 871, in get_db return osdb(db_url, db_name) File "/usr/lib/python3.6/site-packages/opensipscli/db.py", line 233, in __init__ raise osdbError("unable to connect to the database") opensipscli.db.osdbError: unable to connect to the database The contents of the opensips-cli.cfg file are as follows: [default] database_modules: ALL log_level: DEBUG database_admin_url: mysql://root at localhost database_name: opensips database_url: mysql://opensips:opensipsrw at localhost database_path: /usr/share/opensips/ communication_type: fifo fifo_file: /var/run/opensips/opensips_fifo The OS is CentOS 7 x86, and the version of MySql installed on the server is MySQL Community Server v8.0.34. Any advice or assistance would be greatly appreciated! Regards, Brian -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy_james2023 at proton.me Fri Aug 18 10:40:32 2023 From: andy_james2023 at proton.me (Andrew James) Date: Fri, 18 Aug 2023 10:40:32 +0000 Subject: [OpenSIPS-Users] Webrtc Error Message-ID: Hi All, I am currently using webrtc with the WSS module to mid_registrar in opensips 3.2 I notice when a device is unregistered it does not de-register but i get this error in the logs ERROR:proto_wss:ws_sync_connect: tcp_blocking_connect failed ERROR:tm:msg_send: send() to xxxx:57816 for proto wss/6 failed I am using opensips 3.2 in Docker, does anyone have any advice what it might be and how i can possibly look for a solution? Thanks! Andy Sent with [Proton Mail](https://proton.me/) secure email. -------------- next part -------------- An HTML attachment was scrubbed... URL: From prathibhab.tvm at gmail.com Mon Aug 21 08:03:47 2023 From: prathibhab.tvm at gmail.com (Prathibha B) Date: Mon, 21 Aug 2023 13:33:47 +0530 Subject: [OpenSIPS-Users] Error in opensips.cfg file Message-ID: Aug 21 08:02:24 [210480] CRITICAL:Traceback (last included file at the bottom): Aug 21 08:02:24 [210480] CRITICAL: 0. //etc/opensips/opensips.cfg Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:250:16-18: syntax error Aug 21 08:02:24 [210480] CRITICAL: if (is_method("REGISTER")) Aug 21 08:02:24 [210480] CRITICAL: { Aug 21 08:02:24 [210480] CRITICAL: if(proto_wss == WSS) { Aug 21 08:02:24 [210480] CRITICAL: ^~~ Aug 21 08:02:24 [210480] CRITICAL: fix_nated_register(); Aug 21 08:02:24 [210480] CRITICAL: } Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:250:16-18: bare word found, command calls need '()' Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:250:16-18: bad command!) Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:250:22-23: bare word found, command calls need '()' Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:250:22-23: bad command: missing ';'? Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:250:24-25: bad command!) Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:256:3-5: syntax error Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:256:3-5: Aug 21 08:02:24 [210480] ERROR:core:parse_opensips_cfg: bad config file (8 errors) Aug 21 08:02:24 [210480] ERROR:core:main: failed to parse config file (null) Aug 21 08:02:24 [210480] NOTICE:core:main: Exiting.... -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From prathibhab.tvm at gmail.com Mon Aug 21 08:04:51 2023 From: prathibhab.tvm at gmail.com (Prathibha B) Date: Mon, 21 Aug 2023 13:34:51 +0530 Subject: [OpenSIPS-Users] Error in opensips.cfg file In-Reply-To: References: Message-ID: if(proto === WSS) On Mon, 21 Aug 2023 at 13:33, Prathibha B wrote: > Aug 21 08:02:24 [210480] CRITICAL:Traceback (last included file at the > bottom): > Aug 21 08:02:24 [210480] CRITICAL: 0. //etc/opensips/opensips.cfg > Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:250:16-18: syntax error > Aug 21 08:02:24 [210480] CRITICAL: if (is_method("REGISTER")) > Aug 21 08:02:24 [210480] CRITICAL: { > Aug 21 08:02:24 [210480] CRITICAL: if(proto_wss == WSS) { > Aug 21 08:02:24 [210480] CRITICAL: ^~~ > Aug 21 08:02:24 [210480] CRITICAL: > fix_nated_register(); > Aug 21 08:02:24 [210480] CRITICAL: } > Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:250:16-18: bare word found, command > calls need '()' > Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:250:16-18: bad command!) > Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:250:22-23: bare word found, command calls > need '()' > Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:250:22-23: bad command: missing ';'? > Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:250:24-25: bad command!) > Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:256:3-5: syntax error > Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:256:3-5: > Aug 21 08:02:24 [210480] ERROR:core:parse_opensips_cfg: bad config file (8 > errors) > Aug 21 08:02:24 [210480] ERROR:core:main: failed to parse config file > (null) > Aug 21 08:02:24 [210480] NOTICE:core:main: Exiting.... > > -- > Regards, > B.Prathibha > -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From prathibhab.tvm at gmail.com Mon Aug 21 10:41:07 2023 From: prathibhab.tvm at gmail.com (Prathibha B) Date: Mon, 21 Aug 2023 16:11:07 +0530 Subject: [OpenSIPS-Users] ERROR:core:handle_new_connect: failed to accept connection(24): Too many open files Message-ID: Getting this error while starting opensips -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From amel.guesmi at sofrecom.com Mon Aug 21 14:21:11 2023 From: amel.guesmi at sofrecom.com (amel.guesmi at sofrecom.com) Date: Mon, 21 Aug 2023 14:21:11 +0000 Subject: [OpenSIPS-Users] REFER- detect 200 OK to send notify - B2BUA Message-ID: <5cc12cb7d3364e0b8cf2a4d053f621b8@orange.com> Hello all, Sending this question one more time, hope i can’t get some ideas to move forward. We are trying to implement the « REFER » method in opensips 3.3. we used this documentation : openSIPS | Documentation / Tutorials-B2BUA When we detect a REFER method, we are excuting those functions : b2b_send_reply(202, "Accepted"); # Example: Send NOTIFY request $var(destination) = $hdr(Refer-From); $var(message_body) = "This is the message body of the NOTIFY"; send_request("NOTIFY", $var(destination), $hdr(Refer-To), $var(message_body)); # create the client entity corresponding to # the user specified in the 'Refer-To' header b2b_client_new("referee", $hdr(Refer-To)); # bridge the referrer's peer with the referee b2b_bridge("peer", "referee"); #b2b_end_dlg_leg(); With that scenario, we succeeded in transfering a call after the REFER and we are tryning now to implement that process with « Notify » after the REFER (see the flow in the following link). REFER_-_User_docs_2.width-800.png (720×540) (twilio.com) For this, when we open the new client session, we don’t end the session with the one sending the REFER and we need to detect when the call is accepted by the Callee (200 OK) when we are using that function : b2b_client_new("referee", $hdr(Refer-To)); My question : How can we detect the 200 OK in that B2B mode in order to send the NOTIFY before ending the session with Alice. Thank you very much BR, Amel Orange Restricted -------------- next part -------------- An HTML attachment was scrubbed... URL: From jjackson at aninetworks.net Mon Aug 21 16:20:26 2023 From: jjackson at aninetworks.net (Joseph Jackson) Date: Mon, 21 Aug 2023 16:20:26 +0000 Subject: [OpenSIPS-Users] ERROR:core:handle_new_connect: failed to accept connection(24): Too many open files In-Reply-To: References: Message-ID: You can set the open file limit - https://www.opensips.org/Documentation/Script-CoreParameters-3-1#open_files_limit But you should find out why you are hitting the open file limit. ________________________________ From: Users on behalf of Prathibha B Sent: Monday, August 21, 2023 5:41 AM To: users at lists.opensips.org Subject: [OpenSIPS-Users] ERROR:core:handle_new_connect: failed to accept connection(24): Too many open files Getting this error while starting opensips -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From prathibhab.tvm at gmail.com Tue Aug 22 03:36:33 2023 From: prathibhab.tvm at gmail.com (Prathibha B) Date: Tue, 22 Aug 2023 09:06:33 +0530 Subject: [OpenSIPS-Users] ERROR:core:handle_new_connect: failed to accept connection(24): Too many open files In-Reply-To: References: Message-ID: How to find out the open files? On Mon, 21 Aug 2023 at 21:53, Joseph Jackson wrote: > You can set the open file limit - > https://www.opensips.org/Documentation/Script-CoreParameters-3-1#open_files_limit > > But you should find out why you are hitting the open file limit. > ------------------------------ > *From:* Users on behalf of Prathibha B > > *Sent:* Monday, August 21, 2023 5:41 AM > *To:* users at lists.opensips.org > *Subject:* [OpenSIPS-Users] ERROR:core:handle_new_connect: failed to > accept connection(24): Too many open files > > Getting this error while starting opensips > > -- > Regards, > B.Prathibha > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From vinayak.makwana at ecosmob.com Wed Aug 23 11:38:19 2023 From: vinayak.makwana at ecosmob.com (Vinayak Makwana) Date: Wed, 23 Aug 2023 17:08:19 +0530 Subject: [OpenSIPS-Users] Compatibility Inquiry: Opensips 3.2.12 with RHEL 9 Message-ID: Hello all, I hope this message finds you well. I am currently in the process of installing Opensips 3.2.12 Version on RHEL 9 OS. However, I've encountered some dependency issues during the compilation of the required modules. To address this, I am actively working on resolving these issues and installing the necessary dependencies by compiling them from their respective source codes. My primary concern is to determine the compatibility of Opensips 3.2.12 with the RHEL 9 Operating System. I would greatly appreciate any insights or guidance you can provide on this matter. Thank you for your time and assistance. Regards, Vinayak Makwana -- *Disclaimer* In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis of any of the information contained in this email is hereby excluded. *Confidentiality* This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error. *Caution for viruses, malware etc.* This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware, interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems.  -------------- next part -------------- An HTML attachment was scrubbed... URL: From prathibhab.tvm at gmail.com Thu Aug 31 04:34:57 2023 From: prathibhab.tvm at gmail.com (Prathibha B) Date: Thu, 31 Aug 2023 10:04:57 +0530 Subject: [OpenSIPS-Users] Error in opensips.cfg file In-Reply-To: References: Message-ID: bare word found, command calls need '()' On Mon, 21 Aug 2023 at 13:34, Prathibha B wrote: > if(proto === WSS) > > On Mon, 21 Aug 2023 at 13:33, Prathibha B > wrote: > >> Aug 21 08:02:24 [210480] CRITICAL:Traceback (last included file at the >> bottom): >> Aug 21 08:02:24 [210480] CRITICAL: 0. //etc/opensips/opensips.cfg >> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >> //etc/opensips/opensips.cfg:250:16-18: syntax error >> Aug 21 08:02:24 [210480] CRITICAL: if (is_method("REGISTER")) >> Aug 21 08:02:24 [210480] CRITICAL: { >> Aug 21 08:02:24 [210480] CRITICAL: if(proto_wss == WSS) { >> Aug 21 08:02:24 [210480] CRITICAL: ^~~ >> Aug 21 08:02:24 [210480] CRITICAL: >> fix_nated_register(); >> Aug 21 08:02:24 [210480] CRITICAL: } >> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >> //etc/opensips/opensips.cfg:250:16-18: bare word found, command >> calls need '()' >> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >> //etc/opensips/opensips.cfg:250:16-18: bad command!) >> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >> //etc/opensips/opensips.cfg:250:22-23: bare word found, command calls >> need '()' >> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >> //etc/opensips/opensips.cfg:250:22-23: bad command: missing ';'? >> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >> //etc/opensips/opensips.cfg:250:24-25: bad command!) >> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >> //etc/opensips/opensips.cfg:256:3-5: syntax error >> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >> //etc/opensips/opensips.cfg:256:3-5: >> Aug 21 08:02:24 [210480] ERROR:core:parse_opensips_cfg: bad config file >> (8 errors) >> Aug 21 08:02:24 [210480] ERROR:core:main: failed to parse config file >> (null) >> Aug 21 08:02:24 [210480] NOTICE:core:main: Exiting.... >> >> -- >> Regards, >> B.Prathibha >> > > > -- > Regards, > B.Prathibha > -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From prathibhab.tvm at gmail.com Thu Aug 31 05:15:47 2023 From: prathibhab.tvm at gmail.com (Prathibha B) Date: Thu, 31 Aug 2023 10:45:47 +0530 Subject: [OpenSIPS-Users] Error in opensips.cfg file In-Reply-To: References: Message-ID: Aug 31 04:14:49 [339966] CRITICAL:Traceback (last included file at the bottom): Aug 31 04:14:49 [339966] CRITICAL: 0. //etc/opensips/opensips.cfg Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:183:12-14: syntax error Aug 31 04:14:49 [339966] CRITICAL: Aug 31 04:14:49 [339966] CRITICAL: # check if the clients are using WebSockets or WebSocketSecure Aug 31 04:14:49 [339966] CRITICAL: if (proto == "WS" || proto == "WSS") Aug 31 04:14:49 [339966] CRITICAL: ^~~ Aug 31 04:14:49 [339966] CRITICAL: setflag(SRC_WS); Aug 31 04:14:49 [339966] CRITICAL: Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:183:12-14: bare word found, command calls need '()' Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:183:12-14: bad command!) Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:183:16-17: bad command!) Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:183:18-20: bad command!) Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:183:27-29: bare word found, command calls need '()' Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:183:27-29: bad command: missing ';'? Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:183:31-32: bad command!) Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:183:32-33: bad command!) Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:184:17-18: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:193:17-23: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:193:23-24: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:194:13-19: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:194:19-20: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:239:16-22: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:239:22-23: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:239:38-44: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:239:44-45: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:241:21-27: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:241:27-28: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:241:44-50: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:241:50-51: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:243:22-28: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:243:28-29: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:243:44-50: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:243:50-51: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:245:22-28: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:245:28-29: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:245:45-51: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:245:51-52: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:257:16-22: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:257:22-23: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:257:38-44: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:257:44-45: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:259:21-27: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:259:27-28: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:259:44-50: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:259:50-51: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:261:22-28: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:261:28-29: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:261:44-50: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:261:50-51: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:263:22-28: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:263:28-29: bad arguments for command Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:263:45-51: syntax error Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:263:51-52: bad arguments for command Aug 31 04:14:49 [339966] ERROR:core:parse_opensips_cfg: bad config file (46 errors) Aug 31 04:14:49 [339966] ERROR:core:main: failed to parse config file (null) Aug 31 04:14:49 [339966] NOTICE:core:main: Exiting.... On Thu, 31 Aug 2023 at 10:04, Prathibha B wrote: > bare word found, command calls need '()' > > On Mon, 21 Aug 2023 at 13:34, Prathibha B > wrote: > >> if(proto === WSS) >> >> On Mon, 21 Aug 2023 at 13:33, Prathibha B >> wrote: >> >>> Aug 21 08:02:24 [210480] CRITICAL:Traceback (last included file at the >>> bottom): >>> Aug 21 08:02:24 [210480] CRITICAL: 0. //etc/opensips/opensips.cfg >>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>> //etc/opensips/opensips.cfg:250:16-18: syntax error >>> Aug 21 08:02:24 [210480] CRITICAL: if (is_method("REGISTER")) >>> Aug 21 08:02:24 [210480] CRITICAL: { >>> Aug 21 08:02:24 [210480] CRITICAL: if(proto_wss == WSS) { >>> Aug 21 08:02:24 [210480] CRITICAL: ^~~ >>> Aug 21 08:02:24 [210480] CRITICAL: >>> fix_nated_register(); >>> Aug 21 08:02:24 [210480] CRITICAL: } >>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>> //etc/opensips/opensips.cfg:250:16-18: bare word found, command >>> calls need '()' >>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>> //etc/opensips/opensips.cfg:250:16-18: bad command!) >>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>> //etc/opensips/opensips.cfg:250:22-23: bare word found, command calls >>> need '()' >>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>> //etc/opensips/opensips.cfg:250:22-23: bad command: missing ';'? >>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>> //etc/opensips/opensips.cfg:250:24-25: bad command!) >>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>> //etc/opensips/opensips.cfg:256:3-5: syntax error >>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>> //etc/opensips/opensips.cfg:256:3-5: >>> Aug 21 08:02:24 [210480] ERROR:core:parse_opensips_cfg: bad config file >>> (8 errors) >>> Aug 21 08:02:24 [210480] ERROR:core:main: failed to parse config file >>> (null) >>> Aug 21 08:02:24 [210480] NOTICE:core:main: Exiting.... >>> >>> -- >>> Regards, >>> B.Prathibha >>> >> >> >> -- >> Regards, >> B.Prathibha >> > > > -- > Regards, > B.Prathibha > -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From prathibhab.tvm at gmail.com Thu Aug 31 07:18:55 2023 From: prathibhab.tvm at gmail.com (Prathibha B) Date: Thu, 31 Aug 2023 12:48:55 +0530 Subject: [OpenSIPS-Users] bad arguments for command Message-ID: Aug 31 06:58:48 [346547] CRITICAL:Traceback (last included file at the bottom): Aug 31 06:58:48 [346547] CRITICAL: 0. //etc/opensips/opensips.cfg Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:184:11-17: syntax error Aug 31 06:58:48 [346547] CRITICAL: # check if the clients are using WebSockets or WebSocketSecure Aug 31 06:58:48 [346547] CRITICAL: if ($socket_in(proto) == "WS" || $socket_in(proto) == "WSS") Aug 31 06:58:48 [346547] CRITICAL: setflag(SRC_WS); Aug 31 06:58:48 [346547] CRITICAL: ^~~~~~~ Aug 31 06:58:48 [346547] CRITICAL: Aug 31 06:58:48 [346547] CRITICAL: # consider the client is behind NAT - always fix the contact Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:184:17-18: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:193:17-23: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:193:23-24: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:194:13-19: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:194:19-20: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:239:16-22: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:239:22-23: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:239:38-44: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:239:44-45: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:241:21-27: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:241:27-28: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:241:44-50: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:241:50-51: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:243:22-28: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:243:28-29: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:243:44-50: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:243:50-51: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:245:22-28: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:245:28-29: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:245:45-51: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:245:51-52: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:257:16-22: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:257:22-23: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:257:38-44: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:257:44-45: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:259:21-27: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:259:27-28: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:259:44-50: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:259:50-51: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:261:22-28: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:261:28-29: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:261:44-50: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:261:50-51: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:263:22-28: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:263:28-29: bad arguments for command Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:263:45-51: syntax error Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in //etc/opensips/opensips.cfg:263:51-52: bad arguments for command Aug 31 06:58:48 [346547] ERROR:core:parse_opensips_cfg: bad config file (38 errors) Aug 31 06:58:48 [346547] ERROR:core:main: failed to parse config file (null) Aug 31 06:58:48 [346547] NOTICE:core:main: Exiting.... -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From prathibhab.tvm at gmail.com Thu Aug 31 07:35:35 2023 From: prathibhab.tvm at gmail.com (Prathibha B) Date: Thu, 31 Aug 2023 13:05:35 +0530 Subject: [OpenSIPS-Users] check_actions: check failed for function Message-ID: Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be an integer or variable Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for function , //etc/opensips/opensips.cfg:102 Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be an integer or variable Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for function , //etc/opensips/opensips.cfg:103 Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be an integer or variable Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for function , //etc/opensips/opensips.cfg:229 Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be an integer or variable Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for function , //etc/opensips/opensips.cfg:134 Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be an integer or variable Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for function , //etc/opensips/opensips.cfg:163 Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be an integer or variable Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for function , //etc/opensips/opensips.cfg:178 Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be an integer or variable Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for function , //etc/opensips/opensips.cfg:205 Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be an integer or variable Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for function , //etc/opensips/opensips.cfg:212 Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be an integer or variable Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for function , //etc/opensips/opensips.cfg:229 Aug 31 07:31:21 [346724] ERROR:core:main: bad function call in config file -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From kwem at gmx.de Thu Aug 31 07:52:47 2023 From: kwem at gmx.de (Karsten Wemheuer) Date: Thu, 31 Aug 2023 09:52:47 +0200 Subject: [OpenSIPS-Users] bad arguments for command In-Reply-To: References: Message-ID: <30979f43b1aae83289aa89094777b99d2fa8dbd5.camel@gmx.de> Hi, Am Donnerstag, dem 31.08.2023 um 12:48 +0530 schrieb Prathibha B: > Aug 31 06:58:48 [346547] CRITICAL:Traceback (last included file at > the bottom): > Aug 31 06:58:48 [346547] CRITICAL: 0. //etc/opensips/opensips.cfg > Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:184:11-17: syntax error > Aug 31 06:58:48 [346547] CRITICAL: # check if the clients are > using WebSockets or WebSocketSecure > Aug 31 06:58:48 [346547] CRITICAL: if ($socket_in(proto) == "WS" > > > $socket_in(proto) == "WSS") > Aug 31 06:58:48 [346547] CRITICAL: setflag(SRC_WS); > Aug 31 06:58:48 [346547] CRITICAL: ^~~~~~~ > Aug 31 06:58:48 [346547] CRITICAL: > Aug 31 06:58:48 [346547] CRITICAL: # consider the client is > behind NAT - always fix the contact > Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:184:17-18: bad arguments for command > maybe use quotes around parameter like setflag("SRC_WS"); HTH, Best regards Karsten From prathibhab.tvm at gmail.com Thu Aug 31 07:56:18 2023 From: prathibhab.tvm at gmail.com (Prathibha B) Date: Thu, 31 Aug 2023 13:26:18 +0530 Subject: [OpenSIPS-Users] bad arguments for command In-Reply-To: <30979f43b1aae83289aa89094777b99d2fa8dbd5.camel@gmx.de> References: <30979f43b1aae83289aa89094777b99d2fa8dbd5.camel@gmx.de> Message-ID: using quotes around parameter resolved the issue. On Thu, 31 Aug 2023 at 13:25, Karsten Wemheuer wrote: > Hi, > > Am Donnerstag, dem 31.08.2023 um 12:48 +0530 schrieb Prathibha B: > > Aug 31 06:58:48 [346547] CRITICAL:Traceback (last included file at > > the bottom): > > Aug 31 06:58:48 [346547] CRITICAL: 0. //etc/opensips/opensips.cfg > > Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in > > //etc/opensips/opensips.cfg:184:11-17: syntax error > > Aug 31 06:58:48 [346547] CRITICAL: # check if the clients are > > using WebSockets or WebSocketSecure > > Aug 31 06:58:48 [346547] CRITICAL: if ($socket_in(proto) == "WS" > > > > $socket_in(proto) == "WSS") > > Aug 31 06:58:48 [346547] CRITICAL: setflag(SRC_WS); > > Aug 31 06:58:48 [346547] CRITICAL: ^~~~~~~ > > Aug 31 06:58:48 [346547] CRITICAL: > > Aug 31 06:58:48 [346547] CRITICAL: # consider the client is > > behind NAT - always fix the contact > > Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in > > //etc/opensips/opensips.cfg:184:17-18: bad arguments for command > > > > maybe use quotes around parameter like > setflag("SRC_WS"); > > HTH, > Best regards Karsten > > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From prathibhab.tvm at gmail.com Thu Aug 31 08:29:45 2023 From: prathibhab.tvm at gmail.com (Prathibha B) Date: Thu, 31 Aug 2023 13:59:45 +0530 Subject: [OpenSIPS-Users] Failed to start rtpengine Message-ID: ERR: [http] libwebsockets: ERROR on binding fd 9 to port 2225 (-1 98) Aug 31 08:27:33 ip-172-31-34-24 rtpengine[347912]: ERR: [http] libwebsockets: init server failed Aug 31 08:27:33 ip-172-31-34-24 rtpengine[347912]: ERR: [http] Failed to start websocket listener: LWS failed to create vhost Aug 31 08:27:33 ip-172-31-34-24 rtpengine[347912]: Fatal error: Failed to init websocket listener Aug 31 08:27:33 ip-172-31-34-24 rtpengine[347912]: CRIT: [core] Fatal error: Failed to init websocket listener Aug 31 08:27:33 ip-172-31-34-24 systemd[1]: ngcp-rtpengine-daemon.service: Main process exited, code=exited, status=255/EXCEPTION Aug 31 08:27:33 ip-172-31-34-24 systemd[1]: ngcp-rtpengine-daemon.service: Failed with result 'exit-code'. Aug 31 08:27:33 ip-172-31-34-24 systemd[1]: Failed to start NGCP RTP/media Proxy Daemon. -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Thu Aug 31 08:40:39 2023 From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=) Date: Thu, 31 Aug 2023 11:40:39 +0300 Subject: [OpenSIPS-Users] check_actions: check failed for function In-Reply-To: References: Message-ID: Hi, Prathibha! Please let us know what were your attempts to fix this error before posting on the mailing list? Did you read the error message? How did you interpret it, and what were the steps you attempted to fix it but did not work? Best regards, Răzvan Crainea OpenSIPS Core Developer / SIPhub CTO http://www.opensips-solutions.com / https://www.siphub.com On 8/31/23 10:35, Prathibha B wrote: > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > an integer or variable > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > function , //etc/opensips/opensips.cfg:102 > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > an integer or variable > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > function , //etc/opensips/opensips.cfg:103 > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > an integer or variable > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > function , //etc/opensips/opensips.cfg:229 > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > an integer or variable > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > function , //etc/opensips/opensips.cfg:134 > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > an integer or variable > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > function , //etc/opensips/opensips.cfg:163 > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > an integer or variable > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > function , //etc/opensips/opensips.cfg:178 > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > an integer or variable > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > function , //etc/opensips/opensips.cfg:205 > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > an integer or variable > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > function , //etc/opensips/opensips.cfg:212 > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > an integer or variable > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > function , //etc/opensips/opensips.cfg:229 > Aug 31 07:31:21 [346724] ERROR:core:main: bad function call in config file > > -- > Regards, > B.Prathibha > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From prathibhab.tvm at gmail.com Thu Aug 31 08:45:49 2023 From: prathibhab.tvm at gmail.com (Prathibha B) Date: Thu, 31 Aug 2023 14:15:49 +0530 Subject: [OpenSIPS-Users] check_actions: check failed for function In-Reply-To: References: Message-ID: I've fixed this issue by changing the strings to integrer. On Thu, 31 Aug 2023 at 14:13, Răzvan Crainea wrote: > Hi, Prathibha! > > Please let us know what were your attempts to fix this error before > posting on the mailing list? Did you read the error message? How did you > interpret it, and what were the steps you attempted to fix it but did > not work? > > Best regards, > > Răzvan Crainea > OpenSIPS Core Developer / SIPhub CTO > http://www.opensips-solutions.com / https://www.siphub.com > > On 8/31/23 10:35, Prathibha B wrote: > > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > > an integer or variable > > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > > function , //etc/opensips/opensips.cfg:102 > > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > > an integer or variable > > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > > function , //etc/opensips/opensips.cfg:103 > > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > > an integer or variable > > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > > function , //etc/opensips/opensips.cfg:229 > > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > > an integer or variable > > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > > function , //etc/opensips/opensips.cfg:134 > > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > > an integer or variable > > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > > function , //etc/opensips/opensips.cfg:163 > > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > > an integer or variable > > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > > function , //etc/opensips/opensips.cfg:178 > > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > > an integer or variable > > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > > function , //etc/opensips/opensips.cfg:205 > > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > > an integer or variable > > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > > function , //etc/opensips/opensips.cfg:212 > > Aug 31 07:31:21 [346724] ERROR:core:check_cmd: Param [1] expected to be > > an integer or variable > > Aug 31 07:31:21 [346724] ERROR:core:check_actions: check failed for > > function , //etc/opensips/opensips.cfg:229 > > Aug 31 07:31:21 [346724] ERROR:core:main: bad function call in config > file > > > > -- > > Regards, > > B.Prathibha > > > > _______________________________________________ > > 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 > -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From prathibhab.tvm at gmail.com Thu Aug 31 08:47:52 2023 From: prathibhab.tvm at gmail.com (Prathibha B) Date: Thu, 31 Aug 2023 14:17:52 +0530 Subject: [OpenSIPS-Users] Getting error while running rtpengine Message-ID: while running the following command: rtpengine -p /var/run/rtpengine.pid -i eth0/1.1.1.1 -n 172.31.34.24:60000 -c 172.31.34.24:60001 -m 50000 -M 55000 -E -L 7 I get the following error: [1693471138.245811] ERR: [core] FAILED TO CREATE KERNEL TABLE 0 (No such file or directory), KERNEL FORWARDING DISABLED [1693471138.256508] DEBUG: [http] Starting HTTP/WS 'localhost:2225' [1693471138.257007] DEBUG: [http] http-only callback 35 0x564634db0e40 (nil) [1693471138.257142] DEBUG: [http] Unhandled HTTP callback 35 [1693471138.257304] DEBUG: [http] http-only callback 32 0x564634db0e40 (nil) [1693471138.257483] DEBUG: [http] Unhandled HTTP callback 32 [1693471138.257633] DEBUG: [http] http-only callback 36 0x564634db0e40 (nil) [1693471138.257758] DEBUG: [http] Unhandled HTTP callback 36 [1693471138.257963] DEBUG: [http] Websocket init complete with 4 threads -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Thu Aug 31 08:51:48 2023 From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=) Date: Thu, 31 Aug 2023 11:51:48 +0300 Subject: [OpenSIPS-Users] Failed to start rtpengine In-Reply-To: References: Message-ID: Hi, Prathibha! This is the OpenSIPS mailing list - posting a RTPEngine error here without additional details of why you posted it and why this error is related to OpenSIPS is a bit out of context. Before opening a new inquiry, please make your own research and describe in the email what are the steps you attempted to fix the issue, what work, what doesn't. People on this list are just here to help you, not do your work - please describe what was your work, so that we can help you investigate further. Best regards, Răzvan Crainea OpenSIPS Core Developer / SIPhub CTO http://www.opensips-solutions.com / https://www.siphub.com On 8/31/23 11:29, Prathibha B wrote: > ERR: [http] libwebsockets: ERROR on binding fd 9 to port 2225 (-1 98) > Aug 31 08:27:33 ip-172-31-34-24 rtpengine[347912]: ERR: [http] > libwebsockets: init server failed > Aug 31 08:27:33 ip-172-31-34-24 rtpengine[347912]: ERR: [http] Failed to > start websocket listener: LWS failed to create vhost > Aug 31 08:27:33 ip-172-31-34-24 rtpengine[347912]: Fatal error: Failed > to init websocket listener > Aug 31 08:27:33 ip-172-31-34-24 rtpengine[347912]: CRIT: [core] Fatal > error: Failed to init websocket listener > Aug 31 08:27:33 ip-172-31-34-24 systemd[1]: > ngcp-rtpengine-daemon.service: Main process exited, code=exited, > status=255/EXCEPTION > Aug 31 08:27:33 ip-172-31-34-24 systemd[1]: > ngcp-rtpengine-daemon.service: Failed with result 'exit-code'. > Aug 31 08:27:33 ip-172-31-34-24 systemd[1]: Failed to start NGCP > RTP/media Proxy Daemon. > > -- > Regards, > B.Prathibha > > _______________________________________________ > Users mailing list > Users at lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users From prathibhab.tvm at gmail.com Thu Aug 31 08:52:24 2023 From: prathibhab.tvm at gmail.com (Prathibha B) Date: Thu, 31 Aug 2023 14:22:24 +0530 Subject: [OpenSIPS-Users] systemctl status opensips Message-ID: opensips.service - LSB: Start the OpenSIPS SIP server Loaded: loaded (/etc/init.d/opensips; generated) * Active: active (exited) since Thu 2023-08-31 08:17:20 UTC; 32min ago* Docs: man:systemd-sysv-generator(8) Process: 347316 ExecStart=/etc/init.d/opensips start (*code=exited, status=0/SUCCESS*) CPU: 44ms Aug 31 08:17:20 ip-172-31-34-24 systemd[1]: Starting LSB: Start the OpenSIPS SIP server... Aug 31 08:17:20 ip-172-31-34-24 opensips[347316]: * Starting opensips opensips Aug 31 08:17:20 ip-172-31-34-24 opensips[347333]: Listening on Aug 31 08:17:20 ip-172-31-34-24 opensips[347333]: udp: 127.0.0.1 [127.0.0.1]:5060 Aug 31 08:17:20 ip-172-31-34-24 opensips[347333]: tls: 127.0.0.1 [127.0.0.1]:5061 Aug 31 08:17:20 ip-172-31-34-24 opensips[347333]: ws: 127.0.0.1 [127.0.0.1]:8080 Aug 31 08:17:20 ip-172-31-34-24 opensips[347333]: wss: 127.0.0.1 [127.0.0.1]:443 Aug 31 08:17:20 ip-172-31-34-24 opensips[347333]: Aliases: Aug 31 08:17:20 ip-172-31-34-24 opensips[347316]: already running ...done. Aug 31 08:17:20 ip-172-31-34-24 systemd[1]: Started LSB: Start the OpenSIPS SIP server. *netstat -ltnup doesn't show 5060, 5061, 8080 and 443* -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From razvan at opensips.org Thu Aug 31 14:58:35 2023 From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=) Date: Thu, 31 Aug 2023 17:58:35 +0300 Subject: [OpenSIPS-Users] [Release] OpenSIPS 3.1.x LTS end of support Message-ID: Hi, all! The OpenSIPS 3.1.x LTS branch has finally come to its end of support. Starting today, 31st of August 2023, after the last 3.1.17 release, we will no longer offer support for this branch, nor integrate any upcoming bug fixes. We strongly advise you to upgrade your setup to a supported LTS release, either 3.2, or, ideally 3.4. More details about the available stable releases be found here[1]. [1] https://www.opensips.org/About/AvailableVersions Best regards, -- Răzvan Crainea OpenSIPS Core Developer / SIPhub CTO http://www.opensips-solutions.com / https://www.siphub.com From razvan at opensips.org Thu Aug 31 14:58:51 2023 From: razvan at opensips.org (=?UTF-8?Q?R=C4=83zvan_Crainea?=) Date: Thu, 31 Aug 2023 17:58:51 +0300 Subject: [OpenSIPS-Users] [Release] OpenSIPS 3.4.1, 3.3.7, 3.2.14 and 3.1.17 minor releases Message-ID: Hi all, Today we have released four new minor releases of OpenSIPS: * 3.4.1 - the first minor release of the 3.4.x LTS branch * 3.3.7 - minor release of the 3.3.x branch * 3.2.14 - minor release of the 3.2.x LTS branch * 3.1.17 - the last release of the 3.1.x LTS branch All new releases contain only bug fixes and are backwards compatible with their previous minor releases. Detailed ChangeLogs can be found on the website[1][2][3][4]. [1] https://opensips.org/pub/opensips/3.4.1/ChangeLog [2] https://opensips.org/pub/opensips/3.3.7/ChangeLog [3] https://opensips.org/pub/opensips/3.2.14/ChangeLog [4] https://opensips.org/pub/opensips/3.1.17/ChangeLog Happy Hacking! -- Răzvan Crainea OpenSIPS Core Developer / SIPhub CTO http://www.opensips-solutions.com / https://www.siphub.com From amejia at voxdatacomm.com Thu Aug 3 19:01:35 2023 From: amejia at voxdatacomm.com (Alejandro Mejia Evertsz) Date: Thu, 03 Aug 2023 19:01:35 -0000 Subject: [OpenSIPS-Users] mid_registrar and nathelper problem Message-ID: Hi! This is my first OpenSIPS installation, and I'm trying to achieve a simple sip proxy for my office extensions to register to our PBX. Got some configurations from samples all over docs and google searches and everything seems to work fine until there's a call from the PBX to a registered endpoint. The endpoint rings, but when it answers the call, it sends OK to proxy, and proxy to PBX, but when PBX sends ACK and proxy to endpoint, the ACK gets lost on the proxy (never reaching the endpoint). Same problem reported by another user on Dec. 2020 here: https://opensips.org/pipermail/users/2020-December/044146.html He didn't got any replies to his thread, so I would appreciate anyone's help here. Configuration file: https://pastebin.com/GaQEMzmb SIP Trace: https://pastebin.com/3cREhszJ As you can see, the ACK doesn't even try to leave the public (WAN) interface of the proxy. Thanks in advance for your help. Alejandro -------------- next part -------------- An HTML attachment was scrubbed... URL: From rkumar at pandorarndlabs.com Wed Aug 9 08:16:57 2023 From: rkumar at pandorarndlabs.com (rkumar at pandorarndlabs.com) Date: Wed, 09 Aug 2023 08:16:57 -0000 Subject: [OpenSIPS-Users] Unable to enable secure renegotiation option in WolfSSL from OpenSIPs 3.2.2 Message-ID: <003601d9ca99$d476e8f0$7d64bad0$@pandorarndlabs.com> Hello, We are getting issue with OpenSIPs using TLS library "WolfSSL" when clients using OpenSSL 3.0. we are getting Pre TLS handshake Errors . Please check and let us know what can be done to resolve this issue. ERROR:tls_wolfssl:_wolfssl_tls_accept: New TLS connection [0x7f1276c51740] from 202.65.142.206:51053 failed to accept ERROR:tls_wolfssl:_wolfssl_tls_accept: TLS accept error: -313, received alert fatal error , connection [0x7f1276c51740] ERROR:proto_tls:tls_read_req: failed to do pre-tls handshake! INFO:core:tcp_trigger_report: Connection [0x7f1276c51740] is getting release because of [Read error] To address above issue we are trying to enable "secure-renegotiation" from WolfSSL end but when we enable this , we are getting following error from WolfSSL library error "WRITE DUP and SECURE RENEGOTIATION cannot both be on" so we disabled "WRITE DUP" and enabled "SECURE RENEGOTIATION" , and compilation is getting succeeded but OpenSIPs unable to load WolfSSL module as it is using "WRITE DUP" functions in WolfSSL module . ERROR:core:sr_load_module: could not open module tls_wolfssl.so: undefined symbol: wolfSSL_write_dup ERROR:core:load_module: failed to load module Software versions used : OpenSIPs : 3.2.2 Embedded WolfSSL: 4.7.1 Regards, V Ravi Kumar -------------- next part -------------- An HTML attachment was scrubbed... URL: From prathibhab.tvm at gmail.com Mon Aug 14 11:13:35 2023 From: prathibhab.tvm at gmail.com (Prathibha B) Date: Mon, 14 Aug 2023 11:13:35 -0000 Subject: [OpenSIPS-Users] Failed to init TLS domain 'default' Message-ID: ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'default'. ERROR:core:init_mod: failed to initialize module tls_mgm ERROR:core:main: failed to initialize modules! -- Regards, B.Prathibha -------------- next part -------------- An HTML attachment was scrubbed... URL: From william.jin at superloop.com Wed Aug 16 05:54:01 2023 From: william.jin at superloop.com (William Jin) Date: Wed, 16 Aug 2023 05:54:01 -0000 Subject: [OpenSIPS-Users] ul_dump brief is not accepted, opensips 3.4 Message-ID: Hi, 1, looks like ul_dump brief params is not accepted OS: Ubuntu 22 opensips -V version: opensips 3.4.0-rc1 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, HP_MALLOC, DBG_MALLOC, CC_O0, 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: c64766a85 main.c compiled on with gcc 11 apt policy opensips-cli opensips-cli: Installed: 0.1~20230512~161b5ea-1 Candidate: 0.1~20230512~161b5ea-1 Version table: *** 0.1~20230512~161b5ea-1 500 500 https://apt.opensips.org jammy/cli-nightly amd64 Packages opensips-cli --version OpenSIPS CLI 0.2.0 opensips-cli -x mi ul_dump brief ERROR: command 'ul_dump' returned: -32602: Invalid params (Bad type for parameter 'brief') 2, When doing dr_reload through httpd, the load of the HTTPD ps will increase and other services rely on it like opensips prometheus will stuck and return nothing until dr_reload is completed curl -s -X POST -H 'Content-Type: application/json' {server-IP}:8888/mi -d'{"jsonrpc": "2.0","id": 1,"method": "dr_reload"}' | json_pp curl 127.0.0.1:8888/metrics Is it possible to increase the worker number of HTTPD ps? Regards, William Jin -------------- next part -------------- An HTML attachment was scrubbed... URL: From belogistics83 at gmail.com Thu Aug 17 14:05:15 2023 From: belogistics83 at gmail.com (BE. Logistics LLC) Date: Thu, 17 Aug 2023 14:05:15 +0000 Subject: [OpenSIPS-Users] We need you to fill out our Carrier Application!! Message-ID: <202317081405.pfojuy5p42rfj@bf.d.mailin.fr> # # [BE. Logistics LLC](https://5y0ou.r.a.d.sendibm1.com/mk/cl/f/sh/1t6Af4OiGsDg0ir9CZLQIyf8RbaBmN/YzTb1Uuosclo) # # Fill Out Our Carrier Application for Dispatch Services **No Dispatching for Sprinter Vans, Car Haulers, or Dump Trucks** We are looking to partner with: Hotshots (32ft+ OTR 2-6 weeks on the road) Box Trucks (24ft+ OTR 2-6 weeks on the road) Flatbed- 48ft+ Local, Regional & OTR DRY Van- Local, Regional & OTR REEFER - Local, Regional, or OTR We would love to talk with you! Click below to fill out our Carrier Application. # [Carrier Application](https://5y0ou.r.a.d.sendibm1.com/mk/cl/f/sh/1t6Af4OiGsE8LR3ZavRLTEixpQYvUR/3yD3Q7fm6aan) # The Hot Shots average is $4,000-$6,000. The Box Trucks average is $3,000 to $5,000. The Flatbeds average $8,000-$10,000. The Dry Van average $6,000-$8,000. The Reefer average $7,000-$9,000. If you’re interested, go to our website https://www.belogistics.net/carrier-application and fill out the carrier application. BENEFITS: No contract length No force dispatch No going to areas outside your desire All paperwork included Only loads booked over the national average rate per your equipment **No Dispatching for Sprinter Vans, Car Haulers, or Dump Trucks** [Facebook](https://5y0ou.r.a.d.sendibm1.com/mk/cl/f/sh/1t6Af4OiGsEag9FzzHXGdUmnDFXfCV/NuiBQ0HF7Fju) [LinkedIn](https://5y0ou.r.a.d.sendibm1.com/mk/cl/f/sh/1t6Af4OiGsF30rSQNddBnkqcb4WOuZ/Dt6Wy_2edNdK) [Instagram](https://5y0ou.r.a.d.sendibm1.com/mk/cl/f/sh/1t6Af4OiGsFVLZeqlzj6y0uRytV8cd/FvBhR0Gyvlkk) [YouTube](https://5y0ou.r.a.d.sendibm1.com/mk/cl/f/sh/1t6Af4OiGsFxgHrHALp28GyHMiTsKh/p7wfEKqbQ8xi) # [BE. Logistics LLC](https://5y0ou.r.a.d.sendibm1.com/mk/cl/f/sh/1t6Af4OiGsGQ103hYhuxIX26kXSc2l/9Mbv518XSdFD) -------------- next part -------------- An HTML attachment was scrubbed... URL: From kwe at temp.temp Thu Aug 31 07:38:00 2023 From: kwe at temp.temp (Karsten Wemheuer) Date: Thu, 31 Aug 2023 09:38:00 +0200 Subject: [OpenSIPS-Users] bad arguments for command In-Reply-To: References: Message-ID: <4b024b11a0b852699fbcd9e0954a8823cca835df.camel@temp.temp> Hi, Am Donnerstag, dem 31.08.2023 um 12:48 +0530 schrieb Prathibha B: > Aug 31 06:58:48 [346547] CRITICAL:Traceback (last included file at > the bottom): > Aug 31 06:58:48 [346547] CRITICAL: 0. //etc/opensips/opensips.cfg > Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:184:11-17: syntax error > Aug 31 06:58:48 [346547] CRITICAL: # check if the clients are > using WebSockets or WebSocketSecure > Aug 31 06:58:48 [346547] CRITICAL: if ($socket_in(proto) == "WS" > || $socket_in(proto) == "WSS") > Aug 31 06:58:48 [346547] CRITICAL: setflag(SRC_WS); > Aug 31 06:58:48 [346547] CRITICAL: ^~~~~~~ > Aug 31 06:58:48 [346547] CRITICAL: > Aug 31 06:58:48 [346547] CRITICAL: # consider the client is > behind NAT - always fix the contact > Aug 31 06:58:48 [346547] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:184:17-18: bad arguments for command > maybe use quotes around parameter like setflag("SRC_WS"); HTH, Best regards Karsten From amejia at voxdatacomm.com Thu Aug 31 14:33:48 2023 From: amejia at voxdatacomm.com (Alejandro Mejia Evertsz) Date: Thu, 31 Aug 2023 08:33:48 -0600 Subject: [OpenSIPS-Users] Error in opensips.cfg file In-Reply-To: References: Message-ID: Hello Phrathib It seems you're using some commands used in version 2. You may need to look for the correct syntax to use them on version 3. There is a document on the website that explains migrating from 2 to 3. https://www.opensips.org/Documentation/Migration-2-4-0-to-3-0-0 Hope it helps On Wed, Aug 30, 2023, 11:17 PM Prathibha B wrote: > Aug 31 04:14:49 [339966] CRITICAL:Traceback (last included file at the > bottom): > Aug 31 04:14:49 [339966] CRITICAL: 0. //etc/opensips/opensips.cfg > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:183:12-14: syntax error > Aug 31 04:14:49 [339966] CRITICAL: > Aug 31 04:14:49 [339966] CRITICAL: # check if the clients are using > WebSockets or WebSocketSecure > Aug 31 04:14:49 [339966] CRITICAL: if (proto == "WS" || proto == > "WSS") > Aug 31 04:14:49 [339966] CRITICAL: ^~~ > Aug 31 04:14:49 [339966] CRITICAL: setflag(SRC_WS); > Aug 31 04:14:49 [339966] CRITICAL: > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:183:12-14: bare word found, command > calls need '()' > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:183:12-14: bad command!) > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:183:16-17: bad command!) > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:183:18-20: bad command!) > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:183:27-29: bare word found, command > calls need '()' > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:183:27-29: bad command: missing ';'? > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:183:31-32: bad command!) > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:183:32-33: bad command!) > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:184:17-18: bad arguments for command > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:193:17-23: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:193:23-24: bad arguments for command > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:194:13-19: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:194:19-20: bad arguments for command > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:239:16-22: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:239:22-23: bad arguments for command > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:239:38-44: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:239:44-45: bad arguments for command > > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:241:21-27: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:241:27-28: bad arguments for command > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:241:44-50: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:241:50-51: bad arguments for command > > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:243:22-28: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:243:28-29: bad arguments for command > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:243:44-50: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:243:50-51: bad arguments for command > > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:245:22-28: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:245:28-29: bad arguments for command > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:245:45-51: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:245:51-52: bad arguments for command > > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:257:16-22: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:257:22-23: bad arguments for command > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:257:38-44: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:257:44-45: bad arguments for command > > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:259:21-27: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:259:27-28: bad arguments for command > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:259:44-50: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:259:50-51: bad arguments for command > > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:261:22-28: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:261:28-29: bad arguments for command > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:261:44-50: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:261:50-51: bad arguments for command > > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:263:22-28: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:263:28-29: bad arguments for command > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:263:45-51: syntax error > Aug 31 04:14:49 [339966] CRITICAL:core:yyerror: parse error in > //etc/opensips/opensips.cfg:263:51-52: bad arguments for command > > Aug 31 04:14:49 [339966] ERROR:core:parse_opensips_cfg: bad config file > (46 errors) > Aug 31 04:14:49 [339966] ERROR:core:main: failed to parse config file > (null) > Aug 31 04:14:49 [339966] NOTICE:core:main: Exiting.... > > On Thu, 31 Aug 2023 at 10:04, Prathibha B > wrote: > >> bare word found, command calls need '()' >> >> On Mon, 21 Aug 2023 at 13:34, Prathibha B >> wrote: >> >>> if(proto === WSS) >>> >>> On Mon, 21 Aug 2023 at 13:33, Prathibha B >>> wrote: >>> >>>> Aug 21 08:02:24 [210480] CRITICAL:Traceback (last included file at the >>>> bottom): >>>> Aug 21 08:02:24 [210480] CRITICAL: 0. //etc/opensips/opensips.cfg >>>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>>> //etc/opensips/opensips.cfg:250:16-18: syntax error >>>> Aug 21 08:02:24 [210480] CRITICAL: if (is_method("REGISTER")) >>>> Aug 21 08:02:24 [210480] CRITICAL: { >>>> Aug 21 08:02:24 [210480] CRITICAL: if(proto_wss == WSS) { >>>> Aug 21 08:02:24 [210480] CRITICAL: ^~~ >>>> Aug 21 08:02:24 [210480] CRITICAL: >>>> fix_nated_register(); >>>> Aug 21 08:02:24 [210480] CRITICAL: } >>>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>>> //etc/opensips/opensips.cfg:250:16-18: bare word found, command >>>> calls need '()' >>>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>>> //etc/opensips/opensips.cfg:250:16-18: bad command!) >>>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>>> //etc/opensips/opensips.cfg:250:22-23: bare word found, command calls >>>> need '()' >>>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>>> //etc/opensips/opensips.cfg:250:22-23: bad command: missing ';'? >>>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>>> //etc/opensips/opensips.cfg:250:24-25: bad command!) >>>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>>> //etc/opensips/opensips.cfg:256:3-5: syntax error >>>> Aug 21 08:02:24 [210480] CRITICAL:core:yyerror: parse error in >>>> //etc/opensips/opensips.cfg:256:3-5: >>>> Aug 21 08:02:24 [210480] ERROR:core:parse_opensips_cfg: bad config file >>>> (8 errors) >>>> Aug 21 08:02:24 [210480] ERROR:core:main: failed to parse config file >>>> (null) >>>> Aug 21 08:02:24 [210480] NOTICE:core:main: Exiting.... >>>> >>>> -- >>>> Regards, >>>> B.Prathibha >>>> >>> >>> >>> -- >>> Regards, >>> B.Prathibha >>> >> >> >> -- >> Regards, >> B.Prathibha >> > > > -- > Regards, > B.Prathibha > _______________________________________________ > 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: