- sr-users - kamailio.org

Kamailio - Initiating invite on REFER
by Muhammad Danish Moosa 02 Jan '24

02 Jan '24

Hi champs, In this flow like endpoint -> B2BUA 1-> kamailio -> B2BUA 2, there is a requirement that REFER should be handled by Kamailio and it should manage the transfer , initiating a new invite based on REFER. Any pointer will be helpful -- Danish

3 2

Connect to a remote ENUM(E.164 Number Mapping) server
by elhar.mohamed＠gmail.com 25 Dec '23

25 Dec '23

Hello, I'm using the Kamailio version 5.7.x, I didn't find in the module "enum.so" any option that allow to connect to a remote ENUM server. Could you please help me ! Thanks in advance

2 3

Merry Christmas and Happy Holidays 2023-2024!
by Daniel-Constantin Mierla 25 Dec '23

25 Dec '23

Kamailio project continued to evolve steadily, a new major release was out during this year, next one planned in a few months, relying on an amazing community of developers and users. We hope it kept helping people and companies world wide to connect with the dear ones and build a better way of living. The season holidays are ahead, time to relax, spend time with family and friends! I take again this chance to express my thanks and greetings to all the friends, developers, supporting companies and community members that made 2023 another fantastic year for Kamailio project. Enjoy the holidays! Merry Christmas! Daniel * Santa is flying Kamailio! * -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services Kamailio World Conference - April 18-19, 2024, Berlin

2 1

kemi python3s - module 'KSR' has no attribute 'nathelper'
by marek 22 Dec '23

22 Dec '23

hi, trying kamailio 5.7.3 with KEMI pythons3s sample from https://github.com/kamailio/kamailio/blob/master/misc/examples/kemi/kamaili… trying simple register with sipsak sipsak -U --sip-uri "sip:cervajs@kamailio.example.com" -u cervajs -a top_secret 4(28805) ERROR: PY8 {REGISTER}: app_python3s [apy3s_kemi.c:141]: apy3s_exec_func(): error exception occurred 4(28805) ERROR: PY8 {REGISTER}: app_python3s [apy3s_exception.c:167]: apy3s_handle_exception(): apy3s_exec_func: ksr_request_route((null)): Unhandled exception in the Python code: Traceback (most recent call last): File "/etc/kamailio/kamailio.py", line 31, in ksr_request_route if ksr_route_natdetect()==-255 : File "/etc/kamailio/kamailio.py", line 238, in ksr_route_natdetect if KSR.nathelper.nat_uac_test(19)>0 : AttributeError: module 'KSR' has no attribute 'nathelper' i see nat_uac_test in doc https://kamailio.org/docs/tutorials/5.7.x/kamailio-kemi-framework/modules/#… any tips/ideas? happy christmas Marek

1 1

Errors with TLS
by SAMUEL MOYA TINOCO 21 Dec '23

21 Dec '23

Hi everyone, All my environment was working properly. But a few days ago I've started to have problems with my websocket connectios. Everytime I try to register my websocket Kamailio log this Dec 20 09:02:10 prod-kamailio /usr/sbin/kamailio[599]: ERROR: tls [tls_server.c:1330]: tls_h_read_f(): protocol level error Dec 20 09:02:10 prod-kamailio /usr/sbin/kamailio[599]: ERROR: tls [tls_util.h:50]: tls_err_ret(): TLS accept:error:0A000416:SSL routines::sslv3 alert certificate unknown (sni: unknown) Dec 20 09:02:10 prod-kamailio /usr/sbin/kamailio[599]: ERROR: tls [tls_server.c:1334]: tls_h_read_f(): src addr: IP_webclient:61423 Dec 20 09:02:10 prod-kamailio /usr/sbin/kamailio[599]: ERROR: tls [tls_server.c:1337]: tls_h_read_f(): dst addr: IP_Kamailio:8443 Dec 20 09:02:10 prod-kamailio /usr/sbin/kamailio[599]: ERROR: <core> [core/tcp_read.c:1476]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7fbc423053b0 r: 0x7fbc423054d8 (-1) My tls.cfg: [server:default] method = TLSv1.2+ verify_certificate = no require_certificate = yes private_key = /etc/kamailio/cert/clave_SSL.key certificate = /etc/kamailio/cert/certificado.pem Kamailio version: root@prod-kamailio:/etc/kamailio# kamailio -v version: kamailio 5.6.3 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 12.2.0 I don't know why it stopped working. And I'm not sure what to do or what to check. Has anyone faced this problem? Any help would be appreciated Thanks in advance Samuel Moya Tinoco Departamento de Sistemas y Redes Móvil: (+34) 606985997 smoya(a)vivelibre.es<mailto:smoya@vivelibre.es> [cid:image001.png@01DA33E6.D2D833D0] Soluciones inteligentes para la autonomía personal

2 2

How to hang up the call in xhttp routing
by mm e 21 Dec '23

21 Dec '23

event_route[xhttp:request] { if ($hu =~ "hangupCall"){ $var(body) = $rb; xhttp_reply("200", "OK", "",""); jansson_get_field($var(body), "callid", "$var(callid)"); jansson_get_field($var(body), "cseq", "$var(cseq)"); if (t_cancel_callid("$var(callid)", "$var(cseq)", "22")) { xlog("L_NOTICE", "t_cancel_callid============"); } exit; } xhttp_reply("404", "Not Found", "",""); exit; } According to this route, the answered call cannot be hung up。How should I hang up the answered call in xhttp routing, similar to freeswitch's uuid_kill。

1 0

Kamailio - Ms Teams direct Routing - dispatcher issues | FLAGS: IP
by faisal.jamil.khan＠gmail.com 19 Dec '23

19 Dec '23

Hi Team, I am trying to setup Kamailio with MS Teams Direct Routing and after resolving TLS issues now I am getting this at my dispatcher flags. Possible suggestions required. kamcmd dispatcher.list | egrep "URI|FLAGS" URI: sip:sip.pstnhub.microsoft.com:5061;transport=tls FLAGS: IP URI: sip:sip2.pstnhub.microsoft.com:5061;transport=tls FLAGS: IP URI: sip:sip3.pstnhub.microsoft.com:5061;transport=tls FLAGS: IP Dec 14 20:23:27 abcsbc.com /usr/sbin/kamailio[9479]: INFO: <script>: Sent out tm request: OPTIONS sip:sip.pstnhub.microsoft.com:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS abcsbc.com:5061;branch=z9hG4bKd9f6.c2e7d2f4000000000000000000000000.0 To: <sip:sip.pstnhub.microsoft.com:5061;transport=tls> From: <sip:abcsbc.com>;tag=64ff6b492a7d9ab14de1f0b7c15c9c17-c7b52d5e CSeq: 10 OPTIONS Call-ID: 23b2dc436850e949-9479(a)0.0.0.0 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (5.6.5 (x86_64/linux)) Dec 14 20:23:28 abcsbc.com /usr/sbin/kamailio[9479]: INFO: <script>: Sent out tm request: OPTIONS sip:sip2.pstnhub.microsoft.com:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS abcsbc.com:5061;branch=z9hG4bKccf6.53fea6f0000000000000000000000000.0 To: <sip:sip2.pstnhub.microsoft.com:5061;transport=tls> From: <sip:abcsbc.com>;tag=64ff6b492a7d9ab14de1f0b7c15c9c17-7a126c3a CSeq: 10 OPTIONS Call-ID: 23b2dc436850e94a-9479(a)0.0.0.0 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (5.6.5 (x86_64/linux)) Dec 14 20:23:28 abcsbc.com /usr/sbin/kamailio[9479]: INFO: <script>: Sent out tm request: OPTIONS sip:sip3.pstnhub.microsoft.com:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS abcsbc.com:5061;branch=z9hG4bKdcf6.5a4f89e6000000000000000000000000.0 To: <sip:sip3.pstnhub.microsoft.com:5061;transport=tls> From: <sip:abcsbc.com>;tag=64ff6b492a7d9ab14de1f0b7c15c9c17-992aa610 CSeq: 10 OPTIONS Call-ID: 23b2dc436850e94b-9479(a)0.0.0.0 Max-Forwards: 70 Content-Length: 0 User-Agent: kamailio (5.6.5 (x86_64/linux))

3 33

Info: Next Kamailio World Conference - April 18-19, 2024, Berlin, Germany
by Daniel-Constantin Mierla 18 Dec '23

18 Dec '23

Hello, a short announcement to inform that the dates for next Kamailio World Conference have been set to April 18-19, 2024, the event to take place again in Berlin, Germany. It will be a different venue than the past editions, that one not being available. A pre-conference day is considered on April 17, 2024, but it is not yet known in what form and where. The conference is scheduled a bit earlier than the usual in the year because Germany hosts the Euro 2024 football championship during June-July 2024, making May very busy and harder to find adequate conferencing space in Berlin. The website and more details will be published soon. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services Kamailio Advanced Training -- asipto.com

1 0

Regretfully we were unable to process the URI
by Gavin Baumanis 18 Dec '23

18 Dec '23

Hi Everyone, Very new to SIP And to Kamailio Configuration / administration. I have a working AWS instance with Kamailio installed on it - and it works fine. We are creating a whole new environment and I have cloned the existing AWS EC2 instances. I have edited all the configs to ensure that they are using the correct DNS names and / or IP addresses. Otherwise the "configs" are identical. While attempting to call a SIP number, I get the following message, returned to the soft phone I am using (microSIP) *Regretfully we were unable to process the URI (479/SL)* I can also see the same error message in the console of the Kamailio server. I am hoping that this might mean something to someone enough - to suggest some troubleshooting steps, please. Thanks;

3 3

Encoded Call-ID - Topoh module
by Vanderlei Torres Batistela 15 Dec '23

15 Dec '23

Hello all, How can I get the encoded Call-Id generated by TOPOH module to store in the CDR ? Regards, Vanderlei

2 1

{uri.duri} not working
by hanxiaofang＠x-y-t.cn 13 Dec '23

13 Dec '23

Hi Kamailio experts, OS: Debian11 Kamailio ver: 5.7.3 {uri.duri} doesn't seem to work The following script can be reproduced: ``` debug=2 log_stderror=yes # mpath="/usr/local/lib/kamailio/modules/" loadmodule "tm.so" loadmodule "sl.so" loadmodule "pv.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "ctl.so" loadmodule "htable.so" modparam("tm", "failure_reply_mode", 3) modparam("tm", "fr_timer", 30000) modparam("tm", "fr_inv_timer", 120000) request_route { xinfo("*** $sel(msg)\n"); sl_send_reply("404", "Not here"); exit; } event_route[htable:mod-init] { $var(ouri) = "sip:alice@server.com:5060;nat=yes;transport=tcp;line=xyz"; $var(duri) = $(var(ouri){uri.duri}); # => "sip:server.com:5060;transport=tcp" xinfo("ouri = $var(ouri)\n"); xinfo("duri = $var(duri)\n"); if ($var(duri) == "sip:server.com:5060;transport=tcp" ) { xinfo("uri.duri work well\n"); } else { xerr("something is wrong\n"); } } ```

2 4

Proxy Inactivity and Kamailio Log Disruption Issue.
by satyaprakash ch 12 Dec '23

12 Dec '23

HI, Scenario: We possess 2 proxies and 2 registrar servers equipped with dmq functionality. Unexpectedly, one of the Proxy IP addresses was marked as inactive (FLAG: IP) in the dispatcher list, causing the proxy to cease responding. Simultaneously, Kamailio logs stopped recording any activity. Upon restarting the Kamailio service, the problem was resolved, and the proxy resumed normal operation, with the Flag changing back to AP (ACTIVE). The sudden occurrence of this issue is not clear, and due to the cessation of logs during the incident, we lack information for the investigation. Any suggestions on how to address this issue would be appreciated. And is this scenario happened to any one in your experience?

2 3

usrloc ka_mode - Flooding OPTIONS at same time?
by Benoit Panizzon 12 Dec '23

12 Dec '23

Hi We have reached 20000 registered CPE and start facing issues. Am I observing correctly that when ka_mode 4 is enabled, OPTIONS are send simultaneously to all registered CPE and not spread over the interval? They could be the cause very high pps peaks on network equipment? If so, is there a way to spread the ka options over time so they don't cause such high peaks? Or even better, is there a way to enable them for only some customers via a variable? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

4 5

is_method_f(): cannot parse cseq header in xhttp:request event route?
by Benoît Panizzon 12 Dec '23

12 Dec '23

Hi all I use event_route[xhttp:request] on Kamailio 5.5 Every time a xhttp request is processed I get this log entry: ERROR: textops [textops.c:3541]: is_method_f(): cannot parse cseq header Almost identical config on Kamailio 5.6 does not show this error. Is that something that got fixed in 5.6? I see a change in the documentation, While 5.5 does not state $rm can be accessed, 5.6 states $rm contains the HTTP method. Or do I somehow leak the http request to somewhere I call is_method() on it after terminating the event route? How should the event_route[xhttp:request] properly be terminated? With 'return' or with 'exit'? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

Upgrade Minor versions
by Gavin Baumanis 11 Dec '23

11 Dec '23

Hi there, I have taken over a project that uses Kamailio. I am aware of what we use it for - I am just not sure on the how... apart from what I have read in the docs. We're currently running 5.4.2 and I'd like to upgrade to (at least) the latest 5.4 offering - as that seems as if it would be the easiest and safest option. So I am hoping I might get some direction, please - on the way forward for an upgrade. The documentation seems OK if you're upgrading minor versions... but I couldn;t find anything about upgrading patch versions. Thanks!

2 2

Updated: Online devel meeting on matrix - 15:00 UTC, Dec 5, 2023
by Daniel-Constantin Mierla 05 Dec '23

05 Dec '23

Hello, we should consider an online devel meeting sometime soon to summarize what was done at (and still needs to be done after) devel meeting in Dusseldorf and plan a bit the targets for next major release (5.8 or 6.0)? If considered useful, I propose Dec 5 at 15:00UTC (16:00 Berlin/Paris/Madrid/Rome), but we can also look for other dates as well. Topics to be discussed can be added at: - https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings… Pull requests can be made by users without git access. Cheers, Daniel PS: Previous announcement indicated the start time 14:30 UTC, this message changes it to 15:00 UTC - 30min later due to a constraint in availability of one of the Kamailio developers. -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 3

stats.get_statistucs dialog: counter over/underrun?
by Benoit Panizzon 05 Dec '23

05 Dec '23

Hi List Kamailio 5.5 # kamcmd stats.get_statistics dialog: dialog:active_dialogs = 17 dialog:early_dialogs = 18446744073709551615 dialog:expired_dialogs = 0 dialog:failed_dialogs = 31198 dialog:processed_dialogs = 107519 Where could this early_dialog value come from? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

Setting up Kamailio as SIP Proxy
by Saul Ibarra 04 Dec '23

04 Dec '23

Hi, I am needing some help setting up kamailio as a sip proxy between a provider(trunk) and a test pbx The trunk requires username&password and i would like to add that information to the request within the Kamailio proxy, so that the PBX can authenticate directly by IP (without username&password) through the Kamailio proxy. As a programmer with a limited background in SIP (currently learning), I am keen on understanding the intricacies of this setup at the SIP level. Could you please direct me to resources or documentation that covers scenarios similar to mine? Any help or guidance you could provide would be greatly appreciated. Thanks

4 8

tsilo dependency on usrloc
by Alex Balashov 03 Dec '23

03 Dec '23

Hi, I wanted to revisit the topic of tsilo dependence on the location service. All three ts_append*() functions have the following quality: - ts_append(): "performing a contact lookup on the table specified by the domain parameter." - ts_append_by_contact(): "the contact lookup is performed" - ts_append_to(): "performing a contacts lookup on the table specified by the domain parameter" Why is this extensive coupling to usrloc necessary? This makes it impossible to use `tsilo` in case of providing a push-notification add-on that front-ends an upstream registrar, requiring a kind of local shadow registrar or mid-registrar. What would make more sense is a generic mechanism that allows one to "drip" new contacts into an existing transaction, whether suspended or active. Kamailio has a mechanism to add more branches to an existing transaction, but the scope of that mechanism is only from *inside* the vantage point of the transaction in question. The key parlour trick of `tsilo` is that it permits dripping new branches into a *different* transaction. ts_append_to() almost does the trick, providing a target index and label, but it just insists on doing a registrar lookup to source the contacts. What is really wanted and needed for the downstream PN gateway use-case is a means of extracting contacts from incoming registrations (or other sources, potentially) without storing them in any fashion locally, without using or even loading usrloc, and just throwing them over the fence into a different transaction. Is this somehow possible by means other than tsilo? Am I overlooking something? Cheers, -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800

2 3

Unable to use db_alias_lookup to call multiple extensions
by Merul Patel, PhD 01 Dec '23

01 Dec '23

Hi, Kamailio newby here. Having some trouble with using alias_db to forward an incoming call to two extensions. Thanks in advance for any help. I've tried using the Ubuntu Jammy ARM64 packages, as well as compiling the source for version 5.7.3. In both cases, I've added three extensions, and calls directly between them work fine with the vanilla kamailio.cfg. However, I then wanted to add an alias so that when called it would dial two extensions, but only the first extension is ever called. My kamailio.cfg only differs in a few places: $ diff kamailio.cfg kamailio.cfg.original 3,6d2 < #!define WITH_AUTH 1 < #!define WITH_DEBUG 1 < #!define WITH_ALIASDB 1 < # 268,270d263 < loadmodule "db_sqlite.so" < #!define DBURL "sqlite:///usr/local/kamailio-devel/etc/kamailio/kamailio.sqlite" < 367c360 < modparam("tm", "failure_reply_mode", 0) --- > modparam("tm", "failure_reply_mode", 3) 450d442 < modparam("alias_db", "append_branches", 1) I can see from the log that when dialling the desired alias (5000) an alias_db query is performed: Dec 01 20:00:23 merrivale /usr/local/kamailio-devel/sbin/kamailio[3264]: DEBUG: {1 2 INVITE 651794328853009-230332414159388(a)192.168.17.145} alias_db [alookup.c:169]: alias_db_query(): new URI [0] is [sip:6002@merrivale.localdomain] Dec 01 20:00:23 merrivale /usr/local/kamailio-devel/sbin/kamailio[3264]: DEBUG: {1 2 INVITE 651794328853009-230332414159388(a)192.168.17.145} alias_db [alookup.c:169]: alias_db_query(): new URI [1] is [sip:6001@merrivale.localdomain] But only the first result is called. I've changed the order of the aliases in the sqlite db and just the first result is called. What am I missing? Merul

1 0

How to use: kamcmd ul.db_users?
by Benoit Panizzon 01 Dec '23

01 Dec '23

Hi List I want to find a way to check how many users are regsitered. https://www.kamailio.org/docs/modules/devel/modules/usrloc.html#usrloc.r.db… But no matter how I try, I get a 500 error... # kamcmd ul.db_users location And yes, the table is called 'location'. I did try to find out how kamctl ul show --brief pulls that information, but did not succeed. Also that command takes way too long how that we have several thousand registered users. Or would I need to query this directly from the database? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 2

Info: RTC Devroom at FOSDEM 2024
by Daniel-Constantin Mierla 01 Dec '23

01 Dec '23

Hello, another edition of FOSDEM is approaching and it will include again a Real Time Communications devroom. If anyone wants to share their interesting applications or experiences in the field, consider to submit a presentation proposal. The CfP is available at: - https://lists.fosdem.org/pipermail/fosdem/2023q4/003518.html It does not have to be about Kamailio, all RTC topics are welcome, just think to be something useful for developers, as the event is targeting them. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services Kamailio Advanced Training -- asipto.com

1 0

No access to variables within timer route
by dries＠degendt.com 30 Nov '23

30 Nov '23

Hi, I have a timer which is called each 5 seconds: modparam("timer", "declare_timer", "REFRESH_CALLSTATE_TIMER=REFRESH_CALLSTATE_TIMER,5000,slow"); I'm enabling setting the variable "testvar" and enabling the timer when an INVITE is received: if (is_method("INVITE|ACK|UPDATE|CANCEL|BYE")) { $var(testvar) = "blablabla"; timer_enable("REFRESH_CALLSTATE_TIMER", "1"); ... route[REFRESH_CALLSTATE_TIMER] { xlog("L_INFO", "Testvariable: $var(test)\n"); } However, the variable is always 0: INFO: <script>: Testvariable: 0 I've also tried printing pseudovariables like $ci, $du but nothinh seems accessible. Is there a workaround for this? Best regards, Dries

3 6

kamailio t_on_failure tcp timeout
by Julien Chavanton 29 Nov '23

29 Nov '23

Hi, I would like to catch TCP timeouts when I use a socket that was not closed. In this example I am sending SIP MESSAGE ... t_on_reply("ON_REPLY_MESSAGE"); t_on_failure("FAILURE_MESSAGE"); if (!t_relay()) sl_reply_error();

1 2

Evapi Async - suspend transaction for a limited time
by Ilie Soltanici 29 Nov '23

29 Nov '23

Hello, I'm trying to use the evapi_async_relay function from the evapi module, however,I don't want the transaction to be suspended for more than 1 second. For instance, if there's no response from the external application within this time frame, I want the script to continue and remove that transaction from memory. One potential approach I am considering is to add suspended transactions to a hash table with a timestamp value. Then, using rtimer module, I could periodically parse this table every second and process the results, but I'm not sure how efficient is that. Maybe you know other alternative, more efficient solutions (from a performance point of view) that could achieve the same goal? Any insights or recommendations would be greatly appreciated. Thank you.

3 6

5.6.4 debian htable dbmode=1 not writing at shutdown
by Bernd Krueger-Knauber 29 Nov '23

29 Nov '23

Hi, I have still the problem that my htables are not written into a sqlite db when I shutdown kamailio. Manual writing via: kamcmd htable.store ... is working. As I can see in the logs with highest loglevel, the function destroy() is never called. ht_db_url.len is > 0 ht_db_init_con() should work, else nothing would work with the db. But I can not see the debug messages from ht_db_open_con() Any ideas? Best regards, Bernd

5 5

Incompatibility of the DMQ htable protocol with older Kamailio versions
by Denys Pozniak 29 Nov '23

29 Nov '23

Hello! I noticed that there are differences in the DMQ htable replication protocol for the old version of Kamailio 5.2 and the new 5.7. For example, the new version uses action 2 when updating values and action 4 to remove. The old Kamailio version uses the values 1 and 3 respectively. Well, as a result, the htable data is not shared between such nodes, plus there are errors in the syslog of the old version: ERROR: htable [ht_dmq.c:328]: ht_dmq_handle_msg(): failed to replay action It would probably be worth introducing some kind of DMQ htable protocol versioning to maintain compatibility? And is there any option to make them work together (I wouldn’t really want to change the action number in sip/sdp/json on the fly)? Kamialio 5.2 {"action":1,"htname":"shared","cname":"user","type":2,"strval":"uri","mode":1} {"action":3,"htname":"shared","cname":"user","mode":0} Kamailio 5.7 {"action":2,"htname":"shared","cname":"user","type":2,"strval":"uri","mode":1} {"action":4,"htname":"shared","cname":"user","mode":0} -- BR, Denys Pozniak

2 2

tps_storage_fill_contact(): no r-uri user
by Denys Pozniak 28 Nov '23

28 Nov '23

Hello! My topology is like this: PBX -> Kamailio Topos -> User When calling the user, PBX does not add the user part in the Contact URI, something like: Contact: <sip:10.10.10.10:5080;transport=udp> When the customer sends a reinvite, the topos turns off for this transaction and the sip partially breaks down with error: topos [tps_storage.c:319]: tps_storage_fill_contact(): no r-uri user topos [tps_storage.c:615]: tps_storage_record(): failed to store As far as I understand, the RFC allows the absence of the user part in the URI and this occurs quite often. I can provide the pcap file and debug log in a private message if this helps identify the essence of the problem. # kamailio -v version: kamailio 5.7.1 (x86_64/linux) 1cf389-dirty -- BR, Denys Pozniak

3 5

Kamailio ver 5.7.3 - source installation warnings
by Muhammad Danish Moosa 28 Nov '23

28 Nov '23

Hi, I am planning to upgrade Kamailio to version 5.7.3 to manage some memory leaks issues. I am installing from source and came across these warnings, just wanted to be sure if they are safe to be ignored. cr_func.c: In function ‘set_next_domain_on_rule’: cr_func.c:160:2: warning: missing braces around initializer [-Wmissing-braces] pv_value_t val = {0}; ^ cr_func.c:160:2: warning: (near initialization for ‘val.rs’) [-Wmissing-braces] cr_func.c: In function ‘actually_rewrite’: cr_func.c:348:2: warning: missing braces around initializer [-Wmissing-braces] pv_value_t val = {0}; ^ cr_func.c:348:2: warning: (near initialization for ‘val.rs’) [-Wmissing-braces] cr_func.c: In function ‘ki_cr_load_user_carrier_helper’: cr_func.c:782:2: warning: missing braces around initializer [-Wmissing-braces] pv_value_t val = {0}; ^ -- LD (gcc) [M p_usrloc.so] p_usrloc.so CC (gcc) [M evrexec.so] evrexec_mod.o evrexec_mod.c:64:1: warning: missing braces around initializer [-Wmissing-braces] static evrexec_info_t _evrexec_info = {0}; ^ evrexec_mod.c:64:1: warning: (near initialization for ‘_evrexec_info.data’) [-Wmissing-braces] LD (gcc) [M evrexec.so] evrexec.so CC (gcc) [M avp.so] avp.o LD (gcc) [M avp.so] avp.so CC (gcc) [M acc_diameter.so] diam_message.o CC (gcc) [M acc_diameter.so] acc_diameter_mod.o CC (gcc) [M acc_diameter.so] diam_avp.o CC (gcc) [M acc_diameter.so] diam_tcp.o LD (gcc) [M acc_diameter.so] acc_diameter.so CC (gcc) [M dmq.so] bind_dmq.o CC (gcc) [M dmq.so] message.o CC (gcc) [M dmq.so] dmq_funcs.o dmq_funcs.c: In function ‘ki_dmq_send_message’: dmq_funcs.c:304:3: warning: missing braces around initializer [-Wmissing-braces] dmq_peer_t new_peer = {0}; ^ dmq_funcs.c:304:3: warning: (near initialization for ‘new_peer.peer_id’) [-Wmissing-braces] dmq_funcs.c: In function ‘ki_dmq_bcast_message’: dmq_funcs.c:374:3: warning: missing braces around initializer [-Wmissing-braces] dmq_peer_t new_peer = {0}; ^ dmq_funcs.c:374:3: warning: (near initialization for ‘new_peer.peer_id’) [-Wmissing-braces] CC (gcc) [M dmq.so] notification_peer.o CC (gcc) [M dmq.so] dmq.o dmq.c:61:1: warning: missing braces around initializer [-Wmissing-braces] sip_uri_t dmq_server_uri = {0}; ^ dmq.c:61:1: warning: (near initialization for ‘dmq_server_uri.user’) [-Wmissing-braces] dmq.c:67:1: warning: missing braces around initializer [-Wmissing-braces] static sip_uri_t dmq_notification_uri = {0}; ^ dmq.c:67:1: warning: (near initialization for ‘dmq_notification_uri.user’) [-Wmissing-braces] Muhammad Danish Moosa " The core of mans' spirit comes from new experiences. "___ Christopher McCandless

2 2

Info: Issue and PR automatic management
by Daniel-Constantin Mierla 27 Nov '23

27 Nov '23

Hello, during the Kamailio Development Meeting that took place in Dusseldorf earlier this month, one topic was related to administrative tasks related to project development and management, how to simplify/automatize such tasks. To reduce the work load on volunteering contributors, GitHub Actions were already used for various tasks related to project development and management (e.g., automatic builds on commits and pull requests to detect compile errors or code formatting mistakes). In Dusseldorf another task was configured to be managed with GitHub Actions, respectively the check of open issues and pull requests to evaluate the interest of submitters, developers and community users to pursue them. If there is no activity on an issue (potential bug or feature request) or a pull request, after 6 weeks it is marked with the label `stale`. After two more weeks of no activity, the issue or the pull request is marked with the label `expired` and closed. Note that any comment postpones the expire timeline, being considered that there is interest in pursuing the issue or the pull request. Requests for features were already treated in this way: if nobody commits to implement it, it can be closed after one month, but it needed manual work and many were still kept open. Potential bug reports that become very old are hard to tackle if the source code changes or new major releases are out, they might even not be valid anymore. Anyhow, this automatic operations can be reverted if there is still interest in pursuing the specific issues or pull requests. A registered developer can remove labels and reopen a closed issue or pull request. The non-registered-developer contributors have to make a comment that includes the token `/notstale` to remove the label `stale` or includes the token `/notexpired` to reopen a closed item. This new kind of automatic task management might add a little inconvenience because one has to restate the interest from time to time for those items that could not be addressed. However, considering that Kamailio is an open source collaborative project, in order to be fair for those that volunteer to spend time and resources for development of Kamailio, also the users/submitters have to stay engaged, not just report and forget about. The process to automatize tasks related to Kamailio development and administration is work in progress. Everything can be adjusted based on feedback (e.g., time lines), feel free to suggest improvements or new solutions to make things easier for everyone within the project ecosystem. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services Kamailio Advanced Training -- asipto.com

1 0

How to remove record-route and via from a forwarded call?
by Benoit Panizzon 27 Nov '23

27 Nov '23

Hi List Two Kamailio Nodes situation. Node A: Routing Instance. Node B: Registrar Instance. An invite is sent from Node A to B. Customer registered on B is 'busy' as example. B initiates Call Forwarding by adding a Diversion Header and sending the Invite back to A with a new R-URI towards the CFB destination. The Invite sent from B to A still has Node B in it's Record-Route. So all subsequent SIP messages pass via B, which is not needed and cause issue with rtpengine running on B. I attempted to remove_record_route(); when sending the call back to A, but this causes: parse_headers(): bad header field [;lr;ftag=3910078620-883101371> It looks like only the beginning of the RR header is removed leaving back a competely broken line. What is the propper was to remove a node from RR and Via routing? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 4

WEBRTC-to-SIP & Vice Versa
by Vishal Pai 26 Nov '23

26 Nov '23

Hello All Good Day Here I am trying to achieve something like this WSS to UDP Ext registartion which works well using https://github.com/havfo/WEBRTC-to-SIP/tree/master/etc Note here i am forwarding the registartion to asterisk pbx server and define WSS of kamailio Now for calls - Webrtc - SIP calls works - SIP - Webrtc calls not working Here I am getting the request of the call on kamailio but kamailio send 404 not found to Asterisk PBX Webrtc - Webrtc calls not working Can anyone guide me on what I am doing wrong? Thanks Vishal P

3 3

refer-to to new INVITE
by Social Boh 26 Nov '23

26 Nov '23

Hello, I'd like to know if there is a way, from Kamailio side, take the refer-to header Kamailio receive in a REFER request and create a new INVITE whit this data; then bridge the call between the originating user and the new destination user. Thank you Regards -- --- I'm SoCIaL, MayBe

3 4

Re: RADIUS - Can't use extra attributes
by Duarte Rocha 24 Nov '23

24 Nov '23

Hello Daniel, Thanks for the reply. The extra dictionary is already included otherwise an error is thrown and Kamailio doesn't start. However, i realized my mistake now and you were right. I was checking for the extra attributes in a tcpdump and on radius server and i didn't had the dictionary configured on both of them. The extra attributes are in the packet but weren't being listed. One more question. Kamailio doesn't have a way to do a totally custom RADIUS access-request packet right? (Sorry if this opens another thread. I usually just hit reply on the mailing list and let Outlook create the e-mail, but it usually creates another thread and i'm not sure why). Thanks again. Cheers, Duarte

1 0

Re: RADIUS - Can't use extra attributes
by Duarte Rocha 24 Nov '23

24 Nov '23

Hello Daniel, Thanks for the reply. The extra dictionary is already included otherwise an error is thrown and Kamailio doesn't start. However, i realized my mistake now and you were right. I was checking for the extra attributes in a tcpdump and on radius server and i didn't had the dictionary configured on both of them. The extra attributes are in the packet but weren't being listed. One more question. Kamailio doesn't have a way to do a totally custom RADIUS access-request packet right? (Sorry if this opens another thread. I usually just hit reply on the mailing list and let Outlook create the e-mail, but it usually creates another thread and i'm not sure why). Thanks again. Cheers, Duarte

1 0

Max-Forwards header missing in OPTIONS keep-alive messages
by Christian Schnell 24 Nov '23

24 Nov '23

Hello, in RFC 3261 (sec. 8.1.1.6) it states about the Max-Forwards header field: > A UAC MUST insert a Max-Forwards header field into each request it originates with a value that SHOULD be 70. > > Source: https://datatracker.ietf.org/doc/html/rfc3261#section-8.1.1.6 When Kamailio sends its OPTIONS keep-alive requests (from the nathelper module I believe), Max-Forwards is missing: > OPTIONS sip:alice@example.com:61266 SIP/2.0 > Via: SIP/2.0/UDP aa.bb.cc.dd:5060;branch=z9hG4bK5124450 > From: sip:pinger@sip.example.com;tag=uloc-6550aa14-7456-2461-6390f173-5fdb4667 > To: sip:alice@example.com:61266 > Call-ID: aba25282-2ca72be1-9d1fd53(a)aa.bb.cc.dd > CSeq: 1 OPTIONS > Content-Length: 0 The user agent library I'm using (libre from baresip) rejects these requests with a "400 Bad Request" response, I looked at the sources and it denies these requests because of the missing Max-Forwards header. Of course this suffices for the keep-alive logic because all that's needed is any traffic in both directions to keep both (potential) NATs open. However you might agree that it does look a bit confusing at first, and the RFC is clear about that. So it's not a bug, but is this behavior intended? Thanks, also thanks for all the great work that has been put into Kamailio. Christian

3 3

error sending message to heplify server.
by masoud96＠mail.ru 24 Nov '23

24 Nov '23

Hello, I have an error when sending a message to the heplify server: Nov 23 15:09:59 sip1-life3 kamailio[1045006]: CRITICAL: {2 1395 INVITE ad25bc92-16a8-4be6-a29f-a4e4ee3a2c0c} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045006]: ERROR: {2 1395 INVITE ad25bc92-16a8-4be6-a29f-a4e4ee3a2c0c} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044995]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549fc5f0, len: 445, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044995]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044995]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154948b18, len: 1511, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044994]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044995]: ERROR: {2 28117 BYE 65297c88-0834-44ce-a4da-cfd7012c2b85} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154979898, len: 485, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044995]: CRITICAL: {2 28117 BYE 65297c88-0834-44ce-a4da-cfd7012c2b85} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044995]: ERROR: {2 28117 BYE 65297c88-0834-44ce-a4da-cfd7012c2b85} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549d9c50, len: 532, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044994]: CRITICAL: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549d9c80, len: 560, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044994]: CRITICAL: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549d9c40, len: 529, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044994]: CRITICAL: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044994]: ERROR: {1 1 INVITE yjaewdcbicjidajxj0td800z8ba3ta09(a)10.18.5.64} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044996]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f215494b6a8, len: 823, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044996]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044996]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045015]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549fc5a0, len: 507, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045015]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045015]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1044996]: ERROR: {2 16492 INVITE sOPq2dosBQcFpqitxVMlyLxFiuWNLZyk} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549fc158, len: 1037, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1044996]: CRITICAL: {2 16492 INVITE sOPq2dosBQcFpqitxVMlyLxFiuWNLZyk} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1044996]: ERROR: {2 16492 INVITE sOPq2dosBQcFpqitxVMlyLxFiuWNLZyk} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154978c18, len: 506, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045009]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045195]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154948e00, len: 567, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045195]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045195]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: {2 6972 INVITE 8f4b30bb-01fa-462d-ab66-8b30c0f7b78e} <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f2154948fe8, len: 488, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045009]: CRITICAL: {2 6972 INVITE 8f4b30bb-01fa-462d-ab66-8b30c0f7b78e} siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: {2 6972 INVITE 8f4b30bb-01fa-462d-ab66-8b30c0f7b78e} siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: <core> [core/udp_server.c:697]: udp_send(): sendto(sock, buf: 0x7f21549fc158, len: 542, 0, dst: (10.241.60.115:9060), tolen: 16) - err: Bad file descriptor (9) Nov 23 15:09:59 sip1-life3 kamailio[1045009]: CRITICAL: siptrace [../../core/forward.h:231]: msg_send_buffer(): udp_send failed Nov 23 15:09:59 sip1-life3 kamailio[1045009]: ERROR: siptrace [siptrace_hep.c:229]: trace_send_hep3_duplicate(): cannot send hep duplicate message version: kamailio 5.7.2 (x86_64/linux) 95629c flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 95629c compiled on 14:30:56 Nov 20 2023 with gcc 10.2.1

2 1

Hump presence mwi htable
by David VILLAUME 24 Nov '23

24 Nov '23

Hello, I'm running presence_mwi without database. I'm looking for a way to dump the presence htable content, is there any way to perform that ? Regards [https://storage.letsignit.com/6009878cd5039f000742d6a1/generated/effects_bf…] David VILLAUME Ingénieur Voix Tel : +33 156377321 david.villaume(a)sewan.fr 2 cité Paradis - 75010 PARIS www.sewan.fr<https://cloud.letsignit.com/collect/bc/649d2ea2264803323682b26f?p=qPDZoXyim…> [https://storage.letsignit.com/6009878cd5039f000742d6a1/generated/effects_78…]<https://cloud.letsignit.com/collect/bc/649d2ea2264803323682b26f?p=qPDZoXyim…> [https://storage.letsignit.com/6009878cd5039f000742d6a1/generated/effects_13…]<https://cloud.letsignit.com/collect/bc/649d2ea2264803323682b26f?p=qPDZoXyim…> [https://storage.letsignit.com/6009878cd5039f000742d6a1/generated/effects_24…]<https://cloud.letsignit.com/collect/bc/649d2ea2264803323682b26f?p=qPDZoXyim…>

2 1

RADIUS - Can't use extra attributes
by duarterocha91＠gmail.com 24 Nov '23

24 Nov '23

Hello all, I'm currently implementing a Kamailio with RADIUS. I want to send an Access-Request to my RADIUS server and in order to do that i'm using misc_radius module and radius_does_uri_exist() function without any arguments : "if (radius_does_uri_exist()) {" For my module configuration I have the following configurations : "modparam("misc_radius", "radius_config", "/etc/radcli/radiusclient.conf") modparam("misc_radius", "uri_extra", "Sip-Method=$rm")" From what i understand, with this config my access-request should contain the default attributes and Sip-Method Attribute but that is not happening. Only defaults attributes are included. I've tried to run Kamailio with "-ddd" flag for better debug and i only get this error : "1(176) DEBUG: misc_radius [functions.c:615]: radius_does_uri_user_host_exist(): failure". Is there any other configuration that i must do? Thanks for the help. Cheers, Duarte

2 1

Online devel meeting on matrix - 14:30 UTC, Dec 5, 2023
by Daniel-Constantin Mierla 24 Nov '23

24 Nov '23

Hello, we should consider an online devel meeting sometime soon to summarize what was done at (and still needs to be done after) devel meeting in Dusseldorf and plan a bit the targets for next major release (5.8 or 6.0)? If considered useful, I propose Dec 5 at 14:30UTC (15:30 Berlin/Paris/Madrid/Rome), but we can also look for other dates as well. Topics to be discussed can be added at: - https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings… Pull requests can be made by users without git access. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 1

sips to sip
by David Villasmil 24 Nov '23

24 Nov '23

Hello guys, I have this setup where one side is TLS and the other UDP. Normally this works fine, but we have this provider sending sips as the schema everywhere (from, to, rr, contacts), kamailio sends the same sips to the upstream usp freeswitch. My problem is when FS sends back a 200OK and kamailio forwards it back to the provider, the provider sends an ACK and kamailio can't match it with the dialog and doesn't know where to forward it. i think this is happening because FS when is sees SIPS is setting the contact port as 5081 instead of the usual 5080... Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

5 8

Dialog + DMQ: dlg_ontimeout() triggered on wrong node!
by Benoît Panizzon 23 Nov '23

23 Nov '23

Hello World! Kamailio 5.5 in use. I wonder, how I could prevent this issue. modparam("dialog", "send_bye", 1) modparam("dialog", "default_timeout", 21600) in the corresponding route: $dlg_ctx(timeout_route) = "DIALOG_TIMEOUT"; dlg_manage(); Dialog starts on Node01 and it's variables, status and timer are DMQ synced to Node02 As both nodes have the same information, I guess both arm the timeout trigger and sometimes the wrong node is more trigger friendly. If dlg_ontimeout() is triggered on Node02 then: * No Bye is send, as Node02 is not handling that Dialog. * Dialog is removed from Memory on Node02 and state synced back to Node01 * Dialog is removed from Memory on Node01 too, but NOT from database [*1] * Dialog CDR is never commited on Node01 * Call is never sent to timeout_route And subsequent in dialog messages on Node01 result in: dlg_onroute(): unable to find dialog Did I misconfigure something? Is there a way to make sure the timer is NOT triggered on the node not handling the dialogue? Shall I try by setting the default_timeout and then use a timeout_avp to set that timeout slightly lower AFTER the dialog has started? Or would this be synced to the other node too? I found out, session timer changes are not synced after an initial timer was synced, so you can not extend the session timer after setting a initial timeout. So maybe this is also true for dialog timeout? [*1] this also explains why upon restarting kamailio, the dialog suddenly is back and after timing out again, a CDR is then written with a way too long duration. -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 3

set_body() adding or replacing existing body?
by Benoit Panizzon 23 Nov '23

23 Nov '23

Hi I'm trying to change the lifetime timer on a KDMQ dialog message before handing it with dmq_handle_message(); if(has_body("application/json") && $fU == 'dialog') { if (jansson_get("lifetime", $rb, "$var(lifetime)")) { xlog("L_INFO", "$cfg(route): DIALOG JSON action: $var(action) state: $var(state) lifetime: $var(lifetime)\n"); $var(new_lifetime) = $var(lifetime) + 60; $var(newrb) = $rb; jansson_set("integer", "lifetime", $var(new_lifetime), "$var(newrb)"); xlog("L_INFO", "$cfg(route): DIALOG JSON NEW: $var(newrb)\n"); set_body("$var(newrb)","application/json"); msg_apply_changes(); } } dmq_handle_message(); exit; The JSON string looks good after that manipulation, it contains the updated lifetime. But dmq_handle_message() does not seem to get the body anymore. So I wonder what set_body() exactly does. Is it replacing the body or appending to it? Is there a way to crank up debug output in the dialog and/or dmq module? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 1

Kamailio v5.6.5 Released
by Daniel-Constantin Mierla 23 Nov '23

23 Nov '23

Hello, Kamailio SIP Server v5.6.5 stable release is out. This is a maintenance release of the latest stable branch, 5.6, that includes fixes since the release of v5.6.4. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.6.x. Deployments running previous v5.6.x versions are strongly recommended to be upgraded to v5.6.5. Note that 5.6 is the second last stable branch, still officially maintained by Kamailio development team. The latest stable branch is 5.7, with v5.7.3 being release out of it. For more details about version 5.6.5 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2023/11/kamailio-v5-6-5-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services Kamailio Advanced Training -- asipto.com

1 0

Releasing v5.6.5
by Daniel-Constantin Mierla 23 Nov '23

23 Nov '23

Hello, I am considering to release Kamailio v5.6.5 (out of branch 5.6) later this week (likely on Thursday or Friday, Nov 23/24, 2023). If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services Kamailio Advanced Training -- asipto.com

1 1

Crash on core/mem/q_malloc.c
by Igor Potjevlesch 22 Nov '23

22 Nov '23

Hello! I'm facing an issue 2/3 times a day with the following errors in the logs: Nov 22 00:09:02 /usr/local/sbin/kamailio[3720]: CRITICAL: <core> [core/mem/q_malloc.c:150]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten(c0c0c000, abcdefed)[0x7f9600b754f8:0x7f9600b75530]! Memory allocator was called from core: core/re.c:430. Fragment marked by core: db_res.c:139. Exec from core/mem/q_malloc.c:391. Nov 22 00:09:02 /usr/local/sbin/kamailio[3720]: CRITICAL: <core> [core/mem/q_malloc.c:155]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten [0x7f9600b75460:0x7f9600b75498] - fragment marked by tm: t_fwd.c:230 Nov 22 00:09:02 abrt-hook-ccpp: Process 3720 (kamailio) of user 0 killed by SIGABRT - ignoring (repeated crash) Do you have any idea where it could come from? I'm running Kamailio 5.6.4. Regards, Igor. -- Cet e-mail a été vérifié par le logiciel antivirus d'Avast. www.avast.com

2 2

Obsoleting unmaintained modules
by Daniel-Constantin Mierla 21 Nov '23

21 Nov '23

Hello, during the Kamailio Developers Meeting 2023 in Dusseldorf that took place last week, it was proposed to obsolete modules that seem to be unmaintained and no activity about them was noticed during the past years. It is quite some overhead in packaging them and trying to keep them compiling when they have external dependencies, therefore such step should spare some resources in the future. The list (see below) was built based on the options of those present at the meeting, now we want to discuss it on the larger communities of developers and users. If you are using any of these modules or you think any of them worth keeping, reply with the names of the modules that you want to be kept. The proposed action is to relocate the obsoleted modules to a new git repository "kamailio-obsolete" to still keep some visibility to them and in the eventually of future interest on any of them, it can be reintroduced in the main repository. Next is the initial list of modules proposed to be considered obsolete: - app_java - app_lua_sr - app_mono - app_python - app_sqlang - auth_identity - call_control - db2_ldap - db2_ops - db_cassandra - db_perldvdb - dnssec - domainpolicy - h350 - mediaproxy - osp - peering - print - print_lib - pua_xmpp - ratelimit - uid_auth_db - uid_avp_db - uid_domain - uid_gflags - uid_uri_db - uri_db - xmpp - xprint Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services Kamailio Advanced Training -- asipto.com

3 5

UAC DNS SRV timeout
by Sergiu Pojoga 17 Nov '23

17 Nov '23

Hi, Setup: kamailio acting as a UAC needs to register with a server whose outbound proxy is DNS SRV based only, there's no A record on the proxy's FQDN. The provider advertises two SRV records. ;; ANSWER SECTION: _sips._tcp.sip.provider.com. 10 IN SRV 10 50 5061 sip11-sip.provider.com. _sips._tcp.sip.provider.com. 10 IN SRV 15 50 5061 sip10-sip.provider.com. Everything was working fine, until the provider changed the SRV priority, putting a lower priority on the host that is actually down at the moment. In this case, sip11-sip.provider.com is DOWN and sip10-sip.provider.com is UP. Now, what's happening is Kamailio tries to REGISTER with the lower priority host, gets no reply back (TCP connection doesn't get established). It then takes 30 seconds for Kamailio to try the host with the higher priority, registering successfully. And so it goes for every re-register: failure => 30 seconds => register OK. The same happens for INVITES to the downstream: INVITE => timeout => 30 seconds => INVITE (other host 200 OK). I've tried to play with TCP and DNS params, but so far no luck: no matter what I did - it took the same 30 seconds for Kamailio to detect failure and retry the secondary host. Any suggestions will be highly appreciated. Kamailio 5.6.4 (x86_64/linux) 239d0a tcp_connection_lifetime=3604 tcp_max_connections=60 tcp_connect_timeout=10 tcp_keepalive = yes tcp_crlf_ping=yes tcp_keepcnt=3 tcp_keepidle=30 tcp_keepintvl=30 tcp_reuse_port=1 tcp_accept_no_cl=yes tcp_rd_buf_size=16384 use_dns_cache = on use_dns_failover = on dns_srv_loadbalancing = on dns_try_naptr = on dns_try_ipv6=no dns_try_naptr=no dns_use_search_list=no dns_retr_time=1 dns_retr_no=3 Thanks --Sergiu

1 0

auth_check : sip user / authentication user mismatch
by Jawaid Bazyar 17 Nov '23

17 Nov '23

Hi, I am trying to register an endpoint as follows: REGISTER sip:siptest.booger.net SIP/2.0 Via: SIP/2.0/UDP X.X.X.X.76:31114;branch=z9hG4bK223420485;rport From: sip:1720XXXXXXX@siptest.booger.net;tag=962873337 To: sip:1720XXXXXXX@siptest.booger.net Call-ID: 2053687751-32761-1(a)EH.BJI.BAE.HG CSeq: 2067 REGISTER Contact: sip:1720XXXXXXX@X.X.X.X:31114;reg-id=2;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000B82A1C58B>" Authorization: Digest username="654fe87c-67ff-42dd-8d5e-79786a99713c", realm="siptest.booger.net", nonce="ZVaJtmVWiIrsuWc5hkzM3MUUUs8MgRFR", uri=sip:siptest.booger.net, response="119a3b6426cdcfa037bf1825b69139a5", algorithm=MD5 X-Grandstream-PBX: true Max-Forwards: 70 User-Agent: Grandstream GXP2170 1.0.11.64 Supported: path Expires: 120 MAC: 00:0b:82:a1:c5:8b Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE Content-Length: 0 Note that the Authorization username differs from the To-From username. This is intentional, as I am testing use of randomly generated credential . This worked with this endpoint directly against Asterisk, for instance. However, registering against Kamailio now, I am getting: Nov 16 21:24:26 vs-rs01 /usr/sbin/kamailio[584855]: DEBUG: {1 2067 REGISTER 2053687751-32761-1(a)EH.BJI.BAE.HG} auth_db [authorize.c:503]: auth_check(): authentication username mismatch with from/to username Even though I have this set in the config: if (!auth_check("$fd", "subscriber", 0)) { // default 1, change to 0 to skip check 0 is supposed to mean no user checks performed. I am doing this because I want to use the complex credentials for authentication, but want the endpoint to tell me the phone number in an INVITE to/from, instead of putting in the extremely long credential. Is there a way to get Kamailio to accept different SIP User ID and Authentication ID fields? Thanks, Jawaid

2 2

pv cache limit is going to be exceeded
by Ali Taher 17 Nov '23

17 Nov '23

Hello all, I'm using the following Lua script to fetch data from Redis, which is in form of list: function split(str, delimiter) for token in string.gmatch(str, "[^" .. delimiter .. "]+") do return token end end function contains(mainString, subString) return string.find(mainString, subString, 1, true) ~= nil end function longest_match_acode() local currentSeconds = os.time() local milliseconds = os.clock() * 1000 local ddate = os.date("%Y-%m-%d %H:%M:%S", currentSeconds) .. string.format(".%03d", milliseconds) KSR.xlog.xinfo("starting date:" ..ddate) local size = 0 local result local acode = "29192" local inputbcode = "4474173" local delimiter = ":" while size == 0 do local currentSeconds = os.time() acode = string.sub(acode, 1, string.len(acode) - 1) KSR.ndb_redis.redis_cmd("srvN", "LRANGE price:" .. acode .." 0 -1", "r") size = tonumber(KSR.pv.get("$redis(r=>size)")) end local left = 0 local right = size - 1 while left <= right do local currentSeconds = os.time() local milliseconds = os.clock() * 1000 local ddate = os.date("%Y-%m-%d %H:%M:%S", currentSeconds) .. string.format(".%03d", milliseconds) resultRight = tostring(KSR.pv.get("$redis(r=>value[" .. right .. "])")) resultLeft = tostring(KSR.pv.get("$redis(r=>value[" .. left .. "])")) local bcodeLeft = split(resultLeft, delimiter) local bcodeRight = split(resultRight, delimiter) if contains(inputbcode, bcodeRight) then KSR.xlog.xinfo("Input bcode contains bcode value from Redis: " .. resultRight .. " at index: " .. right .. " with date: " .. ddate) end if contains(inputbcode, bcodeLeft) then KSR.xlog.xinfo("Input bcode contains bcode value from Redis: " .. resultLeft .. " at index: " .. left .. " with date: " .. ddate) end left = left + 1 right = right - 1 end local currentSeconds = os.time() local milliseconds = os.clock() * 1000 local ddate = os.date("%Y-%m-%d %H:%M:%S", currentSeconds) .. string.format(".%03d", milliseconds) KSR.xlog.xinfo("ending date:" ..ddate) end function ksr_request_route() if KSR.is_INVITE() then longest_match_acode() KSR.sl.send_reply("404", "Not found"); end end I'm getting the following warning in the log : WARNING: LUA {INVITE}: <core> [core/pvapi.c:340]: pv_cache_add(): pv cache limit is going to be exceeded - pkg memory may get filled with pv declarations I think the issue is in the following lines: resultRight = tostring(KSR.pv.get("$redis(r=>value[" .. right .. "])")) resultLeft = tostring(KSR.pv.get("$redis(r=>value[" .. left .. "])")) the list coming from Redis has around 30k items, which I'm iterating through using value[x] which is exhausting the pv declaration as per my understanding. How to overcome this issue? Is it possible to save the list as an array variable and then iterate through that array? Regards,

2 3

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