I am working on the configuration to enable RADIUS in Kamailio 4.0. The
basic install worked successfully and the daemon started without problems.
I then install radiusclient-ng and configured RADIUS in the Kamailio
build/configuration. All seemed OK until the Kamailio restart and I
encountered the following error during the restart:
Nov 13 06:52:23 lax-vproxy2-a kernel: [ 348.808624] kamailio[5346]:
segfault at 0 ip 00007f375d249a5d sp 00007fff4d42eed0 error 4 in
libradiusclient-ng.so.2.0.…
[View More]0[7f375d243000+c000]
Nov 13 06:52:23 lax-vproxy2-a kamailio: ERROR: <core> [daemonize.c:307]:
daemonize(): Main process exited before writing to pipe
After some research it seemed that others encountered a similar error and
traced it to the dictionary. I have gone through the dictionary
configuration and all seems to be correct. Any guidance on what might be
the issue or some troubleshooting steps?
Jonathan
[View Less]
Hi,
I need help. I encounter a segfault error in dialog.so when I do an
http_query containing shared pseudovariables in the event_routes of
dialog:start and dialog:end. How can I fix this?
It may be my lack of understanding, but I moved from using auth_check function to www_authenticate function and now see kamailio sending qop in auth header. It's my understanding this is not necessary (based on UA types in use) so I would like to remove it. Per module doc, it is "" by default, I tried adding auth param as below but made no difference. What could be causing this?
U x.x.x.x:5060 -> y.y.y.y:5060
REGISTER sip:y.y.y.y SIP/2.0.
Via: SIP/2.0/UDP x.x.x.x:5060;branch=z9hG4bK-…
[View More]bd3965f2.
From: user <sip:user@y.y.y.y>;tag=682bdce181bb953eo0.
To: user <sip:user@y.y.y.y>.
Call-ID: 1b886b6c-b283de31(a)x.x.x.x.
CSeq: 612 REGISTER.
Max-Forwards: 70.
Contact: user <sip:100@x.x.x.x:5060>;expires=1800.
User-Agent: agent
Content-Length: 0.
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER.
Supported: x-sipura, replaces.
.
U y.y.y.y:5060 -> x.x.x.x:5060
SIP/2.0 401 Unauthorized.
Via: SIP/2.0/UDP x.x.x.x:5060;branch=z9hG4bK-bd3965f2;rport=5060.
From: user <sip:user@y.y.y.y>;tag=682bdce181bb953eo0.
To: user <sip:user@y.y.y.y>;tag=02500e456b34f8655aebe61627730a5a.852c.
Call-ID: 1b886b6c-b283de31(a)x.x.x.x.
CSeq: 612 REGISTER.
WWW-Authenticate: Digest realm="y.y.y.y", nonce="UoV8q1KFe38amcNXXHXmuDU83y1OXg2n", qop="auth".
Server: SIP Proxy.
Content-Length: 0..
version: kamailio 4.0.3 (i386/linux) 090035
# ----- auth params -----
modparam("auth", "qop", "")
# ----- auth_db params -----
#!ifdef WITH_AUTH
modparam("auth_db", "db_url", DBURL)
modparam("auth_db", "calculate_ha1", yes)
modparam("auth_db", "password_column", "password")
modparam("auth_db", "load_credentials", "id")
modparam("auth_db", "use_domain", MULTIDOMAIN)
modparam("auth_db", "version_table", 0)
.........
if (!www_authenticate("$td", SIP_TABLE)) {
www_challenge("$td", "1");
exit;
}
.........
[cid:image001.gif@01CEE17B.A12FBB50]
[View Less]
Hello,
the stable branch from where we are going to package the release series
4.1.x has been created - its name: 4.1
There is now a 'kamailio' alias for the repository name, therefore it
can be used instead of 'sip-router' in the git path. Getting the git
branch 4.1 with read only access:
git clone --depth 1 --no-single-branch
git://git.sip-router.org/kamailio kamailio
cd kamailio
git checkout -b 4.1 origin/4.1
For developers that have write access:
git clone --depth 1 --…
[View More]no-single-branch
ssh://_USERID_@git.sip-router.org/kamailio kamailio
cd kamailio
git checkout -b 4.1 origin/4.1
Note that older versions of git application may not have the option
--no-single-branch. Just remove it when is the case.
I created also the wiki tutorial about installing kamailio 4.1.x from
git, it is available at:
- http://www.kamailio.org/wiki/install/4.1.x/git
After few more days of testing, we can loot at nailing down the release
date for v4.1.0.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
- more details about Kamailio trainings at http://www.asipto.com -
[View Less]
Hello,
a dedicated branch 4.1 has been created for upcoming major release. From
now on, the master can take again code with new features to be part of
future release series 4.2.x.
Any new bug fix that is applicable to stable branches has to be
committed first in master and then backported.
I will follow with another email describing how to use branch 4.1 for
those that want to switch testing from master to it.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://…
[View More]twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
- more details about Kamailio trainings at http://www.asipto.com -
[View Less]
Hello,
we are preparing for a new VUC session to give an update about Kamailio
project - a perfect timing as we are just about to release a new major
version.
We will like to get many developers involved to be able to highlight
properly what is new, especially those that did new development for v4.1
- new modules or enhancement to existing modules. However, any developer
and community member is welcome to join, we will appreciate it very
much, in support of the project.
Those that have …
[View More]a google hangout account can participate with video,
otherwise there are options to join via sip or pstn audio calls - you
can see more details at:
- http://vuc.me
The number of participants with video is limited, therefore if you plan
to do it, let me know to be able to coordinate and send you the invite
link when the session starts.
No matter you participate with audio/video, you can join the IRC channel
#vuc on freenode.net for text chatting during the event.
I made quickly a news about the event:
- http://www.kamailio.org/w/2013/10/kamailio-update-on-vuc-nov-15-2013/
I will add names of other participants as I get confirmations. Do
suggest topics to highlight/discuss there as well.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Trainings - Berlin, Nov 25-28
- more details about Kamailio trainings at http://www.asipto.com -
[View Less]
Hello all,
I have a kamailio server on a public IP address with a private interconnect into my office network. The private interconnect allows the server to see requests from individual 10.x.x.x IP addresses instead of everything coming through the public NAT. This avoids timeout issues and reduces keepalive traffic.
The problem is the SIP headers from clients on the 10.x.x.x IP range match nat_uac_test because of the RFC1918 address in the via and contact headers and so NAT support is …
[View More]enabled regardless of no NAT being present.
Is it possible to disable NAT support for a given IP range, in my case 10.x.x.x ?
Thanks,
John
[View Less]