sr-users

sr-users@lists.kamailio.org

7 participants
37390 discussions

Branching 5.5 on git repo for 5.5.x releases
by Daniel-Constantin Mierla 21 Apr '21

21 Apr '21

Hello, since freezing the development for 5.5 series, I did quite a lot of code analyzing with a bunch of tools as well as run various tests, no major issue being in my list at this moment, therefore I think we can plan branching 5.5 on git repo in the near future. If there is no other suggestion or argument against it, I propose to create the branch 5.5 on Thursday next week (April 22, 2021). After that, master branch will be open for new features (to become part of 5.6 or what ever version will be decided to be next), testing will continue for branch 5.5 for another 1-2 weeks, then we will release 5.5.0 as first stable version in the 5.5.x series. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online May 17-20, 2021 (Europe Timezone) - June 7-10, 2021 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 1

Dialog - Profile cleanup before event_route[dialog:end]
by Andre Barbosa 21 Apr '21

21 Apr '21

Hi guys, I was trying to read the profile of a dialog on the event_route[dialog:end] and noticed that dialog profiles are not available at this point. My cfg code that doesn't work: event_route[dialog:end] { if (is_in_profile("orig")) { xinfo("this dialog belongs to a orig call\n"); route(EMIT_ORIG_CALL_ENDED); } } Log: | 3(12) INFO: <script>: Managing dialog... for BYE | 3(12) ERROR: *** cfgtrace:dbg_cfg_trace(): request_route=[DEFAULT_ROUTE] c=[/etc/kamailio/kamailio.cfg] l=263 a=24 n=dlg_manage | 3(12) DEBUG: dialog [dlg_hash.c:887]: internal_get_dlg(): ref dlg 0x7f8edda138e0 with 1 -> 3 | 3(12) DEBUG: dialog [dlg_hash.c:891]: internal_get_dlg(): dialog callid='96af5356-4663-4f5d-b6ca-c0d2381c992a' found on entry 16097, dir=1 to-tag='5' | 3(12) DEBUG: dialog [dlg_profile.c:536]: set_current_dialog(): setting current dialog [16097:1304] | 3(12) DEBUG: dialog [dlg_hash.c:1290]: next_state_dlg(): dialog 0x7f8edda138e0 changed from state 4 to state 5, due event 7 (ref 3) | 3(12) DEBUG: dialog [dlg_hash.c:1071]: dlg_ref_helper(): ref op on 0x7f8edda138e0 with 1 from dlg_handlers.c:1799 | 3(12) DEBUG: dialog [dlg_hash.c:1075]: dlg_ref_helper(): ref dlg 0x7f8edda138e0 with 1 -> 4 | 3(12) DEBUG: dialog [dlg_handlers.c:1803]: dlg_run_event_route(): executing event_route 3 on state 5 | 3(12) ERROR: *** cfgtrace:dbg_cfg_trace(): local_route=[dialog:end] c=[/etc/kamailio/kamailio.cfg] l=453 a=16 n=if | 3(12) ERROR: *** cfgtrace:dbg_cfg_trace(): local_route=[dialog:end] c=[/etc/kamailio/kamailio.cfg] l=448 a=25 n=is_in_profile Looking at code I can see that dialog profiles are cleaned on next_state_dlg() when the dialog moves from state 4 to state 5 /* remove the dialog from profiles when is not no longer active */ if(*new_state==DLG_STATE_DELETED && dlg->profile_links!=NULL && *old_state!=*new_state) { destroy_linkers(dlg->profile_links); dlg->profile_links = NULL; } My question for the more experienced guys: is this behaviour by design? Can we change it to only clean profiles at same time we clean dlg_vars for example? Thanks! Andre Barbosa

2 2

Http_client error encryption md5
by Daniel Hermann N'don 20 Apr '21

20 Apr '21

Hello guys !!! i'm a beginner in kamailio technology and i want to use kamailio http_client module to get data from API, but i got : Access error : Unauthorized Access Denied Wrong Password My user IDs are correct. API's encryption is MD5 (digest Auth ). So i use: modparam("http_client", "authmethod", 2) ... modparam("http_client", "cipher_suites", "ecdhe_ecdsa_aes_128_gcm_sha_256, rsa_aes_128_gcm_sha_256") then modparam("http_client", "cipher_suites", "rc4-md5") Can someone help me please ?

2 1

Kamailio 5.4.4 and Siptrace
by pwerspire 20 Apr '21

20 Apr '21

Hi list, I have the following configuration for siptrace: #################### modparam("siptrace", "duplicate_uri", "{{ homer_uri }}") modparam("siptrace", "hep_mode_on", 1) modparam("siptrace", "trace_to_database", 0) modparam("siptrace", "trace_flag", 22) modparam("siptrace", "trace_on", 1) modparam("siptrace", "trace_mode", 1) modparam("siptrace", "hep_version", 3) modparam("siptrace", "hep_capture_id", 2070) ####################### But we saw that local replies from Kamailio in some cases would not appear. For example, Invite is sent to Kamailio and Kamailio replies with a Forbidden, in homer only the Invite and the ACK would appear. So any scenario that the Invite has the final answer locally on Kamailio would not appear the reply in Homer. I tried to use the following modified config: #################### modparam("siptrace", "duplicate_uri", "{{ homer_uri }}") modparam("siptrace", "hep_mode_on", 1) modparam("siptrace", "trace_to_database", 0) modparam("siptrace", "trace_on", 1) modparam("siptrace", "trace_mode", 0) modparam("siptrace", "hep_version", 3) modparam("siptrace", "hep_capture_id", 2070) and in the Request Route: request_route { sip_trace_mode("t"); .... } ####################### With this last configuration, I can see now all the messages (for example the forbidden appears) but we found out a problem with this configuration. In a normal scenario if we have some mapping for example from 487 to 480 in the onreply_route { .... change_reply_status(480,"Temporary unavailable"); ..... } in homer it will appear that Kamailio received the 480 instead of the 487, so basically siptrace is reporting the message after being change instead of the original message received. Any ideas what I need to change on the siptrace to have this correctly working? Thanks for the help, Regards, Tiago

1 0

lots of syslog messages if sqlops fails to connect
by Juha Heinanen 20 Apr '21

20 Apr '21

I noticed that Kamailio produces huge (3400+) number qm_free() syslog messages if sqlops fails to connect to database. Don't know if it is intentional. -- Juha ... Apr 19 18:02:40 edge /usr/bin/edge-proxy[1467]: CRITICAL: <core> [main.c:1716]: main_loop(): Cannot fork Apr 19 18:02:40 edge /usr/bin/edge-proxy[1484]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 12 Apr 19 18:02:40 edge /usr/bin/edge-proxy[1466]: ERROR: db_mysql [km_my_con.c:163]: db_mysql_new_connection(): driver error: Can't connect to MySQL server on '192.26.134.10' (110) Apr 19 18:02:40 edge /usr/bin/edge-proxy[1466]: ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool Apr 19 18:02:40 edge /usr/bin/edge-proxy[1466]: ERROR: sqlops [sql_api.c:165]: sql_connect(): failed to connect to the database [main_proxy] Apr 19 18:02:40 edge /usr/bin/edge-proxy[1466]: ERROR: <core> [core/sr_module.c:865]: init_mod_child(): error while initializing module sqlops (/usr/lib/x86_64-linux-gnu/edge-proxy/modules/sqlops.so) (idx: 1 rank: 1 desc: [udp receiver child=0 sock=192.26.134.11:5060]) Apr 19 18:02:40 edge /usr/bin/edge-proxy[1466]: ERROR: <core> [core/pt.c:338]: fork_process(): init_child failed for process 1, pid 1466, "udp receiver child=0 sock=192.26.134.11:5060" Apr 19 18:02:40 edge /usr/bin/edge-proxy[1466]: CRITICAL: <core> [main.c:1716]: main_loop(): Cannot fork Apr 19 18:02:40 edge /usr/bin/edge-proxy[1466]: INFO: <core> [core/mem/q_malloc.c:529]: qm_free(): freeing a free fragment (0x7f82ea9dc2d0/0x7f82ea9dc2e0) - ignore Apr 19 18:02:40 edge /usr/bin/edge-proxy[1466]: INFO: <core> [core/mem/q_malloc.c:529]: qm_free(): freeing a free fragment (0x7f82ea9dc540/0x7f82ea9dc550) - ignore Apr 19 18:02:40 edge /usr/bin/edge-proxy[1466]: INFO: <core> [core/mem/q_malloc.c:529]: qm_free(): freeing a free fragment (0x7f82ea9daff0/0x7f82ea9db000) - ignore Apr 19 18:02:40 edge /usr/bin/edge-proxy[1466]: INFO: <core> [core/mem/q_malloc.c:529]: qm_free(): freeing a free fragment (0x7f82ea9d47d0/0x7f82ea9d47e0) - ignore Apr 19 18:02:40 edge /usr/bin/edge-proxy[1466]: INFO: <core> [core/mem/q_malloc.c:529]: qm_free(): freeing a free fragment (0x7f82ea9d4660/0x7f82ea9d4670) - ignore ...

2 3

TLS Error
by rob.van.den.bulk＠gmail.com 19 Apr '21

19 Apr '21

Hallo, I try to run kamailio 5.4 (new install) on Debian10 with TLS, I become errors. ksr_tls_fill_missing When I disable TLS in the config file Kamailio runs. Apr 19 18:47:36 server6120 /usr/local/sbin/kamailio[17959]: INFO: tls [tls_domain.c:356]: ksr_tls_fill_missing(): TLSs<default>: verify_depth=9 Apr 19 18:47:36 server6120 /usr/local/sbin/kamailio[17959]: INFO: tls [tls_domain.c:359]: ksr_tls_fill_missing(): TLSs<default>: verify_client=0 Can someone help me please ? Greetings Rob van den Bulk

2 1

Switch from SRTP to RTP when using Zoiper and Bria
by Markus Bönke 19 Apr '21

19 Apr '21

Hello NG, I saw the following threads discussing how to switch to RTP when a client does not support SRTP. https://lists.kamailio.org/pipermail/sr-users/2018-May/101341.html <https://lists.kamailio.org/pipermail/sr-users/2018-May/101341.html> https://lists.kamailio.org/pipermail/sr-users/2016-September/094457.html <https://lists.kamailio.org/pipermail/sr-users/2016-September/094457.html> There are some issues with Zoiper and Bria which also persist in the latest versions. Has anyone got it work with Zoiper and Bria? Thanks and regards Markus

2 2

Create accounta with multiple DIDs
by John Tuxies 19 Apr '21

19 Apr '21

I am novice in the area and i have a Kamailio basic setup where i create users and each user can call each other. No connection to an ITSP. i am trying to simulate things and need to send multiple numbers to each user. For example i have users 1000-1003. I need each user to have a range of 100 numbers (fake since it ia not connected anywhere) and routed to all the other users as well. The idea is to connect Asterisk servers and each one have a registered account 1000-1003. Then each Asterisk's extension have a particular DID and call another Asterisk server to a different DID. Off course this will go through Kamailio. Now i call from one Asterisk to the other by using the 1000-1003 and it works. But i need the DID routing

4 5

Info: regression for AVP with integer ID on v5.4.5
by Daniel-Constantin Mierla 16 Apr '21

16 Apr '21

Hello, a notification to inform about a regression to the AVPs with the integer IDs that was introduced in the v5.4.5 release when trying to fix an issue reported from a static code analyzer/fuzzer. The workaround is to use string names for AVPs, so if you have AVPs like $avp(i:123), they can be changed to $avp(s:123) in the kamailio.cfg (ie., replace i: with s: ). Regression is already fixed in the git branch 5.4, so if you install it from there, all should be ok. For Debian packages, you can wait till tomorrow and use the nightly builds of 5.4.x series from the repos listed at: * http://deb.kamailio.org/#dev54 Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online May 17-20, 2021 (Europe Timezone) - June 7-10, 2021 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 0

Dispatcher algorithms 11 using only weight
by Antonio Couto 16 Apr '21

16 Apr '21

I have a dispatcher setting using only rweight and the customer is complaining that not all destinations are reached, do I doing something wrong here ? below the dispatcher.list, the sum of all the weight values is 100 # asterisk group 2 2 sip:192.168.16.20:5060 0 rweight=45;duid=asterisk_1 2 sip:192.168.16.13:5060 0 rweight=11;duid=asterisk_2 2 sip:192.168.16.14:5060 0 rweight=11;duid=asterisk_3 2 sip:192.168.16.15:5060 0 rweight=11;duid=asterisk_4 2 sip:192.168.16.16:5060 0 rweight=11;duid=asterisk_5 2 sip:192.168.16.21:5060 0 rweight=11;duid=asterisk_6 Thanks in advance.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users