sr-users March 2015

sr-users@lists.kamailio.org

88 participants
149 discussions

ndb_redis set <null> reply to EXISTS query

by Yuriy Gorlichenko

Hello I try to get some replies from redis. Time after time redis request give me null result. But redis bs not disconnected. This happens only with websocket endpoints. My queries is: redis_cmd("srv1", "EXISTS $si", "s"); So at xLOG i see that $si correctly sended, but result is null. At db I keep key IP with value TIMESTAMP Intresting that route, that givesme this result idependend of WS or UDP endpoint. IT does not know about it anything.

9 years, 8 months

Route Between WebSockets without rtpengine getting into the mix

by Don Fanning

Hello All, Prior to going down the rtpengine path for another need, calling was working fine between WSS client. Now that I've added in some pieces from caruizdiaz's config [ https://github.com/caruizdiaz/kamailio-ws/blob/master/kamailio-ws.cfg] relating to SETUP_BY_TRANSPORT, it has broken that functionality. Is there a way to skip rtpengine if the originator and destination are both on wss? route[RELAY] { # enable additional event routes for forwarded requests # - serial forking, RTP relaying handling, a.s.o. if (is_method("INVITE|BYE|SUBSCRIBE|UPDATE")) { t_on_branch("MANAGE_BRANCH"); t_on_reply("MANAGE_REPLY"); } if (is_method("INVITE")) { route(SETUP_BY_TRANSPORT); if(!t_is_set("failure_route")) t_on_failure("MANAGE_FAILURE"); } if (!t_relay()) { sl_reply_error(); } exit; } route[SETUP_BY_TRANSPORT] { if ($ru =~ "transport=ws") { xlog("L_INFO", "Request going to WS"); if(sdp_with_transport("RTP/SAVPF")) { rtpengine_manage("rtcp-mux-demux trust-address replace-origin replace-session-connection ICE=force DTLS=passive"); t_on_reply("REPLY_WS_TO_WS"); return; } #rtpengine_manage("rtcp-mux-demux trust-address replace-origin replace-session-connection ICE=force DTLS=passive RTP/SAVP"); t_on_reply("REPLY_FROM_WS"); } else if ($proto =~ "ws") { xlog("L_INFO", "Request coming from WS"); rtpengine_manage("rtcp-mux-demux trust-address replace-origin replace-session-connection ICE=remove DTLS=passive RTP/SAVP"); t_on_reply("REPLY_TO_WS"); } else { xlog("L_INFO", "This is a classic phone call"); rtpengine_manage("replace-origin replace-session-connection"); t_on_reply("MANAGE_CLASSIC_REPLY"); } } Thanks for any help! -Don

9 years, 8 months

segfault problem with unixodbc module

by Lucas Wals Ochoa

Hello, this is the first time I send a question here, hope my english is good enough to explain my problem. I have a Kamailio 4.1.8+RTPProxy setup working, but recently I saw RTP Engine proxy, so I decided to give a try. I installed the latest kamailio stable version (4.2.3) and adapt the configuration I have(that uses a MariaDB database), to try the rtpengine module, but I couldn't even start kamailio process, cause I received a segfault problem at unixodbc module. The version of unixodbc that I installed is 2.3.1-10 That was the first time I encounter this error. I thought that maybe the database I have created with the version 4.1.8 wasn't compatible, so I decided to create a new database, but the problem persisted. So I'm here to know if someone know something about this, or have had a similar problem. I attached the system log for Kamailio, and a backtrace I made using "gdb" with the corefile that Kamailio creates when it crash. Log: Mar 4 12:46:35 localhost systemd: Starting SYSV: Kamailio is a fast, reliable and flexible SIP Server.... Mar 4 12:46:35 localhost kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve 10.0.0.70 Mar 4 12:46:35 localhost /usr/sbin/kamailio[2369]: WARNING: tm [tm.c:845]: mod_init(): WARNING: mod_init: reparse_on_dns_failover is enabled on a multihomed host -- check the readme of tm module! Mar 4 12:46:35 localhost /usr/sbin/kamailio[2369]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob Mar 4 12:46:35 localhost /usr/sbin/kamailio[2369]: INFO: rr [rr_mod.c:160]: mod_init(): outbound module not available Mar 4 12:46:35 localhost /usr/sbin/kamailio[2369]: INFO: usrloc [hslot.c:53]: ul_init_locks(): locks array size 1024 Mar 4 12:46:35 localhost /usr/sbin/kamailio[2369]: INFO: auth [auth_mod.c:350]: mod_init(): auth: qop set, but nonce-count (nc_enabled) support disabled Mar 4 12:46:35 localhost kernel: kamailio[2369]: segfault at 10070 ip 00007fc3d554df7e sp 00007fff89556450 error 4 in libmyodbc5w.so[7fc3d5527000+47000] Mar 4 12:46:35 localhost kamailio: ERROR: <core> [daemonize.c:315]: daemonize(): Main process exited before writing to pipe Mar 4 12:46:35 localhost kamailio: Starting kamailio: Mar 4 12:46:35 localhost systemd: kamailio.service: control process exited, code=exited status=1 Mar 4 12:46:35 localhost systemd: Failed to start SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Mar 4 12:46:35 localhost systemd: Unit kamailio.service entered failed state. Backtrace of gdb: Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio'. Program terminated with signal 11, Segmentation fault. #0 0x00007fc3d554df7e in get_ctype () from /usr/lib64/libmyodbc5.so Missing separate debuginfos, use: debuginfo-install kamailio-4.2.3-3.1.x86_64 (gdb) backtrace #0 0x00007fc3d554df7e in get_ctype () from /usr/lib64/libmyodbc5.so #1 0x00007fc3d554dfac in init_parser () from /usr/lib64/libmyodbc5.so #2 0x00007fc3d554ec41 in parse () from /usr/lib64/libmyodbc5.so #3 0x00007fc3d5553484 in prepare () from /usr/lib64/libmyodbc5.so #4 0x00007fc3d5559e9c in SQLPrepareWImpl () from /usr/lib64/libmyodbc5.so #5 0x00007fc3d5559eb9 in SQLExecDirectW () from /usr/lib64/libmyodbc5.so #6 0x00007fc3de43b05f in SQLExecDirect () from /lib64/libodbc.so.2 #7 0x00007fc3de695302 in db_unixodbc_submit_query () from /usr/lib64/kamailio/modules/db_unixodbc.so #8 0x00007fc3de21522e in db_do_submit_query () from /usr/lib64/kamailio/libsrdb1.so.1 #9 0x00007fc3de215cf7 in db_do_query_internal () from /usr/lib64/kamailio/libsrdb1.so.1 #10 0x00007fc3de21661a in db_do_query () from /usr/lib64/kamailio/libsrdb1.so.1 #11 0x00007fc3de696d90 in db_unixodbc_query () from /usr/lib64/kamailio/modules/db_unixodbc.so #12 0x00007fc3de20ce90 in db_table_version () from /usr/lib64/kamailio/libsrdb1.so.1 #13 0x00007fc3da209693 in init_ds_db () from /usr/lib64/kamailio/modules/dispatcher.so #14 0x00007fc3da1f4f1a in mod_init () from /usr/lib64/kamailio/modules/dispatcher.so #15 0x0000000000520e8d in init_mod () #16 0x0000000000520be8 in init_mod () #17 0x000000000052119a in init_modules () #18 0x0000000000517951 in main () Hope someone can help me. Thanks in advance.

9 years, 8 months

WARNING: <core> [local_timer.c:83]: _local_timer_dist_tl(): 0 expire timer added"?

by Anthony Messina

Good day. Is anyone able to let me in on what this means "WARNING: <core> [local_timer.c:83]: _local_timer_dist_tl(): 0 expire timer added"? I just started seeing this after pulling down 5c1a9df from git and it seems like something that I probably don't want happening. -- Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

9 years, 8 months

wss calls between devices works but strange error

by Don Fanning

Hi All, I'm placing calls between two devices over WSS and sipML5. Connection seems to work and stays up (despite some grumbling sometimes with 603 failed to get local SDP) but my question is the following log entries - could someone translate what is happening here? Thanks! Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: WARNING: <core> [tcp_main.c:1221]: tcp_do_connect(): 127.0.0.2:5061: could not find corresponding listening socket for 127.0.0.1, using default... Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2740]: tcpconn_1st_send(): connect 127.0.0.2:5061 failed (RST) Connection refused Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2750]: tcpconn_1st_send(): 127.0.0.2:5061: connect & send for 0x7f0eb3944ac0 failed: Connection refused (111) Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [forward.h:247]: msg_send(): tcp_send failed Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: INFO: <script>: Request in RELAY - call is {<null>} for {106E} Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: WARNING: <core> [tcp_main.c:1221]: tcp_do_connect(): 127.0.0.2:5061: could not find corresponding listening socket for 127.0.0.1, using default... Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2740]: tcpconn_1st_send(): connect 127.0.0.2:5061 failed (RST) Connection refused Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2750]: tcpconn_1st_send(): 127.0.0.2:5061: connect & send for 0x7f0eb3944ac0 failed: Connection refused (111) Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [forward.h:247]: msg_send(): tcp_send failed Mar 5 03:35:19 sandbox /usr/local/sbin/kamailio[4917]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Mar 5 03:35:21 sandbox /usr/local/sbin/kamailio[4917]: INFO: <script>: Request in RELAY - call is {<null>} for {106E} Mar 5 03:35:21 sandbox /usr/local/sbin/kamailio[4917]: WARNING: <core> [tcp_main.c:1221]: tcp_do_connect(): 127.0.0.2:5061: could not find corresponding listening socket for 127.0.0.1, using default... Mar 5 03:35:21 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2740]: tcpconn_1st_send(): connect 127.0.0.2:5061 failed (RST) Connection refused Mar 5 03:35:21 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2750]: tcpconn_1st_send(): 127.0.0.2:5061: connect & send for 0x7f0eb3944ac0 failed: Connection refused (111) Mar 5 03:35:21 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [forward.h:247]: msg_send(): tcp_send failed Mar 5 03:35:21 sandbox /usr/local/sbin/kamailio[4917]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Mar 5 03:35:25 sandbox /usr/local/sbin/kamailio[4917]: INFO: <script>: Request in RELAY - call is {<null>} for {106E} Mar 5 03:35:25 sandbox /usr/local/sbin/kamailio[4917]: WARNING: <core> [tcp_main.c:1221]: tcp_do_connect(): 127.0.0.2:5061: could not find corresponding listening socket for 127.0.0.1, using default... Mar 5 03:35:25 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2740]: tcpconn_1st_send(): connect 127.0.0.2:5061 failed (RST) Connection refused Mar 5 03:35:25 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [tcp_main.c:2750]: tcpconn_1st_send(): 127.0.0.2:5061: connect & send for 0x7f0eb3944ac0 failed: Connection refused (111) Mar 5 03:35:25 sandbox /usr/local/sbin/kamailio[4917]: ERROR: <core> [forward.h:247]: msg_send(): tcp_send failed Mar 5 03:35:25 sandbox /usr/local/sbin/kamailio[4917]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Mar 5 03:35:33 sandbox /usr/local/sbin/kamailio[4918]: INFO: <script>: Request in RELAY - call is {<null>} for {106E} Mar 5 03:35:33 sandbox /usr/local/sbin/kamailio[4918]: WARNING: <core> [tcp_main.c:1221]: tcp_do_connect(): 127.0.0.2:5061: could not find corresponding listening socket for 127.0.0.1, using default... Mar 5 03:35:33 sandbox /usr/local/sbin/kamailio[4918]: ERROR: <core> [tcp_main.c:2740]: tcpconn_1st_send(): connect 127.0.0.2:5061 failed (RST) Connection refused Mar 5 03:35:33 sandbox /usr/local/sbin/kamailio[4918]: ERROR: <core> [tcp_main.c:2750]: tcpconn_1st_send(): 127.0.0.2:5061: connect & send for 0x7f0eb3944ac0 failed: Connection refused (111) Mar 5 03:35:33 sandbox /usr/local/sbin/kamailio[4918]: ERROR: <core> [forward.h:247]: msg_send(): tcp_send failed Mar 5 03:35:33 sandbox /usr/local/sbin/kamailio[4918]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL) Mar 5 03:35:49 sandbox /usr/local/sbin/kamailio[4918]: INFO: <script>: Request in RELAY - call is {<null>} for {106E} Mar 5 03:35:49 sandbox /usr/local/sbin/kamailio[4918]: WARNING: <core> [tcp_main.c:1221]: tcp_do_connect(): 127.0.0.2:5061: could not find corresponding listening socket for 127.0.0.1, using default... Mar 5 03:35:49 sandbox /usr/local/sbin/kamailio[4918]: ERROR: <core> [tcp_main.c:2740]: tcpconn_1st_send(): connect 127.0.0.2:5061 failed (RST) Connection refused Mar 5 03:35:49 sandbox /usr/local/sbin/kamailio[4918]: ERROR: <core> [tcp_main.c:2750]: tcpconn_1st_send(): 127.0.0.2:5061: connect & send for 0x7f0eb3944ac0 failed: Connection refused (111) Mar 5 03:35:49 sandbox /usr/local/sbin/kamailio[4918]: ERROR: <core> [forward.h:247]: msg_send(): tcp_send failed Mar 5 03:35:49 sandbox /usr/local/sbin/kamailio[4918]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unfortunately error on sending to next hop occurred (477/SL)

9 years, 8 months

How to Use Multiple DMQ Notification Addresses

by Robert Boisvert

Hello all, I would like to setup a DMQ bus where servers can come on and offline and have DMQ continue working with the online servers. I'm having trouble understanding how to do that with the notification address. Can someone point me in the right direction? More specifically, suppose I have five servers named A, B, C, D, and E. I would like all of them to be on the DMQ bus when active but they may come up at different times. For example, when A, B and C start I want each of them to be on the same DMQ bus. However, the way I understand it, if I make E the notification address none will be on the bus because E is not active. I could create a circular notification chain where A uses B as a notification server, B uses C, and so on. Of course, there are problems when one or more servers are missing from the chain. Any help on this is greatly appreciated. Thanks, Bob

9 years, 8 months

SCA fails to update appearance

by Andreas Granig

Hi guys, Playing with SCA for the first time, I'm hittin the following issue: User phone1(a)domain.org is registered on two devices A and B, and device B sends SUBSCRIBE to phone1(a)domain.org with call-info Event. Subscription is handled properly, and my DB content is this: id: 4 subscriber: sip:phone1@10.15.20.174:5100;alias=1.2.3.4~5100~1 aor: sip:phone1@domain.org event: 1 expires: 1425296906 state: 0 app_idx: 0 call_id: dacf5194-3d6a8e16d03338102a940080f0e9071c(a)10.15.20.174 from_tag: 4247246264 to_tag: f3067022b00c564156251ba2f28f331f-7c92 record_route: <sip:127.0.0.1;r2=on;lr=on;ftag=4247246264;nat=yes;ngcplb=yes;socket=udp:1.2.3.4:5060>,<sip:1.2.3.4;r2=on;lr=on;ftag=4247246264;nat=yes;ngcplb=yes;socket=udp:1.2.3.4:5060> notify_cseq: 3 subscribe_cseq: 2 Kamcmd reports this: kamcmd> sca.all_subscriptions phone1 10.15.20.174:5100 call-info 2697 active If phone1(a)domain.org on device A does a call, I get this in my logs when calling sca_call_info_update() right as first thing in my routing config handling the INVITE: Mar 2 12:02:33 sp2 proxy[34517]: WARNING: sca [sca_appearance.c:976]: sca_appearance_update_index(): Cannot update sip:phone1@domain.org index 0 to unknown: index 0 not in use Mar 2 12:02:33 sp2 proxy[34517]: ERROR: sca [sca_call_info.c:1046]: sca_call_info_invite_request_handler(): Failed to update sip:phone1@domain.org appearance-index 0 to unknown Is there something I'm obviously doing wrong here? Andreas

9 years, 8 months

switch called number

by jaflong jaflong

Hi Guys I want to archive this setup Kamailio to switch called number and the switch to be hidden from the client so there should be no mention of the switched number in any of the messages back to the client. for example phone client calls "alex" kamailio to switch "alex" to "54321" and send to asterisk on response from asterisk, kamailio to revert all references to "54321" back to "alex" before send to client Any suggestions please

9 years, 8 months

TLS conversion

by Kelvin Chua

I have 2 kamailio servers and 1 asterisk server. 1. asterisk calls kamailio1 2. kamailio1 relays INVITE to kamailio2 3. kamailio2 relays INVITE to client registered using TLS 4. client answers with 200 OK, sends to kamailio2 5. kamailio2 relays 200 OK to kamailio1 6. kamailio1 relays 200 OK to asterisk 7. asterisk sends ACK to kamailio1 8. kamailio1 complains "forward_request(): forward_req: ERROR: cannot forward to af 2, proto 3 no corresponding listening socket" which is because 200 OK has a contact header with tls transport from client 9. call drops in 30 secs which is expected because client never received the ACK any ideas on a fix or workaround? Kelvin Chua

9 years, 8 months

Any suggestion if I just want to update one or some modules?

by jack wang

For example, If I modify only the registrar module, I thought the steps were: 1. make modules=modules\registrar modules 2. copy the registrar.so to the installed path And when starting kamailio I got the error message below: ERROR: <core> [sr_module.c:417]: version_control(): ERROR: module compile flags mismatch for [my installed path]/registrar.so I've searched for the answer and it seems to need to re-build and re-install kamailio and all the module again... Is there more efficient way for just updating the specified module ?? Thanks a lot.:)

9 years, 8 months

Jump to page:

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 March 2015