Hi, we use pretty recent kamailio:
```
version: kamailio 4.4.0-dev2 (x86_64/linux) 1a758d
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 1a758d
compiled on 14:49:47 Jul 20 2015 with gcc 4.8.2
```
The case:
consider the mobile SIP agent which switches between networks (e.g. wifi -> mobile) during the call. It sends re-INVITE with its new location.
We use keep-alives provided by dialog module. And it seems that keep-alives don't use new address and are always sent to initial address.
Any thoughts?
Thanks.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/273
Hello,
during the past few days I made some updates related to the security
aspects of kamailio.org services.
Two are relevant for the community.
1) First, kamailio.org uses now a TLS certificate signed by
letsencrypt.org, a free trusted CA backed up by Mozilla and other
internet companies, so browsing via HTTPS should no longer issue any
warning of untrusted certificate (previously we used a CACert.org
certificate which was not trusted automatically by browsers).
Wiki and mailing lists portals use the letsencrypt certificate as well,
so is no reason not to browse all kamailio.org and lists.sip-router.org
pages only via HTTPS. Perhaps in the near future we will try to enable
redirect of HTTP to HTTPS at least for the main page and login pages for
wiki, mailing lists and other places that require sensitive data.
Now SSLLabs test ranks https://kamailio.org with grade A:
* https://www.ssllabs.com/ssltest/analyze.html?d=kamailio.org&latest
As a side note, for those that haven't noticed it, for quite some time
kamailio.org is available also over IPv6.
2) Second, emails forwarded by kamailio.org and lists.sip-router.org are
having now a DKIM signature. Also, there are SPF records in DNS for
these domains. Hopefully, those two will help getting the emails to be
allowed by various spam filters out there, as their legit origin can be
checked.
If you check the sources of an email messages and the email server of
receiving party is doing DKIM/SPF checks, you should see some headers
like next (taken from an email I received to my gmail account from
sr-users mailing list):
"""
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of sr-users-bounces(a)lists.sip-router.org designates 193.22.119.66 as permitted sender) smtp.mailfrom=sr-users-bounces(a)lists.sip-router.org;
dkim=pass header.i=(a)lists.sip-router.org
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.sip-router.org; s=20151206;
h=Sender:Content-Type:List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id:Reply-To:Subject:MIME-Version:Message-ID:To:From:Date; bh=lGjvCZYcxBHUHaJDnut1j2YTyPsXTnXHzUb0CgcDc1Q=;
b=DlD+MKoEqyISB5Ba775t3zg70FC6ouC+tEo7j5zv4dn2Dhm4pWqkQXSfU4Kp1NqW1ZRYFC/mpg/7LEcGW2FlDL9J0FpUg1VjNmN7D1wvtW08hBBw91tsXImu9yf7KZjg/p4IbXu6vznldubrSxweIaV3q/xbrLgaqP5Dsrvs/9A=;
"""
Kamailio is not enforcing any of those policies on received email
messages, so sending to the lists should not be affected.
Should anyone discover problems when browsing the web portals or notices
issues with emails from our mailing lists, report them to sr-dev mailing
list.
Also, if anyone has more hints on increasing the security/privacy for
the web server and email systems we run for kamailio.org, do not
hesitate to provide us suggestions.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu
Hi all,
I had configured my pdb module to accept 5 number prefixes by modifying:
In pdbt.c:
bufsize = slen + 1 + 1 + 4 + 1 + 1; // line buffer (telephone number + colon + white space + carrier ID + newline + \0)
...
ret = snprintf(p, 7, "%d\n", node->carrier);
if (ret < 1 || ret > 6) {
And in common.h:
#define MAX_PDB_CARRIERID 99999
And i hadn't had any problem until now. I had rows in my .csv like:
0645052050;10122
And it worked. The problem I have now is with prefixes bigger than 40000. I get segmentation fault when doiong a query with pdbt, however the pdbt build works good without any error.
At first i thought of a buffer problem but eventhough testing with a .csv of 2 rows with 50000 prefixes will not work. Another curious effect is that for a prefix like 84238 the server changes the answer to 18754. I dont know why...
Could anyone help me please?
Thanks.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/433
Hello,
upon a process initiated before the summer during the IRC Devel Meeting,
when we started to look for refreshing the logo of Kamailio project, we
are now trying to finalize the decision and we are proposing a new logo
for Kamailio project.
The new proposed logo, as well as more details, can be seen at:
*
http://www.kamailio.org/w/2015/12/proposing-new-logo-for-kamailio-project/
We look forward to the feedback from community about this proposal - you
like it or not, is too similar with other logos, etc...
This announcement was sent to few of our mailing lists, but please reply
to sr-users(a)lists.sip-router.org, being something concerning the
community and definitely not something about development.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.comhttp://miconda.eu