Hello,
I have set up my Asterisk server with Kamailio where Kamailio handles the user authentication as per http://kb.asipto.com/asterisk:realtime:kamailio-3.1.x-asterisk-1.6.2-astdb. It is working well, I am able to make calls, two way sound, etc. The problem I am facing is that after making a couple of calls the CPU utilization spikes to 100% and I see that RTPproxy is what is consuming this resource. Even after the call is completed it looks like RTPproxy is still active and the CPU usage stays at 100%, once I kill the rtp process the memory usage is back to normal. Can someone let me know how to correct this issue? Thank you.
A
Hello,
On 7/10/13 1:48 PM, Shankar wrote:
>
> Hello,
>
> The 'type' of 'expires' column in location table is 'datetime' whereas
> in table presentity the type is 'int'. Is there any reason behind this?
>
> I hope for the sake of uniformity 'expires' can be changed to 'datetime'.
>
it was developer choice for each module, the one being 'int' is storing
the unixtimestamp which is actually easier to use inside the code,
because it does not need conversion, not timezone adjustments. usrloc
(using location) is one of the very old modules, whereas presence was
developed many year after it.
Cheers,
Daniel
--
Daniel-Constantin Mierla - http://www.asipto.comhttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Greetings!
I've gotten kamailio configured and am attempting to connect with Jitsi.
I've added users to the kamailio MySQL database, and double checked that
they have passwords. But when I attempt to connect through Jitsi I get this
message:
"Authentication failed for user@domain (SIP). The password you entered is
not valid."
(where user and domain are my actual user name and domain name)
The fact that I'm getting a connection at all seems like a good sign, but I
don't know where it's going wrong with the password authentication step.
I admit I'm in over my head with kamailio, so any help would be greatly
appreciated.
Syslog, in case it's helpful:
Jul 7 16:30:51 Server /usr/sbin/kamailio[9474]: NOTICE: <core>
[main.c:743]: handle_sigs(): Thank you for flying kamailio!!!
Jul 7 16:30:51 Server /usr/sbin/kamailio[9501]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9497]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9496]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9495]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9491]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9490]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9487]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9484]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9483]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9482]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9481]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9480]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9479]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9478]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9477]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9476]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9502]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9486]: INFO: <core> [main.c:854]:
sig_usr(): INFO: signal 15 received
Jul 7 16:30:51 Server /usr/sbin/kamailio[9474]: ERROR: ctl [ctl.c:379]:
mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl:
Operation not permitted (1)
Jul 7 16:30:51 Server kamailio: INFO: tls [tls_init.c:385]:
init_tls_compression(): tls: init_tls: disabling compression...
Jul 7 16:30:51 Server kamailio: INFO: <core> [tcp_main.c:4846]:
init_tcp(): init_tcp: using epoll_lt as the io watch method (auto detected)
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: rr
[../outbound/api.h:49]: ob_load_api(): Failed to import bind_ob
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: rr [rr_mod.c:159]:
mod_init(): outbound module not available
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: usrloc [hslot.c:53]:
ul_init_locks(): locks array size 512
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: auth
[auth_mod.c:350]: mod_init(): auth: qop set, but nonce-count (nc_enabled)
support disabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_init.c:549]: init_tls_h(): tls: _init_tls_h: compiled with openssl
version "OpenSSL 1.0.1 14 Mar 2012" (0x1000100f), kerberos support: off,
compression: on
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_init.c:557]: init_tls_h(): tls: init_tls_h: installed openssl library
version "OpenSSL 1.0.1c 10 May 2012" (0x1000103f), kerberos support: off,
zlib compression: on#012 compiler: cc -fPIC -DOPENSSL_PIC -DZLIB
-DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN
-DTERMIO -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions
-Wl,-z,relro -Wa,--noexecstack -Wall -DOPENSSL_NO_TLS1_2_CLIENT
-DOPENSSL_MAX_TLS1_2_CIPHER_LENGTH=50 -DOPENSSL_BN_ASM_PART_WORDS
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM
-DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DRMD160_ASM -DAES_ASM -DVPAES_ASM
-DWHIRLPOOL_ASM -DGHASH_ASM
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: WARNING: tls
[tls_init.c:611]: init_tls_h(): tls: openssl bug #1491 (crash/mem leaks on
low memory) workaround enabled (on low memory tls operations will fail
preemptively) with free memory thresholds 9961472 and 4980736 bytes
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: <core>
[cfg/cfg_ctx.c:613]: cfg_set_now(): INFO: cfg_set_now():
tls.low_mem_threshold1 has been changed to 9961472
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: <core>
[cfg/cfg_ctx.c:613]: cfg_set_now(): INFO: cfg_set_now():
tls.low_mem_threshold2 has been changed to 4980736
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: <core>
[udp_server.c:179]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF
is initially 180224
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: <core>
[udp_server.c:230]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF
is finally 360448
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: <core>
[udp_server.c:179]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF
is initially 180224
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: <core>
[udp_server.c:230]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF
is finally 360448
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:187]: fill_missing(): TLSs<default>: tls_method=12
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:199]: fill_missing(): TLSs<default>:
certificate='/etc/kamailio/kamailio-selfsigned.pem'
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:206]: fill_missing(): TLSs<default>: ca_list='(null)'
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:213]: fill_missing(): TLSs<default>: crl='(null)'
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:217]: fill_missing(): TLSs<default>: require_certificate=0
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:224]: fill_missing(): TLSs<default>: cipher_list='(null)'
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:231]: fill_missing(): TLSs<default>:
private_key='/etc/kamailio/kamailio-selfsigned.key'
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:235]: fill_missing(): TLSs<default>: verify_certificate=0
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:238]: fill_missing(): TLSs<default>: verify_depth=9
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:576]: set_verification(): TLSs<default>: No client
certificate required and no checks performed
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:187]: fill_missing(): TLSc<default>: tls_method=9
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:199]: fill_missing(): TLSc<default>: certificate='(null)'
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:206]: fill_missing(): TLSc<default>: ca_list='(null)'
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:213]: fill_missing(): TLSc<default>: crl='(null)'
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:217]: fill_missing(): TLSc<default>: require_certificate=0
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:224]: fill_missing(): TLSc<default>: cipher_list='(null)'
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:231]: fill_missing(): TLSc<default>: private_key='(null)'
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:235]: fill_missing(): TLSc<default>: verify_certificate=0
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:238]: fill_missing(): TLSc<default>: verify_depth=9
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: tls
[tls_domain.c:579]: set_verification(): TLSc<default>: Server MAY present
invalid certificate
Jul 7 16:30:51 Server /usr/sbin/kamailio[9583]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9584]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9585]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9586]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9582]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9588]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9587]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9589]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9590]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9591]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9580]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9598]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9597]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9597]: INFO: ctl
[io_listener.c:225]: io_listen_loop(): io_listen_loop: using epoll_lt io
watch method (config)
Jul 7 16:30:51 Server /usr/sbin/kamailio[9602]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9603]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9601]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9604]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Jul 7 16:30:51 Server /usr/sbin/kamailio[9609]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Can someone let me know how I can increase the registration expiration time for my endpoint devises? Currently the expiration time is at 60 secs. Thank you.
U 2013/07/03 04:39:53.000710 71.252.xxx.xxx:1029 -> 10.164.62.166:5060
REGISTER sip:54.235.xx.xx SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.8:5060;branch=z9hG4bKa775b36b50d37b56ad4f012eb8f00401.
From: 1003 <sip:1003@54.235.xxx.xxx>;tag=995579843abc595234624.
To: 1003 <sip:1003@54.235.xxx.xxx>.
Call-ID: 612dd4ee0c06a49fa5b1eff9659d0A1a(a)192.168.1.8.
CSeq: 1210 REGISTER.
Contact: <sip:1003@192.168.1.8>.
Max-Forwards: 70.
Authorization: Digest nonce="UdOsRFHTqxj7x8IySw9CzOb1262xg37B",realm="54.235.xxx.xxx",response="122d1065528ac5620b8f0855d30bf297",uri="sip:54.235.xxx.xxx:5060",username="1003".
Expires: 60.
User-agent: ET747.
Content-Length: 0.
Arun
Hello,
The 'type' of 'expires' column in location table is 'datetime' whereas in
table presentity the type is 'int'. Is there any reason behind this?
I hope for the sake of uniformity 'expires' can be changed to 'datetime'.
Please clarify.
Regards,
Shankar
Hi list,
I have a loadbalancer before sipproxies. I call t_reley() on the dispatcher to forward requests to destinations.
All goes well under low load.
But when load goes up to 500 requests/s, the loadbalancer still sends requests via only one tcp connection. This maxes out the tcp write queue.
Of course I can increase the 'tcp_conn_wq_max' value but it doesn't solve the root problem.
How do I make the loadbalancer start a new tcp connection to the destination when existing one becomes too busy? (Is it possible?)
Regards,
Allen
Hi Gertjan,
are you sure, you loaded Kamailio's Dialog Module? In 3.3 there are
two dialog modules: One of old SER and one of Kamailio...
Did you compile Kamailio from the GIT branch or did you use any sort
of prebuilt packages? Can you send the output of "kamailio -V"?
Thanks,
Carsten
2013/7/10 Gertjan Wolzak <g.wolzak(a)foize.com>:
>
>
> Hello All,
>
>
>
> I am trying to have all dialogs terminated after one hour.
>
>
>
> So I have set the following parameters
>
>
>
> modparam("dialog", "enable_stats", 1)
>
> modparam("dialog", "profiles_with_value", "caller")
>
> modparam("dialog", "dlg_flag", 24)
>
> modparam("dialog", "dlg_match_mode", 1)
>
> modparam("dialog", "default_timeout", 3600)
>
> modparam("dialog", "send_bye", 1)
>
>
>
> But when I check the Kamailio configuration I get the following error:
>
>
>
> # kamailio -c
>
> loading modules under
> /usr/local/lib/kamailio/modules_k/:/usr/local/lib/kamailio/modules/
>
> 0(10335) ERROR: <core> [modparam.c:151]: set_mod_param_regex: parameter
> <send_bye> not found in module <dialog>
>
> 0(10335) : <core> [cfg.y:3532]: parse error in config file
> /usr/local/etc/kamailio/kamailio.cfg, line 495, column 33: Can't set module
> parameter
>
> ERROR: bad config file (1 errors)
>
>
>
> Does anyone have an idea where I go wrong…..?
>
>
>
> Rgds,
>
>
>
> Gertjan Wolzak
>
>
> _______________________________________________
> 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
>
--
Carsten Bock
CEO (Geschäftsführer)
ng-voice GmbH
Schomburgstr. 80
D-22767 Hamburg / Germany
http://www.ng-voice.com
mailto:carsten@ng-voice.com
Office +49 40 34927219
Fax +49 40 34927220
Sitz der Gesellschaft: Hamburg
Registergericht: Amtsgericht Hamburg, HRB 120189
Geschäftsführer: Carsten Bock
Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
http://www.ng-voice.com/imprint/
Sorry....
Important... Kamailio version 3.3
Rgds,
Gertjan
From: sr-users-bounces(a)lists.sip-router.org
[mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Gertjan Wolzak
Sent: woensdag 10 juli 2013 8:58
To: sr-users(a)lists.sip-router.org
Subject: [SR-Users] send_bye dialog parameter
Hello All,
I am trying to have all dialogs terminated after one hour.
So I have set the following parameters
modparam("dialog", "enable_stats", 1)
modparam("dialog", "profiles_with_value", "caller")
modparam("dialog", "dlg_flag", 24)
modparam("dialog", "dlg_match_mode", 1)
modparam("dialog", "default_timeout", 3600)
modparam("dialog", "send_bye", 1)
But when I check the Kamailio configuration I get the following error:
# kamailio -c
loading modules under
/usr/local/lib/kamailio/modules_k/:/usr/local/lib/kamailio/modules/
0(10335) ERROR: <core> [modparam.c:151]: set_mod_param_regex: parameter
<send_bye> not found in module <dialog>
0(10335) : <core> [cfg.y:3532]: parse error in config file
/usr/local/etc/kamailio/kamailio.cfg, line 495, column 33: Can't set module
parameter
ERROR: bad config file (1 errors)
Does anyone have an idea where I go wrong...?
Rgds,
Gertjan Wolzak