[SR-Users] 302 Message Handling

2024-05-13 Thread tfayomi--- via sr-users
Hi All,

I'm having trouble understanding/finding resources on how to handle a 302 
message I receive. I'm working on making an inbound sbc with kamailio with 
clearip integration. I'm successfully sending to kamailio, but am having 
trouble retrieving the response from clearip in kamailio.

For some background, the intended call flow should be this:
first it should send from caller to kamailio (caller > kamailio), then over tcp 
kamailio sends to clearip (kamailio > clearip) [This is what is working as 
expected]
Then I should be able to signal to kamailio to continue the call to the 
intended destination.

When clearip sends a code back (in this case 302), I want to be able to see 
that code and send the caller to the correct destination. The problem I keep 
running into is that I can't seem to see the 302 code in a reply, branch or 
failure root or checking the status. I'm just lost on what I am 
misunderstanding and would appreciate if anyone could point me in the right 
direction on how to approach retrieving the 302 message.

I'm using kamailio version 5.6.3 and debian 12.1

Thanks in advance,
Temi
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:


[SR-Users] Re: q_malloc.c:520 WARNINGs

2024-05-13 Thread Ben Kaufman via sr-users
I’ve just noticed a similar behavior in kamailio 5.8.1 after upgrading from 
5.6.3.  I haven’t had time to poke around on it much yet.  Wondering if anyone 
found the root cause?  In my case I’m calling just `dp_match("1", "$rU");`

I’ll try to update with a simplified scenario, etc.


From: Joel Serrano via sr-users 
Sent: Saturday, March 9, 2024 9:30 AM
To: Kamailio (SER) - Users Mailing List 
Cc: Joel Serrano 
Subject: [SR-Users] Re: q_malloc.c:520 WARNINGs


CAUTION: This email originated from outside the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

I've tried setting corelog=L_INFO but I can still see the WARNINGS.

Also, one correction in my previous msg, I don't have 2 "debug" lines, I have 
them defined within a condition:

#!ifdef WITH_DEBUG
debug=L_DBG
#!else
debug=L_NOTICE
#!endif
...
...


Joel.




On Fri, Mar 8, 2024 at 9:54 PM Joel Serrano 
mailto:j...@textplus.com>> wrote:
Hi,

Does anyone know what this WARNING means or how to fix it?

2024-03-09T00:39:15.406674-05:00 csbc03 csbc[33024]: WARNING: {1 1 INVITE 
CALL-ID}  [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called 
from dialplan: dp_db.c: pcre2_free(206)
2024-03-09T00:39:15.406823-05:00 csbc03 csbc[33024]: WARNING: {1 1 INVITE 
CALL-ID}  [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called 
from dialplan: dp_db.c: pcre2_free(206)
2024-03-09T00:39:15.406973-05:00 csbc03 csbc[33024]: WARNING: {1 1 INVITE 
CALL-ID}  [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called 
from dialplan: dp_db.c: pcre2_free(206)
2024-03-09T00:39:15.407089-05:00 csbc03 csbc[33024]: WARNING: {1 1 INVITE 
CALL-ID}  [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called 
from dialplan: dp_db.c: pcre2_free(206)
2024-03-09T00:39:15.407178-05:00 csbc03 csbc[33024]: WARNING: {1 1 INVITE 
CALL-ID}  [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called 
from dialplan: dp_db.c: pcre2_free(206)
2024-03-09T00:39:15.407278-05:00 csbc03 csbc[33024]: WARNING: {1 1 INVITE 
CALL-ID}  [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called 
from dialplan: dp_db.c: pcre2_free(206)
2024-03-09T00:39:15.407375-05:00 csbc03 csbc[33024]: WARNING: {1 1 INVITE 
CALL-ID}  [core/mem/q_malloc.c:520]: qm_free(): WARNING: free(0) called 
from dialplan: dp_db.c: pcre2_free(206)
It happens after running dp_translate().

These are my settings:

debug=L_DBG
debug=L_NOTICE
memdbg=L_INFO
memlog=L_INFO
corelog=L_ERR
mem_summary=12
log_stderror=no
log_facility=LOG_LOCAL0
log_name="csbc"
log_prefix="{$mt $hdr(CSeq) $ci} "
mem_join=1


Any ideas?

Thanks,
Joel.


__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:


[SR-Users] Prefix match in htable

2024-05-13 Thread Antonio Reale via sr-users

Hello,
I'm testing Kamailio 5.x as a redirecting server based on calling number.
The calling numbers are stored on a DB and loaded in htable at runtime.
When the INVITE or REGISTER arrive Kamailio checks if there is a match 
on $fU in htable (KEY_NAME) and if there is one, it replies with 302 
adding the Contact HF with $fU@$sht(cli=>$fU)(with the domain part found 
in KEY_VALUE):

append_to_reply("$fU)>\r\n");

If I use the full number as KEY_NAME it works as expected, but how can I 
match on a prefix instead of the whole $fU?
For example, If I receive a call form 0655123456 I want to match it also 
if I have the prefix 0655 in htable.
Do you have some advice to achieve this goal with htable or in a similar 
way?

Thank you.
Best regards.

--
Antonio Reale
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:


[SR-Users] Re: TLS module crashes with FIPS OpenSSL

2024-05-13 Thread Marat Gareev via sr-users
Hello Henning,

yes, I use this major version

$ openssl version
OpenSSL 3.0.7 1 Nov 2022 (Library: OpenSSL 3.0.7 1 Nov 2022)

Thanks, I'll try updating Kamailio and report the results.


пн, 13 мая 2024 г. в 13:19, Henning Westerholt :

> Hello,
>
>
>
> are you on openssl 3.x by any chance? If yes, please upgrade to kamailio
> 5.7.5 or 5.8.1 and set tls_thread_mode=2 in the kamailio.cfg, as it fixes
> certain memory corruption issues on this openssl version.
>
> If you are still getting crashes after the upgrade and setting, please let
> us know, it might be something related to the FIPS mode.
>
>
>
> Cheers,
>
>
>
> Henning
>
>
>
> *From:* Marat Gareev via sr-users 
> *Sent:* Montag, 13. Mai 2024 09:19
> *To:* Kamailio (SER) - Users Mailing List 
> *Cc:* Marat Gareev 
> *Subject:* [SR-Users] TLS module crashes with FIPS OpenSSL
>
>
>
> Hello,
>
>
>
> I encountered a problem stopping Kamailio with FIPS OpenSSL:
>
>
>
> Program terminated with signal SIGSEGV, Segmentation fault.
>
> #0  0x7ff7292380ac in OPENSSL_sk_pop () from /lib64/libcrypto.so.3
>
> Missing separate debuginfos, use: dnf debuginfo-install 
> kamailio-5.7.3-4816.x86_64
>
> (gdb) bt
>
> #0  0x7ff7292380ac in OPENSSL_sk_pop () from /lib64/libcrypto.so.3
>
> #1  0x7ff72914bf5b in conf_modules_finish_int () from 
> /lib64/libcrypto.so.3
>
> #2  0x7ff72914c694 in CONF_modules_unload () from /lib64/libcrypto.so.3
>
> #3  0x7ff7291efff9 in OPENSSL_cleanup () from /lib64/libcrypto.so.3
>
> #4  0x7ff72954702b in ?? ()
>
> #5  0x000100061c08 in ?? ()
>
> #6  0x7ff7190566c8 in ?? ()
>
> #7  0x7ffccf196a20 in ?? ()
>
> #8  0x0071da8a in futex_release (lock=0x7ff729f08b50 ) at 
> core/mem/../mem/../futexlock.h:134
>
> #9  0x006e9448 in destroy_tls () at core/tls_hooks.c:75
>
> #10 0x0041f278 in cleanup (show_status=1) at main.c:594
>
> #11 0x00420af1 in shutdown_children (sig=15, show_status=1) at 
> main.c:721
>
> #12 0x00421717 in handle_sigs () at main.c:752
>
> #13 0x00430c88 in main_loop () at main.c:1988
>
> #14 0x00439d13 in main (argc=14, argv=0x7ffccf1973f8) at main.c:3212
>
> (gdb)
>
>
>
> Environment:
>
> Oracle Linux Server 9.3
>
> Kamailio 5.7.3
>
> yum list --installed | grep ssl
>
> openssl.x86_6410:3.0.7-24.0.3.el9_fips
>   @tools
>
> openssl-libs.x86_64   10:3.0.7-24.0.3.el9_fips
>   @tools
>
> openssl-pkcs11.x86_64 0.4.11-7.el9
>   @anaconda
>
> xmlsec1-openssl.x86_641.2.29-9.el9
>   @AppStream
>
>
>
> What can I do for further investigation?
>
>
>
> Thanks
>
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:


[SR-Users] Re: TLS module crashes with FIPS OpenSSL

2024-05-13 Thread Henning Westerholt via sr-users
Hello,

are you on openssl 3.x by any chance? If yes, please upgrade to kamailio 5.7.5 
or 5.8.1 and set tls_thread_mode=2 in the kamailio.cfg, as it fixes certain 
memory corruption issues on this openssl version.
If you are still getting crashes after the upgrade and setting, please let us 
know, it might be something related to the FIPS mode.

Cheers,

Henning

From: Marat Gareev via sr-users 
Sent: Montag, 13. Mai 2024 09:19
To: Kamailio (SER) - Users Mailing List 
Cc: Marat Gareev 
Subject: [SR-Users] TLS module crashes with FIPS OpenSSL

Hello,

I encountered a problem stopping Kamailio with FIPS OpenSSL:


Program terminated with signal SIGSEGV, Segmentation fault.

#0  0x7ff7292380ac in OPENSSL_sk_pop () from /lib64/libcrypto.so.3

Missing separate debuginfos, use: dnf debuginfo-install 
kamailio-5.7.3-4816.x86_64

(gdb) bt

#0  0x7ff7292380ac in OPENSSL_sk_pop () from /lib64/libcrypto.so.3

#1  0x7ff72914bf5b in conf_modules_finish_int () from /lib64/libcrypto.so.3

#2  0x7ff72914c694 in CONF_modules_unload () from /lib64/libcrypto.so.3

#3  0x7ff7291efff9 in OPENSSL_cleanup () from /lib64/libcrypto.so.3

#4  0x7ff72954702b in ?? ()

#5  0x000100061c08 in ?? ()

#6  0x7ff7190566c8 in ?? ()

#7  0x7ffccf196a20 in ?? ()

#8  0x0071da8a in futex_release (lock=0x7ff729f08b50 ) at 
core/mem/../mem/../futexlock.h:134

#9  0x006e9448 in destroy_tls () at core/tls_hooks.c:75

#10 0x0041f278 in cleanup (show_status=1) at main.c:594

#11 0x00420af1 in shutdown_children (sig=15, show_status=1) at 
main.c:721

#12 0x00421717 in handle_sigs () at main.c:752

#13 0x00430c88 in main_loop () at main.c:1988

#14 0x00439d13 in main (argc=14, argv=0x7ffccf1973f8) at main.c:3212

(gdb)

Environment:
Oracle Linux Server 9.3
Kamailio 5.7.3

yum list --installed | grep ssl

openssl.x86_6410:3.0.7-24.0.3.el9_fips  
@tools

openssl-libs.x86_64   10:3.0.7-24.0.3.el9_fips  
@tools

openssl-pkcs11.x86_64 0.4.11-7.el9  
@anaconda

xmlsec1-openssl.x86_641.2.29-9.el9  
@AppStream

What can I do for further investigation?

Thanks
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:


[SR-Users] TLS module crashes with FIPS OpenSSL

2024-05-13 Thread Marat Gareev via sr-users
Hello,

I encountered a problem stopping Kamailio with FIPS OpenSSL:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7ff7292380ac in OPENSSL_sk_pop () from /lib64/libcrypto.so.3
Missing separate debuginfos, use: dnf debuginfo-install
kamailio-5.7.3-4816.x86_64
(gdb) bt
#0  0x7ff7292380ac in OPENSSL_sk_pop () from /lib64/libcrypto.so.3
#1  0x7ff72914bf5b in conf_modules_finish_int () from /lib64/libcrypto.so.3
#2  0x7ff72914c694 in CONF_modules_unload () from /lib64/libcrypto.so.3
#3  0x7ff7291efff9 in OPENSSL_cleanup () from /lib64/libcrypto.so.3
#4  0x7ff72954702b in ?? ()
#5  0x000100061c08 in ?? ()
#6  0x7ff7190566c8 in ?? ()
#7  0x7ffccf196a20 in ?? ()
#8  0x0071da8a in futex_release (lock=0x7ff729f08b50 )
at core/mem/../mem/../futexlock.h:134
#9  0x006e9448 in destroy_tls () at core/tls_hooks.c:75
#10 0x0041f278 in cleanup (show_status=1) at main.c:594
#11 0x00420af1 in shutdown_children (sig=15, show_status=1) at
main.c:721
#12 0x00421717 in handle_sigs () at main.c:752
#13 0x00430c88 in main_loop () at main.c:1988
#14 0x00439d13 in main (argc=14, argv=0x7ffccf1973f8) at main.c:3212
(gdb)


Environment:
Oracle Linux Server 9.3
Kamailio 5.7.3

yum list --installed | grep ssl
openssl.x86_6410:3.0.7-24.0.3.el9_fips
 @tools
openssl-libs.x86_64   10:3.0.7-24.0.3.el9_fips
 @tools
openssl-pkcs11.x86_64 0.4.11-7.el9
 @anaconda
xmlsec1-openssl.x86_641.2.29-9.el9
 @AppStream


What can I do for further investigation?

Thanks
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe: