sr-users

sr-users@lists.kamailio.org

18 participants
37397 discussions

null branch(count) variable
by Ilie Soltanici 18 Jun '20

18 Jun '20

Hello, As per documentation after lookup() function I have to get the number of branches from the main branch by using $branch(count) variable, but for some reason, I'm getting always only <null> value, can someone help me to understand what I'm doing wrong? lookup(); xlog("Branch Count: $branch(count)\n"); Kamailio Version: 5.2.7 Thanks.

3 4

403 domain not served error in IMS kamailio
by Pavithra Mohanraja 18 Jun '20

18 Jun '20

Hi, Could any one please help me in this issue ASAP. This is logs from SCSCF. Jun 18 06:28:02 396779d9d4e7 kamailio[1796]: DEBUG: <core> [core/socket_info.c:630]: grep_sock_info(): checking if host==us: 10==10 && [172.17.0.8] == [172.17.0.5] Jun 18 06:28:02 396779d9d4e7 kamailio[1796]: DEBUG: <core> [core/socket_info.c:637]: grep_sock_info(): checking if port 4080 (advertise 0) matches port 5060 Jun 18 06:28:02 396779d9d4e7 kamailio[1796]: DEBUG: <core> [core/name_alias.h:62]: grep_aliases(): matching (0:172.17.0.8:5060) vs. (0: sip.example.com:0) Jun 18 06:28:02 396779d9d4e7 kamailio[1796]: DEBUG: <core> [core/name_alias.h:62]: grep_aliases(): matching (0:172.17.0.8:5060) vs. (0: sip.example.com:5060) Jun 18 06:28:02 396779d9d4e7 kamailio[1796]: DEBUG: <core> [core/name_alias.h:62]: grep_aliases(): matching (0:172.17.0.8:5060) vs. (0: scscf.sip.example.com:4080) Jun 18 06:28:02 396779d9d4e7 kamailio[1796]: DEBUG: <core> [*core/forward.c:423]: check_self(): host (0:172.17.0.8:5060 <http://172.17.0.8:5060>) != me* Jun 18 06:28:02 396779d9d4e7 kamailio[1796]: ERROR: <script>: sip:bob at sip.example.com *Jun 18 06:28:02 396779d9d4e7 kamailio[1796]: ERROR: <script>: Domain not served 403* Jun 18 06:28:02 396779d9d4e7 kamailio[1796]: ERROR: <script>: BYE ( sip:alice@sip.example.com (172.17.0.3:4060) to sip:bob@sip.example.com, -KT6eSWl7Dm77fe5hbNbeiHR2kwBjni0) Jun 18 06:28:02 396779d9d4e7 kamailio[1796]: DEBUG: <core> [core/mem/q_malloc.c:374]: qm_malloc(): qm_malloc(0x7fd1f6db5010, 30) called from core: core/ut.c: as_asciiz(161) scscf.cfg # SIP / UDP listen=udp:172.17.0.5:4080 # SIP / TCP listen=tcp:172.17.0.5:4080 # SIP / TCP/TLS listen=tls:172.17.0.5:4081 #!define NETWORKNAME "sip.example.com" #!define HOSTNAME "scscf.sip.example.com" #!define URI "sip:scscf.sip.example.com:4080" alias=scscf.sip.example.com:4080 alias=sip.example.com:5060 alias=sip.example.com # ENUM-Server to query:

1 0

docker images for kamailio IMS
by Pavithra Mohanraja 18 Jun '20

18 Jun '20

Hi , Could anyone kindly tell me if there is docker images for kamailio IMS. I can able to see docker images for only Kamailio as a SIP server. Please help. Thanks, Pavithra

4 10

Re: [SR-Users] kamailio 5.2.2 enabling hashing_type -Please Ignore
by Martin W Woscek 17 Jun '20

17 Jun '20

Found my answer, use correct version of doc: https://kamailio.org/docs/modules/5.2.x/modules/ims_usrloc_pcscf.html#idm10… From: sr-users <sr-users-bounces(a)lists.kamailio.org> On Behalf Of Martin W Woscek Sent: Wednesday, June 17, 2020 8:47 AM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: [SR-Users] kamailio 5.2.2 enabling hashing_type Hello, I'm revisiting some initial issues I had with P-CSCF. I could not set the hashing type in my PCSCF (kamalio 5.2.2) so I simply commented it out and moved on. But now, I may need it as the P-CSCF is not handling INVITES coming from I-CSCF that originated from external SIP server, where the endpoint (UE) is registered to the IMS but the P-CSCF sends the INVITE back to the S rather that the registered UE and fails. kamailio.cfg: modparam("ims_usrloc_pcscf", "hashing_type", 1) So with that, when I set the hashing_type to 1,1 or 2 I get the following starting the pcscf: Starting the P-CSCF: Jun 17 08:25:30 ubuntu kamailio_pcscf[5753]: * Not starting Kamailio IMS P-CSCF: invalid configuration file! Jun 17 08:25:30 ubuntu kamailio_pcscf[5753]: * Jun 17 08:25:30 ubuntu kamailio_pcscf[5753]: * 0(5766) ERROR: <core> [core/modparam.c:140]: set_mod_param_regex(): parameter <hashing_type> of type <2> not found in module <ims_usrloc_pcscf> Jun 17 08:25:30 ubuntu kamailio_pcscf[5753]: 0(5766) CRITICAL: <core> [core/cfg.y:3510]: yyerror_at(): parse error in config file /etc/kamailio/pcscf/kamailio.cfg, line 364, column 47: Can't set module parameter Am I missing some module that I did not include at compile time? According to the docs, it has no additional dependencies other than the ims_usrloc_pcscf.so https://kamailio.org/docs/modules/5.0.x/modules/ims_usrloc_pcscf.html#idp35… Any help is appreciated. Thanks, _Martin

1 0

Kamailio IMS support
by Pavithra Mohanraja 16 Jun '20

16 Jun '20

Hi, I am trying to connect EPC with IMS. EPC is separate installation of comac-in-a-box . IMS is kamailio based. Do i have SGi interface configurations in kamailio so that i can establish communication between EPC and IMS. One more clarification. I have seen PCRF communication can be done using CDP .Is there any way to build PCRF as part of kamailio. Kindly help .. Thanks, Pavithra

2 1

Re: [SR-Users] [EXT] RE: kamailio 522 S-CSCF failing to start
by Martin W Woscek 16 Jun '20

16 Jun '20

Hi Henning, The following are the mysql related logging I see on initial spinup of the Kamailio 5.2.2 IMS VM: Jun 16 06:15:28 ubuntu systemd[1]: Starting MySQL Community Server... Jun 16 06:15:33 ubuntu systemd[1]: Started MySQL Community Server. Jun 16 06:16:09 ubuntu /usr/local/sbin/kamailio[1617]: ERROR: db_mysql [km_dbase.c:127]: db_mysql_submit_query(): driver error on query: Table 'scscf.impu_subscriber' doesn't exist (1146) Jun 16 06:16:09 ubuntu kernel: traps: kamailio[1617] general protection fault ip:7f3dfa2874f0 sp:7ffe387dc8c0 error:0 in libmysqlclient.so.20.3.16[7f3dfa261000+33c000] Our mysql version: mysql --version mysql Ver 14.14 Distrib 5.7.29, for Linux (x86_64) using EditLine wrapper Thanks, _Martin From: Henning Westerholt <hw(a)skalatan.de> Sent: Monday, June 8, 2020 4:50 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Cc: Martin W Woscek <mwoscek(a)mitre.org> Subject: [EXT] RE: kamailio 522 S-CSCF failing to start Hello, the error message below is from the DB startup version check. So do you have sometimes DB errors on this virtual machine? Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/> From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of Martin W Woscek Sent: Monday, June 8, 2020 2:46 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Subject: [SR-Users] kamailio 522 S-CSCF failing to start Hello, There are times that our S-CSCF module just wont start. I’ve tried correlating the issue with some operation such as not de-registering an IMS client (Boghe or imsdroid) prior to shutting down the Kamailio server. But this isn’t always the case. Being that we are running this an a Ubuntu Virtual Machine, simply overwriting the image with a backed up VM is the temporary solution. I’ve dropped and created the db for S (kamdbctl) and rearranged the order of loading the presence module with same result. Status of the S-CSCF daemon on failure to start: # systemctl status kamailio_scscf ● kamailio_scscf.service - LSB: Start the Kamailio SIP proxy server Loaded: loaded (/etc/init.d/kamailio_scscf; generated) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) Jun 08 08:22:55 ubuntu /usr/local/sbin/kamailio[16511]: INFO: cdp [cdp_mod.c:255]: cdp_exit(): CDiameterPeer child stopping ... Jun 08 08:22:55 ubuntu /usr/local/sbin/kamailio[16511]: INFO: cdp [cdp_mod.c:257]: cdp_exit(): ... CDiameterPeer child stopped Jun 08 08:22:55 ubuntu /usr/local/sbin/kamailio[16511]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Jun 08 08:22:55 ubuntu kamailio_scscf[16495]: * already running Jun 08 08:22:55 ubuntu kamailio_scscf[16495]: ...done. Jun 08 08:22:55 ubuntu systemd[1]: Started LSB: Start the Kamailio SIP proxy server. Jun 08 08:24:03 ubuntu systemd[1]: Stopping LSB: Start the Kamailio SIP proxy server... Jun 08 08:24:03 ubuntu kamailio_scscf[16517]: * Stopping Kamailio IMS S-CSCF: kamailio_scscf Jun 08 08:24:03 ubuntu kamailio_scscf[16517]: ...done. Jun 08 08:24:03 ubuntu systemd[1]: Stopped LSB: Start the Kamailio SIP proxy server. root@ubuntu:~/IMS_manual_scripts# systemctl start kamailio_scscf root@ubuntu:~/IMS_manual_scripts# systemctl status kamailio_scscf ● kamailio_scscf.service - LSB: Start the Kamailio SIP proxy server Loaded: loaded (/etc/init.d/kamailio_scscf; generated) Active: active (exited) since Mon 2020-06-08 08:27:23 EDT; 58s ago Docs: man:systemd-sysv-generator(8) Process: 16543 ExecStart=/etc/init.d/kamailio_scscf start (code=exited, status=0/SUCCESS) Jun 08 08:27:23 ubuntu /usr/local/sbin/kamailio[16559]: ERROR: <core> [db.c:457]: db_check_table_version(): invalid version 0 for table presentity found, expected 5 (check table structure and ta Jun 08 08:27:23 ubuntu /usr/local/sbin/kamailio[16559]: ERROR: presence [presence.c:367]: mod_init(): error during table version check Jun 08 08:27:23 ubuntu /usr/local/sbin/kamailio[16559]: ERROR: <core> [core/sr_module.c:898]: init_mod(): Error while initializing module presence (/usr/local/lib64/kamailio/modules/presence.so) Jun 08 08:27:23 ubuntu /usr/local/sbin/kamailio[16559]: WARNING: <core> [core/mem/q_malloc.c:480]: qm_free(): WARNING: free(0) called from cdp_avp: cdp_avp_mod.c: cdp_avp_destroy(226) Jun 08 08:27:23 ubuntu /usr/local/sbin/kamailio[16559]: INFO: cdp [cdp_mod.c:255]: cdp_exit(): CDiameterPeer child stopping ... Jun 08 08:27:23 ubuntu /usr/local/sbin/kamailio[16559]: INFO: cdp [cdp_mod.c:257]: cdp_exit(): ... CDiameterPeer child stopped Jun 08 08:27:23 ubuntu /usr/local/sbin/kamailio[16559]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Jun 08 08:27:23 ubuntu kamailio_scscf[16543]: * already running Jun 08 08:27:23 ubuntu kamailio_scscf[16543]: ...done. Jun 08 08:27:23 ubuntu systemd[1]: Started LSB: Start the Kamailio SIP proxy server. Any insight is appreciated. Thanks, _Martin

1 0

I use kamailio with fusionpbx And I have a question
by idan katz 16 Jun '20

16 Jun '20

HI I use kamailio with fusionpbx The fusionpbx on one server with a fixed IP address The kamailio on one server with a fixed IP address Two separate servers I use domains I redirect the domains to the kamailio server To register for phones Everything is fine and it works fine But I'm trying to connect to the fusionpbx GUI In a specific domain I'm not going into the fusionpbx The domain is targeted to kamailio Because of the telephone registration I need to provide a domain GUI for my clients Is there any way to perform only port 80 browser routing That I can access the GUI at the s fusionpbx Without prejudice to the routing of telephone registration in kamailio Thanks in advance for their reply Idan

2 1

Re: [SR-Users] How to resolve these mod_param errors in Kamailio 5.3.1?
by Henning Westerholt 15 Jun '20

15 Jun '20

Hello, please keep the list in CC have a look to the docs later in the README: 3.13. xavp_dst_mode (int) Control what fields are added to the XAVP specified by xavp_dst parameter. Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/> From: Muhammad Maab Saleem <Maab.Saleem(a)telenor.com.pk> Sent: Monday, June 15, 2020 7:10 AM To: Henning Westerholt <hw(a)skalatan.de> Subject: RE: How to resolve these mod_param errors in Kamailio 5.3.1? Hi, Henning. Thanks for your response. However, as I pointed out to him, this only fixes one of the parameter. I have three others where there is a conflict. I can't find any replacements for them. Do you have any pointers regarding them? Best, Maab Sensitivity: Internal From: Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> Sent: Saturday, June 13, 2020 6:50 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>> Cc: Muhammad Maab Saleem <Maab.Saleem(a)telenor.com.pk<mailto:Maab.Saleem@telenor.com.pk>> Subject: RE: How to resolve these mod_param errors in Kamailio 5.3.1? Hello, To quote the e-mail from Ovidiu some days ago: "Take a look at the new param: https://kamailio.org/docs/modules/5.3.x/modules/dispatcher.html#dispatcher.…<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkamailio.…> Up to version 5.2, regular AVPs were used, but starting with version 5.3 the regular AVPs were replaced by an XAVP." So you need to replace the old parameter with the new one. Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fskalatan.…> Kamailio services - https://gilawa.com<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgilawa.co…> From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of Muhammad Maab Saleem Sent: Friday, June 12, 2020 8:37 AM To: sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Subject: [SR-Users] How to resolve these mod_param errors in Kamailio 5.3.1? This is the error I get when I run ./kamailio -f /etc/kamailio/kamailio.cfg -E ________________________________ loading modules under config path: /usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/:/usr/lib/kamailio/modules_k/:/usr/lib/kamailio/modules/ 0(28369) ERROR: [core/modparam.c:140]: set_mod_param_regex(): parameter <dst_avp> of type <1> not found in module 0(28369) CRITICAL: [core/cfg.y:3539]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 378, column 61: Can't set module parameter 0(28369) ERROR: [core/modparam.c:140]: set_mod_param_regex(): parameter <grp_avp> of type <1> not found in module 0(28369) CRITICAL: [core/cfg.y:3539]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 379, column 61: Can't set module parameter 0(28369) ERROR: [core/modparam.c:140]: set_mod_param_regex(): parameter <cnt_avp> of type <1> not found in module 0(28369) CRITICAL: [core/cfg.y:3539]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 380, column 61: Can't set module parameter 0(28369) ERROR: [core/modparam.c:140]: set_mod_param_regex(): parameter <sock_avp> of type <1> not found in module 0(28369) CRITICAL: [core/cfg.y:3539]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 381, column 63: Can't set module parameter ERROR: bad config file (4 errors) ________________________________ These are the lines 378-381 from the config file modparam("dispatcher", "dst_avp", "$avp(DISPATCHER_DST_AVP)") modparam("dispatcher", "grp_avp", "$avp(DISPATCHER_GRP_AVP)") modparam("dispatcher", "cnt_avp", "$avp(DISPATCHER_CNT_AVP)") modparam("dispatcher", "sock_avp", "$avp(DISPATCHER_SOCK_AVP)") Best, Maab Sensitivity: Internal

1 0

How to resolve these mod_param errors in Kamailio 5.3.1?
by Muhammad Maab Saleem 13 Jun '20

13 Jun '20

This is the error I get when I run ./kamailio -f /etc/kamailio/kamailio.cfg -E ________________________________ loading modules under config path: /usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/:/usr/lib/kamailio/modules_k/:/usr/lib/kamailio/modules/ 0(28369) ERROR: [core/modparam.c:140]: set_mod_param_regex(): parameter <dst_avp> of type <1> not found in module 0(28369) CRITICAL: [core/cfg.y:3539]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 378, column 61: Can't set module parameter 0(28369) ERROR: [core/modparam.c:140]: set_mod_param_regex(): parameter <grp_avp> of type <1> not found in module 0(28369) CRITICAL: [core/cfg.y:3539]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 379, column 61: Can't set module parameter 0(28369) ERROR: [core/modparam.c:140]: set_mod_param_regex(): parameter <cnt_avp> of type <1> not found in module 0(28369) CRITICAL: [core/cfg.y:3539]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 380, column 61: Can't set module parameter 0(28369) ERROR: [core/modparam.c:140]: set_mod_param_regex(): parameter <sock_avp> of type <1> not found in module 0(28369) CRITICAL: [core/cfg.y:3539]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 381, column 63: Can't set module parameter ERROR: bad config file (4 errors) ________________________________ These are the lines 378-381 from the config file modparam("dispatcher", "dst_avp", "$avp(DISPATCHER_DST_AVP)") modparam("dispatcher", "grp_avp", "$avp(DISPATCHER_GRP_AVP)") modparam("dispatcher", "cnt_avp", "$avp(DISPATCHER_CNT_AVP)") modparam("dispatcher", "sock_avp", "$avp(DISPATCHER_SOCK_AVP)") Best, Maab Sensitivity: Internal

2 1

Dispatcher module and hash algorithm
by Luis Rojas G. 12 Jun '20

12 Jun '20

Hello, I noticed a couple of strange behaviors, using this version : kamailio-5.3.3-4.1.x86_64 I am using algorithm "0". Hash over Call-ID. The reason for that is that I am just re-sending the message, using send_udp(), to a destination in a group from file dispatcher.list. Kamailio is completely stateless, it does not need to remember anything. And using a hash over Call-ID I can be sure that any other message related to the same call will be sent to the same destination : retransmissions of the INVITE, CANCEL, ACK, BYE, etc. I general, it works, but I detected two problems. I have a group of 5 destinations, where every server is running at 80% of the nominal load. It's a 4 + 1 configuration, for redundancy. I know it's not 100% evenly distributed using hash over Call-ID, but in practice it's almost perfectly even. However, if one node is down, instead of having the four alive running at 100%, I get three running still at 80% capacity, and one is sent 160% of the load (which of course can't process). it seems, all traffic that was supposed to be sent to the failed node is transferred to the same unique destination. That implementation makes my solution for redundancy worthless. Why didn't the implementation use, for instance, a re-hash over the hash? That would allow to redistribute "evenly" over the remaining servers. I tried to solve this by repeating the entries in dispatcher.list, as I noticed that kamailio doesn't check if different lines contain duplicated uris. For instance, if I have two lines with "destination A", and one line with "destination B", like this: 0 sip:server_A 0 sip:server_A 0 sip:server_B I see that "destination A" receives twice the amount of SIP OPTIONS that "destination B" receives. And so, I used this dispatcher.list : 0 sip:server_1 0 sip:server_2 0 sip:server_3 0 sip:server_4 0 sip:server_5 0 sip:server_1 0 sip:server_3 0 sip:server_5 0 sip:server_2 0 sip:server_4 0 sip:server_1 0 sip:server_4 0 sip:server_2 0 sip:server_5 0 sip:server_3 0 sip:server_1 0 sip:server_5 0 sip:server_4 0 sip:server_3 0 sip:server_2 (it's not a random order. It follows a sequence) I thought : "what a genius I am. This way, if any node fails, and kamailio select the "next" to send the traffic to, it will distribute evenly over the rest". It doesn't work. I detected something that looks like a bug. If one entry is repeated at least once, for instance : 0 sip:server_1 0 sip:server_1 0 sip:server_2 0 sip:server_3 0 sip:server_4 0 sip:server_5 if server_1 is down, kamailio still sends some of the INVITEs to it. Not all of them, but many. I can see the SIP OPTIONS been sent to it, and the response "ICMP Destination Unreachable", so Kamailio knows that server_down. However, still sends INVITE requests to that failed node. Look at this trace : You can see all the failed SIP OPTIONS. Still, kamailio sends traffic to that server. It does not send traffic to a failed destination if it's listed only once in dispatcher.list Any ideas? Thanks in advance, Luis -- Luis Rojas Software Architect Sixbell Los Leones 1200 Providencia Santiago, Chile Phone: (+56-2) 22001288 mailto:luis.rojas@sixbell.com http://www.sixbell.com

1 1

Jump to page:

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