Dear all,
Greetings.
I am working on Kamailio for Linux environment. But, i don't have any idea
regarding usage of Kamailio in arm/embedded Linux environment.
Please help me in this regard, how can i port Kamailio into an embedded
linux device.
Kindly advice.
Regards
Sermj2012
Hi,
I was testing the new dynamic pipelimit instantiation functionality
heralded in 4.2, and, strangely enough, it doesn't seem to work at all.
Every time I call pl_check(), it just blocks the worker thread
indefinitely, until I--rather quickly--run out of available workers.
I've tried it with db_url (which I gathered to not be mandatory),
without a db_url, using every algorithm possible, with a static pipe
name, with a PV pipe name, etc. It all yields the same results. Here is
my current employment of it:
if($(xavp(call=>ingress_cps_limit){s.int}) > 0) {
xlog("L_INFO", "DEBUG: PRE PL CHECK $ci\n");
if(!pl_check("1", "RED", "2")) {
xlog("L_INFO", "DEBUG: AFTER PL CHECK $ci\n");
pl_drop();
xlog("L_INFO", "Ingress call setup rate limit
for this BG "
"$(xavp(call=>ingress_cps_limit){s.int}) has "
"been exceeded; rejecting call\n");
exit;
}
xlog("L_INFO", "DEBUG: AFTER PL CHECK $ci\n");
}
modparam("pipelimit", "hash_size", 12)
modparam("pipelimit", "timer_interval", 5)
modparam("pipelimit", "reply_code", 503)
modparam("pipelimit", "reply_reason", "Call Setup Rate Exceeded")
I never reach "AFTER PL CHECK".
Here's what I actually want to do:
if($(xavp(call=>ingress_cps_limit){s.int}) > 0) {
if(!pl_check("$avp(trunk_id)", "RED",
"$(xavp(call=>ingress_cps_limit){s.int})")) {
pl_drop();
xlog("L_INFO", "!> "
"Ingress call setup rate limit for this BG "
"$(xavp(call=>ingress_cps_limit){s.int}) has "
"been exceeded; rejecting call\n");
exit;
}
}
I tried upping debug to debug=3 but get nothing insightful that pertains
to pipelimit at all, as far as I can see.
This is on a stock CentOS 6.5 install,
sip-router:master:36e695453762b5ed15e5048fad2c559bb239dad5 compiled from
source.
Thanks!
--
Alex Balashov - Principal
Evariste Systems LLC
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
Please be kind to the English language:
http://www.entrepreneur.com/article/232906
Hello list,
thanks for creating kamailio and good documentation for it.
Also thanks to Daniel for this guide
http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb
I managed to integrate kamailio with asterisk and a2billing and I do have
some small issues with some UA's.
Generally all soft phones are OK but from some I can not generate calls.
Especially it is true for Linksys SPA and Grandstream gxv3140. From 10
phones I have one with this issue, all config is the same on device side
and on server/config side, but some are failing to generate calls. These UA
will receive calls but will not be able to call. They are registered OK and
I see these devices as all other ones in location table. One work around I
have found is to update manually the cc_sip_buddy table(from asterisk
realtime) with IP address and port and big part of these US's will start
working. But still I have some that will not work even after that. What I
see when capturing with ngrep is this:
1) Invite with SDP
2) 407 Proxy Authentication Required
3) ACK
4) Invite with SDP
5) 100 trying -- your call is important to us
6) 401 Unauthorized
7) ACK
Not all captured calls have all 7 steps some of these drop at 4th step and
I mention that all UA-s are showing OK as registered.
I use sip.Server == "kamailio (4.1.6 (x86_64/linux))" ;
Please suggest some steps to increase that authentication time(i suspect
that these UA's do not have sufficient time to authenticate) and help me to
understand why this is happening.
Thank you in andvance.
Vitalie Alex Bugaian.
Dear All
I have tried a lot and looks getting Kamailio IMS setup is very difficult
and no proper documentation available. Though I have setup all CSCFs and
FHoSS , still REGISTRATION fails with 483 response.
I have setup DNS properly as shown below.
*root@necs04:/etc/kamailio/pcscf# root@necs04:/etc/kamailio/pcscf# ping
pcscf.group1-imslab11.in <http://pcscf.group1-imslab11.in>PING
pcscf.group1-imslab11.in <http://pcscf.group1-imslab11.in> (192.168.1.100)
56(84) bytes of data.64 bytes from localhost (192.168.1.100): icmp_req=1
ttl=64 time=0.037 ms64 bytes from localhost (192.168.1.100): icmp_req=2
ttl=64 time=0.028 ms^C--- pcscf.group1-imslab11.in
<http://pcscf.group1-imslab11.in> ping statistics ---2 packets transmitted,
2 received, 0% packet loss, time 1000msrtt min/avg/max/mdev =
0.028/0.032/0.037/0.007 msroot@necs04:/etc/kamailio/pcscf#
root@necs04:/etc/kamailio/pcscf# root@necs04:/etc/kamailio/pcscf#
root@necs04:/etc/kamailio/pcscf# ping icscf.group1-imslab11.in
<http://icscf.group1-imslab11.in>PING icscf.group1-imslab11.in
<http://icscf.group1-imslab11.in> (192.168.1.100) 56(84) bytes of data.64
bytes from localhost (192.168.1.100): icmp_req=1 ttl=64 time=0.023 ms64
bytes from localhost (192.168.1.100): icmp_req=2 ttl=64 time=0.029 ms64
bytes from localhost (192.168.1.100): icmp_req=3 ttl=64 time=0.024 ms^C---
icscf.group1-imslab11.in <http://icscf.group1-imslab11.in> ping statistics
---3 packets transmitted, 3 received, 0% packet loss, time 1999msrtt
min/avg/max/mdev = 0.023/0.025/0.029/0.004
msroot@necs04:/etc/kamailio/pcscf# root@necs04:/etc/kamailio/pcscf# ping
scscf.group1-imslab11.in <http://scscf.group1-imslab11.in>PING
scscf.group1-imslab11.in <http://scscf.group1-imslab11.in> (192.168.1.100)
56(84) bytes of data.64 bytes from localhost (192.168.1.100): icmp_req=1
ttl=64 time=0.022 ms64 bytes from localhost (192.168.1.100): icmp_req=2
ttl=64 time=0.022 ms64 bytes from localhost (192.168.1.100): icmp_req=3
ttl=64 time=0.021 ms^C--- scscf.group1-imslab11.in
<http://scscf.group1-imslab11.in> ping statistics ---3 packets transmitted,
3 received, 0% packet loss, time 1998msrtt min/avg/max/mdev =
0.021/0.021/0.022/0.005 msroot@necs04:/etc/kamailio/pcscf# *
Also dig result is as shown below.
*root@necs04:/etc/kamailio/pcscf# root@necs04:/etc/kamailio/pcscf# dig
naptr group1-imslab11.in <http://group1-imslab11.in>; <<>> DiG 9.8.1-P1
<<>> naptr group1-imslab11.in <http://group1-imslab11.in>;; global options:
+cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:
10919;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL:
3;; QUESTION SECTION:;group1-imslab11.in <http://group1-imslab11.in>.
IN NAPTR;; ANSWER SECTION:group1-imslab11.in
<http://group1-imslab11.in>. 86400 IN NAPTR 10 50 "s" "SIP+D2T"
"" _sip._tcp.pcscf.group1-imslab11.in
<http://tcp.pcscf.group1-imslab11.in>.group1-imslab11.in
<http://group1-imslab11.in>. 86400 IN NAPTR 10 50 "s" "SIP+D2U"
"" _sip._udp.pcscf.group1-imslab11.in
<http://udp.pcscf.group1-imslab11.in>.;; AUTHORITY
SECTION:group1-imslab11.in <http://group1-imslab11.in>. 86400 IN
NS necs04.group1-imslab11.in <http://necs04.group1-imslab11.in>.;;
ADDITIONAL SECTION:pcscf.group1-imslab11.in
<http://pcscf.group1-imslab11.in>. 86400 IN A
192.168.1.100necs04.group1-imslab11.in <http://necs04.group1-imslab11.in>.
86400 IN A 192.168.1.100_sip._udp.pcscf.group1-imslab11.in
<http://udp.pcscf.group1-imslab11.in>. 86400 IN SRV 0 0 4060
pcscf.group1-imslab11.in <http://pcscf.group1-imslab11.in>.;; Query time: 0
msec;; SERVER: 192.168.1.100#53(192.168.1.100);; WHEN: Fri Oct 17 17:34:22
2014;; MSG SIZE rcvd: 259root@necs04:/etc/kamailio/pcscf# *
When I send a REGISTER message from a sip client, I get 483 Too Many Hops.
I am totally clueless whats going wrong.
Can somebody guide me , where is the fault.
On thing I do not understand is dispatcher.list stuff.
So I have kept empty disptacher.list file for PCSCF and SCSCF.
Can that be an issue.
The REGISTER and 483 response looks as below.
*REGISTER sip:pcscf.group1-imslab11.in <http://pcscf.group1-imslab11.in>
SIP/2.0Via: SIP/2.0/TCP 192.168.1.114:49732;branch=z9hG4bK457115572From:
<sip:necs_0@group1-imslab11.in
<sip%3Anecs_0(a)group1-imslab11.in>>;tag=1068512852To:
<sip:necs_0@group1-imslab11.in <sip%3Anecs_0(a)group1-imslab11.in>>Call-ID:
1874336526CSeq: 16 REGISTERContact:
<sip:necs_0@192.168.1.114:49732;transport=TCP;line=a126427bb8e82c9>;+sip.instance="<urn:uuid:2dab9970-55f5-11e4-ae19-41032d8f6492>"Authorization:
Digest username="necs_0(a)group1-imslab11.in <necs_0(a)group1-imslab11.in>",
realm="pcscf.group1-imslab11.in <http://pcscf.group1-imslab11.in>", nonce="
", uri="sip:pcscf.group1-imslab11.in <http://pcscf.group1-imslab11.in>",
response=" "Max-Forwards: 70User-Agent: NECS IMS client v1.01Expires:
600000Supported: pathSupported: gruuContent-Length: 0*
*SIP/2.0 483 Too Many HopsVia: SIP/2.0/TCP
192.168.1.114:49732;branch=z9hG4bK457115572From:
<sip:necs_0@group1-imslab11.in
<sip%3Anecs_0(a)group1-imslab11.in>>;tag=1068512852To:
<sip:necs_0@group1-imslab11.in
<sip%3Anecs_0(a)group1-imslab11.in>>;tag=68c95b6520b8472128534dfbca9fcb81.d739Call-ID:
1874336526CSeq: 16 REGISTERServer: Kamailio P-CSCFContent-Length: 0*
Kindly somebody help me how I can troubleshoot and fix it.
Many thanks
Kamal
Hi
Thanks a lot for your reply. I'll check the cn and let you know. In my configuration I'm listening to tcp port but no tls port? Can that be the reason? Otherthan that if it was rejected because of the certificate shouldn't I get some errors in the log? Every time I'm trying it's getting request timed out.
Sent from my Samsung Galaxy smartphone.
-------- Original message --------
From: Gonzalo Gasca <gascagonzalo(a)gmail.com>
Date:10-17-2014 19:33 (GMT-06:00)
To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.sip-router.org>
Cc: ben(a)langfeld.me
Subject: Re: [SR-Users] Configuring TLS and WSS with Kamailio
Hi Ben,
In regards your certificates, please double check the following:
a) CN field:
In your webrtc client check the URL used for wss. and verify it matches the
CN field of the certificate installed in kamailio:
Example:
In my sipml5 client I configured wss://ramenlabs.io:5063 and my certificate
in fact contains in the cn field ramenlabs.io
Subject: OU=Domain Control Validated, OU=PositiveSSL, CN=ramenlabs.io
openssl x509 -in /etc/certs/sip.192.168.146.133/cert.pem -noout -text
b)
I have successfully configured Kamailio 4.1 with TLS and WSS using TLS port
5063
Topology:
1) sipml5 --wss--> ngnix -wss-> kamailio (sip registrar)
2) sipml5 --wss---> kamailio
Relevant configurations:
kamailio.cfg
tls.cfg
certificates
Kamailio:
loading modules under /usr/lib/x86_64-linux-gnu/kamailio/modules/
Listening on
udp: 172.31.27.85:5060
tcp: 172.31.27.85:5060
tcp: 172.31.27.85:5062
tls: 172.31.27.85:5061
* tls: 172.31.27.85:5063 <http://172.31.27.85:5063>*
Aliases:
* tls: ip-172-31-27-85.us-west-2.compute.internal:5063*
tls: ip-172-31-27-85.us-west-2.compute.internal:5061
tcp: ip-172-31-27-85.us-west-2.compute.internal:5062
tcp: ip-172-31-27-85.us-west-2.compute.internal:5060
udp: ip-172-31-27-85.us-west-2.compute.internal:5060
*: ramenlabs.io:*
*: 172.31.27.85:*
kamailio.cfg
tls.cfg
https://github.com/spicyramen/llamato/blob/LlamatoReg/kamailio.cfghttps://github.com/spicyramen/llamato/blob/LlamatoReg/tls.cfg
openssl s_client -connect 172.31.27.85:5063 where this i my internal IP
address I get presented the certificates.
HTH
-G
On Fri, Oct 17, 2014 at 5:10 PM, Kamrul Khan <dodul(a)live.com> wrote:
> ok. I have made some changes. rather than getting the TLS configaration
> from a file I added this lines:
>
> #!ifdef WITH_TLS
> # ----- tls params -----
>
> modparam("tls", "private_key", "/etc/certs/sip.192.168.146.133/key.pem")
> modparam("tls", "certificate", "/etc/certs/sip.192.168.146.133/cert.pem")
> modparam("tls", "ca_list", "/etc/certs/demoCA/cert.pem")
>
> now, Im getting different logs which looks good. Getting positive results
> from openssl test,
>
> openssl s_client -connect 192.168.146.133:5061 -tls1
> CONNECTED(00000003)
> ^C
>
> But when I try to connect using my webRTC client or even from web-browsers
> im getting timed out. I think im close .. please help me fixing this issue.
>
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:275]: fill_missing(): TLSs<default>: tls_method=9
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:287]: fill_missing(): TLSs<default>:
> certificate='/etc/certs/sip.192.168.146.133/cert.pem'
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:294]: fill_missing(): TLSs<default>:
> ca_list='/etc/certs/demoCA/cert.pem'
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:301]: fill_missing(): TLSs<default>: crl='(null)'
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:305]: fill_missing(): TLSs<default>:
> require_certificate=0
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:312]: fill_missing(): TLSs<default>:
> cipher_list='(null)'
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:319]: fill_missing(): TLSs<default>:
> private_key='/etc/certs/sip.192.168.146.133/key.pem'
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:323]: fill_missing(): TLSs<default>:
> verify_certificate=0
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:326]: fill_missing(): TLSs<default>: verify_depth=9
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:670]: set_verification(): TLSs<default>: No client
> certificate required and no checks performed
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:275]: fill_missing(): TLSc<default>: tls_method=9
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:287]: fill_missing(): TLSc<default>:
> certificate='/etc/certs/sip.192.168.146.133/cert.pem'
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:294]: fill_missing(): TLSc<default>:
> ca_list='/etc/certs/demoCA/cert.pem'
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:301]: fill_missing(): TLSc<default>: crl='(null)'
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:305]: fill_missing(): TLSc<default>:
> require_certificate=0
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:312]: fill_missing(): TLSc<default>:
> cipher_list='(null)'
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:319]: fill_missing(): TLSc<default>:
> private_key='/etc/certs/sip.192.168.146.133/key.pem'
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:323]: fill_missing(): TLSc<default>:
> verify_certificate=0
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:326]: fill_missing(): TLSc<default>: verify_depth=9
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12123]:
> INFO: tls [tls_domain.c:673]: set_verification(): TLSc<default>: Server MAY
> present invalid certificate
> Oct 17 16:35:38 ubuntu /usr/local/kamailio-devel//sbin/kamailio[12136]:
> INFO: ctl [io_listener.c:225]: io_listen_loop(): io_listen_loop: using
> epoll_lt io watch method (config)
>
>
> ------------------------------
> From: dodul(a)live.com
> To: ben(a)langfeld.me; sr-users(a)lists.sip-router.org
> Date: Sat, 18 Oct 2014 05:08:20 +0600
>
> Subject: Re: [SR-Users] Configuring TLS and WSS with Kamailio
>
> I dint find any in my installation directory. probably it doesn't come
> with standard installation unless you explicitly mention for it... not sure
> though
>
> ------------------------------
> Date: Fri, 17 Oct 2014 19:56:50 -0300
> From: ben(a)langfeld.co.uk
> To: sr-users(a)lists.sip-router.org
> Subject: Re: [SR-Users] Configuring TLS and WSS with Kamailio
>
> Out of curiosity, why don't you use the pre-built packaged binaries
> instead of building from source?
>
> On 17 October 2014 19:53, Kamrul Khan <dodul(a)live.com> wrote:
>
> Hi,
>
>
> Im trying to connect my WebRTC clietn to kamailio via WSS. I
> successfully connected it via WS but having trouble connecting it via WSS.
> My first issue is I get error messages while i try to compile TLS
> module(console log in the end of the document). But, still it creates
> tls.so file. So i copied the tls.so to my kamailio modules directory and
> then updated my kamailio configuration as below:
>
>
> #!define WITH_TLS
>
> .
>
> .
>
> listen=tcp:127.0.0.1:5061
>
> listen=tcp:192.168.146.133:5061
>
> .
>
> .
>
> #!ifdef WITH_TLS
>
> enable_tls=yes
>
> #!endif
>
> .
>
> .
>
> #!ifdef WITH_TLS
>
> # ----- tls params -----
>
> modparam("tls", "config", "/usr/local/kamailio-devel/etc/kamailio/tls.cfg")
>
> #!endif
>
>
> Now, according to this mailing list,
> http://lists.sip-router.org/pipermail/sr-users/2013-March/077182.html : “*when
> tls module is installed, a self signed pair of certificate-private key is
> generated in /usr/local/etc/kamailio”*
>
>
> In my case, I dont even have the /usr/local/etc/kamailio directory. So,
> I followed
> http://www.kamailio.org/dokuwiki/doku.php/tls:create-certificates to
> create my certificate and key. And updated my tsl.cfg, this is how my
> tsl.cfg looks like:
>
>
> [server:192.168.146.133:5061]
>
> method = TLSv1
>
> verify_certificate = no
>
> require_certificate = no
>
>
> private_key = /etc/certs/sip.192.168.146.133/key.pem
>
> certificate = /etc/certs/sip.192.168.146.133/cert.pem
>
> ca_list = /etc/certs/demoCA/cert.pem
>
>
> [client:192.168.146.133:5061]
>
> verify_certificate = yes
>
> require_certificate = yes
>
>
>
> Then I restarted my kamailio server. And i get the following errors in
> my kamailio log:
>
>
> Im not sure what wrong im doing. Please help me:
>
>
> Oct 17 15:44:50 ubuntu kamailio: INFO: tls [tls_init.c:385]:
> init_tls_compression(): tls: init_tls: disabling compression...
>
> Oct 17 15:44:50 ubuntu kamailio: WARNING: <core> [socket_info.c:1397]:
> fix_hostname(): WARNING: fix_hostname: could not rev. resolve
> 192.168.146.133
>
> Oct 17 15:44:50 ubuntu kamailio: message repeated 2 times: [ WARNING:
> <core> [socket_info.c:1397]: fix_hostname(): WARNING: fix_hostname: could
> not rev. resolve 192.168.146.133]
>
> Oct 17 15:44:50 ubuntu kamailio: INFO: <core> [tcp_main.c:4836]:
> init_tcp(): init_tcp: using epoll_lt as the io watch method (auto detected)
>
> Oct 17 15:44:50 ubuntu kamailio: WARNING: <core> [daemonize.c:352]:
> daemonize(): pid file contains old pid, replacing pid
>
> Oct 17 15:44:50 ubuntu /usr/local/kamailio-devel//sbin/kamailio[11013]:
> INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob
>
> Oct 17 15:44:50 ubuntu /usr/local/kamailio-devel//sbin/kamailio[11013]:
> INFO: rr [rr_mod.c:159]: mod_init(): outbound module not available
>
> Oct 17 15:44:50 ubuntu /usr/local/kamailio-devel//sbin/kamailio[11013]:
> INFO: usrloc [hslot.c:53]: ul_init_locks(): locks array size 512
>
> Oct 17 15:44:50 ubuntu /usr/local/kamailio-devel//sbin/kamailio[11013]:
> INFO: utils [utils.c:288]: mod_init(): forward functionality disabled
>
> Oct 17 15:44:50 ubuntu /usr/local/kamailio-devel//sbin/kamailio[11013]:
> INFO: utils [utils.c:197]: pres_db_init(): xcap_auth_status function is
> disabled
>
> Oct 17 15:44:50 ubuntu /usr/local/kamailio-devel//sbin/kamailio[11013]:
> ERROR: tls [tls_init.c:668]: tls_check_sockets(): TLSs<
> 192.168.146.133:5061>: No listening socket found
>
> Oct 17 15:44:50 ubuntu /usr/local/kamailio-devel//sbin/kamailio[11013]:
> ERROR: <core> [sr_module.c:970]: init_mod(): init_mod(): Error while
> initializing module tls
> (/usr/local/kamailio-devel/lib64/kamailio/modules/tls.so)
>
> Oct 17 15:44:50 ubuntu /usr/local/kamailio-devel//sbin/kamailio[11013]: :
> tls [tls_locking.c:103]: locking_f(): BUG: tls: locking_f (callback):
> invalid lock number: 30 (range 0 - 0), called from eng_table.c:227
>
> Oct 17 15:44:51 ubuntu kamailio: ERROR: <core> [daemonize.c:307]:
> daemonize(): Main process exited before writing to pipe
>
>
> tls module compile log
>
>
> xxx@ubuntu:/usr/local/src/kamailio-4.1/kamailio$ sudo make -C modules/tls
> make: Entering directory `/usr/local/src/kamailio-4.1/kamailio/modules/tls'
> make: Leaving directory `/usr/local/src/kamailio-4.1/kamailio/modules/tls'
> make: Entering directory `/usr/local/src/kamailio-4.1/kamailio/modules/tls'
> CC (gcc) [M tls.so] tls_bio.o
> CC (gcc) [M tls.so] tls_cfg.o
> CC (gcc) [M tls.so] tls_config.o
> CC (gcc) [M tls.so] tls_ct_wrq.o
> CC (gcc) [M tls.so] tls_domain.o
> In file included from tls_domain.c:39:0:
> tls_domain.c: In function âload_certâ:
> tls_util.h:52:6: warning: variable âretâ set but not used
> [-Wunused-but-set-variable]
> int ret; \
> ^
> tls_domain.c:506:4: note: in expansion of macro âTLS_ERRâ
> TLS_ERR("load_cert:");
> ^
> tls_domain.c: In function âload_ca_listâ:
> tls_util.h:52:6: warning: variable âretâ set but not used
> [-Wunused-but-set-variable]
> int ret; \
> ^
> tls_domain.c:536:4: note: in expansion of macro âTLS_ERRâ
> TLS_ERR("load_ca_list:");
> ^
> tls_util.h:52:6: warning: variable âretâ set but not used
> [-Wunused-but-set-variable]
> int ret; \
> ^
> tls_domain.c:543:4: note: in expansion of macro âTLS_ERRâ
> TLS_ERR("load_ca_list:");
> ^
> tls_domain.c: In function âload_crlâ:
> tls_util.h:52:6: warning: variable âretâ set but not used
> [-Wunused-but-set-variable]
> int ret; \
> ^
> tls_domain.c:575:4: note: in expansion of macro âTLS_ERRâ
> TLS_ERR("load_crl:");
> ^
> tls_domain.c: In function âload_private_keyâ:
> tls_util.h:52:6: warning: variable âretâ set but not used
> [-Wunused-but-set-variable]
> int ret; \
> ^
> tls_domain.c:990:5: note: in expansion of macro âTLS_ERRâ
> TLS_ERR("load_private_key:");
> ^
> tls_util.h:52:6: warning: variable âretâ set but not used
> [-Wunused-but-set-variable]
> int ret; \
> ^
> tls_domain.c:998:4: note: in expansion of macro âTLS_ERRâ
> TLS_ERR("load_private_key:");
> ^
> tls_util.h:52:6: warning: variable âretâ set but not used
> [-Wunused-but-set-variable]
> int ret; \
> ^
> tls_domain.c:1005:4: note: in expansion of macro âTLS_ERRâ
> TLS_ERR("load_private_key:");
> ^
> CC (gcc) [M tls.so] tls_dump_vf.o
> CC (gcc) [M tls.so] tls_init.o
> CC (gcc) [M tls.so] tls_locking.o
> CC (gcc) [M tls.so] tls_mod.o
> CC (gcc) [M tls.so] tls_rpc.o
> CC (gcc) [M tls.so] tls_select.o
> CC (gcc) [M tls.so] tls_server.o
> In file included from tls_server.c:52:0:
> tls_server.c: In function âtls_complete_initâ:
> tls_util.h:52:6: warning: variable âretâ set but not used
> [-Wunused-but-set-variable]
> int ret; \
> ^
> tls_server.c:192:3: note: in expansion of macro âTLS_ERRâ
> TLS_ERR("Failed to create SSL or BIO structure:");
> ^
> tls_server.c: In function âtls_shutdownâ:
> tls_util.h:52:6: warning: variable âretâ set but not used
> [-Wunused-but-set-variable]
> int ret; \
> ^
> tls_server.c:521:4: note: in expansion of macro âTLS_ERRâ
> TLS_ERR("SSL error:");
> ^
> tls_server.c: In function âtls_encode_fâ:
> tls_util.h:52:6: warning: variable âretâ set but not used
> [-Wunused-but-set-variable]
> int ret; \
> ^
> tls_server.c:798:5: note: in expansion of macro âTLS_ERRâ
> TLS_ERR(err_src);
> ^
> tls_util.h:52:6: warning: variable âretâ set but not used
> [-Wunused-but-set-variable]
> int ret; \
> ^
> tls_server.c:832:5: note: in expansion of macro âTLS_ERRâ
> TLS_ERR(err_src);
> ^
> tls_server.c: In function âtls_read_fâ:
> tls_util.h:52:6: warning: variable âretâ set but not used
> [-Wunused-but-set-variable]
> int ret; \
> ^
> tls_server.c:1186:4: note: in expansion of macro âTLS_ERRâ
> TLS_ERR(err_src);
> ^
> tls_util.h:52:6: warning: variable âretâ set but not used
> [-Wunused-but-set-variable]
> int ret; \
> ^
> tls_server.c:1220:4: note: in expansion of macro âTLS_ERRâ
> TLS_ERR(err_src);
> ^
> CC (gcc) [M tls.so] tls_util.o
> CC (gcc) [M tls.so] tls_verify.o
> LD (gcc) [M tls.so] tls.so
> make: Leaving directory `/usr/local/src/kamailio-4.1/kamailio/modules/tls'
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
> _______________________________________________ SIP Express Router (SER)
> and Kamailio (OpenSER) - sr-users mailing list
> sr-users(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
> _______________________________________________ SIP Express Router (SER)
> and Kamailio (OpenSER) - sr-users mailing list
> sr-users(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users(a)lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hiiii everyone,
Forgive me for such simple question but i'm newbie to Kamailio. i was
reading about the dispatcher module
http://www.kamailio.org/docs/modules/4.2.x/modules/dispatcher.html#dispatch…
and i want someone to explain to me in a simple way what is AVP , for
example the AVP in the *modparam("dispatcher", "grp_avp", "$avp(dsgrp)")*
and what the "dsgrp" represents and how to configure the AVP values ...
Kinda Regards
Thanks in advance...
Hi,
After some testing it appears that kamailio can do maximum 12 serial forks
using transaction manager (tm module). Is it possible to make it
configurable in kamailio.cfg or at least increase it with static higher
value (e.g. 15)?
Thank you.
>It is a matter of config file, mainly the route[AUTH] -- remove the if
>condition about what has to be authenticated and authenticate all the
>requests.
>
>Cheers,
>Daniel
Perfect, solved the issue :)
Regards
Manuel
Hi,
I have installed kamailio stable on Debian Wheezy from the repository,
followed the main tutorial and pretty much everything looked like it was
working at first. I can connect to my sip server but when I try to log
in I keep getting a failed login.
In the mysql database I have the correct username and domain in the
subscriber table. No typos there so then I enabled logging with debug=3
to check the logs but I am not sure how to interprete what I see.
It seems like there 2 two login procedures. The first one seems to
fail, the second one seems to work since I see a "check_response:
Authorization is OK" in there but still on Jitsi I keep getting told my
password is incorrect. Here is the log dump of both login procedures
from the same login attempt (I only tried to login once and as you see
on the timestamp it all happens within the same second)
This is the first attempt where the realm is not found even though it
is exactly the domain I have in the subscriber mysql table:
Oct 17 08:21:17 video /usr/sbin/kamailio[5170]: DEBUG: auth_db
[authorize.c:486]: auth_check(): realm [video.mydomain.de] table
[subscriber] flags [1]
Oct 17 08:21:17 video /usr/sbin/kamailio[5170]: DEBUG: auth [api.c:86]:
pre_auth(): auth:pre_auth: Credentials with realm 'video.mydomain.de'
not found
Oct 17 08:21:17 video /usr/sbin/kamailio[5170]: DEBUG: auth_db
[authorize.c:252]: digest_authenticate_hdr(): no credentials
Oct 17 08:21:17 video /usr/sbin/kamailio[5170]: DEBUG: auth
[challenge.c:127]: get_challenge_hf(): build_challenge_hf:
realm='video.mydomain.de'
Oct 17 08:21:17 video /usr/sbin/kamailio[5170]: DEBUG: auth
[challenge.c:269]: get_challenge_hf(): auth: 'WWW-Authenticate: Digest
realm="video.mydomain.de",
nonce="VEEK6VRBCb32GLPSTiKlfAo4loEn7BTY"#015#012'
Oct 17 08:21:17 video /usr/sbin/kamailio[5170]: DEBUG: sl [sl.c:288]:
send_reply(): reply in stateless mode (sl)
Oct 17 08:21:17 video /usr/sbin/kamailio[5170]: DEBUG: <core>
[msg_translator.c:204]: check_via_address():
check_via_address(79.212.239.151, 192.168.2.32, 0)
Oct 17 08:21:17 video /usr/sbin/kamailio[5170]: DEBUG: <core>
[usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying
list 0x7f2f830daa10
Then a second login attempt takes place where it looks different:
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/msg_parser.c:623]: parse_msg(): SIP Request:
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/msg_parser.c:625]: parse_msg(): method: <REGISTER>
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/msg_parser.c:627]: parse_msg(): uri:
<sip:video.mydomain.de:5188>
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/msg_parser.c:629]: parse_msg(): version: <SIP/2.0>
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/msg_parser.c:170]: get_hdr_field(): get_hdr_field: cseq <CSeq>:
<2> <REGISTER>
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header
reached, state=10
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/msg_parser.c:190]: get_hdr_field(): DEBUG: get_hdr_field: <To>
[46]; uri=[sip:oliver2@video.mydomain.de]
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/msg_parser.c:192]: get_hdr_field(): DEBUG: to body ["oliver2"
<sip:oliver2@video.mydomain.de>#015#012]
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/parse_via.c:1284]: parse_via_param(): Found param type 232,
<branch> = <z9hG4bK-383534-d21acd094f094ec7f76ca01734bb9c80>; state=16
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/parse_via.c:2672]: parse_via(): end of header reached, state=5
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found,
flags=2
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the
first via
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[receive.c:152]: receive_msg(): After parse_msg...
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[receive.c:193]: receive_msg(): preparing to run routing scripts...
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: maxfwd
[mf_funcs.c:85]: is_maxfwd_present(): value = 70
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/msg_parser.c:204]: get_hdr_field(): DEBUG: get_hdr_body :
content_length=0
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/msg_parser.c:106]: get_hdr_field(): found end of header
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/parse_addr_spec.c:176]: parse_to_param(): DEBUG: add_param:
tag=f59174d
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[parser/parse_addr_spec.c:898]: parse_addr_spec(): end of header
reached, state=29
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: sanity
[mod_sanity.c:255]: w_sanity_check(): sanity checks result: 1
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: siputils
[checks.c:103]: has_totag(): no totag
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: tm
[t_lookup.c:1072]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global
id=1 T start=(nil)
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: tm
[t_lookup.c:527]: t_lookup_request(): t_lookup_request: start searching:
hash=60350, isACK=0
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: tm
[t_lookup.c:485]: matching_3261(): DEBUG: RFC3261 transaction matching
failed
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: tm
[t_lookup.c:709]: t_lookup_request(): DEBUG: t_lookup_request: no
transaction found
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: tm
[t_lookup.c:1141]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global
id=2 T end=(nil)
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: auth_db
[authorize.c:486]: auth_check(): realm [video.mydomain.de] table
[subscriber] flags [1]
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: auth [api.c:96]:
pre_auth(): auth: digest-algo: parsed value: 0
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[db_res.c:118]: db_new_result(): allocate 56 bytes for result set at
0x7f2f8d09c040
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: db_mysql
[km_res.c:68]: db_mysql_get_columns(): 1 columns returned from the query
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[db_res.c:155]: db_allocate_columns(): allocate 8 bytes for result names
at 0x7f2f8d09c148
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[db_res.c:165]: db_allocate_columns(): allocate 4 bytes for result types
at 0x7f2f8d09c0d8
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: db_mysql
[km_res.c:86]: db_mysql_get_columns(): allocate 16 bytes for
RES_NAMES[0] at 0x7f2f8d0aa448
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: db_mysql
[km_res.c:93]: db_mysql_get_columns():
RES_NAMES(0x7f2f8d0aa448)[0]=[password]
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: db_mysql
[km_res.c:137]: db_mysql_get_columns(): use DB1_STRING result type
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[db_res.c:184]: db_allocate_rows(): allocate 16 bytes for rows at
0x7f2f8d09c288
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[db_row.c:119]: db_allocate_row(): allocate 32 bytes for row values at
0x7f2f8d09e480
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[db_val.c:117]: db_str2val(): converting STRING [xxxxxxx]
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: auth_db
[authorize.c:196]: get_ha1(): HA1 string calculated:
a4fe9f8e75b2cb7b19da2cbc37b33bcc
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: auth
[api.c:211]: auth_check_response(): check_response: Our result =
'1aab3cbf895ec5c2491135a0a6869f4e'
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: auth
[api.c:218]: auth_check_response(): check_response: Authorization is OK
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[db_res.c:81]: db_free_columns(): freeing 1 columns
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[db_res.c:85]: db_free_columns(): freeing RES_NAMES[0] at 0x7f2f8d0aa448
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[db_res.c:94]: db_free_columns(): freeing result names at 0x7f2f8d09c148
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[db_res.c:99]: db_free_columns(): freeing result types at 0x7f2f8d09c0d8
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[db_res.c:54]: db_free_rows(): freeing 1 rows
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[db_row.c:97]: db_free_row(): freeing row values at 0x7f2f8d09e480
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[db_res.c:62]: db_free_rows(): freeing rows at 0x7f2f8d09c288
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[db_res.c:136]: db_free_result(): freeing result set at 0x7f2f8d09c040
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: auth
[challenge.c:127]: get_challenge_hf(): build_challenge_hf:
realm='video.mydomain.de'
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: auth
[challenge.c:269]: get_challenge_hf(): auth: 'WWW-Authenticate: Digest
realm="video.mydomain.de",
nonce="VEEK6VRBCb32GLPSTiKlfAo4loEn7BTY"#015#012'
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: sl [sl.c:288]:
send_reply(): reply in stateless mode (sl)
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[msg_translator.c:204]: check_via_address():
check_via_address(79.212.239.151, 192.168.2.32, 0)
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying
list 0x7f2f830daa10
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying
list (nil)
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying
list (nil)
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying
list (nil)
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying
list (nil)
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[usr_avp.c:644]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying
list (nil)
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil)
Oct 17 08:21:17 video /usr/sbin/kamailio[5172]: DEBUG: <core>
[receive.c:296]: receive_msg(): receive_msg: cleaning up
Any help on what I did wrong is appreciated...
Best regards
Oliver
Hello,
being brought in discussions many times, including in the recent past
days, I replaced the static define of max branches limit with a core
parameter. It impacts the destination set stored in core and the uac
fields stored in transaction.
It can be set now with global parameter: max_branches
The old limit was 12, now it can be set in the range of 1 to 31.
Few aspects that I would like to discuss to get this refactored to fit
the best of common scenarios:
1) the 31 upper limit comes from tm cancelled branches bitmask, which
now is stored in an integer. Should be easy to get it to 63 (planned
after some testing that proves the concept used now is ok). Would it be
a need for even more?
2) would it make sense to specify the max number of branches per
transaction, in config, before creating the transaction? The upper limit
will be the max_branches value from the core.
3) thinking of common cases of what can be forked a lot, I thought that
we can a simplification of 2) by specifying two limits: one for initial
requests which are very likely to have many branches (think of initial
INVITE via LCR or location) and one for requests within dialog which are
likely to have one or very few branches (e.g., replicating BYE to a peer
server). Opinions?
The main benefit for 2) and 3) would be less memory usage.
Testing and feedback of the new max_branches parameter is very appreciated.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
