Re: [OpenSIPS-Users] Long reload time for mi tls_reload for 200 tls/ssl certs

[Liviu Chircu]

Hi Denys,

The report shows OpenSSL library doing small SHM allocations (4, 10, 
608, 24... bytes), which seem to frequently take place inside the 
PEM_read_bio_X509() loop (as part of the load_certificate_db() 
function).  Such a sequence of allocations could be stress-testing the 
allocator in a way that could justify 250 ms per certificate in total, 
as it is fragmenting the memory.  The effect can be more pronounced the 
*less* stuff is going on in your OpenSIPS instance, as the process of 
breaking up the big memory chunk into smaller units may use up to 
hundreds of cycles on each allocation.  For example:  testing box with 
no SIP traffic, or 'tls_reload' after a fresh restart, etc.


Please try the following:

- still using F_MALLOC, try doing more 'tls_reload' operations in a 
row.  Does performance improve?


- try using the "-a HP_MALLOC" allocator when booting your OpenSIPS - 
that one favors memory fragmentation a bit more, so subsequent reloads 
should be faster


Best regards,

Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com

On 14.05.2024 16:47, Denys Pozniak wrote:

I disabled logging and added some resources to the virtual machine.
On a working OpenSIPS, I reloaded the tls several times and in 
parallel ran a trap.

#opensips-cli -x mi tls_reload
#opensips-cli -x trap

If possible, please analyze it again, maybe you could find something 
interesting:

https://github.com/denyspozniak/opensips_tls_debug/tree/main

Thanks in advance!


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Error Initializing auth_aaa Module on Startup

[Liviu Chircu]

Hello Ionuț,

On 25.04.2024 12:38, Ionut Boangiu wrote:
Apr 25 05:03:29 debian /usr/sbin/opensips[24397]: 
ERROR:auth_aaa:mod_init: auth_aaa: can't get code for the Digest-Qop 
attribute (type 0)


Thanks for the report!  You actually ran into a bug there, and I just 
pushed a fix on `master` branch, see this commit 
<https://github.com/OpenSIPS/opensips/commit/a86b7e2cdde3924621d4cda5adb5bf83462ba544>.  
It should become available along with tomorrow's nightly packages, if 
you don't build from source.


About your C dev question: rather than looking for a tool or a method, 
why not look for an XML library that /you /like working with, first and 
foremost?  Once you've decided, just walk the dict, build the XML tree, 
then print it out as some kind of (char *) buffer using the library's 
functionality.


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 May 14-17 Valencia |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Minor Release] OpenSIPS 3.4.5 and 3.2.18 Minor Releases

[Liviu Chircu]

Hi, everyone!

A new round of stable minor releases is now out: *3.4.5 *and *3.2.18*, 
which include all fixes done in the past two months.


Do make sure to schedule an update as soon as possible!

Full changelogs:

https://opensips.org/pub/opensips/3.4.5/ChangeLog
https://opensips.org/pub/opensips/3.2.18/ChangeLog 



Please enjoy!

OpenSIPS Team___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] log_next_state_dlg: bogus event 8 in state 5

[Liviu Chircu]

Hi Alain,

Event 8 stands for DLG_EVENT_REQ in the C code, which means: "mid-dialog 
request".


I would recommend you don't turn off that warning message, because there 
may be several other events (5? 7? etc.) which could reach the same 
codepath and could be useful hints for troubleshooting.  Rather, try to 
make a /monitoring exception/ for the specific "event 8 state 5" warning 
message in order to avoid unwanted alerts.


PS: as far as the function itself goes, there is no way of turning the 
message off, only by raising the /log_level/ -- again, not recommended 
(warnings are useful).


Best regards,

Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 |www.opensips.org/events

On 05.04.2024 12:46, Alain Bieuzent wrote:


WARNING:dialog:log_next_state_dlg: bogus event 8 in state 5 for dlg

The code works, but I continue to receive these error messages in the 
logs, how can I delete them (without changing the log level)?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Packet analysis using wireshark

[Liviu Chircu]

If you are not able to decode the WebRTC TLS connection in Wireshark, 
it's possible you are dealing with a TLS 1.3 connection.


In TLS 1.3, there is an extra "secrets" file which must be plugged into 
Wireshark before it can decode the communication, which contains 
transient data (per connection!).  It is no longer sufficient to go to 
Edit -> Preferences -> Protocols -> TLS / SSL -> *RSA keys list* and 
plug in your private key.  In that same dialog box, the field 
*(Pre)-Master-Secret log filename* also becomes mandatory.


Now, how to obtain the Master-Secret file?  In Chrome/Firefox as well as 
in cURL, you should find support for the *SSLKEYLOGFILE=* environment 
variable. Just make sure to set this variable to the desired filepath 
before running the WebRTC client and it /should/ dump the secrets 
there.  Which will ultimately get picked up by Wireshark and the traffic 
will decode.


Good luck! :)

Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 |www.opensips.org/events

On 06.04.2024 17:39, Prathibha B wrote:
I am unable to see the Voip calls in wireshark. For signaling opensips 
is used. The calls are encrypted and it is webrtc communication.___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Continously ringing

[Liviu Chircu]

Make a SIP trace with *sngrep *program and check the routing of the 486 
Busy / 603 Decline message sent by phone B.  If A is still in ringing, 
it most likely means the reply isn't reaching it.


It is possible phone A is behind a NAT and its /Via/ SIP header needs a 
small adjustment for the replies to be properly routed back, using this 
useful /opensips.cfg/ function call:


force_rport() 
<https://www.opensips.org/Documentation/Script-CoreFunctions-3-5#force_rport>


Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 |www.opensips.org/events

On 06.04.2024 17:35, Prathibha B wrote:
User A makes a call to user B. User B didn't accept the call. User B 
stopped ringing after 1 minute. But User A continues to be in the 
ringing state until it is manually canceled.___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [Blog] HTTP/2 Server Support for Next-Generation Services in OpenSIPS 3.5

[Liviu Chircu]

On 28.03.2024 00:30, VoIP Australia NOC wrote:
I have tried more than 3 times to be removed from this mailing list 
and my emails are still bombarded, can someone whom runs this please 
remove me from it?


Unsubscribing from a GNU Mailman public mailing list is a standard 
procedure, there are no mysteries or hidden "gotchas" around it:


1. go to http://lists.opensips.org
2. pick your Mailman list to unsubscribe from 
(e.g. Users)
3. scroll down, fill in your email and click the "*Unsubscribe or edit 
options*" button

4. have a Snickers
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Blog] HTTP/2 Server Support for Next-Generation Services in OpenSIPS 3.5

[Liviu Chircu]

Hi all,

OpenSIPS "master" branch got better just a few hours ago as we merged 
the new "http2d" module, offering HTTP/2 server-side support.  Read all 
about it in this blog post:


https://blog.opensips.org/2024/03/27/http-2-server-support-for-next-generation-services-in-opensips-3-5/

Enjoy!

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] pn still problems

[Liviu Chircu]

Hi rvg,

I took a look at the logs you provided and, indeed, your "rvg" AoR has 
exactly 1 contact registered, with flags value of "4" in the MI ul_dump, 
confirming that it is RFC 8599 PN enabled.  Now, regarding the INVITE 
looping, if you still have this issue, make sure to avoid t_relay() 
after the lookup, as discussed earlier.


Finally, if the call does not connect... that's because, logically 
speaking, there is *always* a need to generate a Push Notification on 
*every* call attempt.  While I do agree this might be a bit of overkill, 
it is the only way to cover all timing-related corner-cases (imagine 
this race condition: the phone registered 1.5 minutes ago or earlier, 
but the NAT pinhole only lasts for 1 minute, so by the time you call, it 
is unreachable).  So please make sure to get your *PN_SEND* route to 
actually do the work -- send the PN, wake up the app and get it to 
Re-REGISTER, which will cause OpenSIPS to /inject/ an INVITE over to it.


Alternatively, if you just want to play with the Push Notification 
support /without sending Push Notifications/... try to bump the 
registrar's pn_skip_pn_interval 
<https://opensips.org/docs/modules/3.5.x/registrar.html#param_pn_skip_pn_interval> 
setting to some ridiculous value like *600* seconds, causing the module 
to refrain from mandating any Push Notification to be sent in the first 
10 minutes following the app's REGISTER, as it delivers calls 
straight-through to the app.


Best regards,

Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 |www.opensips.org/events

On 09.03.2024 15:46, r...@rvgeerligs.nl wrote:

I still have problems with opensips3.4 push notifications:

Somehow INVITEs keep looping and get rejected.___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] pn still problems

[Liviu Chircu]

Hello rvg,

Please find some answers below.

On 09.03.2024 15:46, r...@rvgeerligs.nl wrote:


I still have problems with opensips3.4 push notifications:

Somehow INVITEs keep looping and get rejected.
If the INVITE loops to your server, then you likely have an undesired 
t_relay() operation after a lookup() which only finds "Push 
Notification" contacts, which are not immediately routable.  Here, it 
would be helpful to provide the output of: "opensips-cli -x mi ul_dump", 
corresponding to the AoR you are trying to reach, right before placing 
the call.


Additionally, please post the full opensips.log, so we can see if the 
script logic post-lookup falls under "case 1" or "case 2".  Of course, 
in case of the latter, you should just "exit" the script without any 
further routing, as the INVITE will be put on hold, until a REGISTER 
arrives.




question: Does the route[pm_send] need to return any value? exit does 
not not return value does it?
Indeed, the return value of that route will be ignored.  FYI, "exit;" 
implicitly returns 1 (success).




does the [pm_send] acually need to send the push for the INVITE to be 
answered by 200 OK?


Yes, that is the main role of that route ("pn_send", as in: "Push 
Notification Send").


Best regards,

Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 | www.opensips.org/events


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Blog] Diameter Server Support for IMS Flows in OpenSIPS 3.5

[Liviu Chircu]

Hi all,

The OpenSIPS IMS support is shaping up, with the Diameter Server support 
now being available for alpha testing, on the development (master) branch.


As documentation, we have prepared:

* a wiki tutorial^[1] 
<https://www.opensips.org/Documentation/Tutorials-Diameter-Client-Server> 
on how to use it
* a blog post^[2] <https://blog.opensips.org/?p=9325=true> with 
a more concrete example: processing Push-Profile-Requests (PPR) 
originated by the HSS to our P-CSCF


[1]: https://www.opensips.org/Documentation/Tutorials-Diameter-Client-Server
[2]: 
https://blog.opensips.org/2024/03/07/diameter-server-support-for-ims-flows-in-opensips-3-5/


Enjoy!

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 May 14-17 Valencia |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] stir_shaken date header discrepancy

[Liviu Chircu]

On 20.02.2024 16:06, James Seer wrote:


In my example, the "iat" PASSporT value is correct. The only issue 
lies with the Date header field.


It is also worth noting that there are already some automated SIPssert 
tests for both past 
 
and future 
 
Date hfs, which are *passing* as of latest commit.  And nothing major 
has changed in /stir_shaken/ since *3.4.2*.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] stir_shaken date header discrepancy

[Liviu Chircu]

Hi James,

On 20.02.2024 16:06, James Seer wrote:


I am already running the last version of OpenSIPS.
opensips -V
version: opensips 3.4.3 (x86_64/linux)
deb https://apt.opensips.org bookworm 3.4-releases'


Strange, so indeed you have the Date fix, so it should correctly detect 
timestamps "in the future".


So, the only explanation for the check still passing seems to revolve 
around us assuming a different *server time* than what OpenSIPS actually 
reads.


Some ideas to gather more info on the problem:

* first of all, check for any "silly" reasons for the error such as, but 
not limited to:
  - upgrading the OpenSIPS package to 3.4.2+, but forgetting to restart 
the instance, which is still running 3.4.1
  - an extra line somewhere "lower" in the config file by mistake, 
resembling modparam("stir_shaken", "verify_date_freshness", 7200) or similar
* double-check for any unwanted "TZ" environment variable being set as 
OpenSIPS starts (ideally, this var is not set)

* double-check the system's timezone is really CET, using:

$ date +%s # to match what UNIX timestamp OpenSIPS is pulling from the 
OS as well

$ cat /etc/timezone

Finally, if you still can't get it to reject that Date header, please 
open up a bug report on GitHub with some examples on and I'll take a 
closer look.


Best regards,

Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Minor Release] OpenSIPS 3.4.4 and 3.2.17 Minor Releases

[Liviu Chircu]

Hi, everyone!

A new round of stable minor releases is now out: *3.4.4 *and *3.2.17*.  
As an exception, we've also pushed a final *3.3.10* release for *3.3*, 
which takes care of a couple regressions specific to *3.3.9 
*(specifically: in /tracer/ and /rest_client/).


Do make sure to schedule an update as soon as possible.

Full changelogs:

https://opensips.org/pub/opensips/3.4.4/ChangeLog
https://opensips.org/pub/opensips/3.3.10/ChangeLog
https://opensips.org/pub/opensips/3.2.17/ChangeLog 
<https://opensips.org/pub/opensips/3.2.17/ChangeLog>


Please enjoy!

OpenSIPS Team

On 29.01.2024 11:12, Liviu Chircu wrote:



The 3.4.4 and 3.2.17 OpenSIPS minor versions are scheduled for release 
on *Wednesday, Feb 21st*.


In preparation for the releases, starting *Wednesday, Feb 7th*, we 
will impose the usual *freeze* on any significant fixes (as 
complexity) on these stable branches, in order to ensure a /two-week 
safe window/ for testing.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] stir_shaken date header discrepancy

[Liviu Chircu]

Hi James,

Make sure you're running a recent OpenSIPS build, I recall this bug was 
caught a few months ago 
<https://github.com/OpenSIPS/opensips/commit/75a168a9f43>.


Best regards,

Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 |www.opensips.org/events

On 20.02.2024 15:03, James Seer wrote:

Hello,

I have a question regarding Date Header Verification in our setup:

Server Timezone: Central European Time
Configuration:
require_date_hdr: false
verify_date_freshness : 300 seconds
SIP INVITE Date Header: Tue, 20 Feb 2024 00:26:05 GMT
Server time: 2024-02-20T00:26:06 CET
Identity header payload "iat" value: 1708385165

Despite the Date header being in the future, OpenSIPS proceeded with 
verification. While I can see there's an existing error code (-6: Date 
header value is older than local policy for freshness), it only 
addresses cases where the header is "older" than the local policy.


This could be easily handled in script code, but shouldn't opensips 
trigger a distinct failure with a new error code, considering the 
discrepancy between the Date header and server time ? (More than 300 
seconds of difference)


Thank you

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Release Freeze] Upcoming OpenSIPS 3.4.4 and 3.2.17 Minor Releases

[Liviu Chircu]

Hi, all!

The 3.4.4 and 3.2.17 OpenSIPS minor versions are scheduled for release 
on *Wednesday, Feb 21st*.


In preparation for the releases, starting *Wednesday, Feb 7th*, we will 
impose the usual *freeze* on any significant fixes (as complexity) on 
these stable branches, in order to ensure a /two-week safe window/ for 
testing.


So please make sure to ping any outstanding issues on the GitHub issue 
tracker <https://github.com/OpenSIPS/opensips/issues> that may have 
skipped our attention -- thank you in advance!


PS: we are aware of issue #3286 
<https://github.com/OpenSIPS/opensips/issues/3286>, related to 
rest_client in async mode, and are working towards a resolution in due time.


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] pn push notifications

[Liviu Chircu]

On 15.01.2024 20:28, r...@rvgeerligs.nl wrote:

for your information:
*Sending a push notification to an iOS device using a Bash script*
https://medium.com/@egzon.arifi/sending-a-push-notification-to-an-ios-device-using-a-bash-script-96c056c1544c

I hope the pn in opensips only requires the route to the apn:
https://api.development.push.apple.com/. dev
https://api.push.apple.com/ opp


Hello Ronald,

Indeed, the /PN_SEND /route will most likely invoke a shell script 
(Bash, Go, Python, etc.) which triggers the notification for that 
/specific /SIP device via APNS, using your app developer API 
credentials.  As this logic is not only specific to the mobile 
developer's platform (APNS or Firebase?), but it's also subject to 
change and often depends on the OS as well (Android 11 or 14 API?  iOS 
14 or 16? etc.), we decided to not officially maintain such scripts and 
leave this part to the VoIP platform developer.


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Error in re.subst transformation

[Liviu Chircu]

On 18.01.2024 12:51, Alexander Kogan wrote:

Hi,

There's an error in re.subst transformation, it's not whitespace-safe. 
Is this patch OK?


Index: transformations.c
===
--- transformations.c   (revision 13886)
+++ transformations.c   (working copy)
@@ -3630,7 +3630,7 @@
    }
    p++;
    LM_DBG("preparing to parse param\n");
-   if (tr_parse_sparam(p, in, , 0) == NULL)
+   if (tr_parse_sparam(p, in, , 1) == NULL)
    goto error;
    t->params = tp;
    tp = 0;


Hi Alexander,

Looks OK to me, for example this quick test seems to PASS after your 
patch without any side-effects on other tests:


    $var(in) = "+443 493 2212";
    assert($(var(in){re.subst, /([0-9]) ([0-9])/\1.\2/g}) == 
"+443.493.2212", "test-subst-2");


If you do a Pull Request on `master`, it will most likely get merged.  
For the stable branches, this limitation can be bypassed by assigning 
the regex to a variable:


    $var(in) = "+443 493 2212";
    $var(re) = "/([0-9]) ([0-9])/\1.\2/g";
    assert($(var(in){re.subst, $var(re)}) == "+443.493.2212", 
"test-subst-2");


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2024 May 14-17 Valencia | www.opensips.org/events


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] uac_auth DB support

[Liviu Chircu]

On 06.12.2023 16:18, S.Rosenberg wrote:


I would like to know if OpenSIPS has a way to pull the registrant info 
via code without manually doing a DB query?


Hi Sebastian,

A bit late to the party here, but try giving the sql_cacher 
<https://opensips.org/docs/modules/3.4.x/sql_cacher.html> a spin.  It 
also works on top of cachedb_local (or any other NoSQL, for that 
matter...), however it will help you:


- cut down on the amount of LoC in your script (just configure the 
cached table properties in the "modparam" section and you're good to go)


- solve the problem of reloading the data (you can configure it with 
on_demand=300, for example, in order to cache a given row for a maximum 
of 5 minutes)


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] replicate to HEP using the advertised address - OPENSIPS 3.3.9

[Liviu Chircu]

On 26.12.2023 22:54, James Seer wrote:
Aaaa the good old days before commit 4bd50335a (2023-12-12 by Vlad 
Paiu), life was simpler when my vip network interface and VIP itself 
were just one happy entity in HOMER's eyes :P


This recent commit with its replication to HEP using the advertised 
address has complicated things in homer heplify by treating them as 
two different entities in the sip sequence (precisely during ACKs 
CANCEL and BYEs). Any chance we could make this an optional feature?


Hi James,

First of all, VIP issue aside, there seems to be a bug in that patch 
where the /sourceIP/ and /sourcePort/ are changed to /destinationIP /and 
/destinationPort/ without a good reason (currently started a discussion 
with Vlad - we'll get to the bottom of it).  Maybe if this were tweaked, 
your SIP flows would return back to looking normal?!


Nonetheless, if you have a 3.3 source tree to work with, try the 
following patch onto your root sources directory and see if the behavior 
improves by just fixing the bug instead of reverting the patch:


git apply <(base64 -d <___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mid_register and its possible bad actions with De-REGISTER

[Liviu Chircu]

On 27.12.2023 11:38, Dmitry Ponomaryov wrote:


All this to say, it might make sense to add the ability to disable 
this De-REGISTER, because with a new registration, we will still send 
it a registration with an updated contact before the main registrar 
times out, and there will be no problems, that is, for example, the 
following settings:


modparam("mid_registrar", "outgoing_expires", 600) 
modparam("mid_registrar", "default_expires", 300) 


Hello Dmitry,

From your scenario, it sounds like maybe you should enable AoR 
throttling, not just Ct throttling? Because in Ct throttling, each 
outgoing contact has a unique "ctid=" parameter, so it must be 
de-registered from the main registrar on each contact replace, since the 
replacement Contact has a new "ctid=", making it an entirely different 
SIP URI.


On the other hand, AoR throttling goes beyond this and just makes sure 
there is always 1 AoR registered downstream.  So on a "contact replace" 
operation,  no SIP signaling should reach the Asterisk in that case.


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2024 Valencia, May 14-17 | www.opensips.org/events


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [OpenSIPS-Devel] [Release] OpenSIPS 3.4.3, 3.3.9 and 3.2.16 Minor Releases; EoL for OpenSIPS 3.3!

[Liviu Chircu]

Hello!

It is my pleasure to announce a new round of stable minor releases: 
*3.4.3*, *3.3.9* and *3.2.16*.


Do make sure to schedule an update, as they contain important fixes, to 
name a few:
  * dialog: fix PKG memory fragmentation issues around 'dlg_list' (a 
long-awaited fix for a mysterious, constantly-recurring problem)
  * rest_client: async timeouts now work as intended;  dangling 
requests, due to no response from server, should no longer be possible 
and should always time out
  * B2B: fixes on UAC side (fix To URI vs. R-URI construction;  fix BYE 
generation for dangling entities)

  * drouting: allow rule fallback even across prefixless rules (prefix: "")

Note that OpenSIPS *3.3* has reached its *end-of-life*, according to the 
release policy <https://www.opensips.org/Development/Development>.  It 
will no longer receive any more fixes, with *3.2 LTS *and *3.4 LTS* 
being the currently supported stable versions.


Full changelogs:

https://opensips.org/pub/opensips/3.4.3/ChangeLog
https://opensips.org/pub/opensips/3.3.9/ChangeLog
https://opensips.org/pub/opensips/3.2.16/ChangeLog

Happy Holidays!
OpenSIPS Team

On 27.11.2023 18:07, Liviu Chircu wrote:


Hi, everyone!

The 3.4.3, 3.3.9 and 3.2.16 OpenSIPS minor versions are scheduled for 
release on *Wednesday, Dec 20th*.


In preparation for the releases, starting *Wednesday, Dec 6th*, we 
will impose the usual *freeze* on any significant fixes (as 
complexity) on these stable branches, in order to ensure a /two-week 
safe window/ for testing.


So please make sure to ping any outstanding issues on the GitHub issue 
tracker <https://github.com/OpenSIPS/opensips/issues> that may have 
skipped our attention.  And thank you in advance!


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Facing some issue with opensips while configuration .

[Liviu Chircu]

Hi folks,

An explanation + solution for this specific CLI issue related to *Python 
3.6* + the *zipp* package version can be found on the CLI tracker, part 
of issue #113 
<https://github.com/OpenSIPS/opensips-cli/issues/113#issuecomment-1861311868>


Hope this helps,

On 13.12.2023 08:45, Sasmita Panda wrote:

python3 -V
Python 3.6.8

This is the exact version I have .

*/Thanks & Regards/*
/Sasmita Panda/
/Senior Network Testing and Software Engineer/
/3CLogic , ph:07827611765/


On Tue, Dec 12, 2023 at 8:12 PM Bogdan-Andrei Iancu 
 wrote:


What is the exact version of Python you have?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 12.12.2023 13:42, Sasmita Panda wrote:

I am trying to install opensips-cli on the same version of linux
but facing some issue while connecting to the cli interface .


Steps I have followed :
sudo yum install python3 python3-pip python3-devel gcc
sudo yum install  python3-sqlalchemy python3-pyOpenSSL
git clone https://github.com/opensips/opensips-cli ~/src/opensips-cli
cd /root/src/opensips-cli/
sudo python3 setup.py install clean

*/usr/local/bin/opensips-cli
Traceback (most recent call last):
  File "/usr/local/bin/opensips-cli", line 4, in 
__import__('pkg_resources').run_script('opensipscli==0.2.0',
'opensips-cli')
  File
"/usr/lib/python3.6/site-packages/pkg_resources/__init__.py",
line 654, in run_script
self.require(requires)[0].run_script(script_name, ns)
  File
"/usr/lib/python3.6/site-packages/pkg_resources/__init__.py",
line 1434, in run_script
    exec(code, namespace, namespace)
  File

"/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/EGG-INFO/scripts/opensips-cli",
line 3, in 
    from opensipscli import main
  File

"/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/main.py",
line 22, in 
    from opensipscli import cli, defaults, version
  File

"/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/cli.py",
line 32, in 
    from opensipscli.modules import *
  File

"/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/modules/__init__.py",
line 24, in 
    __import__(modname)
  File

"/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/modules/database.py",
line 23, in 
    from opensipscli.db import (
  File

"/usr/local/lib/python3.6/site-packages/opensipscli-0.2.0-py3.6.egg/opensipscli/db.py",
line 37, in 
    import sqlalchemy_utils
  File

"/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/__init__.py",
line 1, in 
    from .aggregates import aggregated  # noqa
  File

"/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/aggregates.py",
line 374, in 
    from .compat import _select_args, get_scalar_subquery
  File

"/usr/local/lib/python3.6/site-packages/SQLAlchemy_Utils-0.41.1-py3.6.egg/sqlalchemy_utils/compat.py",
line 7, in 
    from importlib_metadata import metadata
  File

"/usr/local/lib/python3.6/site-packages/importlib_metadata-7.0.0-py3.6.egg/importlib_metadata/__init__.py",
line 7, in 
    import zipp
  File

"/usr/local/lib/python3.6/site-packages/zipp-3.17.0-py3.6.egg/zipp/__init__.py",
line 9, in 
    from .py310compat import text_encoding
  File

"/usr/local/lib/python3.6/site-packages/zipp-3.17.0-py3.6.egg/zipp/py310compat.py",
line 5
    def _text_encoding(encoding, stacklevel=2, /):  # pragma: no
cover*


    How should I proceed ?

*/Thanks & Regards/*
/Sasmita Panda/
/Senior Network Testing and Software Engineer/
/3CLogic , ph:07827611765/




--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS eBootcamp, Nov 6-17 |www.opensips.org/training
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Fwd: opensips is restarting after call is finished

[Liviu Chircu]

On 08.12.2023 15:17, Bogdan-Andrei Iancu wrote:
Maybe you have some apport service running on the machine, moving the 
core file. 


Hello,

I second this too, as it's the 90% main cause for corefiles not 
generating on my environment.  To confirm, just do:


$ cat /proc/sys/kernel/core_pattern
|/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E

... if the output includes "apport", it means the "apport" suite is 
handling all corefile writing, which can be good or bad, depending on 
your settings.


Still, to avoid all of this and simply have the OS write any corefile 
into the dying process's working directory, just run the following under 
"root" user:


$ echo "core.%p" > /proc/sys/kernel/core_pattern

Best regards,

--
Liviu Chircu


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Release Freeze] Upcoming OpenSIPS 3.4.3, 3.3.9 and 3.2.16 Minor Releases

[Liviu Chircu]

Hi, everyone!

The 3.4.3, 3.3.9 and 3.2.16 OpenSIPS minor versions are scheduled for 
release on *Wednesday, Dec 20th*.


In preparation for the releases, starting *Wednesday, Dec 6th*, we will 
impose the usual *freeze* on any significant fixes (as complexity) on 
these stable branches, in order to ensure a /two-week safe window/ for 
testing.


So please make sure to ping any outstanding issues on the GitHub issue 
tracker <https://github.com/OpenSIPS/opensips/issues> that may have 
skipped our attention.  And thank you in advance!


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] redis connect with auth

[Liviu Chircu]

On 02.11.2023 13:23, Bogdan-Andrei Iancu wrote:

Hi Jason,

right now there is no generic escaping support, so shortly said you 
cannot use the `@` in the password :(.


We can look into this, but please open a Feature Request on the github 
tracker.


Hi guys,

I just pushed a quick-fix for this on master branch, see this commit 
<https://github.com/OpenSIPS/opensips/commit/1df9afd3886a3bddf837927aafca7bff8763acd1>.


All previous URL tests are still passing as well as 3 new ones, so I 
guess we should be good here. Jason, let me know if you can give it a 
test as well, so I can backport it down to 3.2 stable.


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] 3.2.15 installation

[Liviu Chircu]

Hi!

It seems there was an issue related to the tarball packing introduced in 
the source tree a couple weeks *before* release day which confused me, 
as I thought I was just building the tarball incorrectly on release day 
(e.g. maybe due to a dirty directory or a bad script, etc.).


A fix is now available and all opensips.org tarballs have been rebuilt.  
Still, if you were to download the latest stable git tag and run "make 
tar" yourself, of course you'd run into the same bug again (/no change 
there, the git tag hasn't been moved/)... but that will also get 
resolved on the next stable release round in a month or so.


Best regards,

On 26.10.2023 09:53, L S wrote:
Thanks. We are having issues compiling from source on Centos (error 
because of a patch related to wolfssl). Will try again.




On Wed, Oct 25, 2023, 4:41 PM Knee Oh via Users 
 wrote:


Yes, compiled from source on Ubuntu 22.04. About to move to
production.



On Oct 25, 2023, at 4:35 PM, Joseph Jackson
 wrote:


We have but we use the debian packages and we installed it on
release day.




*From:* Users  on behalf of L S

*Sent:* Wednesday, October 25, 2023 12:46 AM
*To:* OpenSIPS users mailling list 
*Subject:* [OpenSIPS-Users] 3.2.15 installation
Has anyone successfully installed 3.2.15 (revised on Oct 20th)?

Thanks,
Matt


*From:* Users  on behalf of L S

*Sent:* Wednesday, October 25, 2023 12:46 AM
*To:* OpenSIPS users mailling list 
*Subject:* [OpenSIPS-Users] 3.2.15 installation
Has anyone successfully installed 3.2.15 (revised on Oct 20th)?

Thanks,
Matt
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS eBootcamp, Nov 6-17 |www.opensips.org/training
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Correct syntax with statement if

[Liviu Chircu]

Hi, Dmitry!


how different will this expression be from: ### example 2


They are identical, regardless of the presence/absence of any code below.


To what extent is it correct to use one or another type of if statement?

It's not about correctness, rather readability.  Example 1 uses 3 LoC, 
while example 2 uses only LoC and it more readable, thanks to the 
absence of the braces.


I understand that if we have to use else, then only the first option 
will suit us, but here it’s more about a single if.. thanks


I recommend going through the Linux kernel coding style 
<https://www.kernel.org/doc/html/v4.10/process/coding-style.html#placing-braces-and-spaces> 
docs, there is a "placing braces and spaces" section, which includes 
several if-statement examples, with braces, "else" blocks, etc.  Why not 
borrow the same ideas for our own /opensips.cfg/ coding style? :-)


Best,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS eBootcamp, Nov 6-17 |www.opensips.org/training
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [Release Freeze] Upcoming OpenSIPS 3.4.2, 3.3.8 and 3.2.15 Minor Releases

[Liviu Chircu]

On 19.10.2023 20:47, Alexander Kogan wrote:


Hi!

Failed to build 3.2.15 from opensips-3.2.15.tar.gz:

make[3]: *** No rule to make target 
'lib/patches/wolfssl-internal-memleak-fix.patch', needed by 
'lib/patches/wolfssl-internal-memleak-fix.patched'.  Stop.



Hi, Alexander!

Good catch!  I just rebuilt the tarball, as the faulty file (added by 
accident) has been removed in the meantime.


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [Release Freeze] Upcoming OpenSIPS 3.4.2, 3.3.8 and 3.2.15 Minor Releases

[Liviu Chircu]

Hi, all!

A new round of stable minor releases is now available: *3.4.2*, *3.3.8 
*and *3.2.15*!


Do make sure to schedule an update, as they contain important fixes.

Full changelogs:

https://opensips.org/pub/opensips/3.4.2/ChangeLog
https://opensips.org/pub/opensips/3.3.8/ChangeLog
https://opensips.org/pub/opensips/3.2.15/ChangeLog

Enjoy!

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [OpenSIPS Blog] Thoughts after Our Participation in OpenSIPIt’03

[Liviu Chircu]

Hi all,

The OpenSIPS project recently participated in the OpenSIPIt online 
testing event, so we wrote a blog piece summing up how the events unfolded:


https://blog.opensips.org/2023/10/05/thoughts-after-our-participation-in-opensipit03/

Please enjoy!

--
Liviu Chircu


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Release Freeze] Upcoming OpenSIPS 3.4.2, 3.3.8 and 3.2.15 Minor Releases

[Liviu Chircu]

Hi, everyone!

The 3.4.2, 3.3.8 and 3.2.15 OpenSIPS minor versions are scheduled for 
release on *Wednesday, Oct 18th*.


In preparation for the releases, starting *Monday, Oct 9th*, we will 
impose the usual *freeze* on any significant fixes (as complexity) on 
these stable branches, in order to ensure a safe window for testing in 
the days ahead.


Happy testing,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS eBootcamp, Oct 16-27 |www.opensips.org/training
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Release] OpenSIPS 3.3.6, 3.2.13 and 3.1.16 Minor Releases

[Liviu Chircu]

Hi, everyone!

The OpenSIPS 3.3.6, 3.2.13 and 3.1.16 minor releases have just been 
tagged, packing an important number of fixes done in the past two months 
(over 30 backports in total).


Detailed changelogs are available on the website^[1][2][3] .

[1]: https://opensips.org/pub/opensips/3.1.16/ChangeLog
[2]: https://opensips.org/pub/opensips/3.2.13/ChangeLog
[3]: https://opensips.org/pub/opensips/3.3.6/ChangeLog

Happy Hacking!
OpenSIPS Team___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Value comparison issue

[Liviu Chircu]

On 31.05.2023 13:00, Michele Pinassi via Users wrote:

User  has 2 calls (max 10 calls): BUSY
...
User  has 1 calls (max 10 calls): ALLOW

Any hints or suggestion?


Hi, Michele!

It looks like there is some string comparison going on in there, which 
would explain both samples. For example:


"2" > "10" (true)  ---> BUSY
"1" > "10" (false) ---> ALLOW

Just make sure both variables contain integer values and you should be 
good.  I'm suspecting avp_db_load() produces string outputs, so you must 
perform integer conversion using the {s.int} transformation: 
$(avp(maxcalls){s.int})


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Blog] Stress-Testing OpenSIPS 3.4 LTS

[Liviu Chircu]

Hi all,

Lately, we've been busy stress-testing and profiling various OpenSIPS 
3.4 components, in order to both label them with up-to-date performance 
numbers, as well as to address potential issues ahead of the beta release.


See this blog for a summary on how all of this went:

https://blog.opensips.org/2023/05/10/stress-testing-opensips-3-4-lts/

.. with the full results (with numbers, graphs and config files) 
published in a dedicated wiki page:


https://www.opensips.org/About/PerformanceTests-3-4

Enjoy!

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2023 Houston, May 23-26 | www.opensips.org/events


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [OpenSIPS-Devel] [Release] OpenSIPS 3.3.5, 3.2.12 and 3.1.15 minor releases

[Liviu Chircu]

On 10.04.2023 13:25, Liviu Chircu wrote:


The *3.3.5*, *3.2.12* and *3.1.15* OpenSIPS minor versions are 
scheduled for release on *Wednesday, April 19th*.  This round of minor 
releases will contain some important stability fixes around the 
*$param* changes done in the previous minor release round, so do 
consider rolling out an upgrade to your instances soon!




Hi all,

Unlike this announcement email, the OpenSIPS *3.3.5*, *3.2.12* and 
*3.1.15* minor releases have been tagged on schedule last week, packing 
a significant number of fixes across various modules done in the past 
two months (over 50 backports!), including a critical fix on the 
*$param* recent changes, several B2B module crash-fixes, a TCP engine 
bugfix and a F_MALLOC improvement which should minimize 
de-fragmentation, just to mention a few!


Detailed changelogs are available on the website^[1][2][3] . Packaging 
available on https://apt.opensips.org/ or https://yum.opensips.org/.


[1]: https://opensips.org/pub/opensips/3.1.15/ChangeLog
[2]: https://opensips.org/pub/opensips/3.2.12/ChangeLog
[3]: https://opensips.org/pub/opensips/3.3.5/ChangeLog

Happy Hacking!
OpenSIPS Team___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] AUTH module HA hash question

[Liviu Chircu]

On 10.04.2023 14:07, Yury Kirsanov wrote:
I'm actually NOT using any type of DB, hence the problem, how do I 
specify multiple hashes with $var(password) for different auth types, 
as per the documentation?


I think there is a bit of confusion on the "timings" when the 
multi-algorithm "xxx_challenge()" function is used vs. the 
single-algorithm reply verification for the client step.  As such:


* during the challenge step, you simply invoke xxx_challenge(MD5, 
SHA256), to advertise multiple challenge headers to the client
* during the verification step, you are supposed to read the 
*$auth.alg*, thus "learning" what the auth algorithm the client selected 
(*modern*** phone vs. *classic* phone, i.e. SHA256 or MD5), then
    populate *$var(password)***with the corresponding hash selected 
from your cache or database


Hope this helps,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2023 Houston, May 23-26 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] AUTH module HA hash question

[Liviu Chircu]

Hi, Yuri!

On 09.04.2023 17:27, Yury Kirsanov wrote:


Question is - how do I put TWO hashes into this variable if I'm trying 
to do a 'SHA-256,MD5' authentication, or a 'SHA-256, SHA-512-256' or 
something like that?


The "password_column" name is a bit unfortunate given there are 3 types 
of hashes as you already observed, but it was kept for 
backwards-compatibility reasons as holder for the MD5 hash :)


The other two hash column module params are right below it in the docs: 
hash_column_sha256 
<https://opensips.org/docs/modules/3.4.x/auth_db.html#param_hash_column_sha256> 
and hash_column_sha512t256 
<https://opensips.org/docs/modules/3.4.x/auth_db.html#param_hash_column_sha512t256>!


I tried putting these values with a comma, with a semicolon, with a 
'\r\n' but all that leads to is a crash in OpenSIPS without a 
segfault, like this:


Wow!  Maybe this needs to be looked into...  I'm assuming you had to 
manually edit the DB schema a bit for that extra-long data to fit in, 
right?  If so, I think a crash may be normal / expected, since you are 
using OpenSIPS in a /customized/, /non-standard/ way, so you are on your 
own!


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2023 Houston, May 23-26 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Release Freeze] Upcoming OpenSIPS 3.3.5, 3.2.12 and 3.1.15 minor releases

[Liviu Chircu]

Hi, everyone!

The *3.3.5*, *3.2.12* and *3.1.15* OpenSIPS minor versions are scheduled 
for release on *Wednesday, April 19th*.  This round of minor releases 
will contain some important stability fixes around the *$param* changes 
done in the previous minor release round, so do consider rolling out an 
upgrade to your instances soon!


Moreover, we are aware of some occasional de-fragmentation related 
performance issues on the F_MALLOC allocator in some corner-cases 
(usually around a 'dlg_list' MI command with a large output), in GH#2726 
<https://github.com/OpenSIPS/opensips/issues/2726>. A mitigation fix is 
already available, which will help avoid the de-fragmentation and its 
typical CPU usage spike, however average CPU usage at runtime may 
increase -- so the patch is still under testing/evaluation and we are 
doing our best to include it into this stable release round without 
compromising quality.


In preparation for the releases, we are imposing the usual freeze on any 
significant fixes (as complexity) on these stable branches, in order to 
ensure a safe window for testing in the days ahead.


Happy testing,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2023 Houston, May 23-26 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] route parameters ($param) on opens ips 3.2.11

[Liviu Chircu]

On 09.03.2023 11:32, Alain Bieuzent wrote:


When, I my script I call the route :

route(Q850enable,38);

Opensips generate this error and sometime segfault .


Hi Alain,

Indeed, this is a known issue with 3.2.11, please see #3024 [1] on 
GitHub.  A fix should be available soon, I'll keep you posted!


[1]: https://github.com/OpenSIPS/opensips/issues/3024

Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Release] OpenSIPS 3.3.4, 3.2.11 and 3.1.14 minor releases

[Liviu Chircu]

Hi, everyone!

The OpenSIPS 3.3.4, 3.2.11 and 3.1.14 minor releases have just been 
tagged, packing a significant number of fixes across various modules 
done in the past two months (~76 backports in total!).


*Important note: *on***OpenSIPS 3.2+*, route parameters have been fixed 
to be "/pass-by-value/" as originally intended, instead of 
/pass-by-reference/!  Make sure this doesn't cause any side-effects in 
your script -- normally, this should not affect you, but depending on 
the structure of your script, you /MAY/ experience a different behavior 
when using /$param(1), $param(2), etc./ throughout your routes than 
previously!//


Detailed changelogs are available on the website^[1][2][3] . Packaging 
to be available within the next couple of hours.


[1]: https://opensips.org/pub/opensips/3.1.14/ChangeLog
[2]: https://opensips.org/pub/opensips/3.2.11/ChangeLog
[3]: https://opensips.org/pub/opensips/3.3.4/ChangeLog

Happy Hacking!
OpenSIPS Team___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Release Freeze] Upcoming OpenSIPS 3.3.4, 3.2.11 and 3.1.14 minor releases

[Liviu Chircu]

Hi, everyone!

The 3.3.4, 3.2.11 and 3.1.14 OpenSIPS minor versions are scheduled for 
release on Wednesday, February 22nd (two weeks from now).  This round of 
minor releases contains a significant number of fixes across various 
modules done in the past two months (~50 commits in total!), so make 
sure to schedule an upgrade and deploy it as soon as possible.


*Important note: *on***OpenSIPS 3.2+*, route parameters have been fixed 
to be "/pass-by-value/", as originally intended, instead of 
/pass-by-reference/! Make sure this doesn't cause any side-effects in 
your script -- normally, this should not affect you, but depending on 
the structure of your script, you /MAY/ experience a different behavior 
when using /$param(1), $param(2), etc./ than previously!


In preparation for the releases, we are imposing the usual freeze on any 
significant fixes (as complexity) on these stable branches, in order to 
ensure a safe window for testing in the days ahead.


Happy testing,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2023 Houston, May 23-26 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Question on mid_registrar de-registrations

[Liviu Chircu]

On 17.01.2023 19:01, Daren FERREIRA wrote:
Jan 17 17:26:16 opensips[2810991]: 
DBG:mid_registrar:build_unregister_hdrs: extra hdrs: 'Contact: 
;expires=0#015#012'
Jan 17 17:26:16 opensips[2810991]: DBG:tm:t_uac: 
next_hop=

Jan 17 17:26:16 opensips[2810991]: DBG:core:mk_proxy: doing DNS lookup...
Jan 17 17:26:16 opensips[2810991]: DBG:core:sip_resolvehost: no port, 
no proto -> do NAPTR lookup!


If I well understand, OpenSIPS tries to generate the de-register, and 
first, determine the destination of the de-register (from AOR ?)
It considers it knows not enough about the protocol and port to use to 
generate the de-register and try to fill these informations from DNS.
This logically fails because there is no SRV nor NAPTR records for the 
FQDN extracted (from AOR).


The mid-registrar will typically *store* the R-URI ($ru) + 
Destination-URI ($du) combination, after you t_relay() the REGISTER 
towards the main registrar.  This info will be used in order to route a 
De-REGISTER in the exact same way (same message R-URI, sent to the same 
box).


Apparently, you are routing the REGISTER without setting a *$du *(notice 
the *"adding next hop: ..."* debug log in send_unregister() 
<https://github.com/OpenSIPS/opensips/blob/master/modules/mid_registrar/ulcb.c#L75>, 
which is NOT printed), so the mid-registrar attempts to send the 
De-REGISTER to *sip:myhost.mydomain.com*, which was grabbed either from 
the R-URI (most likely) or To header of the initial REGISTER.  And, 
before sending the packet, of course it needs to resolve the hostname to 
an IP address.  If there are any issues during this resolution... you 
must let me know of any relevant logs, as I have no idea.


Hopefully, you have some pointers to look out for now.

Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Question on mid_registrar de-registrations

[Liviu Chircu]

On 17.01.2023 17:09, Daren FERREIRA wrote:


My understanding was opensips should do the cleaning, as mentioned on 
the documentation.


/A common occurence is for some SIP User Agents to lose their network 
connection (especially when dealing with mobile devices), hence they 
do not properly de-register from the mid-registrar. In this case, in 
order to avoid stale registrations on the main registrar (which 
contains SIP contacts with greatly extended lifetimes!), the 
mid-registrar will appropriately generate De-REGISTER requests and 
remove these contacts from the main registrar's location service as 
soon as it considers them to have expired. /


Have I misunderstood?
If not, what can explain the un-register to never been sent by OpenSIPS?

You understood it perfectly.  My suggestion would be to skim through the 
code of mid_reg_aor_event() 
<https://github.com/OpenSIPS/opensips/blob/master/modules/mid_registrar/ulcb.c#L249> 
internal callback (it's pretty straight-forward), to get an idea of the 
DEBUG logging it can do, as well as "OK" code paths and "NOT OK" code paths.


Once you know what to look for, try to put OpenSIPS in debug mode 
("opensips-cli -x mi log_level 4") and follow with the DEBUG logs when 
the AoR is deleted by the timer process.  Let's see what it prints!  Of 
course, you should put it back to normal logging ASAP afterwards.


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Question on mid_registrar de-registrations

[Liviu Chircu]

On 12.01.2023 17:26, Daren FERREIRA wrote:
If I well understood, if a client is registered with a 500 seconds 
expiry, the server side is set to outgoing_expires, and, if the 
register is not renewed by the client, opensips should de-register.


In my case, the de-registers that should be triggered are never triggered.

I found no parameters relative to this in mid_registrar module, but, 
looking at the source code, it seems it depends on usrloc module.
On usrloc module, it seems that contact_refresh_timer is in charge of 
treating events, like expires, so I tried to enable it, without success.
Even after client expiry + timer_interval, the client is not 
de-registered on server side.


Is there anything I may have missed?


Hi Daren,

I notice you are using "mode == 2", which means De-REGISTERs will only 
be generated when the AoR gets deleted.  For example, if you have 2 SIP 
UAs registering to the same AoR and you are trying to kill one of them 
in an attempt to see a De-REGISTER being auto-generated downstream, that 
will never happen!  This is because the remaining Contact is enough to 
maintain "liveness" of the AoR to the downstream registrar.


Let me know if this is the case - if not, we can continue digging.  
Ideally, a SIP trace (.pcap or .txt) for the entire flow  would be 
helpful (you can email it to me personally, if privacy is an issue).


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Question on mid_registrar de-registrations

[Liviu Chircu]

On 12.01.2023 17:26, Daren FERREIRA wrote:


In my case, the de-registers that should be triggered are never triggered.


Hi Daren,

Please provide the output of "opensips -V", so we have something to work 
with here.


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Version 3.1 it stops writing cdrs

[Liviu Chircu]

On 13.01.2023 06:29, Saint Michael wrote:

This is the nth times that it happens. Opensips 3.1 It stops writing
cdr to the hard drive. The calls keep flowing, and I keep losing
records, money.


Make sure you are running at least version 3.1.13, so you benefit from a 
couple

race condition fixes in db_flatstore.  For example, something like what you
are describing could happen due to a bug in 3.1.12 or older whenever you 
called
"flat_rotate" 2+ times in the same second - this would internally bug 
some writers,

which would continue writing to the old (rotated) file descriptor.

However, a new "flat_rotate" should fix the internal state, even when 
the above bug
occurs.  If that doesn't it for you, then the issue is probably not 
related to db_flatstore

at all and you should review your ".sh" script.

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Release] OpenSIPS 3.3.3, 3.2.10 and 3.1.13 minor releases

[Liviu Chircu]

Hi, everyone!

The OpenSIPS 3.3.3, 3.2.10 and 3.1.13 minor releases have just been 
tagged, packing a significant number of fixes across various modules 
done in the past two months (~40 fixes in total!), including a rare 
crash in "db_mysql" after a disconnect and a first failed reconnect on 
any connection.


Detailed changelogs are available on the website^[1][2][3] . Packaging 
to be available within the next couple of hours.


[1]: https://opensips.org/pub/opensips/3.1.13/ChangeLog
[2]: https://opensips.org/pub/opensips/3.2.10/ChangeLog
[3]: https://opensips.org/pub/opensips/3.3.3/ChangeLog

Happy Hacking and Happy Holidays!
OpenSIPS Team
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Release Freeze] Upcoming OpenSIPS 3.3.3, 3.2.10 and 3.1.13 minor releases

[Liviu Chircu]

Hi, everyone!

The 3.3.3, 3.2.10 and 3.1.13 OpenSIPS minor versions are scheduled for 
release on Wednesday, December 21st (two weeks from now).  This round of 
minor releases contains a significant number of fixes across various 
modules done in the past two months (~40 fixes in total!), so make sure 
to schedule an upgrade and deploy it as soon as possible (especially if 
you are using db_flatstore with a high rate of traffic!).


In preparation for the releases, we are imposing the usual freeze on any 
significant fixes (as complexity) on these stable branches, in order to 
ensure a safe window for testing in the days ahead.


Happy testing,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips-CLI Upgrade

[Liviu Chircu]

On 30.11.2022 16:14, Social Boh wrote:


Hello,

I have to downgrade the package:

yum downgrade opensips-cli

Regards

---
I'm SoCIaL, MayBe
El 30/11/2022 a las 8:59 a. m., Wadii ELMAJDI | Evenmedia escribió:


Hello,

After running a system upgrade opensips-cli package was upgraded.
Since then, no opensips mi commands is working , error :

Nov 30 13:54:07 1 /usr/sbin/opensips[2484]: 
ERROR:mi_fifo:get_reply_filename: forbidden filename: 
opensips_fifo_reply_1669816447.3951223:{"jsonrpc": "2.0", "id": 
"8296", "method": "which", "params": []}


Nov 30 13:54:07 1 /usr/sbin/opensips[2484]: 
ERROR:mi_fifo:mi_fifo_callback: error trimming filename: 
opensips_fifo_reply_1669816447.3951223



Hi, all!

Indeed: I introduced this "unnaceptable '.' character in filename" error 
yesterday, in the hope of making the filenames unique in time.  The bug 
has been fixed today, but the new "opensips-cli" build will be available 
starting tomorrow!


So, until tomorrow, try to downgrade if you can (as Social Boh suggested 
above), otherwise there is also the option of installing from source 
code 
<https://github.com/OpenSIPS/opensips-cli/blob/master/docs/INSTALLATION.md#from-source-code>!


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS eBootcamp 5-16 Dec |www.opensips.org/training
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mid_Registrar contact

[Liviu Chircu]

On 17.11.2022 12:37, nutxase wrote:
Just to confirm can registrar also forward the registration similar to 
how mid_registrar does?


Approach 1: the save() 
<https://opensips.org/docs/modules/3.4.x/registrar.html#func_save> 
function has an "r" flag (do not auto-send a reply upstream) which may 
be useful here, allowing you to t_relay() your REGISTER further 
downstream.  A caveat here is that you're saving the Contact before the 
Asterisk, which may fail (e.g. 500 Internal Server Error).  So what do 
you do then?  You must delete it somehow...


Approach 2: if I remember correctly, the save() 
<https://opensips.org/docs/modules/3.4.x/registrar.html#func_save> 
function was also designed to work on a 200 OK reply!  But I haven't 
tested this scenario in a long time, so I'm not sure how well or if it 
works at all nowadays.


Best,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS eBootcamp 5-16 Dec |www.opensips.org/training
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips freeDiameter integration...

[Liviu Chircu]

On 11.11.2022 11:21, Palivela Sheshu Pavan wrote:


05:48:28  FATAL! PS Loading of extension 
/usr/local/lib/freeDiameter/dict_dcca_3gpp.fdx failed: 
/usr/local/lib/freeDiameter/dict_dcca_3gpp.fdx: undefined symbol: 
fd_g_config


05:48:28  ERROR  ERROR: in '((fd_ext_load()))' :    Invalid argument

Nov 11 05:48:28 [5396] ERROR:aaa_diameter:freeDiameter_init: error in 
((fd_core_parseconf(dm_conf_filename))): -22


Nov 11 05:48:28 [5396] ERROR:aaa_diameter:diameter_peer_loop: failed 
to init freeDiameter library


Latest free diameter I have used.

But as suggested by @liviuchircu, I have used free diameter version 
1.2.0, But still facing the issue.


Can some one please suggest how to processed with the issue.


Hi Panvan,

It seems you have built that "dict_dcca_3gpp.fdx" module by yourself, 
since it's installed under "/usr/local/lib", so maybe the issue is 
related to your build/install and usage process. What we know:


* the "fd_g_config" variable is located in the "libfdcore" shared 
library (provided by "libfdcore6" package on Debian 10)
* the "freeDiameterd" daemon *depends* on the "libfdcore" library, 
otherwise it won't start


So if you get the "fd_g_config missing symbol" error, it means the 
libfdcore library failed to load, or it wasn't located.  Maybe you 
should try creating a "/etc/ld.so.conf.d/freeDiameter.conf" file with 
the "/usr/local/lib/" or whatever library path you build & installed the 
"libfdcore.so" file, then hit "sudo ldconfig", so your loader knows 
*where *to load your development library from!


But even simpler:  why not just work on a Debian 10 VM, which comes with 
nice packaging, including the extension you need:


# dpkg -L freediameter-extensions | grep fdx
/usr/lib/freeDiameter/acl_wl.fdx
/usr/lib/freeDiameter/dbg_monitor.fdx
/usr/lib/freeDiameter/dbg_msg_dumps.fdx
/usr/lib/freeDiameter/dbg_msg_timings.fdx
/usr/lib/freeDiameter/dbg_rt.fdx
/usr/lib/freeDiameter/dict_dcca.fdx
*/usr/lib/freeDiameter/dict_dcca_3gpp.fdx*
/usr/lib/freeDiameter/dict_dcca_starent.fdx
/usr/lib/freeDiameter/dict_eap.fdx
/usr/lib/freeDiameter/dict_mip6a.fdx
/usr/lib/freeDiameter/dict_mip6i.fdx
/usr/lib/freeDiameter/dict_nas_mipv6.fdx
/usr/lib/freeDiameter/dict_nasreq.fdx
/usr/lib/freeDiameter/dict_rfc5777.fdx
/usr/lib/freeDiameter/dict_sip.fdx
/usr/lib/freeDiameter/rt_busypeers.fdx
/usr/lib/freeDiameter/rt_default.fdx
/usr/lib/freeDiameter/rt_ignore_dh.fdx
/usr/lib/freeDiameter/rt_load_balance.fdx
/usr/lib/freeDiameter/rt_randomize.fdx
/usr/lib/freeDiameter/rt_redirect.fdx

In this package-based setup, you would only need the "freeDiameter/" 
source code in order to build the "app_opensips.fdx" extension to go 
with the other extensions installed by packages!  Of course, the source 
code version must be 1.2.1 (follow the freeDiameter Tutorial 
<https://www.opensips.org/Documentation/Tutorials-Diameter-AAA> and you 
should be good!)


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mid_Registrar contact

[Liviu Chircu]

On 16.11.2022 18:56, nutxase via Users wrote:
Is it possible to change the contact on mid_registrar to be the 
endpoint ip etc


as currently when registering to asterisk we see the details of 
opensips, but i want to hide that and rather show the endpoint


is that possible?


Hi nutxase,

The mid-registrar will rewrite the Contact in all 3 usage modes (even in 
"mirror" mode), per design.  If you want to keep the original Contact, 
you probably should not use mid-registrar at all, and try to make it 
work using a Path-based approach (RFC 3327 
<https://datatracker.ietf.org/doc/html/rfc3327>) + "registrar" module.


Best,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS eBootcamp 5-16 Dec |www.opensips.org/training
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] socket_in(port) vs socket_in(advertised_port)

[Liviu Chircu]

On 25.10.2022 19:11, Ross McKillop via Users wrote:


I would have expected $socket_in(port) to contain the actual port that 
was used (53235) and $socket_in(advertised_port) to contain the port 
that is advertised as the listening port for that socket (e.g. 7700) - 
however $socket_in(port) contains 7700 and $socket_in(advertised_port) 
is null.


Is this the intended behaviour and, if so, is there any way to access 
the *actual* destination port that was used (even if it’s ephemeral)?


Any advice anyone can offer would be much appreciated :)


Hey, Ross!

Regarding $socket: there is the READ-ONLY $socket_in [1], concerning the 
ingress traffic and $socket_out [2], READ-WRITE and fully optional, 
controlling the egress traffic.  And an OpenSIPS listener MAY 
additionally have an "advertised" component, for scenarios where it's 
sitting behind a NAT.


I can't think of many good ways of fetching/printing the ephemeral 
source port allocated by the Operating System for a TCP connection:


* Request time: you cannot print it while processing the INVITE since 
the source port is not even allocated until you run the very last t_relay()
* Reply time: replies will be routed using topmost Via, so *maybe* you 
have a chance at printing this port, by looking at the topmost Via 
header (OpenSIPS-generated), using transformations [3].  Even if 
OpenSIPS strips this header during loose_route(), you should still have 
access to it thanks to the "SIP message lumps" lazy evaluation mechanism.


Still: may I ask why you need the "egress ephemeral source port" 
information?  Maybe there is an alternative to the problem itself!


[1]: https://opensips.org/Documentation/Script-CoreVar-3-4#socket_in
[2]: https://opensips.org/Documentation/Script-CoreVar-3-4#socket_out
[3]: https://www.opensips.org/Documentation/Script-Tran-3-4

Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS eBootcamp 5-16 Dec |www.opensips.org/training
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Call Branching in parallel and series

[Liviu Chircu]

On 01.11.2022 17:12, Conrad de Wet wrote:


This works, except I want to extend this even further. I want these 4 
branches to keep trying on a loop until the transaction timeout occurs 
or one of the calls is answered. Except I find that the 
“failure_route” has two main problems, firstly if I try a “t_relay()” 
in the failure_route, the original call gets relayed again and I can’t 
seem to refer back to the branch.


This causes the number of branches to quickly run out (I think max is 
16), as it seem to nest the branch. Also because the t_relay() appears 
to act on the main branch, all the urls are reset, so I don’t really 
know where I was originally sending this request to.


failure_route[my_on_failure]{

    seturi($branch(uri));   # <-- This is null

    t_relay(); # causes new branches that don’t seem to 
kill the old ones.


}


Hi, Conrad!

Re: the confusion around failure_route: the failure route callback 
actually means a "failure to relay", not a "failure of a specific 
branch".  So no matter how many branches you attempted to relay in 
parallel (1, 2, 8, etc.), it means they *all* failed (some explicitly 
with, e.g. a 404, others implicitly with a 408 internal timeout).  So 
now you're in this callback and you're only given the original 
Request-URI of the message, with an opportunity to build a new set of 
branches to relay (optionally with a new failure route callback), or 
just give up and pass the error message back upstream.


On topic:  I'm assuming the need to "keep trying these branches in a 
loop" stems from the fact that the "lookup()" operation may produce 
different results throughout the duration of the call attempt.  So 
instead of having a long transaction timeout, you prefer to have a 
shorter one and keep redo'ing the "failure_route + lookup()" loop in 
hope that the WS device comes online, correct?  If so, you may indeed 
often run into the "max branches exceeded" limitation quite easily this 
way, at least with how the code currently works...


Possible cheap workaround: recompile with a larger MAX_BRANCHES (say, go 
from 12 to 31).  At least you may get your PoC working this way and move 
to solving other problems.  Medium-term, maybe we can look into 
developing some support for creating lots of branches in the "master" 
OpenSIPS tree.


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Blog] How To Generate Self-Signed STIR/SHAKEN Certificates

[Liviu Chircu]

Hi all,

As STIR/SHAKEN is becoming increasingly popular (and mandatory...) in 
the North-American continent, you may want to check out this^[1] blog 
post in order to learn how to generate /free (/as in 
/beer/)//STIR/SHAKEN certificates on your own and begin proof-testing 
your up-and-coming STIR/SHAKEN infrastructure.


[1]: 
https://blog.opensips.org/2022/10/31/how-to-generate-self-signed-stir-shaken-certificates/


Best regards,

--
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Problem with gflags

[Liviu Chircu]

On 27.10.2022 17:55, Saint Michael wrote:

I just need to know how to check for the gflag inside the code
this:
  if (is_gflag("1")) {..}
does not work, even if the flag is (1), as I wrote this test from the
command line works

opensips-cli -x mi is_gflag 1
true

As you can see, unless you can test for the gflag value inside the
code, it cannot be used. The module gflag is of a great importance
when managing Opensips, because it allows for an orderly shutdown
without losing CDR, that is: money.

Many thanks.


Script: is_gflag(0) (is bit "0" set?)
MI: is_gflag(1) (are all bits in bitmask "1" set?)

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Problem with gflags

[Liviu Chircu]

On 27.10.2022 17:20, Saint Michael wrote:

I only get the second xlog()

The documentation may be wrong, it asks us to use
if (is_gflag("1")) {..}
But opensips fails to start.

How do I test for gflag=1 inside my
route


Hi SM,

The set of functions in "gflags" module is a bit strange, however they 
are correct.  The script functions work with *bits* (e.g. bit 0, 1, 2, 
...), while the MI functions work with *bitmasks* (e.g. 1, 2, 4, ...).  
Be careful not to mix the two, and you should get the correct results.


I believe the docs are somewhat accurate about the above - if not, let 
me know and we can make improvements together.


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [OpenSIPS-Devel] [Release] OpenSIPS 3.3.2, 3.2.9 and 3.1.12 minor releases

[Liviu Chircu]

Hi, all!

The OpenSIPS 3.3.2, 3.2.9 and 3.1.12 minor releases have just been 
tagged, packing essential fixes done in the past two months.


Detailed changelogs are available on the website^[1][2][3] . Packaging 
to be available starting tomorrow as part of the daily builds.


[1]: https://opensips.org/pub/opensips/3.1.12/ChangeLog
[2]: https://opensips.org/pub/opensips/3.2.9/ChangeLog
[3]: https://opensips.org/pub/opensips/3.3.2/ChangeLog

Happy Hacking!

--
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Release] OpenSIPS 3.3.2, 3.2.9 and 3.1.12 minor releases

[Liviu Chircu]

Hi, everyone!

The 3.3.2, 3.2.9 and 3.1.12 OpenSIPS minor versions are scheduled for 
release on Wednesday, October 19th -- a week and a half from now.


In preparation for the releases, we are imposing the usual freeze on any 
significant fixes (as complexity) on these stable branches, in order to 
ensure a safe window for testing in the days ahead.


Happy testing,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Formating issue for string that contains pv

[Liviu Chircu]

On 10.10.2022 12:43, Serdar GUCLUER wrote:


In my situation, i want to format string which contains 
pseudo-variables. These string are stored in db and cached with 
"cache_table" module.


I tried it like that;

$avp(value) = $sql_cached_value(caching_name:column_name:key);
pv_printf($var(formatted_value), 
$sql_cached_value(caching_name:column_name:key));
xlog("L_INFO", "*** Value: $avp(value) | Formatted Value: $var(formatted_value) 
***");


Hi Serdar,

I remember that at some point, there was some support for string 
evaluation added as part of the {s.eval} transformation[1].  
Unfortunately, I don't recall an equivalent function, so you may have to 
play around with the transformation only.


[1]: https://www.opensips.org/Documentation/Script-Tran-3-4#s.eval

Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2022 Athens, Sep 27-30 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Push notification

[Liviu Chircu]

On 15.09.2022 10:09, Sergey Pisanko wrote:

Hello.
I have read this article about push notification support according to 
rfc 8599 in Opensips 3.1

https://blog.opensips.org/2020/05/07/sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-i/

But I stay confused about one thing.It may be considered to be a  
"newbie question", but... What can be an "entity" (3rd party app/API)
with help of which I can create a subscription for Message Service 
(for example Firebase) to get the needed "pn" parameters to be 
inserted into the register sip request?


Hi Sergey,

Usually, that "entity" is an application on the respective marketplace.  
For Firebase, it would be an Android App with a unique AppID on the Play 
Store, allowing you to request that PNs get sent for your ecosystem's 
devices (soft phones) on behalf of your AppID.  For APNS, it would 
probably be a similar App Store App, with its own unique ID and a 
similar mechanism.


Usually, the developer documentation for each platform should include 
guides on how to request the PNs using some REST calls, once you 
register your App and obtain your App ID.


Hope this helps,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2022 Athens, Sep 27-30 | www.opensips.org/events


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Need some clarification in opensips cachedb_mongo db configutaion .

[Liviu Chircu]

On 24.08.2022 11:56, Sasmita Panda wrote:


Now my primary cluster goes down so my secondary cluster becomes 
primary . I have updated the connection string against the domain in 
route53 . Now
*primary-cluster.xzy.com <http://primary-cluster.xzy.com>* is pointed 
to the new primary custer connection string .


While creating a connection from the console through the mongo shell 
it's getting connected . But opensips is not able to switch the 
connecting string somehow . still it's trying to connect to the 
previous primary connection string .


It seems like opensips has cached the connection string and is trying 
to connect to the same even after I have updated the string from the 
backend .


libmongo will try each node in your CSV of nodes, there is no going 
around this.  Now, while your usage of two completely different clusters 
in the same connection string seems to be *non-conventional* (I don't 
recall any documentation advising this, all Mongo docs talk about 
connecting to either a *replica set*, or to a *list of* *mongos* 
servers), I still think it could work.  Maybe just configure the 
"connectionTimeousMS" parameters (or others??) and see if you can get 
libmongoc to time out faster on your 1st cluster, when it goes down.


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2022 Athens, Sep 27-30 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Need some clarification in opensips cachedb_mongo db configutaion .

[Liviu Chircu]

On 22.08.2022 08:44, Sasmita Panda wrote:


When I am configuring 2 connectionstrings here , that means
1. Opensips will always honor the 1st one as primary and 2nd one as 
secondary ?


2. If the 1st one will get down and 2nd one becomes primary , what 
will happen to opensips ? Will that keep the 2nd one as primary 
automatically or I have to switch the domain in the config ?


3. How does opensips decide which one is primary and which is secondary ?

Please help me out . I am stuck in the middle of something here .


Hi Sasmita,

This has more to do with the libmongoc library behavior, rather than 
OpenSIPS.  First, the multi-host replica set syntax is part of the 
MongoDB connection string syntax[1], so everything that you can read on 
the Mongo website also applies to the "cachedb_mongodb" module.


1. This means that once you include the "replicaSet=rs0" component, the 
library will automatically establish who is the PRIMARY node on each 
query.  If the PRIMARY should ever change (either due to system failure, 
manual switch, etc.), the library will be able to switch to the new 
PRIMARY, whichever that may become (imagine you have a 5-node replica set).


2. no need to change the config string. The library will always know 
which is the PRIMARY (writer) node.


3. I cannot say... I image the library will connect to each node and run 
an "isMaster()"[2] command?  I suggest you do an ngrep or even a PCAP 
capture - that should give you more info on libmongoc behavior.


[1]: https://www.mongodb.com/docs/v5.2/reference/connection-string/
[2]: https://www.mongodb.com/docs/v4.2/reference/command/isMaster/

Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2022 Athens, Sep 27-30 | www.opensips.org/events


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [Release] OpenSIPS 3.3.1, 3.2.8 and 3.1.11 minor releases

[Liviu Chircu]

On 03.08.2022 18:58, Liviu Chircu wrote:

Hi, everyone!

The 3.1.11 and 3.2.8 OpenSIPS minor versions are scheduled for release 
on Wed, August 17th -- that's two weeks from now.


In preparation for the releases, we are imposing the usual freeze on 
any significant fixes (as complexity) on these stable branches, in 
order to ensure a safe window for testing in the days ahead.


Happy testing,


Hello,

As scheduled, the OpenSIPS 3.3.1, 3.2.8 and 3.1.11 minor releases are 
now available, packing important fixes of the past two months.


Detailed changelogs are available on the website^[1][2][3] .

[1]: https://opensips.org/pub/opensips/3.1.11/ChangeLog
[2]: https://opensips.org/pub/opensips/3.2.8/ChangeLog
[3]: https://opensips.org/pub/opensips/3.3.1/ChangeLog

Happy Hacking!

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2022 Athens, Sep 27-30 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Release] OpenSIPS 3.1.11 and 3.2.8 minor releases

[Liviu Chircu]

Hi, everyone!

The 3.1.11 and 3.2.8 OpenSIPS minor versions are scheduled for release 
on Wed, August 17th -- that's two weeks from now.


In preparation for the releases, we are imposing the usual freeze on any 
significant fixes (as complexity) on these stable branches, in order to 
ensure a safe window for testing in the days ahead.


Happy testing,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2022 Athens, Sep 27-30 | www.opensips.org/events


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Issues running opensips-cli

[Liviu Chircu]

On 02.08.2022 08:01, Tito Cumpen wrote:


I am having issues running opensips-cli from the latest git pull. I am 
attempting to create the db but noticed that running the cli tool 
alone throws an error.


$ opensips-cli
Traceback (most recent call last):
  File 
"/usr/local/lib/python3.6/site-packages/importlib_metadata-4.12.0-py3.6.egg/importlib_metadata/_compat.py", 
line 9, in 

    from typing import Protocol
ImportError: cannot import name 'Protocol'


Hi Tito,

Can you teach us how to reproduce the issue?

* what OS are you using?
* are you using your stock OS Python3.6 or a custom build?
* what commands did you use to install your "opensips-cli"?

Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2022 Athens, Sep 27-30 | www.opensips.org/events


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] I am facing soem issue while taking inbound call from a TLS gateway .

[Liviu Chircu]

On 05.07.2022 15:16, Sasmita Panda wrote:
When I am calling from gw1 , in the config it comes under the function 
*is_from_gw* . But when I am calling from gw4 with TLS , it does not 
come under the *is_from_gw *function .


Outgoung call to gw4 working fine . But Opensips is not accepting call 
from the same gateway .


Hi, Sasmita!

Maybe the TLS gateway uses an emphemeral source port, so you need to 
pass the "n" flag (Ignore port) to is_from_gw() [1]?


[1]: https://opensips.org/docs/modules/3.4.x/drouting.html#func_is_from_gw

Best Regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2022 Athens, Sep 27-30 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] package dependency problems for opensips-cli

[Liviu Chircu]

On 27.06.2022 17:48, Pyle, Jeff wrote:

Then:

# apt install python
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package python is a virtual package provided by:
  python-is-python2 2.7.18-9 [Not candidate version]

E: Package 'python' has no installation candidate


I have the python2 and python3 packages installed, among others. I 
feel like I'm missing something. Any thoughts?


Hi, Jeff!

I pushed a fix[1] for the opensips-cli package, so it depends on 
"python3" instead of "python".  Let's see if the issue is resolved 
tomorrow, after the rebuild.


[1]: https://github.com/OpenSIPS/opensips-cli/commit/a3e0c7d91a

Cheers,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2022 Athens, Sep 27-30 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [Release] OpenSIPS 3.3.0-rc1, 3.2.7 and 3.1.10 minor releases

[Liviu Chircu]

On 06.06.2022 12:41, Liviu Chircu wrote:

Hi, all!

After nearly a month of beta testing for 3.3, we will soon push a 
release candidate version for the 3.3 branch, as well as two new minor 
releases for the stable branches, namely 3.2.7 and 3.1.10.


I am pleased to announce that we have just released a first candidate 
for the 3.3 version, 3.3.0-rc1, after a month of beta testing.  During 
this time, there were significant improvements to the original 
3.3.0-beta release, to name a few:


* new package: "opensips-auth-modules", containing the "auth" and 
"uac_auth" modules, which are OpenSSL dependant.  Thanks to this change, 
the core "opensips" package is once again free of any SSL library 
package dependencies.


* aaa_diameter: it is now possible to access all AVPs from the Diameter 
Response packet, at opensips.cfg level.  Moreover, full support for 
Grouped AVPs was added.  All of these additions re-iterate the initial 
goal of "generic Diameter integrations in 3.3", bringing it that much 
closer to being a reality.  Many thanks to Giovanni Maruzzelli and 
Flavio Goncalves for their excellent feedback here!


* several critical bugfixes/improvements in the msrp_gateway, msrp_relay 
and msrp_ua modules


Of course, along with *3.3.0-rc1* also comes a series of minor releases 
for the stable branches: *3.2.7* and *3.1.10*, with tarballs[1] and 
ChangeLogs[4] being available on the OpenSIPS website.


[1]: https://opensips.org/pub/opensips/3.3.0-rc1/opensips-3.3.0-rc1.tar.gz
[2]: https://opensips.org/pub/opensips/3.2.7/opensips-3.2.7.tar.gz
[3]: https://opensips.org/pub/opensips/3.1.10/opensips-3.1.10.tar.gz
[4]: https://opensips.org/pub/opensips/3.3.0-rc1/ChangeLog
[5]: https://opensips.org/pub/opensips/3.2.7/ChangeLog
[6]: https://opensips.org/pub/opensips/3.1.10/ChangeLog

So please enjoy these releases, as we start the home run for 3.3.0 stable!

Happy Hacking,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS Summit 2022 Athens, Sep 27-30 |www.opensips.org/events
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] version number of 3.3.

[Liviu Chircu]

Hi Johan,

Although we've started a "3.3" branch, the "3.3.0" release is not 
finalized yet, as it's undergoing two months of beta testing.  To 
signify this process, the build tag is currently "3.3.0-beta".  In 
roughly two weeks from now, we will push out a first release candidate 
version, so the build tag will be bumped to "3.3.0-rc1".


Regarding your "db_mysql" module error, maybe you have it under 
"exclude_modules=" in Makefile.conf and it did not get included in a 
"make modules" command you ran?  Try to force a rebuild of the MySQL 
client driver with "make modules module=db_mysql" and see if it picks up 
the module afterwards.


Best Regards,

On 09.06.2022 17:13, johan wrote:

even worse : using latest github of 3.3


Jun  9 10:09:51 debian10opensips31 opensips: ERROR:core:version_control:
module version mismatch for db_mysql; core: opensips 3.3.0-beta
(x86_64/linux); module: opensips 3.3.0-dev (x86_64/linux)

On 9/06/2022 15:57, johan wrote:

Hello,

i just downloaded opensips 3.3.

opensips -V still shows beta version.


version: opensips 3.3.0-beta (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: 05016a0da
main.c compiled on 09:54:58 Jun  9 2022 with gcc 8


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp, May 23 - June 3 | www.opensips.org/training


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Release] OpenSIPS 3.3.0-rc1, 3.2.7 and 3.1.10 minor releases

[Liviu Chircu]

Hi, all!

After nearly a month of beta testing for 3.3, we will soon push a 
release candidate version for the 3.3 branch, as well as two new minor 
releases for the stable branches, namely 3.2.7 and 3.1.10.


All of this will be happening on June 22nd, roughly two weeks from now.  
Until then, the stable branches are frozen from receiving any 
significant fixes, to improve the quality of the upcoming releases.


Happy hacking!

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS Summit 2022 Athens Sep 27 - 30 | opensips.org/events


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Blog] Using the Diameter Client Capability of OpenSIPS 3.3

[Liviu Chircu]

Hi, all!

OpenSIPS 3.3 offers the abilities to send arbitrary Diameter requests 
from the opensips.cfg configuration script, as well as to fully access 
the Diameter answer data. This blog post fully covers all of these:


https://blog.opensips.org/2022/06/02/using-the-diameter-client-capability-of-opensips-3-3/

Enjoy,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mongo for dialog replication.

[Liviu Chircu]

On 29.04.2022 13:21, johan wrote:

How do I create opensipsDB.userlocation ?

I know:-)  I don't have used mongodb ever before.


Hi johan,

That's the beautiful thing about the JavaScript-like MongoDB: *it 
**always**works*. Even if the collection doesn't exist.  Even if the DB 
doesn't exist...


Now, "how good it works" is a topic best left for another day...

Best Regards,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS eBootcamp May 23 - June 3 |www.opensips.org/training
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS 3.1.9 and 3.2.6 minor releases

[Liviu Chircu]

On 11.04.2022 15:40, Liviu Chircu wrote:

Hi, everyone!

The 3.1.9 and 3.2.6 OpenSIPS minor versions are scheduled for release 
on Wed, April 20th -- roughly a week and a half from now.


In preparation for the release, we have already imposed a freeze on 
any significant fixes (as volume) on these two stable branches, in 
order to ensure a safe window for testing in the days ahead.


Best regards,


Hello,

As scheduled, the OpenSIPS 3.1.9 and 3.2.6 minor releases are already 
out there for the taking, packing important fixes done in the last two 
months.


Detailed changelogs are available on the website^[1][2] .

[1]: https://opensips.org/pub/opensips/3.1.9/ChangeLog
[2]: https://opensips.org/pub/opensips/3.2.6/ChangeLog

Happy Hacking!

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
OpenSIPS eBootcamp May 23 - June 3 |www.opensips.org/training
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [Blog] Fine-Grained TCP Configuration Using the "tcp_mgm" Module

[Liviu Chircu]

Hi all,

OpenSIPS 3.3 just got better with the addition of the long-awaited 
"tcp_mgm" module!  Together with some TCP processing throughput 
enhancements, they are all discussed in the following blog post:


https://blog.opensips.org/2022/04/20/fine-grained-tcp-configuration-using-the-tcp_mgm-module/

Happy Testing,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp May 23 - June 3 | www.opensips.org/training


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] [RELEASE] OpenSIPS 3.1.9 and 3.2.6 minor releases

[Liviu Chircu]

Hi, everyone!

The 3.1.9 and 3.2.6 OpenSIPS minor versions are scheduled for release on 
Wed, April 20th -- roughly a week and a half from now.


In preparation for the release, we have already imposed a freeze on any 
significant fixes (as volume) on these two stable branches, in order to 
ensure a safe window for testing in the days ahead.


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp May 23 - June 3 | www.opensips.org/training


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS 3.1.8 and 3.2.5 minor releases

[Liviu Chircu]

Hi all,

It is my pleasure to announce the OpenSIPS 3.1.8 and 3.2.5 minor 
releases, packing all fixes done in the past two months.


Detailed changelogs are available on the website^[1][2] .

[1]: https://opensips.org/pub/opensips/3.1.8/ChangeLog
[2]: https://opensips.org/pub/opensips/3.2.5/ChangeLog

All the best,
OpenSIPS Team

On 09.02.2022 13:15, Răzvan Crainea wrote:

Hi, everyone!

OpenSIPS 3.1.8 and 3.2.5 minor versions are planned to be released in 
two weeks, on Wednesday, 23rd of February 2022.
Starting today until the release day, we are putting a freeze on any 
new commits, unless they are addressing fully tested bug fixes.___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] do_routing() timerec help, OpenSIPS 3.1.7

[Liviu Chircu]

On 28.01.2022 19:22, Kingsley Tart wrote:


Wow yes thank you! I've been trying to get this to work on and off for 
weeks!


Always read the module docs^[1] when in doubt.  All of this is 
documented in section 1.1.4.3 of drouting 3.1 docs, including a pointer 
to the iCalendar RFC.


[1]: https://opensips.org/docs/modules/3.1.x/drouting.html#idp165696

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] do_routing() timerec help, OpenSIPS 3.1.7

[Liviu Chircu]

On 28.01.2022 18:46, Kingsley Tart wrote:


++-+--+---+--+-++--+--+--+-+
| ruleid | groupid | prefix   | timerec   | priority | 
routeid | gwlist | sort_alg | sort_profile | attrs| description |
++-+--+---+--+-++--+--+--+-+
|173 | 0   | 441476292509 | 20220124T00|404999|1 | NULL 
   | #gw9   | N| NULL | endpoint=gw9 | NULL|
|174 | 0   | 441476292509 | 20220128T163000|504096247 |1 | NULL 
   | #gw1   | N| NULL | endpoint=gw1 | NULL|
++-+--+---+--+-++--+--+--+-+


Hi Kingsley,

The 3.1 release is the final release using the classic timerec support.  
Since 3.2, the time recurrence parsing and evaluation is much more 
consistent and well-tested across all modules using this concept.


Still, in order to fix your issue on 3.1, the format I linked is the 
ONLY way in order to define an [A, B) interval, where B is 
non-inclusive.  Looking at your examples, both strings seem wrong 
("20220124T00|404999" and "20220128T163000|504096247"), because of 
the poorly formatted DURATION field -- the second one.  Example correct 
strings for that field: P7W (7 weeks), PT24H (24 hours), PT1M30S (1 
minute 30 seconds), etc..  The official format is detailed here^[1] .  
Fun fact: MySQL's Galera engine uses this exact format as well, in order 
to represent time durations in its config file.


[1]: https://datatracker.ietf.org/doc/html/rfc5545#section-3.3.6

Hope this helps,

--
Liviu Chircu
www.twitter.com/liviuchircu  |www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mid_registrar forking issue when push notifications enabled

[Liviu Chircu]

On 17.01.2022 22:52, Sugar wrote:
Is there a private place to upload debug log including config (in case 
some sanitation of sensitive info is missed)? Can you provide where to 
send? Thanks in advance. And yes it appears the register matching part 
is not occurring. Can also provide pcap of call when contact is pn 
enabled on one test extension that is being called as well. Let me 
know where I can send. And thank you again for responding.
If you have sensitive info, just email it to li...@opensips.org then, 
and I'll take a look.
Also while the column size was fixed in the usrloc table, the dialog 
table was not fixed, it still has char(255). I updated my schema to 
fix it (was using mysql db to save dialogs for testing and possible 
expansion to two opensips instances in dev environment.


My bad, your initial message said "dialog.contact", but I read 
"usrloc.contact", as the CHAR(255) pattern was identical.  Thank you for 
the hint, will push a fix for this as well!


Cheers,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mid_registrar forking issue when push notifications enabled

[Liviu Chircu]

Hi,

Answers inline,

On 17.01.2022 10:18, Sugar wrote:


The log shows the push notification is successful using rest client, 1 
second after successful android push notification, the client 
registers but the call is not forked (it appears no transaction branch 
injection occurs).
So everything worked except for the last step: the REGISTER-INVITE 
matching part.  Could you post some full DEBUG logs of a call sequence, 
including the final Re-REGISTER triggered by the PN?  I need to 
understand why the event_routing module is not properly matching that 
Re-REGISTER to the halted INVITE.


Mid_registrar_save params are p0c2f

Mid_registrar_lookup called with m flag only when si is from main 
registrar.


Mid registrar mode 2

Pn enabled with default values.

E_UL_contact_refresh properly raised

Usrloc fr_timeout raised to 10 seconds

 pn_process_purr is not enabled.
Settings "sound" OK.  Perhaps including them could help to some degree.  
I am actually doing some testing on this 3.2.4 code these days as well, 
so expect more feedback to come, as I run through the same flows.


PS storing call dialog in a database requires the contact fields to be 
changed from char(255) to text when pn enabled. It has been really 
hard trying to find where to alert opensips about that. If someone has 
that info can you let me know (ie github, developer list, other 
support avenue).


Per the timely suggestions of John Quick, this limitation of the DB 
schema was already fixed and backported to 3.1+ five months ago, see 
here^[1] .


[1]: https://github.com/OpenSIPS/opensips/commit/70e8b24b

Best Regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] registrar and kv_store

[Liviu Chircu]

On 11.01.2022 11:50, Alberto wrote:


How do I insert values in the kv_store column?
It's easy to use the attr_avp, but I need to store a couple more 
values upon registrations and the key-value storage would be the 
perfect solution.


Hello, Alberto!

The "kv_store" column is for internal purposes, hence there is no way to 
READ or WRITE values to it from the opensips.cfg script.


Regarding attr_avp^[1] : why not store your data in JSON format (perhaps 
using the $json_compact^[2] ) variable?  This way, you can give it 
structure, using as many nesting levels as necessary in order to fit all 
of it.


[1]: https://opensips.org/docs/modules/3.3.x/registrar.html#param_attr_avp
[2]: https://opensips.org/docs/modules/3.3.x/json.html#pv_json_compact

Best Regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Working out OpenSIPS 3.2 roadmap

[Liviu Chircu]

On 03.12.2020 17:05, Saint Michael wrote:
Some engines like RocksDB, open-source, should be part of Opensips and 
run in the same process space. This would be a first for any 
softswitch technology.
We need full SQL technology, with tables, views, stored procedures, 
functions, timers, etc.


Hi, Saint Michael!

So with embed-able K/V databases such as LevelDB (Google) or RocksDB 
(Facebook, basically a fork of LevelDB), the only gain over the current, 
simplistic approach of "cachedb_local" could only be in terms of 
performance.  Right or wrong?


Regarding your other suggestion: that SQL "access" doesn't seem to have 
much to do with RocksDB anymore. And AFAIK, you can use avp_db_query() 
[1] to send any SQL query, regardless of how complex it is (SELECT, 
INSERT, UPDATE, DELETE, CALL PROCEDURE, CALL FUNCTION, CRATE TABLE, 
etc.).  Can you elaborate as to what you are missing here? :-)


[1]: https://opensips.org/docs/modules/3.3.x/avpops.html#func_avp_db_query

Cheers,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Does anyone have Fraud Detection working in OpenSIPS V3.2?

[Liviu Chircu]

On 15.12.2021 10:53, Adrian Fretwell wrote:


Just wondering if anyone has Fraud Detection working in OpenSIPS 
V3.2?  I just can't get the call to check_fraud to work without crashing.


For the record, the crash has been confirmed and fixed (using anything 
but the default time-recurrence for fraud DB rules will easily lead to a 
crash on OpenSIPS 3.2.0 to 3.2.3).  The fix is to be included in 
OpenSIPS 3.2.4, to be released in two days from now.


Happy Holidays,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [OpenSIPS-Devel] [RELEASE] OpenSIPS 3.1.7 and 3.2.4 minor releases

[Liviu Chircu]

On 08.12.2021 13:04, Răzvan Crainea wrote:

a freeze on commits


Expanding on this: "a freeze on most new fixes, any further commits 
should typically only address newly discovered regressions in the 
upcoming minor release".


--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1

[Liviu Chircu]

On 18.11.2021 12:09, Pete Kelly wrote:
It looks like there are quite a few inconsistencies on the drouting 
documentation page versus the docs here 
https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec 
<https://opensips.org/docs/modules/3.2.x/cfgutils.html#func_check_time_rec> 
- so maybe just a link or reference to check_time_rec would work for 
consistency?


Most likely, any timerec-related info on that page is outdated.  Will 
double-check all the content when I get to this task.  I like the idea 
to link to check_time_rec(), as it will future-proof the drouting docs 
against changes to the core, common function.


--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Drouting /timerec documentation for 3.2 vs 3.1

[Liviu Chircu]

On 18.11.2021 12:02, Pete Kelly wrote:
However the format is documented the same way in both 3.1 and 3.2 
within the "More on time recurrence" section


3.1: https://opensips.org/html/docs/modules/3.1.x/drouting.html 
<https://opensips.org/html/docs/modules/3.1.x/drouting.html>
3.2: https://opensips.org/html/docs/modules/3.2.x/drouting.html 
<https://opensips.org/html/docs/modules/3.2.x/drouting.html>


Should the 3.2 version be updated to reference the new format?


Hi Pete,

Good catch, thanks!  That section definitely slipped through the cracks 
and needs to be updated as well.


Best Regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] restart_persistency Permission denied

[Liviu Chircu]

On 05.11.2021 02:14, Marcin Groszek wrote:
after I changed the ownership of the .restart_persistency.cache to 
opensips I was able to start daemon as opensips user.


Is this proper way of doing this or just a poor workaround?


Hi Marcin,

This is an interesting report and although it looks like the devs could 
do something to improve your experience, ultimately I think this is a 
sysadmin runtime configuration error.  Here is my reasoning:


* by default, OpenSIPS starts as "root" user, with work directory "/".  
So drouting should work fine, as there is full permission to write to 
the "/" directory.


* in your case, you are downgrading permissions from "root" user to 
"opensips" user, but you are not customizing the "-w" work directory 
option, which remains "/". So, of course the "opensips" user cannot 
write to "/".


Hope this helps,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] user script trace option in xlog?

[Liviu Chircu]

On 27.10.2021 12:17, Kingsley Tart wrote:

Thanks - that looks useful, except that it no longer seems to be
present in OpenSIPS, at least with 3.1.x which is the version I'm
using. I can see from the docs that it's available in 2.2.x. I haven't
been able to find the equivalent in 3.1.x yet.


Docs for $cfg_line: 
https://www.opensips.org/Documentation/Script-CoreVar-3-1#toc102


I double-checked and it's in the code as well, so it SHOULD work.  Let 
me know if this is not the case anymore and I'll have a closer look.


Best,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] user script trace option in xlog?

[Liviu Chircu]

On 25.10.2021 20:50, Kingsley Tart wrote:

eg if I want to xlog an error, it would be handy for debugging purposes
to do something like

xlog("L_WARN", "You did a silly thing", 1);

and in the logs, see something like

You did a silly thing
   at opensips.cfg line 2623
   at opensips.cfg line 1874
   at opensips.cfg line 723


Hi,

Sounds to me like you need a route invocation backtrace, which is 
immediately available via the $(route[*]) construct.  See the docs [1] 
for more details.


Disclaimer: no line numbers are provided, only the list of route names 
that led up to the current execution point.


[1]: https://www.opensips.org/Documentation/Script-CoreVar-3-3#toc96

Best,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPS crashing but gdb not recognising core dump symbols

[Liviu Chircu]

On 26.10.2021 11:27, Kingsley Tart wrote:

gdb /usr/local/sbin/opensips core.6645

but on my system the binary is /usr/sbin/opensips.
Improved, thanks! The /usr/sbin/opensips path is much more common 
nowadays, given the excellent packaging that's available.

Anyway, I can now report the crashes with proper traces -
https://github.com/OpenSIPS/opensips/issues  I presume.

Yup, sounds good!

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPS crashing but gdb not recognising core dump symbols

[Liviu Chircu]

Hi,

On 26.10.2021 11:12, Kingsley Tart wrote:

root@ipx-a:/tmp# gdb ./ core.opensips.107.1635217462.23482
I think I figured out what's wrong... why are you using this "./" 
construct?!  That argument MUST be the binary that produced the 
corefile, which is typically /usr/sbin/opensips!  If you look below, gdb 
even briefly complains about this:

./: Is a directory.


Did you get this instruction from the website?  Let me know if there is 
anything to correct on that side.


Hope this helps,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] OpenSIPS crashing but gdb not recognising core dump symbols

[Liviu Chircu]

On 25.10.2021 17:52, Kingsley Tart wrote:

OpenSIPS 3.1.5 is crashing a lot on Debian 10.


Hi Kingsley,

In 3.1.6 there are some critical fixes in the auth, auth_db and 
mid-registrar modules.  If you are using any of those, I highly 
recommend you upgrade to it first, before investing any more time on 
these corefiles.


Regarding your corefile issue, it is definitely uncommon, the basic 
"opensips" + "opensips-dbg" package recipe should be enough for you to 
visualize at least a backtrace out of an OpenSIPS corefile.  One guess 
would be that you are also installing an "opensips" binary through "make 
install" on the same box, which is not symbol-compatible with the 
"opensips-dbg" debugging package.  Could this be the case?


Best,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS 3.1.6 and 3.2.3 minor releases

[Liviu Chircu]

Hello!

It is my pleasure to announce a new set of OpenSIPS minor releases: 
3.1.6 and 3.2.3!


These releases include the fixes of the past couple of months: roughly 
40 bugfixes/improvements, touching critical modules such as tls_wolfssl, 
rtp_relay, dialog, rtpengine, b2b_logic, auth, mid-registrar and 
event_routing.


Both releases are ready for production use, even more stable/accurate 
than before and backwards-compatible with the previous minor release.  
Since they contain the latest bug fixes, we strongly recommend you to 
upgrade your current instances.


Thank you all for your reports, fixes, pull requests and all other 
contributions to this project!


Full ChangeLogs:
    https://opensips.org/pub/opensips/3.1.6/ChangeLog
    https://opensips.org/pub/opensips/3.2.3/ChangeLog

Download instructions: https://opensips.org/Downloads/Downloads

Enjoy,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] concatenate an integer and a string

[Liviu Chircu]

On 18.10.2021 12:08, Alain Bieuzent wrote:


When I try to concatenate with $var(result) = $avp(id_asterisk) + "|" 
+ $avp(codecs);) I got this error message :


ERROR:core:eval_elem: invalid numeric operands

WARNING:core:do_assign: no value in right expression at 
/usr/local//etc/opensips/opensips.cfg:881



Hi,

The issue is that $avp(id_asterisk) contains an integer, so you cannot 
do "integer + string" concatenation in OpenSIPS.  However, what's 
interesting is that the OpenSIPS config language actually allows "string 
+ integer" concatenation!  So just fix it like this:


$var(result) = "" + $avp(id_asterisk) + "|" + $avp(codecs);

Best Regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] DROUTING module flag changes

[Liviu Chircu]

On 04.10.2021 16:35, Ben Newlin wrote:
What’s done is done in this case, but something to think about for 
future breaking changes, especially relating to the DB.


Hi Ben,

I totally agree with you on this one -- the shifting of the carrier 
flags in the /drouting/ module was *completely* unnecessary and must 
have fallen through the cracks during the /qrouting/ module's 
development/review/approval process.


Best,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Dynamic Routing adding + prefix to the called number

[Liviu Chircu]

On 04.10.2021 17:34, Yigit Zorlu wrote:
Dynamic Routing is adding + prefix to the called number. How can we 
strip or disable this behaviour?



Hi,

Check your DB data, this behavior is NOT there by default.  Most likely, 
you or some previous sysadmin have populated the "+" string for the 
"prefix" column of one or more rules in the "opensips.dr_rules" table, 
which does not seem to be a desirable behavior/feature anymore for your 
platform.


Best,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] query cashed dr_rules table

[Liviu Chircu]

On 02.10.2021 00:31, Marcin Groszek wrote:

Is there a way to query cashed dr_rules table?

I know it can be done by avp_db_query("SELECT count(prefix),attrs from 
dr_rules where but this will be resource hungry.


Hi,

See the "dr_number_routing" MI command [1], it provides a way to do the 
longest-prefix matching using the data that's currently cached by 
opensips, rather than the SQL table content.


[1]: https://opensips.org/docs/modules/3.3.x/drouting.html#idp5987920

Best,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] DROUTING module flag changes

[Liviu Chircu]

On 01.10.2021 21:34, Ben Newlin wrote:


Can anyone clarify the expected behavior here? Were the values for the 
flags column changed as part of removing the weight flag?



Hey Ben,

I believe you're referring to a change from 3.1, where the carrier "W" 
flag was removed & all other flags were shifted.  This change in 
behavior is documented in the migration page [1].


[1]: https://opensips.org/Documentation/Migration-3-0-0-to-3-1-0#toc9

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
OpenSIPS eBootcamp 2021: www.opensips.org/training

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users