Re: [OpenSIPS-Users] Help dropping SQL injection attacks

"Forbidden"); exit; } -- Thanks *Gregory Massel* On 2023-12-05 11:33, Bogdan-Andrei Iancu wrote: Hi Gregory, As it is said, there is no single way to skin the cat :). Your approach is a valid one, by using the escaping transformation. Maybe you should check the s.escape.user [1]

[OpenSIPS-Users] Help dropping SQL injection attacks

;transport=UDP SIP/2.0 Contact: To: From:;tag=v2pjtxqb I'm not quite sure how to match the Contact user. Would the following work? if ( $(ct.fields(uri){uri.user}) != $(ct.fields(uri){uri.user}{s.escape.common}) ) { drop(); } -- Regards *Gregory Massel

Re: [OpenSIPS-Users] Odd URI formatting issue when using Exec to return a variable

Just wondering if, perhaps, the script return a line terminated with \r\n instead of just \n ? Or perhaps even just a \n is being pulled into the variable? Perhaps try a {s.trim} transformation? On 2023-11-15 13:27, Bogdan-Andrei Iancu wrote: Out of curiosity, if you replace the:     $branch

[OpenSIPS-Users] tls_peer_subject_cn not set on wolfssl?

? -- Regards *Gregory Massel* *T* +27 87 550 *F* +27 11 783 4877 *W* www.switchtel.co.za <http://www.switchtel.co.za/>___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] SQL injection in usernames

I'm observing that fraudsters are attempting SQL injections within various SIP headers, e.g. Contact: From:;tag=t1cqzx35 Just a head's up to those using SQL queries in their dial plans to be careful to always *escape* the wrath! ___ Users mailing

[OpenSIPS-Users] $si showing contact address

Good day all I'm picking up a weird issue where $si is reflecting the IP address of the contact rather then the IP packet header. If I run "opensips-cli -x mi ul_show_contact location redacted@domain" I get: "Contact": "sip:redacted@1.2.3.1:45066", "Received": "sip:102.132.225.36:45066",

Re: [OpenSIPS-Users] Media server communication with OpenSIPS

You can send custom headers from Asterisk to OpenSIPS using: https://wiki.asterisk.org/wiki/display/AST/Asterisk+18+Function_PJSIP_HEADER If you need Asterisk to receive customer headers from OpenSIPS, you can read custom headers added by OpenSIPS to its 200 response using:

Re: [OpenSIPS-Users] 3.2.3 TLS issue

0x55fdf9093343 in main () No symbol table info available. Regards Greg On 2021-11-18 23:36, Vlad Patrascu wrote: Hi Gregory, It is difficult to draw any conclusions without a backtrace so I'm hoping you'll be able to get the proper core dumps again in order to investigate this further.

Re: [OpenSIPS-Users] 3.2.3 TLS issue

. Thanks, Andrew On Fri, 12 Nov 2021 at 02:30, Gregory Massel wrote: Thanks. This report lists it as a bug in WolfSSL, however, given that I'm got similar errors (although not a segfault) when changing to OpenSSL, it would appear more likely that it's in proto_tls

Re: [OpenSIPS-Users] 3.2.3 TLS issue

is running fine. There does seem to be a bug report about this: https://github.com/OpenSIPS/opensips/issues/2667 On Thu, 11 Nov 2021 at 14:33, Gregory Massel wrote: I've managed to downgrade to 3.2.2 and all is working again. So this appears to be a bug introduced in 3.2.3. Environment

Re: [OpenSIPS-Users] 3.2.3 TLS issue

=3.2.2-1 --Greg On 2021-11-11 15:56, Gregory Massel wrote: I'm running OpenSIPS 3.2.3 and it keeps bombing out on SSL connections. With WolfSSL it segfaults: Nov 11 11:52:04 msteams /usr/sbin/opensips[15322]: NOTICE:tls_wolfssl:verify_callback: depth = 1, verify success Nov 11 11:52:04 msteams

[OpenSIPS-Users] 3.2.3 TLS issue

sful fd add (fd=244,type=19,data=0x7f4b4e1c8240,flags=2) already=0 I didn't have these issues with OpenSIPS 3.1, however, am not sure how to downgrade as, when I do, it complains that the database table structure is not suitable and there does not appear to be a migration script to revert to an olde

Re: [OpenSIPS-Users] OPUS transcoding query

A few factors to consider: _1. Quality_ 1.1. If you transcode to PCMU using RTPengine, you will lose the wideband audio quality benefits of Opus. By contrast, if Asterisk accepts the calls using Opus, it will transcode internally to sln16 for purposes of media processing (playing IVRs,

Re: [OpenSIPS-Users] time going backwards?

Per https://www.opensips.org/Documentation/Script-CoreVar-3-1 $Tsm - reference to current microseconds _*of the current second*_ This means that if the second counter cycles up, the microsecond counter will cycle back to zero and

Re: [OpenSIPS-Users] Handling mobile switch from wifi to data

st Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users <http://lists.opensips.org/cgi-bin/mailman/listinfo/users> ___ Users mailing list Users@lists.opensips.org http://lists.opensip

Re: [OpenSIPS-Users] [BLOG] Exploring SSL/TLS libraries for OpenSIPS 3.2

Are there any temporary ways to mitigate the issues in the mean time? E.g. Would "tcp_workers=1" help? (i.e. avoiding multiple processes calling OpenSSL in parallel). On 2021-02-11 14:33, Vlad Patrascu wrote: Hello everyone, Check out this new blog post [1] that recounts our process of

[OpenSIPS-Users] libcrypto segfault

Does the following mean that the issue is with libcrypto or could it still be something with OpenSIPS? It's intermittent on startup. Feb 20 05:25:44 vpbx2 /usr/sbin/opensips[3726528]: CRITICAL:core:sig_usr: segfault in attendant (starter) process! Reading symbols from /usr/sbin/opensips...

[OpenSIPS-Users] Auto process scaling (UDP worker) and crashes

Hello Is anyone successfully using auto process scaling on a high volume system? I've been having a number of issues, including excessive system load, deadlocks on the UDP worker processes and segmentation faults, both once running as well as in the attendant (starter) process. While I

Re: [OpenSIPS-Users] API Question

@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- Regards *Gregory Massel* *T* +27 87 550 *F* +27 11 783 4877 *W* www.switchtel.co.za <http://www.switchtel.co.za/> ___ Users mailing list Users@lists.opensips.or

[OpenSIPS-Users] opensips-cli and /tmp

I struggled for quite some time to get opensips-cli working on Ubuntu 20.04 LTS. It seems that there are now some security protections within the Linux kernel (|fs.protected_fifos) |against users other then the original creator from writing to fifo files in /tmp.

[OpenSIPS-Users] BLF with parallel forking on OpenSIPS 3.1.1

e this would be greatly appreciated. Regards Gregory Massel ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] shm memory error

y guidance on how I can debug this would be hugely appreciated. Thanks Greg On 2020-09-14 4:20 pm, Gregory Massel wrote: Hello Does anyone know what would cause the following: Sep 14 15:33:39 proxy /usr/sbin/opensips[30920]: ERROR:core:fm_malloc: not enough free shm memory (290427312 bytes left,

[OpenSIPS-Users] shm memory error

Hello Does anyone know what would cause the following: Sep 14 15:33:39 proxy /usr/sbin/opensips[30920]: ERROR:core:fm_malloc: not enough free shm memory (290427312 bytes left, need 6720), please increase the "-m" command line parameter! Sep 14 15:33:39 proxy /usr/sbin/opensips[30920]:

[OpenSIPS-Users] OpenSIPS NOTIFY for MWI on Asterisk PUBLISH?

cemail status should allow for far greater scale. Any help would be greatly appreciated. Regards Gregory Massel ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] TLS handshake failure

Thank you Alexey. Your suggestions solved the problem! On 2020-07-07 8:15 am, Alexey Vasilyev wrote: Hi Gregory, Starting from 01.07.2020 Microsoft requires Route headers with SBC_FQDN in SIP replies too. Instead of simple record_route() for SIP request from MS servers OpenSIPS should add

[OpenSIPS-Users] TLS handshake failure

Hello As of five days ago, my OpenSIPS 'SBC' for Microsoft Teams has started failing outbound Teams calls (with no changes to the config and after everything was working for many weeks prior). In the direction where OpenSIPS sends the INVITE to Microsoft, everything still works normally.