sr-users January 2018

sr-users@lists.kamailio.org

83 participants
123 discussions

OT: question about codetriage
by Daniel-Constantin Mierla 08 Jan '18

08 Jan '18

Hello, anyone here familiar with codetriage service? We got a pull request to refer to it from Kamailio readme.md file: - https://github.com/kamailio/kamailio/pull/1389 The link is to: - https://www.codetriage.com/kamailio/kamailio Which I guess is created by the one who did the pull request. The pull request comments has few references to other projects, including Rails, but as I am not familiar with the service, I thought of asking here and see if others had to deal with and what's the experience. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - March 5-7, 2018, Berlin - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 0

Error in parse json documents in kamailio with jansson module
by Mojtaba 08 Jan '18

08 Jan '18

Hello, I used ndbmongo module in kamailio, I used mongodb_find command to get some data from mongo, like this: if(mongodb_find("sermongo", "Asterisk", "user", "{ \"number\" : \"$fU\" }", "res")) { xlog("L_INFO", "Data from mongodb is \" $mongodb(res=>value) \" \n"); $var(data) = $mongodb(res=>value); } The result in syslog is like this: Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} INFO: <script>: user Data from mongodb is " { "_id" : { "$oid" : "5916def36803fa48468b456b" }, "user_type" : "SIP", "context" : "main_routing", "deny" : "0.0.0.0/0.0.0.0", "call_record" : "no", "dtmfmode" : "rfc2833", "canreinvite" : "no", "directmedia" : "no", "host" : "dynamic", "type" : "friend", "nat" : "force_rport,comedia", "port" : "5060", "qualify" : "yes", "callgroup" : "1", "pickupgroup" : "1", "permit" : "0.0.0.0/0.0.0.0", "callcounter" : "yes", "faxdetect" : "no", "call_limit" : "", "name" : "1000", "number" : "1000", "cid_number" : "1000", "secret" : "123123", "date" : { "$date" : 1494671091612 }, "more_options" : "" } " Now i need to get just some keys like "context" from json and save them in PV, i used jansson2.10 for doing this job, like this: jansson_get("user.context", $var(jdata), "$var(context)"); but i have this error in syslog: Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} ERROR: <core> [core/pvapi.c:903]: pv_parse_spec2(): error searching pvar "oid" Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} ERROR: <core> [core/pvapi.c:1107]: pv_parse_spec2(): wrong char [d/100] in [$oid] at [3 (0)] Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} ERROR: <core> [core/sr_module.c:1268]: fix_param(): bad PVE format: "{ "_id" : { "$oid" : "5916def36803fa48468b456b" }, "user_type" : "SIP", "context" : "main_routing", "deny" : "0.0.0.0/0.0.0.0", "call_record" : "no", "dtmfmode" : "rfc2833", "canreinvite" : "no", "directmedia" : "no", "host" : "dynamic", "type" : "friend", "nat" : "force_rport,comedia", "port" : "5060", "qualify" : "yes", "callgroup" : "1", "pickupgroup" : "1", "permit" : "0.0.0.0/0.0.0.0", "callcounter" : "yes", "faxdetect" : "no", "call_limit" : "", "name" : "1000", "number" : "1000", "cid_number" : "1000", "secret" : "123123", "date" : { "$date" : 1494671091612 }, "more_options" : "" }" Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} ERROR: <core> [core/mod_fix.c:564]: fixup_spve_null(): Cannot convert function parameter 1 to spve Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} ERROR: <core> [core/action.c:1139]: do_action(): runtime fixup failed for jansson_get param 2 Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} ERROR: <core> [core/action.c:1518]: do_action(): run action error at: /usr/local/etc/kamailio/kamailio.cfg:990 Jan 8 07:23:36 ubuntu14 /usr/local/sbin/kamailio[12127]: {1 2 INVITE MDRlMjRlNGVjZGY1Y2JkYjA5OGM2ZTg1ZTFjZTk0Nzg.} ERROR: <script>: Send SIP message to Simotel <192.168.122.1:36854> Let me know how i could fixed this Error in regard of [$oid]? Thanks with regards. -- --Mojtaba Esfandiari.S

2 1

Kamailio World 2018 - Call for Presentations
by Daniel-Constantin Mierla 08 Jan '18

08 Jan '18

Hello, I would like to announce that Call for Presentations at Kamailio World 2018 is now open. You can submit your proposal or see more details at: - https://www.kamailioworld.com/k06/call-for-speakers/ The 6th edition of the event takes place again in Berlin, Germany, during May 14-16, 2018. Expect over 150 participants, developers and community members as well as representatives from other popular open source VoIP projects such as Asterisk or FreeSwitch. Looking forward to meeting many of you there! Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 1

Cnxcc doesn't update amount values in redis
by Donat Zenichev 05 Jan '18

05 Jan '18

Hi community. Have a problem with cnxcc call monitoring. __set_max_credit() allocates new call as expected: "DEBUG: cnxcc [cnxcc_mod.c:444]: __dialog_created_callback(): Flag is not set for this message. Ignoring DEBUG: cnxcc [cnxcc_mod.c:1569]: __set_max_credit(): Setting up new call for client [2], max-credit[0.100000], cost-per-sec[0.010000], initial-pulse [6], final-pulse [6], call-id[2f77fd103d0bfa28718d896876b373fe@b2b.user.agent:50600] DEBUG: cnxcc [cnxcc_mod.c:1470]: set_ctrl_flag(): Flag set! DEBUG: cnxcc [cnxcc_redis.c:313]: redis_get_int(): Got INT value: concurrent_calls=0i DEBUG: cnxcc [cnxcc_redis.c:68]: redis_get_or_create_credit_data(): credit_data with ID=[2] DOES NOT exist in the cluster, creating it... DEBUG: cnxcc [cnxcc_redis.c:92]: redis_insert_credit_data(): Inserting credit_data_t using ID [2] DEBUG: cnxcc [cnxcc_mod.c:1125]: __get_or_create_credit_data_entry(): Credit entry didn't exist. Allocated new entry [0x7f17668f6d70] DEBUG: cnxcc [cnxcc_mod.c:1255]: __alloc_new_call_by_money(): New call allocated for client [2]". So that I can see values inside redis: redis.callision.info:6389> HGETALL cnxcc:money:2 1) "concurrent_calls" 2) "0" 3) "consumed_amount" 4) "0.000000" 5) "ended_calls_consumed_amount" 6) "0.000000" 7) "max_amount" 8) "0.000000" 9) "number_of_calls" 10) "1" 11) "type" 12) "1" But cnxcc doesn't update credit amount during the call. modparam("debugger", "mod_level", "cnxcc=4") but there are no rows in kamailio log like: "DEBUG: cnxcc [cnxcc_check.c:94]: check_calls_by_money(): ec=0.000000, ca=0.600000, ca2=0.600000 DEBUG: cnxcc [cnxcc_check.c:107]: check_calls_by_money(): Client [some_client] | Ended-Calls-Credit-Spent: 0.000000 TotalCredit/MaxCredit: 0.600000/3.000000". cnxcc parameters: modparam("cnxcc", "dlg_flag", FLG_DLG) modparam("cnxcc", "redis", "addr=redis.youwillnever.find;port=6389;db=0") modparam("cnxcc", "credit_check_period", 1) function that performs credit setup: if (!cnxcc_set_max_credit("$var(setid)","$var(credit)","$var(cost_per_sec)","$var(i_pulse)","$var(f_pulse)")) { xlog("L_WARN", "----- cnxcc: $fU - Error setting up credit control - R=$ru ID=$ci\n"); sl_send_reply("402", "Payment Required"); } Why is it so? And as see, all values are set zero. Seems to be problem with redis inserts. Any ideas are highly appreciated. Thanks. -- -- BR, Donat Zenichev Wnet VoIP team Tel Ukraine: +380(44) 5-900-800 Tel USA: +164(67) 8-174-17 https://w-net.us/ <http://wnet.ua>

2 1

NOTIFY generation for REFER
by Konstantin Tumalevich 05 Jan '18

05 Jan '18

I try to build custom attended transfer logick with kamailio and asterisk. My backend can do all work (include interconnect between asterisk servers), so I need to fully handle REFER in kamailio. But I can't send back NOTIFY message with the result of a transfer. Is any way to do this logic inside kamailio or I need to write external SIP service? My route looks like: if(!route(FROM_NODE)) { if(is_method("REFER")) { xlog("L_NOTICE", "Got REFER in call ci:$ci for $(hdr(Refer-To){nameaddr.uri})"); sl_send_reply("202", "Accepted [1]"); # HERE I MAKE async request and want to send NOTIFY back exit; } } -- Skype: konstantin.tumalevich

2 1

BUG: tls [tls_server.c:1229]: tls_read_f(): SSL_ERROR_WANT_READ but data still in the rbio (0x7ffd354fcd30, 8 bytes at 461)
by Abdoul Osséni 05 Jan '18

05 Jan '18

Hello Dear, I use Kamailio 5.1.0 on Linux server: root@sip-africallshop-com:~# kamailio -V version: kamailio 5.1.0 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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: unknown compiled with gcc 4.9.2 I have sometimes the following logs: Dec 14 19:22:16 sd-110402 /usr/local/sbin/kamailio[24197]: BUG: tls [tls_server.c:1229]: tls_read_f(): SSL_ERROR_WANT_READ but data still in the rbio (0x7ffd354fcd30, 8 bytes at 461) Dec 20 10:46:32 sd-110402 /usr/local/sbin/kamailio[24197]: BUG: tls [tls_server.c:1229]: tls_read_f(): SSL_ERROR_WANT_READ but data still in the rbio (0x7ffd354fcd30, 8 bytes at 8) Dec 22 11:02:49 sd-110402 /usr/local/sbin/kamailio[24212]: BUG: tls [tls_server.c:1229]: tls_read_f(): SSL_ERROR_WANT_READ but data still in the rbio (0x7ffd354fcd30, 8 bytes at 3357) Does anybody can explain me these logs? Thanks. Abdoul OSSENI

2 1

One way video using Kamailio, WebRTC, and Asterisk
by Wilkins, Steve 05 Jan '18

05 Jan '18

First I want to give Denys a huge shout-out for all of the help he has given me. It is wonderful that boards like this exists and people are so willing to help a newbie learn. I am on what I am hoping is my last major issue with WebRTC<=>WebRTC calls (using tryit-jssip Chrome or Firefox). I am using Kamailio 5, and Asterisk 15 (pjsip). I am making calls between two WebRTC clients - Client1, and Client2 (using tryit-jssip) Problem: If Client1 calls Client2, and Client2 'ANSWERS', I only have audio/video on Client1. Client2 gets no audio/video, but is connected. If I switch things up and call Client1 from Client2, the same thing happens (Client2 has audio/video and Client1 does not); I can only get audio/video on the calling laptop; the called laptop has no audio/video, but is connected. I see no errors in any of the logs. I am hoping that someone out there has seen this behavior before and has an idea as to the cause and possible solution. Thank you, -Steve

2 1

Is it possible to inject variables into transaction scope
by voipspace voipspace 05 Jan '18

05 Jan '18

2 1

Critical Error
by Nicolas Breuer 04 Jan '18

04 Jan '18

Hello, I got this error when passing a call. CRITICAL: dialog [dlg_hash.c:955]: log_next_state_dlg(): bogus event 5 in state 1 for dlg 0x7f7a17848bd8 [3582:11978] with clid 'ae27f53121fe6d84c6845dedcf2e2793' and tags 'f68d2151b8411946' '' Any ideas ? This is a bug ? Never seen that error before,

3 10

Kamailio Remote User Registration
by Hildah.Ochieng＠deutschebahn.com 04 Jan '18

04 Jan '18

Dear Kamailio experts, I would like to able to register one kamailio (localuser) in another another kamailio (remoteuser) when the jitsi sip account "localuser@localdomain" is online. Using the UAC module for remote registration the uacreg table's l_username and l_domain attributes are set to refer to the local kamailio while the r_username and r_domain attributes refer to the remote kamailio. I would appreciate your advice on the missing piece of the puzzle. Following is my configuration of the "local" kamailio. The "remote" kamailio.cfg is unchanged. /etc/kamailio/kamailio.cfg loadmodule "db_text.so" loadmodule "uac.so" modparam("uac", "reg_timer_interval", 30) modparam("uac", "reg_retry_interval", 60) modparam("uac", "reg_contact_addr","xx.xx.xx.xx:5060") modparam("uac", "reg_db_table", "uacreg") modparam("uac", "reg_db_url", "text:///etc/kamailio/dbtext") /etc/kamailio/dbtext/uacreg l_uuid(string) l_username(string) l_domain(string) r_username(string) r_domain(string) realm(string) auth_username(string) auth_password(string) auth_proxy(string) expires(int) flags(int) reg_delay (int) 11111111:localuser:localdomain:remoteuser:remotedomain:remoteuser::::360:4:30 Thanks Hildah

2 1

Kamailio fail to start with db_mongodb and ndb_mongodb modules
by Abdul Basit 04 Jan '18

04 Jan '18

Hi, I am trying to setup mongo db as database engine for kamailio as described at <http://www.kamailio.org/wiki/tutorials/kamailio-and-mongodb> http://www.kamailio.org/wiki/tutorials/kamailio-and-mongodb and https://telerain.com/kamailio OS: Debian GNU/Linux 8.10 (jessie) MongoDB server version: 3.4.10 mongo-c-driver-1.9.0.tar.gz compiled with ./configure --disable-static --disable-silent-rules --enable-debug-symbols --enable-ssl=no --enable-sasl=yes --with-libbson=bundled --enable-optimizations --disable-automatic-init-and-cleanup version: kamailio 5.0.4 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, 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: unknown compiled on 20:45:44 Dec 27 2017 with gcc 4.9.2 include_modules= utils app_lua db_postgres json evapi db_mongodb ndb_mongodb Kamailio is crashing with segfault as soon as it try to load libmongo-c Dec 28 04:44:14 sipserver systemd[1]: Starting Kamailio (OpenSER) - the Open Source SIP Server... Dec 28 04:44:14 sipserver kamailio: INFO: <core> [core/sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Dec 28 04:44:14 sipserver kamailio: INFO: <core> [core/tcp_main.c:4671]: init_tcp(): using epoll_lt as the io watch method (auto detected) Dec 28 04:44:14 sipserver kamailio[11685]: Listening on Dec 28 04:44:14 sipserver kamailio[11685]: udp: 127.0.0.1:5060 Dec 28 04:44:14 sipserver kamailio[11685]: udp: 192.168.10.20:5060 Dec 28 04:44:14 sipserver kamailio[11685]: tcp: 127.0.0.1:5060 Dec 28 04:44:14 sipserver kamailio[11685]: tcp: 192.168.10.20:5060 Dec 28 04:44:14 sipserver kamailio[11685]: Aliases: Dec 28 04:44:14 sipserver kamailio[11685]: tcp: localhost:5060 Dec 28 04:44:14 sipserver kamailio[11685]: udp: localhost:5060 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: INFO: rr [rr_mod.c:175]: mod_init(): outbound module not available Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: INFO: <core> [core/udp_server.c:203]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: INFO: <core> [core/udp_server.c:203]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Dec 28 04:44:14 sipserver systemd[1]: Started Kamailio (OpenSER) - the Open Source SIP Server. Dec 28 04:44:14 sipserver kernel: [53109.390171] show_signal_msg: 20 callbacks suppressed Dec 28 04:44:14 sipserver kernel: [53109.390176] kamailio[11696] segfault at 78 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] Dec 28 04:44:14 sipserver kernel: [53109.390753] kamailio[11694] segfault at 78 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] Dec 28 04:44:14 sipserver kernel: [53109.391605] kamailio[11698] segfault at 78 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] Dec 28 04:44:14 sipserver kernel: [53109.392073] kamailio[11701] segfault at 78 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] Dec 28 04:44:14 sipserver kernel: [53109.392408] kamailio[11692] segfault at 78 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] Dec 28 04:44:14 sipserver kernel: [53109.392497] kamailio[11700] segfault at 38 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] Dec 28 04:44:14 sipserver kernel: [53109.392761] kamailio[11703] segfault at 78 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] Dec 28 04:44:14 sipserver kernel: [53109.392825] kamailio[11697] segfault at 38 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] Dec 28 04:44:14 sipserver kernel: [53109.393098] kamailio[11705] segfault at 78 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] Dec 28 04:44:14 sipserver kernel: [53109.393147] kamailio[11699] segfault at 38 ip 00007f690c0e6e98 sp 00007ffcde1a4770 error 6 in libmongoc-1.0.so.0.0.0[7f690c0ca000+6e000] Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11689 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11688 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 14 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 15 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 16 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 17 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 18 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 19 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 20 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 21 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 22 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 23 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 24 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 25 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11690 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11691 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11692 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11693 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11694 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11695 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11696 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11697 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11698 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11699 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11700 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11701 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11702 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11703 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11704 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11705 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 26 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 27 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11706 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 28 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 29 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11707 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 30 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 31 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11708 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 32 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 33 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11709 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 34 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 5 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11710 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 9 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 35 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11711 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 37 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 39 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11712 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 41 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 43 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11713 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 45 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 47 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11714 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11715 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11716 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:743]: handle_sigs(): child process 11717 exited by a signal 11 Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: ALERT: <core> [main.c:746]: handle_sigs(): core was not generated Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: INFO: <core> [main.c:768]: handle_sigs(): terminating due to SIGCHLD Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11718]: INFO: <core> [main.c:823]: sig_usr(): signal 15 received Dec 28 04:44:14 sipserver /usr/local/sbin/kamailio[11687]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Dec 28 04:44:14 sipserver systemd[1]: kamailio.service: main process exited, code=exited, status=1/FAILURE Dec 28 04:44:14 sipserver systemd[1]: Unit kamailio.service entered failed state. As I tried googling the issue and found few issues with tls connection. I set in default kamailio.cfg but still facing the saem issue. enable_tls=no ... loadmodule "ndb_mongodb.so" modparam("ndb_mongodb", "server", "name=cgr91rc8;uri='mongodb://localhost/kamailio'") Its mongodb default installation and its accessible without any auth yet. Please suggest the way farward. -- regards, abdul basit

3 6

TLS cipher suites
by Steve 03 Jan '18

03 Jan '18

I have a question about deploying TLSv1.2 with Kamailio 4.3.4-1 on a Lubuntu 16.4.3 desktop environment. I changed the Kamailio default /tls.cfg/ file under the section [server:default] to “method=TLSv1.2” and am using OpenSSL 1.0.2g from the Lubuntu repository. All the programs were loaded through the Synaptic Package Manager. My question is whether this version of Kamailio supports the cipher suite ECDHE-RSA-AES256-GCM-SHA384. My version of OpenSSL lists it as an option, but the highest strength cipher that the Kamailio 4.3.4 server seems to accept is RSA-AES256-GCM-SHA384. My (limited) understanding is that ECDHE is a better method of key exchange than RSA because it is ephemeral with forward secrecy. I used Wireshark to look at the connection protocols for sip clients Jitsi and Blink with the Kamailio server. Jitsi offers only four cipher choices of what I understand are considered compromised security TLS protocols and it connected with the RSA-AES128-CBC-SHA cipher. Blink offers 65 cipher choices, starting with ECDHE-RSA-AES256-GCM-SHA384. My Kamailio server accepted the 29^th offering on the list, RSA-AES256-GCM-SHA384. Unless I am missing something, Kamailio 4.3.4 doesn’t seem to support ephemeral DH key exchanges. Is there some other TLS configuration file or setting for Kamailio that can be changed to allow this? --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 2

Re: [SR-Users] Bind IP to Kamailio without restart
by Duarte Rocha 03 Jan '18

03 Jan '18

Greetings Alex, That's exactly what I need, thanks a lot. Cheers

2 1

Kamailio IMS Proxy Not responding
by Amar Tinawi 03 Jan '18

03 Jan '18

Dears, Good day! i was trying to implement IMS platform in separated servers, i used ubuntu server 16.04 LTS, and ng-voice repository (Kamailio 5.1) with the installation wizard and minimum Conf i also choose FHoSS as HSS bind9 as DNS When i tried to register the Proxy-CSCF is not responding to any request, even no timeout, or error massage, and of course the request is not handled to I-CSCF. The client perform 11 tries, and got no respond Previously i had success with the one image IMS vm, and tried it on separated servers (kamailio version 4.2.4) Am i missing something ? how can i start troubleshoot as there is no error massages ? Is it because i'm using ubuntu 16 instead of 14? your help is highly appreciated ! attached is my configuration files Thanks in Advance Amar

2 1

Re: [SR-Users] Happy New Year 2018!
by Angel Elena 02 Jan '18

02 Jan '18

happy new year and happy sip ;) ----------------------------------------------- Ángel Elena Medina _o) craem(a)craem.net / \ http://blog.craem.net _(___V @craem_ ----------------------------------------------- Zarafa / Zpush Mobile. -------- Mensaje original -------- De: voipspace voipspace <voipspace(a)yandex.com> Fecha: 2/1/18 20:35 (GMT+01:00) Para: miconda(a)gmail.com, "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org>, "Kamailio (SER) - Devel Mailing List" <sr-dev(a)lists.kamailio.org>, business(a)lists.kamailio.org Asunto: Re: [SR-Users] Happy New Year 2018! Happy New Year, Every One. Hope you had great time off with family and friends. May 2018 be prosperous and happy for you all. On to bigger and greater thing in the new year. bw Kamailio is awesome! 01.01.2018, 11:09, "Daniel-Constantin Mierla" <miconda(a)gmail.com>: > A Happy And Prosperous Year 2018 to everyone using Kamailio and helping > to improve the project! > > Looking forward to meeting many of you around this world during 2018 and > collaborate online in a friendly environment! > > Daniel > > -- > Daniel-Constantin Mierla > www.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio Advanced Training - www.asipto.com > Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users(a)lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

1 0

Happy New Year 2018!
by Daniel-Constantin Mierla 02 Jan '18

02 Jan '18

A Happy And Prosperous Year 2018 to everyone using Kamailio and helping to improve the project! Looking forward to meeting many of you around this world during 2018 and collaborate online in a friendly environment! Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

2 1

In failure_route after t_drop and t_relay - cancel problem
by voipspace voipspace 02 Jan '18

02 Jan '18

2 2

does kamailio ims support mrfc&mrfp？
by zhang kevin 02 Jan '18

02 Jan '18

hi, dear all, i am a start user of kamailio and have a question listed in the title. if kamailio does not support mrfc and mrfp, how kamailio play the proper ring tone to the calling party? thx! from 张勇zhangyong:kevin

2 1

Issue with linking contact to IMPU on SCSCF
by Rafi A. 02 Jan '18

02 Jan '18

Hi there, I need some help here to understand why the query in [usrloc_db.c:1084] is empty. This causes the linking of contact to IMPU to fail. I'm using Kamailio 5.0.4. 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:1284]: unref_subscription_unsafe(): un-reffing subscription [rafi(a)mnc001.mcc001.3gppnetwork.org] - was [3] 10(13882) DEBUG: ims_registrar_scscf [save.c:519]: update_contacts_helper(): updating the contacts for IMPU <sip:rafi@mnc001.mcc001.3gppnetwork.org> 10(13882) DEBUG: ims_registrar_scscf [save.c:137]: calc_contact_expires(): Calculated expires for contact is 600000 10(13882) DEBUG: ims_registrar_scscf [save.c:548]: update_contacts_helper(): Need to update contact: <sip:rafi@192.168.10.48:57230;transport=udp>: q_value [-1],sos: [0],expires [600000] 10(13882) DEBUG: ims_registrar_scscf [save.c:550]: update_contacts_helper(): packing contact information 10(13882) DEBUG: ims_registrar_scscf [save.c:556]: update_contacts_helper(): adding/updating contact based on prior existence 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:748]: get_scontact(): looking for contact [sip:rafi@192.168.10.48:57230;transport=udp] in slot 300 10(13882) DEBUG: ims_registrar_scscf [save.c:562]: update_contacts_helper(): inserting new contact 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:562]: insert_scontact(): INSERTing ucontact in usrloc module 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.3gpp.cs-voice] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.3gpp.icsi-ref] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [audio] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.oma.sip-im.large-message] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.3gpp.smsip] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [language] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.oma.sip-im] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [expires] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:173]: new_ucontact(): generating hash based on [sip:rafi@192.168.10.48:57230;transport=udp] 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:280]: mem_insert_scontact(): Created new contact in memory with AOR: [sip:rafi@192.168.10.48:57230;transport=udp] and hash [300] 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:289]: db_insert_ucontact(): DB: inserting ucontact [sip:rafi@192.168.10.48:57230;transport=udp] 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:311]: db_insert_ucontact(): Converted params to string to insert into db: [+g.3gpp.cs-voice;+g.3gpp.icsi-ref=urn%3Aurn-7%3A3gpp-application.ims.iari.g sma-vs;audio;+g.oma.sip-im.large-message;+g.3gpp.smsip;language=en,fr;+g.oma .sip-im;expires=600000] 10(13882) DEBUG: ims_usrloc_scscf [udomain.c:843]: ref_contact_unsafe(): incrementing ref count on contact [sip:rafi@192.168.10.48:57230;transport=udp], was 1 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:1225]: link_contact_to_impu(): number of contacts for IMPU [sip:rafi@mnc001.mcc001.3gppnetwork.org] is 1 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:1065]: db_link_contact_to_impu(): DB: linking contact to IMPU 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:1084]: db_link_contact_to_impu(): QUERY IS [] and len is 0 10(13882) ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Query was empty (1065) 10(13882) ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query 10(13882) ERROR: ims_usrloc_scscf [usrloc_db.c:1086]: db_link_contact_to_impu(): Unable to link impu-contact in DB - impu [sip:rafi@mnc001.mcc001.3gppnetwork.org], contact [sip:rafi@192.168.10.48:57230;transport=udp] 10(13882) ERROR: ims_usrloc_scscf [impurecord.c:1227]: link_contact_to_impu(): Failed to update DB linking contact [sip:rafi@192.168.10.48:57230;transport=udp] to IMPU [sip:rafi@mnc001.mcc001.3gppnetwork.org]...continuing but db will be out of sync! 10(13882) DEBUG: ims_usrloc_scscf [udomain.c:852]: unref_contact_unsafe(): decrementing ref count on contact [sip:rafi@192.168.10.48:57230;transport=udp], was 2 Best Regards, Rafael A.

2 1

error when brining up scscf in kamailio 5.1
by Abdelmuhaimen Seaudi 01 Jan '18

01 Jan '18

Hi, After configuring scscf.cfg + kamailio.cfg + scscf.xml, I cannot start scscf, as I get the below error " can't bind presence" I tried commenting out the lines loading the presence module, but it seems this is not relevant. How can I try troubleshoot this issue ? Dec 31 17:22:55 olc-dd scscf[6659]: DEBUG: <core> [core/sr_module.c:982]: init_mod(): ims_usrloc_scscf Dec 31 17:22:55 olc-dd scscf[6659]: INFO: ims_usrloc_scscf [hslot.c:69]: ul_init_locks(): locks array size 512 Dec 31 17:22:55 olc-dd scscf[6659]: INFO: ims_usrloc_scscf [contact_hslot.c:67]: init_contacts_locks(): locks array size 512 Dec 31 17:22:55 olc-dd scscf[6659]: INFO: ims_usrloc_scscf [hslot_sp.c:70]: subs_init_locks(): locks array size 512 Dec 31 17:22:55 olc-dd scscf[6659]: DEBUG: <core> [core/sr_module.c:714]: find_mod_export_record(): export of <bind_presence> not found (flags 0) Dec 31 17:22:55 olc-dd scscf[6659]: ERROR: ims_usrloc_scscf [ims_usrloc_scscf_mod.c:292]: mod_init(): can't bind presence Dec 31 17:22:55 olc-dd scscf[6659]: ERROR: <core> [core/sr_module.c:984]: init_mod(): Error while initializing module ims_usrloc_scscf (/usr/local/lib64/kamailio/modules/ims_usrloc_scscf.so) Dec 31 17:22:55 olc-dd scscf[6659]: DEBUG: debugger [debugger_api.c:1267]: dbg_destroy_mod_levels(): Destroyed _dbg_mod_table, size 32 Dec 31 17:22:55 olc-dd scscf[6659]: DEBUG: cdp_avp [cdp_avp_mod.c:224]: cdp_avp_destroy(): Destroying module cdp_avp Dec 31 17:22:55 olc-dd scscf[6659]: INFO: cdp [cdp_mod.c:257]: cdp_exit(): CDiameterPeer child stopping ... Dec 31 17:22:55 olc-dd scscf[6659]: INFO: cdp [diameter_peer.c:364]: diameter_peer_destroy(): destroy_diameter_peer(): Terminating all children... Dec 31 17:22:55 olc-dd scscf[6659]: INFO: cdp [diameter_peer.c:383]: diameter_peer_destroy(): destroy_diameter_peer(): All processes terminated. Cleaning up. Abdelmuhaimen Seaudi, CCIE # 25265 Email: aseaudi(a)gmail.com Skype: aseaudi LinkedIn: www.linkedin.com/in/aseaudi Telephone: +2012 84644 733

1 1

error when creating scscf database in kamailio 5.1
by Abdelmuhaimen Seaudi 01 Jan '18

01 Jan '18

Hi, i am upgrading from kamailio 4.x to 5.1, and when i try to create the scscf databse, i get the below error I tried correcting this by removing the indexes, but the ims did not work properly, with lots of inconsistency in registering, and cannot make calls. what is the correct way to handle this error ? root@olc-dd:/usr/local/src/kamailio-5.1/kamailio/utils/kamctl/mysql# mysql -uroot scscf < ims_usrloc_scscf-create.sql ERROR 1071 (42000) at line 2: Specified key was too long; max key length is 767 bytes Thanks. Abdelmuhaimen Seaudi, CCIE # 25265 Email: aseaudi(a)gmail.com Skype: aseaudi LinkedIn: www.linkedin.com/in/aseaudi Telephone: +2012 84644 733

1 1

Issue with linking contact to IMPU
by Rafi A. 01 Jan '18

01 Jan '18

1 0

Issue with linking contact to IMPU
by Rafi Aizenstain 01 Jan '18

01 Jan '18

Hi there, I need some help here to understand why the query in [usrloc_db.c:1084] is empty. This causes the linking of contact to IMPU to fail. I'm using Kamailio 5.0.4. 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:1284]: unref_subscription_unsafe(): un-reffing subscription [rafi(a)mnc001.mcc001.3gppnetwork.org] - was [3] 10(13882) DEBUG: ims_registrar_scscf [save.c:519]: update_contacts_helper(): updating the contacts for IMPU <sip:rafi@mnc001.mcc001.3gppnetwork.org> 10(13882) DEBUG: ims_registrar_scscf [save.c:137]: calc_contact_expires(): Calculated expires for contact is 600000 10(13882) DEBUG: ims_registrar_scscf [save.c:548]: update_contacts_helper(): Need to update contact: <sip:rafi@192.168.10.48:57230;transport=udp>: q_value [-1],sos: [0],expires [600000] 10(13882) DEBUG: ims_registrar_scscf [save.c:550]: update_contacts_helper(): packing contact information 10(13882) DEBUG: ims_registrar_scscf [save.c:556]: update_contacts_helper(): adding/updating contact based on prior existence 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:748]: get_scontact(): looking for contact [sip:rafi@192.168.10.48:57230;transport=udp] in slot 300 10(13882) DEBUG: ims_registrar_scscf [save.c:562]: update_contacts_helper(): inserting new contact 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:562]: insert_scontact(): INSERTing ucontact in usrloc module 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.3gpp.cs-voice] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.3gpp.icsi-ref] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [audio] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.oma.sip-im.large-message] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.3gpp.smsip] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [language] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [+g.oma.sip-im] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:118]: new_ucontact(): Checking param [expires] 10(13882) DEBUG: ims_usrloc_scscf [ucontact.c:173]: new_ucontact(): generating hash based on [sip:rafi@192.168.10.48:57230;transport=udp] 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:280]: mem_insert_scontact(): Created new contact in memory with AOR: [sip:rafi@192.168.10.48:57230;transport=udp] and hash [300] 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:289]: db_insert_ucontact(): DB: inserting ucontact [sip:rafi@192.168.10.48:57230;transport=udp] 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:311]: db_insert_ucontact(): Converted params to string to insert into db: [+g.3gpp.cs-voice;+g.3gpp.icsi-ref=urn%3Aurn-7%3A3gpp-application.ims.iari.gsma-vs;audio;+g.oma.sip-im.large-message;+g.3gpp.smsip;language=en,fr;+g.oma.sip-im;expires=600000] 10(13882) DEBUG: ims_usrloc_scscf [udomain.c:843]: ref_contact_unsafe(): incrementing ref count on contact [sip:rafi@192.168.10.48:57230;transport=udp], was 1 10(13882) DEBUG: ims_usrloc_scscf [impurecord.c:1225]: link_contact_to_impu(): number of contacts for IMPU [sip:rafi@mnc001.mcc001.3gppnetwork.org] is 1 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:1065]: db_link_contact_to_impu(): DB: linking contact to IMPU 10(13882) DEBUG: ims_usrloc_scscf [usrloc_db.c:1084]: db_link_contact_to_impu(): QUERY IS [] and len is 0 10(13882) ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Query was empty (1065) 10(13882) ERROR: <core> [db_query.c:181]: db_do_raw_query(): error while submitting query 10(13882) ERROR: ims_usrloc_scscf [usrloc_db.c:1086]: db_link_contact_to_impu(): Unable to link impu-contact in DB - impu [sip:rafi@mnc001.mcc001.3gppnetwork.org], contact [sip:rafi@192.168.10.48:57230;transport=udp] 10(13882) ERROR: ims_usrloc_scscf [impurecord.c:1227]: link_contact_to_impu(): Failed to update DB linking contact [sip:rafi@192.168.10.48:57230;transport=udp] to IMPU [sip:rafi@mnc001.mcc001.3gppnetwork.org]...continuing but db will be out of sync! 10(13882) DEBUG: ims_usrloc_scscf [udomain.c:852]: unref_contact_unsafe(): decrementing ref count on contact [sip:rafi@192.168.10.48:57230;transport=udp], was 2 Best Regards, Rafael A.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users January 2018