Dear Kamailio Team ,
I have installed Kamailio on Ubuntu 18.04 with SIREMIS and its working fine
. But I want to use the Dispatcher module for load balancing . When enabling
the dispatcher module Kamailio is not starting up and giving error in
syslog. Please check below the logs for your reference.
root@CICTPH01LLB01:/usr/lib/x86_64-linux-gnu/kamailio/modules# kamailio -E
0(19009) INFO: <core> [core/sctp_core.c:74]: sctp_core_check_support(): SCTP
API not enabled - if you want to use it, load sctp module
Listening on
udp: 127.0.0.1:5060
udp: 192.168.180.200:5060
tcp: 127.0.0.1:5060
tcp: 192.168.180.200:5060
Aliases:
tcp: CICTPH01LLB01:5060
tcp: localhost:5060
udp: CICTPH01LLB01:5060
udp: localhost:5060
0(19009) INFO: <core> [core/tcp_main.c:4735]: init_tcp(): using epoll_lt as
the io watch method (auto detected)
0(19011) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import
bind_ob - maybe module is not loaded
0(19011) INFO: rr [rr_mod.c:177]: mod_init(): outbound module not available
0(19011) INFO: auth [auth_mod.c:347]: mod_init(): qop set, but nonce-count
(nonce_count) support disabled
0(19011) INFO: <core> [main.c:2683]: main(): processes (at least): 32 - shm
size: 67108864 - pkg size: 8388608
0(19011) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer():
SO_RCVBUF is initially 212992
0(19011) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer():
SO_RCVBUF is finally 425984
0(19011) INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer():
SO_RCVBUF is initially 212992
0(19011) INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer():
SO_RCVBUF is finally 425984
21(19044) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a
new child 0/19044
root@CICTPH01LLB01:/usr/lib/x86_64-linux-gnu/kamailio/modules# 22(19053)
INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using
epoll_lt io watch method (config)
============================================================================
=====================================
Feb 18 18:33:19 CICTPH01LLB01 systemd[1]: Starting Kamailio (OpenSER) - the
Open Source SIP Server...
Feb 18 18:33:19 CICTPH01LLB01 kamailio: INFO: <core> [core/sctp_core.c:74]:
sctp_core_check_support(): SCTP API not enabled - if you want to use it,
load sct
p module
Feb 18 18:33:19 CICTPH01LLB01 kamailio: INFO: <core> [core/tcp_main.c:4735]:
init_tcp(): using epoll_lt as the io watch method (auto detected)
Feb 18 18:33:19 CICTPH01LLB01 kamailio[18815]: Listening on
Feb 18 18:33:19 CICTPH01LLB01 kamailio[18815]: udp:
127.0.0.1:5060
Feb 18 18:33:19 CICTPH01LLB01 kamailio[18815]: udp:
192.168.180.200:5060
Feb 18 18:33:19 CICTPH01LLB01 kamailio[18815]: tcp:
127.0.0.1:5060
Feb 18 18:33:19 CICTPH01LLB01 kamailio[18815]: tcp:
192.168.180.200:5060
Feb 18 18:33:19 CICTPH01LLB01 kamailio[18815]: Aliases:
Feb 18 18:33:19 CICTPH01LLB01 kamailio[18815]: tcp:
CICTPH01LLB01:5060
Feb 18 18:33:19 CICTPH01LLB01 kamailio[18815]: tcp:
localhost:5060
Feb 18 18:33:19 CICTPH01LLB01 kamailio[18815]: udp:
CICTPH01LLB01:5060
Feb 18 18:33:19 CICTPH01LLB01 kamailio[18815]: udp:
localhost:5060
Feb 18 18:33:19 CICTPH01LLB01 /usr/sbin/kamailio[18817]: INFO: rr
[../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe
module is not loaded
Feb 18 18:33:19 CICTPH01LLB01 /usr/sbin/kamailio[18817]: INFO: rr
[rr_mod.c:177]: mod_init(): outbound module not available
Feb 18 18:33:19 CICTPH01LLB01 /usr/sbin/kamailio[18817]: INFO: auth
[auth_mod.c:347]: mod_init(): qop set, but nonce-count (nonce_count) support
disabled
Feb 18 18:33:19 CICTPH01LLB01 /usr/sbin/kamailio[18817]: INFO: <core>
[main.c:2683]: main(): processes (at least): 32 - shm size: 67108864 - pkg
size: 8388608
Feb 18 18:33:19 CICTPH01LLB01 /usr/sbin/kamailio[18817]: INFO: <core>
[core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially
212992
Feb 18 18:33:19 CICTPH01LLB01 /usr/sbin/kamailio[18817]: INFO: <core>
[core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally
425984
Feb 18 18:33:19 CICTPH01LLB01 /usr/sbin/kamailio[18817]: INFO: <core>
[core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially
212992
Feb 18 18:33:19 CICTPH01LLB01 /usr/sbin/kamailio[18817]: INFO: <core>
[core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally
425984
Feb 18 18:33:19 CICTPH01LLB01 /usr/sbin/kamailio[18817]: ERROR: <core>
[core/tcp_main.c:2863]: tcp_init(): bind(d, 0x7f81495f1efc, 16) on
127.0.0.1:5060 : Address already in use
Feb 18 18:33:19 CICTPH01LLB01 /usr/sbin/kamailio[18817]: INFO: <core>
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Feb 18 18:33:19 CICTPH01LLB01 systemd[1]: kamailio.service: Control process
exited, code=exited status=255
Feb 18 18:33:19 CICTPH01LLB01 systemd[1]: kamailio.service: Failed with
result 'exit-code'.
Feb 18 18:33:19 CICTPH01LLB01 systemd[1]: Failed to start Kamailio (OpenSER)
- the Open Source SIP Server.
Feb 18 18:33:20 CICTPH01LLB01 systemd[1]: kamailio.service: Service hold-off
time over, scheduling restart.
Feb 18 18:33:20 CICTPH01LLB01 systemd[1]: kamailio.service: Scheduled
restart job, restart counter is at 5.
Feb 18 18:33:20 CICTPH01LLB01 systemd[1]: Stopped Kamailio (OpenSER) - the
Open Source SIP Server.
Feb 18 18:33:20 CICTPH01LLB01 systemd[1]: kamailio.service: Start request
repeated too quickly.
Feb 18 18:33:20 CICTPH01LLB01 systemd[1]: kamailio.service: Failed with
result 'exit-code'.
Feb 18 18:33:20 CICTPH01LLB01 systemd[1]: Failed to start Kamailio (OpenSER)
- the Open Source SIP Server.
Regards
Amul Tyagi | Technical Head - Major Accounts & Support
Globe : <tel:+63%20917%20488%200130> +63-9174880130
Skype : amultyagi365
Email : <mailto:am@lgorithmsolutions.com> am(a)lgorithmsolutions.com
Hello,
Kamailio version 5.4.4.
Kamailio segmentation fault after kamctl rpc dialplan.dump <dpid>,
when dialplan includes variables in the replacement expression (repl_exp)
field.
Please see attached corefile.
Thank you,
Julia.
Hi Team,
Kamailio 5.2 getting crashed in tls_accept. Can someone help over here.
#0 0x00007f1b135c09b2 in EVP_DecryptUpdate () from
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
#1 0x00007f1b135f3034 in ?? () from
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
#2 0x00007f1b135f36a3 in ?? () from
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
#3 0x00007f1b135f4051 in RAND_DRBG_reseed () from
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
#4 0x00007f1b135f457d in RAND_DRBG_generate () from
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
#5 0x00007f1b135f46f1 in RAND_DRBG_bytes () from
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
#6 0x00007f1b1378649e in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1
#7 0x00007f1b13777f5f in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1
#8 0x00007f1b13763f34 in SSL_do_handshake () from
/usr/lib/x86_64-linux-gnu/libssl.so.1.1
#9 0x00007f1acf246fce in tls_accept (c=0x7f1ad35fdc60,
error=0x7ffc238dd1dc) at tls_server.c:411
#10 0x00007f1acf2503a3 in tls_read_f (c=0x7f1ad35fdc60,
flags=0x7ffc238dd50c) at tls_server.c:1097
#11 0x0000559ac2ec9b46 in tcp_read_headers (c=0x7f1ad35fdc60,
read_flags=0x7ffc238dd50c) at core/tcp_read.c:462
#12 0x0000559ac2eced1c in tcp_read_req (con=0x7f1ad35fdc60,
bytes_read=0x7ffc238dd514, read_flags=0x7ffc238dd50c) at
core/tcp_read.c:1348
#13 0x0000559ac2ed5442 in handle_io (fm=0x7f1b13d2cef8, events=8193,
idx=-1) at core/tcp_read.c:1715
#14 0x0000559ac2ec424a in io_wait_loop_epoll (h=0x559ac3153f80 <io_w>, t=2,
repeat=0) at core/io_wait.h:1073
#15 0x0000559ac2ed6df4 in tcp_receive_loop (unix_sock=75) at
core/tcp_read.c:1829
#16 0x0000559ac2db8685 in tcp_init_children () at core/tcp_main.c:4802
#17 0x0000559ac2cb6867 in main_loop () at main.c:1714
#18 0x0000559ac2cbd6af in main (argc=15, argv=0x7ffc238ddb88) at main.c:2644
Hi, how are you. I got this mail on github kamalio page. Here is my problem detail :
Everytime when my vps reboot, i got a problem with my kamalio. It seems like service can't start. So i have to restart it myself by using "kamctl restart". When i enter this command, i got an error on screen. Here is error detail :
ERROR: PID file /var/run/kamailio/kamailio.pid does not exist -- Kamailio start failed
How can i solve it ?
Happy Friday!
To clean up contacts that have sent requests to unregister (Expires: 0) I am executing the following after a 200 OK response from the upstream server:
reg_fetch_contacts("location", "$fu", "un_reg");
xlog("L_INFO", "Removing unregistered contact From: $si To: $tu Ruid: $ulc(un_reg=>ruid)\n");
unregister("location", "$fu", "$ulc(un_reg=>ruid)”);
This produces the desired result when there is only one contact per AoR, but when multiple contacts are present, it seems to delete the first ruid (which makes sense as I am only providing the $fu).
So, the question, can I select the contact by call-id or some other unique identifier specific to the desired contact that I can grab from the transaction? Reading the reg_fetch_contact and unregister docs, they do not seem to provide for selection beyond uri.
- Charles
I'm returning to this thread, since after some more testing, I found that
loose_route() does not (at least always) detect that a pair of route
headers denotes itself.
In config I have defined:
listen=tls:192.x.x.x:8005 name "ext_tls"
modparam("rr", "sockname_mode", 1)
and Route header looks like this:
ROUTE: <sip:tenantX.teams.tutpro.com:8005;transport=tls;r2=on;sn=ext_tls;lr;n1;avp=savp;pm=0>,<sip:192.x.x.x:5070;transport=tcp;r2=on;lr;n1;avp=savp;pm=0>
Then this code:
loose_route();
if ($du != "") {
xinfo("Routing in-dialog $rm <$ru> from <$fu> to <$du> based on route uri\n");
}
produces to syslog:
INFO: Routing in-dialog ACK <...> from <...> to <...> based on route uri
-- Juha
Hello !
I will have to connect my Kamailio proxies to a routing server which will
receive INVITE and replies with 302 and a list of a SIP Contact where
(gateways, IP, prefixes or whatever we want) the call must be routed to.
I'm wondering what would be the best approach to handle with Kamalio those
302 and then proceed with the routing?
For the moment, we use to work with carrierroute. But, since the redirect
server will take the routing decision, I believe that carrierroute will no
be useful anymore.
Thank you for your inputs/experience.
Regards,
Igor.
--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus
Hello,
I started from scratch by getting this Docker image:
https://hub.docker.com/layers/kamailio/kamailio/5.4.4-trusty/images/sha256-…
Then running:
docker pull kamailio/kamailio:5.4.4-trusty
Then starting an container with the command:
docker run -d --name mykamailio -h mykamailio -p "5060-5061:5060-5061" -p "5060:5060/udp" -p "5064-5065:5064-5065" -p "5064-5065:5064-5065/udp" -p "7000-7001:7000-7001" -p "7000:7000/udp" -e "KAMAILIO_LOG_LEVEL=info" -e "KAMAILIO_ENABLE_ROLES=websockets,message,presence_query,presence_sync,presence_notify_sync,registrar_sync" -e "RABBITMQ_HOSTS=rabbitmq.local" --cap-add IPC_LOCK --cap-add SYS_NICE --cap-add SYS_RESOURCE --cap-add NET_RAW kamailio/kamailio:5.4.4-trusty
I get into container using cli and ran:
Kamtcl start
Then container stopped with this log:
Listening on
udp: 127.0.0.1:5060
udp: 172.17.0.4:5060
tcp: 127.0.0.1:5060
tcp: 172.17.0.4:5060
Aliases:
tcp: mykamailio:5060
tcp: localhost:5060
0(1) INFO: <core> [core/tcp_main.c:4984]: init_tcp(): using epoll_lt as the io watch method (auto detected)
udp: mykamailio:5060
udp: localhost:5060
0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded
0(1) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available
0(1) INFO: <core> [main.c:2854]: main(): processes (at least): 33 - shm size: 67108864 - pkg size: 8388608
0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992
0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984
0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992
0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984
21(28) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/28
23(30) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config)
0(1) ALERT: <core> [main.c:780]: handle_sigs(): child process 77 exited normally, status=255
0(1) INFO: <core> [main.c:808]: handle_sigs(): terminating due to SIGCHLD
2(9) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
1(8) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
4(11) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
5(12) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
7(14) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
10(17) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
8(15) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
9(16) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
3(10) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
11(18) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
14(21) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
17(24) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
15(22) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
12(19) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
18(25) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
6(13) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
13(20) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
16(23) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
23(30) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
22(29) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
19(26) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
21(28) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
20(27) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
32(39) CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 13
32(39) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
25(32) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
27(34) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
29(36) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
30(37) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
26(33) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
28(35) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
31(38) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
24(31) INFO: <core> [main.c:863]: sig_usr(): signal 15 received
0(1) ERROR: ctl [ctl.c:390]: mod_destroy(): ERROR: ctl: could not delete unix socket /var/run/kamailio//kamailio_ctl: No such file or directory (2)
0(1) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Any idea about what could be the problem?
Thank you in advance
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional.
Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje.
Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.
Hi Guys,
Hope all are well?
We are looking to implement kamailio with cockroachdb due to the advantages it gives us in terms of postgres management and clustering.
I can see from a previous string http://sip-router.1086192.n5.nabble.com/CockroachDB-and-Kamailio-td189233.h… that someone has attempted this and even created their own branch.
Has any further work been done on this, and if so has anyone got any advice/tips relating to it? As I am nervous about potentially using a branch and not a general release of kamailio moving forwards.
I appreciate you cant support all database types but I would just be interested to hear people’s thoughts on the topic.
Many thanks!
Jon
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10