Re: [SR-Users] Unregister with Multiple Contacts

Sorted it. I needed to loop through the contacts, then select the correct ruid based on $ci For completeness, here is my solution: reg_fetch_contacts("location", "$fu", "un_reg"); $var(i) = 0; while ($var(i) < $(ulc(un_reg=>count))) { $var(ul_callid) =

[SR-Users] Kamailio 5.4.4 segmentation fault after kamctl rpc dialplan.dump

Hello, Kamailio version 5.4.4. Kamailio segmentation fault after kamctl rpc dialplan.dump , when dialplan includes variables in the replacement expression (repl_exp) field. Please see attached corefile. Thank you, Julia. (gdb) bt full #0 0x7fd2b64c5641 in __strlen_sse2_pminub () from

Re: [SR-Users] Unregister with Multiple Contacts

Beware that since you’re removing all contacts, if any are valid and if any of the contacts that did not unregister is called, Kamailio won’t find them. If what you need is not force only one contact per user, maybe look at

Re: [SR-Users] Unregister with Multiple Contacts

With the below, we loop through all of the contacts that match $fu, but only unregister the one matching the $ci of the 200 OK that is associated with the unregister (Expires: 0) request from the upstream server. It actually has 3 parts. For completeness, I probably should have added them

[SR-Users] loose_route() does not find socket by name

How about this? https://github.com/kamailio/kamailio/pull/2643 -- Juha ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Cockroachdb and kamailio 5.4

Jon, I’m not sure what would get my branch accepted. Henning mentioned on 9/16/2020 that the .sql files are generated from XML/XLST scripts, I have found: https://github.com/kamailio/kamailio/tree/5.4/doc/stylesheets/dbschema

Re: [SR-Users] Cockroachdb and kamailio 5.4

Welp! Looks like I’ve hit another issue, and I don’t think this is solvable by updating the Postgres configs. For instance, the permissions module is doing a validation on the address rows, and the group has to be a DB1_INT (INT4). However, the default value for INTEGER in Postgres is INT4,

Re: [SR-Users] Problem with kamalio.

Hello, they are different possible causes that Kamailio could not be started. Nowadays Kamailio is usually started with systemd or other init system, depending on the distribution. Have a look to the Kamailio log output (e.g. in /var/log/messages or /var/log/syslog) to get more information,

Re: [SR-Users] Kamailio Crash in TLS acceppt

Hi, try to update to a maintained version (e.g. recent 5.3.x or 5.4.x) – in TLS support there have been several bugs fixed in newer releases. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com From: sr-users On

Re: [SR-Users] Cockroachdb and kamailio 5.4

Hi Noah, sure – let me give you some pointers. So basically, the SQL files are generated from the XSL infrastructure in the quoted directory. This file e.g. is for postgres: https://github.com/kamailio/kamailio/blob/5.4/doc/stylesheets/dbschema/xsl/postgres.xsl You basically need to copy it to

[SR-Users] Kamailio Crash in TLS acceppt

Hi Team, Kamailio 5.2 getting crashed in tls_accept. Can someone help over here. #0 0x7f1b135c09b2 in EVP_DecryptUpdate () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #1 0x7f1b135f3034 in ?? () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #2 0x7f1b135f36a3 in ?? () from