sr-users

sr-users@lists.kamailio.org

39 participants
37513 discussions

route request to multiple pstn gws
by 赵国杰 09 Jun '17

09 Jun '17

Hi all. I need to route calls to different counties to different pstn gateways. But in the config file, i can only set one pstn gw ip:port in pstn section. How should i do it? Can i use carrierroute module to do this? If yes, can anyone paste a config sample? many thanks Jesse

1 0

WITH_NATSIPPING option
by Nguyen Tran Nhan 08 Jun '17

08 Jun '17

I am config rtpproxy with kamailio but I am stuck at - option for NAT SIP OPTIONS keepalives: WITH_NATSIPPING It is configure in client side? Thanks, Nhan

2 3

route to different pstn
by zhaoguojie2010＠163.com 08 Jun '17

08 Jun '17

1 0

Re: [SR-Users] No private memory left
by Vuk Radovanovic 08 Jun '17

08 Jun '17

Its debian 8.8 Regards, Vuk -------- Original message -------- Sender: Daniel-Constantin Mierla <miconda(a)gmail.com> Time: Wed 6/7 12:07 To: Vuk Radovanovic <vuk(a)gripenpro.com>,"Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] No private memory left >Hello, > >what is your operating system? > >Cheers, >Daniel > > >On 07.06.17 11:26, Vuk Radovanovic wrote: >> Hi Daniel, >> >> So the ps auxw is telling me the starting options for shm and pkg >> memory (-m -M) and options for user and group are not defined when >> starting via init script. >> >> Ive checked the init script in case i made an error when changing the >> memory directive but its fine, as provided in the GIT package. >> >> I am running kamailio 5.0 from git. >> >> Userblacklist trying to load whole db at once sounds scary, my main >> goal was implementing a redis whitelist with around 5mil numbers, now >> I am wondering is it even feasible ? >> >> root 3181 0.1 0.3 222300 12216 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3183 0.0 0.0 222300 3856 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3184 0.0 0.0 222300 3732 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3185 0.0 0.0 222300 3732 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3186 0.0 0.0 222300 3732 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3187 0.0 0.0 222300 3732 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3188 0.0 0.0 222300 3736 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3189 0.0 0.0 222300 3736 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3190 0.0 0.0 222300 3736 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3191 0.0 0.0 222300 3736 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3192 0.0 0.0 222300 3736 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3195 0.0 0.0 222300 3736 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3196 0.0 0.0 222300 3736 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3199 0.0 0.0 222300 3736 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3201 0.0 0.0 222300 3736 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3203 0.0 0.0 222300 3736 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3204 0.0 0.0 222300 3740 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3206 0.0 0.0 222300 3736 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3207 0.0 0.0 222300 3736 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3209 0.0 0.0 222300 3736 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3211 0.0 0.0 222304 1620 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3213 0.0 0.0 222300 1620 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3214 0.0 0.1 222300 5524 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3215 0.0 0.1 222300 5520 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3217 0.0 0.1 222300 5520 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3220 0.0 0.1 222300 5520 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.cfg >> root 3221 0.0 0.1 222300 5520 ? S 11:18 0:00 >> /usr/local/sbin/kamailio -P /var/run/kamailio.pid -f >> /usr/local/etc/kamailio//kamailio.c

3 8

DROUTING Tables
by Annus Fictus 08 Jun '17

08 Jun '17

Hello, I can't find DROUTING Tables on the standard kamailio database. dr_gateways dr_rules dr_groups Have I to create them manually? Thank you Regards

3 3

KAMAILIO STARTUP ERROR
by christopher kamutumwa 08 Jun '17

08 Jun '17

hello all, I am new to kamailio on centos 7 and i have finished installation following steps below; http://computingforgeeks.com/how-to-install-latest-kamailio-sip-server-on-c… but when i try to startup service i get fail with below how can this be resolved? [root@li1496-213 ~]# systemctl status kamailio.service -l ● kamailio.service - SYSV: Kamailio is a fast, reliable and flexible SIP Server. Loaded: loaded (/etc/rc.d/init.d/kamailio; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2017-06-07 12:16:26 UTC; 1min 59s ago Docs: man:systemd-sysv-generator(8) Process: 26015 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, status=1/FAILURE) Jun 07 12:16:26 li1496-213.members.linode.com kamailio[26015]: 0(26023) ERROR: <core> [core/cfg.y:3264]: yyparse(): cfg. parser: failed to find command handle_publish (params 0) Jun 07 12:16:26 li1496-213.members.linode.com kamailio[26015]: 0(26023) CRITICAL: <core> [core/cfg.y:3404]: yyerror_at(): parse error in config file //etc/kamailio/kamailio.cfg, line 715, column 18: unknown command, missing loadmodule? Jun 07 12:16:26 li1496-213.members.linode.com kamailio[26015]: 0(26023) ERROR: <core> [core/cfg.y:3264]: yyparse(): cfg. parser: failed to find command handle_subscribe (params 0) Jun 07 12:16:26 li1496-213.members.linode.com kamailio[26015]: 0(26023) CRITICAL: <core> [core/cfg.y:3404]: yyerror_at(): parse error in config file //etc/kamailio/kamailio.cfg, line 718, column 20: unknown command, missing loadmodule? Jun 07 12:16:26 li1496-213.members.linode.com kamailio[26015]: ERROR: bad config file (7 errors) Jun 07 12:16:26 li1496-213.members.linode.com kamailio[26015]: 0(26023) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Jun 07 12:16:26 li1496-213.members.linode.com systemd[1]: kamailio.service: control process exited, code=exited status=1 Jun 07 12:16:26 li1496-213.members.linode.com systemd[1]: Failed to start SYSV: Kamailio is a fast, reliable and flexible SIP Server.. Jun 07 12:16:26 li1496-213.members.linode.com systemd[1]: Unit kamailio.service entered failed state. Jun 07 12:16:26 li1496-213.members.linode.com systemd[1]: kamailio.service failed. regards chris

2 2

Docs: database structure
by Daniel-Constantin Mierla 07 Jun '17

07 Jun '17

Hello, I regenerated recently the document with the details for Kamailio's database structure, it is available at: * https://kamailio.org/docs/db-tables/kamailio-db-devel.html If you haven't read it so far, it is a good source to understand the purpose of the fields needed by kamailio from database. Contributions to the document are more than appreciated! You can update the xml files from src/lib/srdb1/schema/ and then make a pull request via github. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

1 0

No private memory left
by Vuk Radovanovic 07 Jun '17

07 Jun '17

Hello, I am having trouble with userblacklist module. I am using mysql db, when globalblacklist table is empty or has couple of records kamailio loads fine. When I populate the table with cca 50k entries I get an error no private memory error as pasted below. I have edited both the init.d script and /etc/default cfg file to to have 1GB pkg and 2 GB SHM memory with no change. Init script change: SHM_MEMORY=2048 PKG_MEMORY=1024 Init script output. Jun 07 01:03:45 km systemd[1]: Starting Kamailio SIP Server... Jun 07 01:03:45 km kamctl[1377]: ** INFO: Starting Kamailio : Jun 07 01:03:46 km /usr/local/sbin/kamailio[1405]: ERROR: <core> [db_row.c:114]: db_allocate_row(): no private memory left Jun 07 01:03:46 km /usr/local/sbin/kamailio[1405]: ERROR: db_mysql [km_row.c:57]: db_mysql_convert_row(): could not allocate row Jun 07 01:03:46 km /usr/local/sbin/kamailio[1405]: ERROR: db_mysql [km_res.c:188]: db_mysql_convert_rows(): error while converting row #41249 Jun 07 01:03:46 km /usr/local/sbin/kamailio[1405]: ERROR: db_mysql [km_res.c:217]: db_mysql_convert_result(): error while converting rows Jun 07 01:03:46 km /usr/local/sbin/kamailio[1405]: ERROR: db_mysql [km_dbase.c:261]: db_mysql_store_result(): error while converting result Jun 07 01:03:46 km /usr/local/sbin/kamailio[1405]: ERROR: <core> [db_query.c:139]: db_do_query_internal(): error while storing result Jun 07 01:03:46 km /usr/local/sbin/kamailio[1405]: ERROR: userblacklist [db.c:129]: db_reload_source(): error while executing query on db table 'globalblacklist' Jun 07 01:03:46 km /usr/local/sbin/kamailio[1405]: ERROR: userblacklist [userblacklist.c:610]: reload_sources(): cannot reload source from 'globalblacklist' Jun 07 01:03:46 km /usr/local/sbin/kamailio[1405]: ERROR: <core> [core/sr_module.c:923]: init_mod_child(): Error while initializing module userblacklist (/usr/local/lib64/kamailio/modules/userblacklist.so) Jun 07 01:03:46 km /usr/local/sbin/kamailio[1405]: ERROR: <core> [core/pt.c:330]: fork_process(): init_child failed for process 1, pid 1405, "udp receiver child=0 sock=127.0.0.1:5060" Jun 07 01:03:46 km /usr/local/sbin/kamailio[1405]: CRITICAL: <core> [main.c:1606]: main_loop(): Cannot fork Jun 07 01:03:46 km /usr/local/sbin/kamailio[1403]: ALERT: <core> [main.c:741]: handle_sigs(): child process 1405 exited normally, status=255 Jun 07 01:03:48 km kamctl[1377]: ** ERROR: PID file /var/run/kamailio.pid does not exist -- Kamailio start failed Jun 07 01:03:48 km systemd[1]: kamailio.service: control process exited, code=exited status=1 Jun 07 01:03:48 km systemd[1]: Failed to start Kamailio SIP Server. Jun 07 01:03:48 km systemd[1]: Unit kamailio.service entered failed state. Regards, Vuk

2 4

Dispatcher - postponed GW restoration
by Ivan Matvieiev 07 Jun '17

07 Jun '17

Hello I'm trying to implement following scenario: - remote GW is Active (receives calls) and not Probed (no SIP Options are being sent); - in case if remote GW failes, it starts to be Probed and become Inactive ("ds_probing_threshold" does this); - when remote GW returns it remains in Probed and Inactive state for a while; - after probing for some amount of time (or a number of successful responses) it become Active and not Pobed (it can be achieved with "ds_inactive_threshold"); The issue I'm facing is that "ds_inactive_threshold" will bring GW back only after the number of successful responses that can't be provided using "ds_probing_mode" with value 2. It stops to produce SIP Options by successful reply before threshold of successful replies is reached. In case of "ds_probing_mode" with value 3 I haven't found a way to stop Probing when GW transits to state Active. Is there a way to make GW Active after it was Inactive and was successfully probed for arbitrary number of times? Some valuable information: Kamailio: v 4.4.2 ... modparam("dispatcher", "ds_ping_interval", 3) modparam("dispatcher", "ds_probing_threshold", 3) modparam("dispatcher", "ds_inactive_threshold", 60) modparam("dispatcher", "ds_probing_mode", 2) ... If I missed any information please tell me. With best regards Ivan

1 0

TLS to UDP translation
by 赵国杰 07 Jun '17

07 Jun '17

Hi everyone, I have a kamailio server with TLS enabled. I need to forword UAC request to a PSTN gateway which only support UDP. Is it possible that kamailio can translate this with proper configuration? How can i do this? many thanks Jesse

2 5

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