I am trying to get imsdroid register to pcscf . But failing with 504 server timeout .
PCSCF IP : 192.168.1.28
imsdroid IP : 192.168.1.212
Please help to figure out the reaso for register failure .
I have attached pcap file and pcscf log file
Hi all,
I'm using a central file to define my kamailio cfg configuration.
First question:
In my main kamailio.cfg, I use:
include_file "kamailio-config.cfg"
which contains:
#!substdef "!MY_DOMAIN!kamailio.example.com!g"
I would like to use the same in tls.cfg which is defined this way:
modparam("tls", "config", "/etc/kamailio/tls.cfg")
but I get:
sr_cfg_parse(): tls.cfg:17:1: Unsupported option 'include_file'
Would you advise some way to achieve my goal: ie, I would like only
one file to edit my configuration options which would have an effect on
both kamailio.cfg and tls.cfg
Second question:
Can someone confirm that #!substdef will also not have any effect
when used in tls.cfg
Thanks
Aymeric
--
Antisip - http://www.antisip.com
Hello all,
It is that time of year to start getting the headcount for the FOSDEM voip
dinner on the Saturday of FOSDEM.
Usually Daniel would get the headcount for me and I just make the booking.
However Daniel can't make it this year so I'll also be taking the headcount
If you want to come put your name up one the doodle I've set up for this
https://doodle.com/meeting/participate/id/boAjDENe
Hope to see you there!
Torrey
Hi
This may be a stupid question but after a couple of hours and some headache I
can't see where the problem is.
I'm trying to use SRV records to relay to different servers as I've done many
many times before. But in this case I'm getting a 478 from kamailio and I see
that it's not trying to resolve SRV.
From the log:
[core/dns_cache.c:527]: _dns_hash_find(): (fs.mydomain.dev(16), 1), h=632
[core/resolve.c:784]: get_record(): lookup(fs.mydomain.dev, 1) failed
[core/dns_cache.c:761]: dns_cache_mk_bad_entry(): (fs.mydomain.dev, 1, 60, 1)
[core/dns_cache.c:701]: dns_cache_add(): adding fs.mydomain.dev(16) 1
(flags=1) at 632
[core/dns_cache.c:2807]: dns_a_resolve(): (fs.mydomain.dev, 0) returning -7
[core/dns_cache.c:3176]: dns_srv_sip_resolve(): (fs.mydomain.dev, 0, 0), ip,
ret=-7
uri2dst2(): failed to resolve "fs.mydomain.dev" :unresolvable A or AAAA
request (-7)
When doing tcpdump port 53 I see A record query but no SRV
SRV records of course exist although they are not being checked.
dns params in kamailio:
dns_try_ipv6=no
dns_retr_time=1
dns_retr_no=1
dns_use_search_list=no
use_dns_cache=on
use_dns_failover=on
dns_srv_lb=on
dns_try_naptr=no
dns_sctp_pref=1
dns_tcp_pref=1
dns_tls_pref=1
dns_udp_pref=1
Same exact config in another server is working. There's something I'm missing
and can't see.
Any hints?
cheers,
Jon
--
PekePBX, the multitenant PBX solution
https://pekepbx.com
Hello.
I have some rant with network security dept. Is there some standard, RFC,
what port range should be used for RTP traffic, how RTP ports are selected
during SIP call negotiation?
Thanks.
Hello!
I have a quick question about the internal DNS resolver and cache embedded
in Kamailio.
Is the ability to add an entry with dns.add_a bypass the "real" DNS lookup?
So, let's say that sip.example.com is publicly resolve alternatively with
1.2.3.4 & 5.6.7.8.9, if I do a dns.add_a to add my own sip.example.com with,
alternatively, 127.0.0.1 and 127.0.0.2, will it work?
Thanks for your highlight!
Regards,
Igor.
--
Cet e-mail a été vérifié par le logiciel antivirus d'Avast.
www.avast.com
Hey!
I'm hunting down an issue with xavp_params_explode, maybe somebody has
already come adross it and could confirm it exists and maybe know a
solution?
xavp_params_explode("a=foo;c=hello,world;e=baar", "x");
$xavp(x=>a) is 'foo'
but x=>c and x=>e are null
Am I right to assume the issue being caused by the comma? Is there a
way to allow a comma?
--
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
______________________________________________________
Hello,
Just need a bit of clarification on the usrloc parameter "timer_interval". Let's say this is configured with a value of 60 seconds; every 60 seconds, will this delete all expired contacts in the location table between runs -- as in between runs it will queue up a list of expired contacts, remove them all after the 60 seconds has elapsed, then execute the event route "event_route[usrloc:contact-expired]"?
Or does the event route execute as soon as the contact expires, independent from "timer_interval" timer?
Thank you.
Good evening everyone,
I'm trying to configure my Kamailio to use another DB in case the one it commonly uses fails.
Does Kamailio has any built in function to do this? Do I have to do it with an ha-proxy?
Thank you in advance for your help
Samuel Moya Tinoco
Departamento de Sistemas y Redes
Móvil: (+34) 606985997
smoya(a)vivelibre.es<mailto:smoya@vivelibre.es>
[cid:image001.png@01DA431B.CC9B03A0]
Soluciones inteligentes
para la autonomía personal
After using the uac module to initiate registration to the remote end, is there a method to call back to notify the registration result? I want to get the registration result, such as 200 or 403
good catch. thanks
for the record
ECC
[root@sbc live]# openssl x509 -text -noout -in /etc/letsencrypt/live/<my
domain>/fullchain.pem |grep -i "Public Key Algorithm"
Public Key Algorithm: id-ecPublicKey
certbot certonly --key-type rsa --cert-name <my domain> --manual
--preferred-challenges dns
RSA
[root@sbc live]# openssl x509 -text -noout -in /etc/letsencrypt/live/<my
domain>/fullchain.pem |grep -i "Public Key Algorithm"
Public Key Algorithm: rsaEncryption
but there was another problem
modparam("tls", "cipher_list", "RSA") from
https://kamailio.org/docs/modules/5.7.x/modules/tls.html#tls.p.cipher_list
does nothing
0(2294) INFO: tls [tls_domain.c:390]: ksr_tls_fill_missing():
TLSs<default>: cipher_list='(null)'
valid option is in tls.cfg
cipher_list = RSA
0(2328) INFO: tls [tls_domain.c:390]: ksr_tls_fill_missing():
TLSs<default>: cipher_list='RSA'
ServerHello
Version 3.3
session_id[0]=
cipherSuite TLS_RSA_WITH_AES_256_GCM_SHA384
Marek Cervenka
Dne 2024-01-10 v 13:06 Lukas Tribus napsal(a):
>
>
> On Wednesday 10 January 2024, marek via sr-users
> <sr-users(a)lists.kamailio.org> wrote:
>
> hi,
>
> i'm trying force cipher list through options like
>
> modparam("tls", "cipher_list", "TLS_RSA_WITH_AES_256_CBC_SHA256")
>
> modparam("tls", "cipher_list", "RSA")
>
>
> You are trying a RSA cipher.
>
>
> ...
>
>
> but
>
> ssldump -i enp2s0 port 5061 shows every time
>
> ServerHello
> Version 3.3
>
>
> In TLS 1.2
>
>
>
> session_id[0]=
> cipherSuite TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
>
>
> But the negotiated cipher suggest that you have an ECC certificate.
>
> In TLSv1.2 and older, ciphers available are dependent on the
> certificate type (RSA vs ECC).
>
> In TLSv1.3 its all different again and the certificate doesn't matter
> for cipher negotiation.
>
> Get a RSA (2048bit) certificate instead of a ECC one from Let's
> Encrypt, then you should be able to use those ciphers.
>
>
>
> Lukas
Hi all,
My Kamailio server has been throwing a lot of errors during the manipulation and forwarding of registrations to my Asterisk server (192.168.96.97) using uac_req_send(); and t_relay()
[core/tcp_main.c:1402]: tcp_do_connect(): connect 192.168.96.97:5060: (99) Cannot assign requested address
[core/tcp_main.c:1399]: tcp_do_connect(): connect 192.168.96.97:5060 failed Cannot assign requested address
When looking deeper into the code it appears that the errors are thrown when "tcp_async" is enabled. I've enabled this option a few weeks ago to make sure clients can REGISTER quickly. The parameter "tcp_reuse_port" is also set to yes.
I'm suspecting that on busy moments, the destination can't be reached because no TCP connections are available. Is there any of the following parameters that I can adjust to prevent this issue?
tcp_children = 25
disable_tcp = no
tcp_max_connections = 63536
tcp_connection_lifetime = 3605
tcp_accept_aliases = no
tcp_async = yes
tcp_connect_timeout = 10
tcp_conn_wq_max = 65536
tcp_crlf_ping = yes
tcp_delayed_ack = yes
tcp_fd_cache = yes
tcp_keepalive = yes
tcp_keepcnt = 3
tcp_keepidle = 30
tcp_keepintvl = 10
tcp_linger2 = 30
tcp_rd_buf_size = 80000
tcp_send_timeout = 10
tcp_wq_blk_size = 2100
tcp_wq_max = 10485760
tcp_reuse_port=yes
/* tcp_connection_match=1 */
open_files_limit=63536
A quick tcpdump doesn't show outgoing packet during the error events.
Best regards,
Dries
hi,
i'm trying force cipher list through options like
modparam("tls", "cipher_list", "TLS_RSA_WITH_AES_256_CBC_SHA256")
modparam("tls", "cipher_list", "RSA")
...
but
ssldump -i enp2s0 port 5061 shows every time
ServerHello
Version 3.3
session_id[0]=
cipherSuite TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
i tried lower crypto policy to LEGACY. nothing changed
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/ht…
certificates are from Lets Encrypt if that does matter
OS Rocky9(RHEL9), kamailio 5.7.3 from official repo
any ideas/tips?
thanks
Marek
Hello,
Any idea about the crash below? I found a ticket regarding to this, I made some comments and backtraces there also:
https://github.com/kamailio/kamailio/issues/3635
Now this crash is very frequently, 3-4 times every day. There is a timer mechnism, where kamailio refreshes registrations towards asterisk automically to ensure continuous availability for mobile users.
The crash exists 3-5 secs after this refresh process, but not always. Sometimes this process runs fine only CRITICAL logs appears (mentioned below) after it, but sometimes kamailio crashes during writing these CRITICAL logs.
Peter
From: Dr. Barabás Péter via sr-users <sr-users(a)lists.kamailio.org>
Date: Wednesday, 2023. November 15. 17:03
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Cc: Dr. Barabás Péter <dr.peter.barabas(a)gmail.com>
Subject: [SR-Users] Re: uac_req_send + evroute + crash
Hello Daniel,
I’m using kamailio 5.7.2 currently and this misterious crash occurs again. Now core files are generated also, here is the trace:
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x00007fae9a2d0859 in __GI_abort () at abort.c:79
#2 0x00005614ad79afd8 in qm_debug_check_frag (qm=0x7fae78e77000, f=0x7fae79805028, file=0x7fae77c8c134 "uac: uac_send.c", line=860, efile=0x5614ad936f99 "core/mem/q_malloc.c", eline=511) at core/mem/q_malloc.c:129
#3 0x00005614ad79f7c1 in qm_free (qmp=0x7fae78e77000, p=0x7fae79805060, file=0x7fae77c8c134 "uac: uac_send.c", func=0x7fae77c8cf10 <__func__.15157> "uac_send_tm_callback", line=860, mname=0x7fae77c8c014 "uac") at core/mem/q_malloc.c:511
#4 0x00005614ad7ab410 in qm_shm_free (qmp=0x7fae78e77000, p=0x7fae79805060, file=0x7fae77c8c134 "uac: uac_send.c", func=0x7fae77c8cf10 <__func__.15157> "uac_send_tm_callback", line=860, mname=0x7fae77c8c014 "uac") at core/mem/q_malloc.c:1350
#5 0x00007fae77c3686b in uac_send_tm_callback (t=0x7fae797dcf40, type=131072, ps=0x7fff8bd990d0) at uac_send.c:860
#6 0x00007fae783abc27 in run_trans_callbacks_internal (cb_lst=0x7fae797dcfe8, type=131072, trans=0x7fae797dcf40, params=0x7fff8bd990d0) at t_hooks.c:241
#7 0x00007fae783abd1e in run_trans_callbacks (type=131072, trans=0x7fae797dcf40, req=0x0, rpl=0x0, code=0) at t_hooks.c:261
#8 0x00007fae782bd8cb in free_cell_helper (dead_cell=0x7fae797dcf40, silent=0, fname=0x7fae783e9f62 "timer.c", fline=653) at h_table.c:165
#9 0x00007fae7837649c in wait_handler (ti=724701450, wait_tl=0x7fae797dcff8, data=0x7fae797dcf40) at timer.c:653
#10 0x00005614ad50be68 in timer_list_expire (t=724701450, h=0x7fae78ef5d18, slow_l=0x7fae78ef95e0, slow_mark=33641) at core/timer.c:857
#11 0x00005614ad50c3a7 in timer_handler () at core/timer.c:922
#12 0x00005614ad50c8d5 in timer_main () at core/timer.c:961
#13 0x00005614ad45fbf3 in main_loop () at main.c:1833
#14 0x00005614ad46ae93 in main (argc=14, argv=0x7fff8bd99b48) at main.c:3086
I think it occurs only if $uac_req(evroute) is set to 1 and I define the event_route[uac:reply] route.
My uac_reply route is easy:
if ($uac_req(evcode)==200) {
xlog("L_INFO", "Registration for user $fU has been refreshed successfully.");
$sht(vtp=>asterisk_restarted) = $null;
route(SAVE_REG);
}
else {
xlog("L_INFO", "Registration failed: $uac_req(evcode)");
}
the SAVE_REG route is the following:
route[SAVE_REG] {
xlog("L_INFO", "Saving pbx registration...:$fU");
$var(maxExpiry) = MAX_PBX_REG_EXPIRY;
route(GET_CLIENT_ID);
sql_pvquery("ca", "select count(*) from pbxusers where user = '$fU'", "$var(pbxusersCnt)");
if ($var(pbxusersCnt)>0) {
if ($var(clientId) == 0) {
sql_query("ca", "update pbxusers set expiry = TIMESTAMPADD(SECOND, $var(maxExpiry), SYSDATE()), online=1 where user = '$fU'");
}
else {
sql_query("ca", "update pbxusers set client_id = '$var(clientId)', expiry = TIMESTAMPADD(SECOND, $var(maxExpiry), SYSDATE()), online=1 where user = '$fU'");
}
}
else {
sql_query("ca", "insert into pbxusers (user, expiry, client_id, online) values ('$fU', TIMESTAMPADD(SECOND, $var(maxExpiry), SYSDATE()), '$var(clientId)', 0)");
}
}
And GET_CLIENT_ID route is:
route[GET_CLIENT_ID] {
$var(clientId) = 0;
if (is_present_hf("X-AT-ClientId")) {
$var(clientId) = $hdr(X-AT-ClientId);
}
}
Any idea, is it a bug or I do something wrong in config files?
Peter
From: Dr. Barabás Péter via sr-users <sr-users(a)lists.kamailio.org>
Date: Sunday, 2023. October 8. 18:49
To: miconda(a)gmail.com <miconda(a)gmail.com>, Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Cc: Dr. Barabás Péter <dr.peter.barabas(a)gmail.com>
Subject: [SR-Users] Re: uac_req_send + evroute + crash
Hello Daniel,
I do not see any “failed to send request with authentication”.
The next CRITICAL log appears after calling uac_req_send():
CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f114995ada8), called from uac: uac_send.c: uac_send_tm_callback(860), first free uac: uac_send.c: uac_resend_tm_callback(732) - ignoring
Now we use kamailio 5.7.2 and no crash has come, but the critical logs above exist.
I saw a ticket in github: https://github.com/kamailio/kamailio/issues/3522, may the crash be similar or the same to that?
I will make a try next week with downgrading to 5.6.2 and try to reproduce the crash.
Peter
From: Daniel-Constantin Mierla <miconda(a)gmail.com>
Date: Friday, 2023. October 6. 13:55
To: Dr. Barabás Péter <dr.peter.barabas(a)gmail.com>, Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: Re: [SR-Users] uac_req_send + evroute + crash
Hello,
do you also get error log messages that include "failed to send request with authentication"?
Which CRITICAL log appears when you call uac_req_send()? You pasted a couple of them in the initial email?
Cheers,
Daniel
On 05.10.23 17:32, Dr. Barabás Péter wrote:
Hello,
I used kamailio version 5.6.2. I refreshed to 5.7.2 today.
As I remember it was in kamailio long time ago therefore I could skip evroute route.
But this CRITICAL log appears always when I call uac_req_send().
I call it with settings:
$uac_req(auser) = $var(username);
$uac_req(apasswd) = $var(password);
Where username and password are retrived from web service before call.
In event_route I got first 401 after 200.
Peter
From: Daniel-Constantin Mierla <miconda(a)gmail.com><mailto:miconda@gmail.com>
Date: Thursday, 2023. October 5. 17:25
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org><mailto:sr-users@lists.kamailio.org>
Cc: Dr. Barabás Péter <dr.peter.barabas(a)gmail.com><mailto:dr.peter.barabas@gmail.com>
Subject: Re: [SR-Users] uac_req_send + evroute + crash
Hello,
On 05.10.23 16:34, Dr. Barabás Péter via sr-users wrote:
Hi All,
I use kamailio In front of Asterisk and kamailio needs to refresh registrations periodically towards Asterisk to ensure the availability of users from Asterisk side.
I use uac module and call uac_req_send() for sending REGISTER requests.
I set $uac_req(evroute)=1
The event_route[uac:reply] is called fine, but in kamailio logs I see the next lines:
CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f114995ada8), called from uac: uac_send.c: uac_send_tm_callback(860), first free uac: uac_send.c: uac_resend_tm_callback(732) - ignoring
After some time, kamailio has crashed.
CRITICAL: <core> [core/mem/q_malloc.c:519]: qm_free(): BUG: freeing already freed pointer (0x7f114995ada8), called from uac: uac_send.c: uac_send_tm_callback(860), first free uac: uac_send.c: uac_resend_tm_callback(732) – ignoring
CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 34
ALERT: <core> [main.c:774]: handle_sigs(): child process 1407950 exited by a signal 6
what version of Kamailio are you using? Is Asterisk challenging for authentication?
Does it happen every time or seldom?
Cheers,
Daniel
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training - Online - Nov 14-16, 2023 -- asipto.com
--
Daniel-Constantin Mierla (@ asipto.com)
twitter.com/miconda -- linkedin.com/in/miconda
Kamailio Consultancy and Development Services
Kamailio Advanced Training - Online - Nov 14-16, 2023 -- asipto.com
Hello,
When using http_async_query function, provided by module http_async_client:
https://www.kamailio.org/docs/modules/devel/modules/http_async_client.html#…
If module "tm.so" is not loaded, then immediately upon calling function http_async_query, Kamailio crashes:
9(3807541) CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 8
0(3807527) ALERT: <core> [main.c:791]: handle_sigs(): child process 3807533 exited by a signal 11
0(3807527) ALERT: <core> [main.c:795]: handle_sigs(): core was generated
0(3807527) INFO: <core> [main.c:818]: handle_sigs(): terminating due to SIGCHLD
Of course, I now know that I must load the module "tm.so".
But I think it would be better to catch the issue when Kamailio starts, rather than crashing later on when trying to call http_async_query.
What do you think ?
Regards,
Nicolas.
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
./kamcmd uac.reg_add 789798 789798 mydomain.com 789798 myteldomain.com . 789798 123456 . sip:sip6.telco.nl 360 0 10 mydomain.com:5060 udp:mydomain.com:5060
error: 400 - Invalid Parameters
Can you provide me with a case, I don't know how to enter the correct format.
Hi,
Facing the following error after bumping Kam from 5.3 => 5.4 => 5.5 => 5.6,
following instructions on each step about DB structure and module changes.
These errors show up since. Any clue what they mean? A couple other modules
are using the same DB MySQL connector. The data in the DB also seems to get
updated properly.
Jan 03 15:08:30 sip kamailio[20881]: ERROR: <core> [db.c:489]:
db_use_table(): invalid connection parameter
*Jan 03 15:08:30 sip kamailio[20881]: ERROR: usrloc [ucontact.c:1170]:
db_update_ucontact_ruid(): sql use_table failedJan 03 15:08:30 sip
kamailio[20881]: ERROR: usrloc [urecord.c:438]: wb_timer(): updating
contact in db failed (aor: user(a)domain.com <user(a)domain.com>)*
version: kamailio 5.6.5 (x86_64/linux) 48d48f
compiled on 02:32:48 Jan 2 2024 with gcc 4.9.2
DB structure:
location | CREATE TABLE `location` (
`id` int(10) unsigned NOT NULL AUTO_INCREMENT,
`ruid` varchar(64) NOT NULL DEFAULT '',
`username` varchar(64) NOT NULL DEFAULT '',
`domain` varchar(64) DEFAULT NULL,
`contact` varchar(512) NOT NULL DEFAULT '',
`received` varchar(128) DEFAULT NULL,
`path` varchar(512) DEFAULT NULL,
`expires` datetime NOT NULL DEFAULT '2030-05-28 21:32:15',
`q` float(10,2) NOT NULL DEFAULT 1.00,
`callid` varchar(255) NOT NULL DEFAULT 'Default-Call-ID',
`cseq` int(11) NOT NULL DEFAULT 1,
`last_modified` datetime NOT NULL DEFAULT '2000-01-01 00:00:01',
`flags` int(11) NOT NULL DEFAULT 0,
`cflags` int(11) NOT NULL DEFAULT 0,
`user_agent` varchar(255) NOT NULL DEFAULT '',
`socket` varchar(64) DEFAULT NULL,
`methods` int(11) DEFAULT NULL,
`instance` varchar(255) DEFAULT NULL,
`reg_id` int(11) NOT NULL DEFAULT 0,
`server_id` int(11) NOT NULL DEFAULT 0,
`connection_id` int(11) NOT NULL DEFAULT 0,
`keepalive` int(11) NOT NULL DEFAULT 0,
`partition` int(11) NOT NULL DEFAULT 0,
PRIMARY KEY (`id`),
UNIQUE KEY `ruid_idx` (`ruid`),
KEY `account_contact_idx` (`username`,`domain`,`contact`),
KEY `expires_idx` (`expires`),
KEY `connection_idx` (`server_id`,`connection_id`),
*KEY `tcpcon_idx` (`connection_id`)*
) ENGINE=InnoDB AUTO_INCREMENT=287989 DEFAULT CHARSET=latin1
> select * from version where table_name='location';
table_name: location
table_version: 9
Thanks.
Hi,
I have a Freeswitch installation, fronted by a Kamailio proxy
I would like to configure Kamailio to bridge SIP between webRTC clients and
Freeswitch.
The first issue I hit is how to set up a test webRTC client to make calls
into Kamailio/FS.
Can anyone point me to a simple webRTC client I can use to make
test webRTC/SIP calls into my setup? Thanks
BTW: I'm not JS experienced (I work with Python, C#, C/C++).
Kind regards,
Andy
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
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
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
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
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
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。
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))
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
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;
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?
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
______________________________________________________
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
______________________________________________________
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!
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.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
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
______________________________________________________
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
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
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
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
______________________________________________________
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
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
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();
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.
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
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
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
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
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
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
______________________________________________________