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
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
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
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
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
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
Hello all,
We found out that when using cfg variables certain keywords are not
allowed, and Kamailio logs a generic error:
<core> [cfg.y:3368]: yyerror_at(): parse error in config file
/etc/kamailio/kamailio.cfg, line 256, column 9-14: syntax error
For example we cannot use words like enable/disable for var name or
group name but we can use disabled or enabled:
group_name.enable = 1 descr "test variable"
Looking into the cfg.lex file, I noticed that these are keywords which
will be interpreted as values (I don't have too much experience with
flex/bison so I am not sure I got this right).
We have been using Kamailio 4.4 to test this, but I think it is not
specific to a version.
Is this behavior documented somewhere? If not, where should it be
documented? Also can we have a more specific log message in this case?
Thank you,
Claudiu Boriga.
Hello,
I have an issue with the behavior of ds_select_dst() method in case of
using algorithm 8 (dispatch based on priority). In case both destinations
are available, they are used alternatively, instead of always using the one
with the highest priority.
By searching through the mailing list I found that the lower the priority
number, the higher the priority (1 is first, 2 is second, etc.).
Based on this, I set the following in dispatcher.list:
7 sip:10.126.54.51:5060;transport=sctp 9 1
7 sip:10.126.55.51:5060;transport=sctp 9 2
After running "kamcmd dispatcher.reload" and "kamcmd dispatcher.list", I
have the confirmation that the priorities are correctly set:
SET: {
ID: 7
TARGETS: {
DEST: {
URI: sip:10.126.55.51:5060
;transport=sctp
FLAGS: AP
PRIORITY: 2
}
DEST: {
URI: sip:10.126.54.51:5060
;transport=sctp
FLAGS: AP
PRIORITY: 1
}
}
}
The dispatcher settings from kamailio.cfg is the following:
modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list")
modparam("dispatcher", "flags", 2)
modparam("dispatcher", "ds_ping_interval", 10)
modparam("dispatcher", "ds_ping_method", "OPTIONS")
modparam("dispatcher", "ds_ping_from", "sip:kamailio@sdp-t-lb2")
modparam("dispatcher", "ds_probing_mode", 3)
modparam("dispatcher", "dst_avp", "$avp(AVP_DST)")
modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)")
modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)")
modparam("dispatcher", "sock_avp", "$avp(AVP_SOCK)")
And the code which should do the displatch is the following:
if (ds_is_from_list(7, 3, "$ru")) {
remove_hf("Route");
if(!ds_select_dst("7", "8")) {
send_reply("404", "No destination");
exit;
}
}
With the settings above, I was expecting to always have the messages
delivered to 10.126.54.51. Instead, they are dispathed to 10.126.54.51 and
10.126.55.51 alternatively.
Thanks a lot,
Cristian
Dear Kamailio,
My name is Sain, I from Colombia.
I wonder if is possible to use Kamailio with Docker in Ubuntu 16 ?
Also, respectfully do you have an easy installation manual or any recommendation to start doing some testing?
I am interesting to learn more about Kamailio .
Thank you very much
