sr-users May 2020

sr-users@lists.kamailio.org

66 participants
82 discussions

by nicola defilippo

Hi, i'm a newbie about kamailio, i'd like create an imc chat. I load the module but i don't understand what's the sip uri to use to create the chat (i understand that there is a sip uri for the chat manager, but i don't know what it is). I' became a bit crazy. Thanks for help and sorry for the stupid question (if it's). N.

3 years, 11 months

Incorrect Load Calculation by Dispatcher Module in Kamailio

by harneet singh

Hi All, I have run into an issue with the Dispatcher Module in Kamailio, which apparently seems to be running into issues randomly while calculating the dispatcher load. I have submitted an issue wrt the same at https://github.com/kamailio/kamailio/issues/2322 with all the details and potential fix as well, based on analysis and tests. Can some one please take a look into the same? Regards, Harneet Singh -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

3 years, 11 months

How S-CSCF route SIP INVITEs as per iFC ?

by Hamid Hashmi

I have added an Application Server in iFC and try to route one user to that Application server for testing But INVITE to that subscriber following the default iFC. I am using ng-voice HSS Server. I have been trying to differentiate between iFCs for two different subscribers and unable to find the store location of SAA xml on S-CSCF and I am Unable to find xml file of required subscribers in wireshark traces as well because it says in SAR that USER_DATA_ALREADY_EXISTS and SAA didn't contain any XML file for that specific users. Furthermore if you can describe SIP INVITEs routing mechanism of S-CSCF, on which params or SIP Headers S-CSCF route INVITEs to Application Servers according to iFC ? Regards Hamid R. Hashmi

3 years, 11 months

Video Call for deaf

by www . deaf - tv . com

hello, my Server CentOs 7 with kamailio installed, Chat write good! Video call how modules ?? Kamailio V 5.3.3 Regards Denny Brendel

3 years, 11 months

How Kamailio processes SIP ACK on local 4XX reply?

by Denys Pozniak

Hello! I have some misunderstanding regarding the processing of SIP ACK on local Kamailio 4xx reply (eg 407 Proxy Authentication Required). In the picture below you can see that such a message just goes through the proxy and moreover gets into the *request_route* section. I expect this SIP ACK to be consumed by the sl module without hitting script logic. [image: image.png] I put the part below to the very top of the *request_route* section: *request_route* { if ( is_method("ACK") ) { t_check_trans(); $var(error) = $rc; xlog("L_ERR", "[CATCH_ACK] m=$rm cseq=$cs ru=$ru err=$var(error) [$ci]"); } .... And as a result, I detected in syslog: May 7 16:15:34 test-edge /usr/sbin/kamailio[11642]: ERROR: <script>: [CATCH_ACK] m=ACK cseq=153 ru=sip:mod_sofia@10.0.7.3:5060 err=-1 [051e7c50-0b10-1239-2996-001dd8b71cb2] *SIP re-INVITE (hold) from Phone:* 2020/05/07 16:15:34.629973 176.6.4.6:1024 -> 185.9.7.7:5060 INVITE sip:mod_sofia@10.0.7.3:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.11.111:5060 ;branch=z9hG4bK00475de2da8eea118ec67caaaddc98fb;rport Route: <sip:185.9.7.7;r2=on;lr=on;did=f98.f3f4> Route: <sip:10.0.7.5;r2=on;lr=on;did=f98.f3f4> Route: <sip:10.0.7.6;lr=on;did=f98.fbe> From: <sip:312222222222@10.0.7.6>;tag=00dfd3d8da8eea118ec67caaaddc98fb To: "Denys VOIP" <sip:5008@185.9.7.7>;tag=54Q0XNHgXBUvp Call-ID: 051e7c50-0b10-1239-2996-001dd8b71cb2 CSeq: 153 INVITE Contact: <sip:312222222222@192.168.11.111:5060 ;gr=00DCB21F-BD8E-EA11-8E88-7CAAADDC98FB> Content-Type: application/sdp Allow: INVITE, ACK, BYE, CANCEL, INFO, MESSAGE, NOTIFY, OPTIONS, REFER, UPDATE, PRACK Max-Forwards: 70 Supported: 100rel, replaces, from-change, gruu User-Agent: SIPPER for PhonerLite Content-Length: 313 v=0 o=- 3858283927 2 IN IP4 192.168.11.111 s=SIPPER for PhonerLite c=IN IP4 192.168.11.111 t=0 0 m=audio 5062 RTP/AVP 8 0 9 107 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:9 G722/8000 a=rtpmap:107 opus/48000/2 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ssrc:782125221 a=sendonly *SIP 407 from Kamailio:* 2020/05/07 16:15:34.632298 185.9.7.7:5060 -> 176.6.4.6:1024 SIP/2.0 407 Proxy Authentication Required Via: SIP/2.0/UDP 192.168.11.111:5060 ;branch=z9hG4bK00475de2da8eea118ec67caaaddc98fb;rport=1024;received=176.6.4.6 From: <sip:312222222222@10.0.7.6>;tag=00dfd3d8da8eea118ec67caaaddc98fb To: "Denys VOIP" <sip:5008@185.9.7.7>;tag=54Q0XNHgXBUvp Call-ID: 051e7c50-0b10-1239-2996-001dd8b71cb2 CSeq: 153 INVITE Proxy-Authenticate: Digest realm="185.9.7.7", nonce="XrQaXjfjyrftyrtiyrft7uO" Server: kamailio (5.2.2 (x86_64/linux)) Content-Length: 0 *SIP ACK from Phone:* 2020/05/07 16:15:34.672872 176.6.4.6:1024 -> 185.9.7.7:5060 ACK sip:mod_sofia@10.0.7.3:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.11.111:5060 ;branch=z9hG4bK00475de2da8eea118ec67caaaddc98fb;rport Route: <sip:185.9.7.7;r2=on;lr=on;did=f98.f3f4> Route: <sip:10.0.7.5;r2=on;lr=on;did=f98.f3f4> Route: <sip:10.0.7.6;lr=on;did=f98.fbe> From: <sip:312222222222@10.0.7.6>;tag=00dfd3d8da8eea118ec67caaaddc98fb To: "Denys VOIP" <sip:5008@185.9.7.7>;tag=54Q0XNHgXBUvp Call-ID: 051e7c50-0b10-1239-2996-001dd8b71cb2 CSeq: 153 ACK Content-Length: 0 *SIP ACK (unwanted) from Kamailio to Core:* 2020/05/07 16:15:34.675546 10.0.7.5:5060 -> 10.0.7.6:5060 ACK sip:mod_sofia@10.0.7.3:5060 SIP/2.0 Max-Forwards: 10 Via: SIP/2.0/UDP 10.0.7.5;branch=z9hG4bK0d46.c33c3556c3cffbac49e717352b3575f6.0 Via: SIP/2.0/UDP 192.168.11.111:5060 ;received=176.6.4.6;branch=z9hG4bK00475de2da8eea118ec67caaaddc98fb;rport=1024 Route: <sip:10.0.7.6;lr=on;did=f98.fbe> From: <sip:312222222222@10.0.7.6>;tag=00dfd3d8da8eea118ec67caaaddc98fb To: "Denys VOIP" <sip:5008@185.9.7.7>;tag=54Q0XNHgXBUvp Call-ID: 051e7c50-0b10-1239-2996-001dd8b71cb2 CSeq: 153 ACK Content-Length: 0 loose-route: done *IP addresses and call-flow:* Core (10.0.7.6) --> [ Kamailio (10.0.7.5) -> Kamailio (185.9.7.7) ] --> Phone (176.6.4.6) [root@test-edge kamailio]$ kamailio -v version: kamailio 5.2.2 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, 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_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 19:29:40 Jun 20 2019 with gcc 4.8.5 -- BR, Denys Pozniak

3 years, 11 months

kamdbctl create - failing create kamailio database on secfilter table action column default value

by Voip support

Hello Community, I had created for my solution an installer using ansible. It worked great all the time but suddenly it started to crash on step where i run the command : kamdbctl create root@nlb:/home/nlb# kamdbctl create -e \E[37;33mINFO: creating database kamailio ... mysql: [Warning] Using a password on the command line interface can be insecure. -e \E[37;33mINFO: granting privileges to database kamailio ... mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. -e \E[37;33mINFO: creating standard tables into kamailio ... mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. -e \E[37;33mINFO: Core Kamailio tables succesfully created. -e \E[37;33mINFO: creating presence tables into kamailio ... mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. -e \E[37;33mINFO: Presence tables succesfully created. -e \E[37;33mINFO: creating extra tables into kamailio ... mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. mysql: [Warning] Using a password on the command line interface can be insecure. ERROR 1067 (42000) at line 1: Invalid default value for 'action' -e \E[37;31mERROR: Creating extra tables failed at secfilter! Its saying some error about 'action' column default value. The installation is made using ubuntu 16.04 from repository: deb http://deb.kamailio.org/kamailio53 xenial main deb-src http://deb.kamailio.org/kamailio53 xenial main Maybe the issue is this change i dont know (it mention default value 0 for action column): https://github.com/kamailio/kamailio/commit/b0f1486f8a656922aac02020c9e3141… Best regards, Tom

3 years, 11 months

DMQ Module Crash

by Ilie Soltanici

Hello, I'm trying to replicate a hash table to another 2 nodes by using DMQ Module. That's the related configuration: loadmodule "tm.so" loadmodule "tmx.so" loadmodule "dialog.so" loadmodule "dmq.so" loadmodule "htable.so" modparam("dmq", "server_address", "sip:MY_INTERNAL_IP_ADDR:5062") modparam("dmq", "notification_address", "sip:dmq.domain.local:5062") modparam("dmq", "multi_notify", 1) modparam("dmq", "num_workers", 4) modparam("dmq", "ping_interval", 90) modparam("htable", "enable_dmq", 1) modparam("htable", "dmq_init_sync", 1) modparam("htable", "htable", "test=>size=10;initval=0;dmqreplicate=1;") if(is_method("KDMQ")) { dmq_handle_message(); exit; } After starting Kamailio - everything seems to be working fine, Kamailio is able to discover other nodes and replications is working fine, until after a few minutes I'm getting such errors in the Kamailio Log file: May 8 17:14:26 kamailio kamailio[28064]: CRITICAL: <core> [core/mem/q_malloc.c:521]: qm_free(): BUG: freeing already freed pointer (0x7f0ac62493e0), called from dialog: dlg_var.c: free_local_varlist(145), first free dialog: dlg_var.c: set_dlg_variable_unsafe(205) - ignoring Then, if I'm getting any SIP messages from any Device - Kamailio is crashing with the following info in the log file: May 8 16:03:19 kamailio kam[10963]: CRITICAL: {REGISTER (1) | Seq=45534 | Source IP=192.168.1.5 (tcp) | Call ID=Kyb-KJjf.U9ttdOwQNYu6mUWCKb2bvk7} <core> [core/mem/q_malloc.c:150]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten(0, 0)[0x7f62cc746a10:0x7f62cc746a48]! Memory allocator was called from dialog: dlg_var.c:147. Fragment marked by dialog: dlg_var.c:108. Exec from core/mem/q_malloc.c:511. May 8 16:03:21 kamailio kam[10966]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 59 May 8 16:03:21 kamailio kam[10966]: DEBUG: <core> [core/tcp_main.c:3825]: handle_ser_child(): dead child 37, pid 10963 (shutting down?) May 8 16:03:21 kamailio kam[10966]: DEBUG: <core> [core/io_wait.h:599]: io_watch_del(): DBG: io_watch_del (0xa9e1c0, 59, -1, 0x0) fd_no=48 called May 8 16:03:21 kamailio kam[10966]: DEBUG: <core> [core/tcp_main.c:3593]: handle_tcp_child(): dead tcp child 1 (pid 10963, no 37) (shutting down?) May 8 16:03:21 kamailio kam[10966]: DEBUG: <core> [core/io_wait.h:599]: io_watch_del(): DBG: io_watch_del (0xa9e1c0, 62, -1, 0x0) fd_no=47 called May 8 16:03:21 kamailio kam[10919]: ALERT: <core> [main.c:767]: handle_sigs(): child process 10963 exited by a signal 6 May 8 16:03:21 kamailio kam[10919]: ALERT: <core> [main.c:770]: handle_sigs(): core was generated May 8 16:03:21 kamailio kam[10919]: INFO: <core> [main.c:792]: handle_sigs(): terminating due to SIGCHLD May 8 16:03:21 kamailio kam[10919]: DEBUG: <core> [main.c:794]: handle_sigs(): terminating due to SIGCHLD May 8 16:03:21 kamailio kam[10966]: INFO: <core> [main.c:847]: sig_usr(): signal 15 received This is what i got from the dump core file: uri = {user = {s = 0x3 <Address 0x3 out of bounds>, len = -264573566}, passwd = {s = 0x788 <Address 0x788 out of bounds>, len = 8208}, host = {s = 0x393100000000 <Address 0x393100000000 out of bounds>, len = 1588950199}, port = {s = 0x2 <Address 0x2 out of bounds>, len = 24086112}, params = {s = 0x7ffcbb1600c0 "\200", len = -261173312}, sip_params = {s = 0x7ffcbb1601a8 "\300\317n\360b\177", len = 24086112}, headers = {s = 0x0, len = -261173312}, port_no = 424, proto = 47894, type = 32764, flags = (URI_SIP_USER_PHONE | unknown: 4031456108), transport = { s = 0x16f88cc "16:03:19 kamailio[10963]: CRITICAL: {REGISTER (1) | Seq=45534 | Source IP=192.168.1.5 (tcp) | Call ID=Kyb-KJjf.U9ttdOwQNYu6mUWCKb2bvk7} <core> [core/mem/q_malloc.c:150]: qm_debug_check_frag(): BUG: qm: pr"..., len = -261163168}, ttl = { s = 0x8 <Address 0x8 out of bounds>, len = -263517049}, user_param = { s = 0x16f88cc "16:03:19 kamailio[10963]: CRITICAL: {REGISTER (1) | Seq=45534 | Source IP=192.168.1.5 (tcp) | Call ID=Kyb-KJjf.U9ttdOwQNYu6mUWCKb2bvk7} <core> [core/mem/q_malloc.c:150]: qm_debug_check_frag(): BUG: qm: pr"..., len = -264350686}, maddr = { s = 0x3336393031000080 <Address 0x3336393031000080 out of bounds>, len = 8187}, method = {s = 0x0, len = 24086112}, lr = {s = 0x820ce8 "%s: %s%s(): cseq <%.*s>: <%.*s> <%.*s>\n", len = -1156185384}, r2 = {s = 0xb <Address 0xb out of bounds>, len = 21}, gr = { s = 0xffffffff <Address 0xffffffff out of bounds>, len = -264780793}, transport_val = {s = 0x1ff4 <Address 0x1ff4 out of bounds>, len = 24086720}, ttl_val = {s = 0x7f62f06f0760 <main_arena> "", len = 128}, user_param_val = {s = 0x16f88b0 "`\002", len = 144}, maddr_val = {s = 0x15 <Address 0x15 out of bounds>, len = -264573566}, method_val = {s = 0x788 <Address 0x788 out of bounds>, len = 8208}, lr_val = {s = 0x0, len = 1588950199}, r2_val = {s = 0x2 <Address 0x2 out of bounds>, len = 24086112}, gr_val = { s = 0x7ffcbb1601f0 "\006", len = -261173312}} next_hop = {user = {s = 0x0, len = 0}, passwd = {s = 0x0, len = 0}, host = {s = 0x7f62f06eef20 <_nl_C_LC_NUMERIC+32> "", len = 0}, port = {s = 0x0, len = 0}, params = {s = 0x7f620000000b <Address 0x7f620000000b out of bounds>, len = 0}, sip_params = { s = 0x7f62f03762cd <vfprintf+19661> "\200\275\360\372\377\377", len = 0}, headers = {s = 0x0, len = -1}, port_no = 25293, proto = 61495, type = 32610, flags = (URI_USER_NORMALIZE | URI_SIP_USER_PHONE), transport = {s = 0x7ffcbb160038 "\267t\265^", len = 24086112}, ttl = {s = 0xffffffff <Address 0xffffffff out of bounds>, len = 0}, user_param = {s = 0x7d62e8 "%s: %.*s%s%s(): preparing to run routing scripts...\n", len = 11}, maddr = {s = 0xbd <Address 0xbd out of bounds>, len = 3440}, method = {s = 0x7d631c "", len = -263511186}, lr = {s = 0x16f88cc "16:03:19 kamailio[10963]: CRITICAL: {REGISTER (1) | Seq=45534 | Source IP=192.168.1.5 (tcp) | Call ID=Kyb-KJjf.U9ttdOwQNYu6mUWCKb2bvk7} <core> [core/mem/q_malloc.c:150]: qm_debug_check_frag(): BUG: qm: pr"..., len = -261163168}, r2 = { s = 0x8 <Address 0x8 out of bounds>, len = -263517049}, gr = { s = 0x16f88cc "16:03:19 kamailio[10963]: CRITICAL: {REGISTER (1) | Seq=45534 | Source IP=192.168.1.5 (tcp) | Call ID=Kyb-KJjf.U9ttdOwQNYu6mUWCKb2bvk7} <core> [core/mem/q_malloc.c:150]: qm_debug_check_frag(): BUG: qm: pr"..., len = -264350686}, transport_val = { s = 0x7d62ef "s%s%s(): preparing to run routing scripts...\n", len = 8187}, ttl_val = {s = 0x0, len = -264345823}, user_param_val = {s = 0x3000000010 <Address 0x3000000010 out of bounds>, len = -1156184608}, maddr_val = { s = 0x7ffcbb160520 "\341+:\213'H\027\203\341+\342ޙ>\356|", len = 21}, method_val = {s = 0x7ffcbb160250 "\023", len = -1156186080}, lr_val = {s = 0x7f62f06eef80 <_nl_C_LC_TIME> "r\036K\360b\177", len = -1156185648}, r2_val = {s = 0x17ff710 "IST", len = -1156186048}, gr_val = {s = 0x0, len = -1156186058}} u = 0x400001ff4 By disabling DMQ Module i haven't noticed any crashes or issues like that, so i suppose that Kamailio is crashing because of this module, but i can be wrong. I've tried with 2 versions of Kamailio (5.2.6 and 5.3.4), both of them having the same issue. Thanks

3 years, 11 months

db_redis and PUA

by Carsten Bock

Hi, quick question: Did anyone ever attempt to use PUA with the new db_redis? If yes, could someone share the definition for this? Thanks, Carsten -- Carsten Bock I CTO & Founder ng-voice GmbH Trostbrücke 1 I 20457 Hamburg I Germany T +49 40 524 75 93-40 | M +49 179 2021244 I www.ng-voice.com Registry Office at Local Court Hamburg, HRB 120189 Managing Directors: Dr. David Bachmann, Carsten Bock

3 years, 11 months

RTCP

by David Villasmil

Hello guys, We have clients/vendor who exchange RTP directly to each other. But we'd like to get RTCP packets (and proxy them to the other side). Is this at all possible? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 years, 11 months

Kamailio with dispatcher and asterisks real time

by ospos web

Hi all folks, Hello people, I'm new and I've been reading, so I have some but not much knowledge. I must integrate as work, two asterisk to the kamailio, a month ago I started with the real time guide [1] with only one kamailio, register, start the call, etc.. I am with the basics and it works. Now I must put two asterisk and using dispatcher, but although I read the documentation of the module.. use it and so then configure a list of file (with the asterisk where to dispatch) and not in the database.. MY HELP REQUEST QUESTION: How do I use dispatcher in load balancing mode, but taking in consideration my already working realtime-asterisk worling setup? THE PROBLEM: since with what I did it simply sends the call to both asterisk. i setup only 4 easy steps.. load module, then setup params (where i set the asterisk lists by file, and not db) and then added a "ds_select_dst(1, 4);" before the "route(RELAY);" line. please help! as i know.. the ds_select_dst(1, 4); prepare wicht asterisk will be choose to use and then when the routing RELAY happends no cares if in the realtime previously guide are a main asterisk? right? NOTE: I know it's a big world... but I can't keep reading the kamailio theory, i must goon forward due i have to lear later once are property working.. [1] https://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb

3 years, 11 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

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 May 2020