sr-users September 2018

sr-users@lists.kamailio.org

72 participants
123 discussions

by Евгений Голей

Hello! Kamilio version 5.1.0 Please tell me why the module dispatcher does not correctly determine the availability of destination gateways. The scheme is as follows: Kamailio (udp:XX.XX.XX.XX:5060) ----- Provider_1 -----> (sip:aa.bb.cc.dd:5060) Dest GW Kamailio (udp:YY.YY.YY.YY:5060) ------- Provider_2 -----/ In table dispatcher: setid | destination | flags | priority | attrs 17 | sip:aa.bb.cc.dd:5060 | 8 | 50 | socket=udp:XX.XX.XX.XX:5060 17 | sip:aa.bb.cc.dd:5060 | 8 | 40 | socket=udp:YY.YY.YY.YY:5060 That is, our server controls the availability of the remote gateway through two local sockets, in order to switch to the backup if it is not available through the primary Internet provider. But as I understand at the moment when determining the availability of a remote gateway, the outgoing socket does not play any role, that is, if the remote gateway is not accessible through the secondary operator (priority is less than the primary one), only the one that has priority above is always inactive. Are there any solutions to this problem? BR. Evgeniy

5 years, 10 months

From URI attribute for dispatcher target

by Giacomo Vacca

Hi all, I was looking for a solution to set a dedicated From URI in OPTIONS requests to a specific dispatcher target. ds_ping_from ( https://www.kamailio.org/docs/modules/devel/modules/dispatcher.html#dispatc…) applies globally, why I needed the granularity of a single target. With these changes to the dispatcher module I get what I need: https://github.com/kamailio/kamailio/commit/3f9c38be11416f7abe5c4448088ba66… I can just add an attribute to the others, e.g. instead of *1 sip:127.0.0.1:7070 <http://127.0.0.1:7070> 0 1* something like: *1 sip:127.0.0.1:7070 <http://127.0.0.1:7070> 0 1 ping_from=sip.custom.com <http://sip.custom.com>* When the ping_from attribute is not specified, the general ds_ping_from applies and is used. This would save me from a solution like intercepting the outgoing OPTIONS and manipulating the From header. Does this approach make sense? Are there other ways already available to achieve this? Thanks, Giacomo

5 years, 10 months

SCA: sca_call_info_bye_handler: no in-use callee appearance for BYE

by Asgaroth

Hi All, I've just started playing with the SCA module and am encountering an issue whereby SCA cannot seem to find an in-use appearance for the BYE message. From my limited understanding of SCA, the module, in this case, appears to be trying to track the state of the call using callid as there are no call-info headers in the signalling for it to extract and use. I call sca_call_info_update() for initial invite, 100 response, 180 response, 200 response and again for the terminating bye. When I answer the call, at the 200 ok for the initial invite, I can see sca sending a notify to the subscribed devices indicating appearance state being active. I can verify this with kamcmd sca.all_appearances. However, when I hang up the call, when sca_call_info_update() is fired for the bye message it fails with the following error message: sca [sca_call_info.c:1587]: sca_call_info_bye_handler(): sca_call_info_bye_handler: no in-use callee appearance for BYE <aor> from <from uri>, call-ID 7989c223-2ba4-1237-1888-20474786734e I cannot seem to track down where this is failing for me, or where I may be missing something in my configuration. sca.all_appearances does appear to have the entry mentioned in the failure message, there must be something I'm missing somewhere. Is there anyone out there who is using the sca module and may have a moment to assist with this issue. I have a pcap trace that I can send privately. Any assistance would be greatly appreciated. Thanks

5 years, 10 months

Kamailio v5.1.5 Released

by Daniel-Constantin Mierla

Hello, Kamailio SIP Server v5.1.5 stable release is out. This is a maintenance release of the latest stable branch, 5.1, that includes fixes since the release of v5.1.4. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.1.x. Deployments running previous v5.1.x versions are strongly recommended to be upgraded to v5.1.5. For more details about version 5.1.5 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2018/08/kamailio-v5-1-5-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! 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

5 years, 10 months

Problem with reconnection to database server

by Minh Phan

Hi List, My Kamailio instance is disconnected from database server (Postgres) quite often (after running for some days) and it won't manage to reconnect. Any idea why this happens? Normally it try to reconnect when connection with the DB is lost, desn't it? Bellow are the related log messages. Best regards, Minh Phan Sep 4 11:31:20 : ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query Sep 4 11:31:20 : ERROR: db_postgres [km_dbase.c:559]: db_postgres_store_result(): invalid query, execution aborted Sep 4 11:31:20 : ERROR: db_postgres [km_dbase.c:561]: db_postgres_store_result(): driver error: PGRES_FATAL_ERROR, Sep 4 11:31:20 : WARNING: db_postgres [km_dbase.c:609]: db_postgres_insert(): unexpected result returned Sep 4 11:31:20 : ERROR: topos [tps_storage.c:599]: tps_db_insert_dialog(): failed to store message Sep 4 11:31:20 : ERROR: topos [tps_storage.c:412]: tps_storage_record(): failed to store Sep 4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 : ERROR: db_postgres [km_dbase.c:267]: db_postgres_submit_query(): 0x2b11c92b8b18 PQsendQuery Error: Query: select rectime,a_callid,a_uuid,b_uuid,direction,x_via,x_vbranch,x_rr,y_rr,s_rr,x_uri,x_tag,s_method,s_cseq,a_contact,b_contact,as_contact,bs_contact,a_tag,b_tag from topos_t where x_vbranch='z9hG4bK66fa.3f007792000000000000000000000000.0' Sep 4 11:31:20 : ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Sep 4 11:31:20 : ERROR: topos [tps_storage.c:961]: tps_db_load_branch(): failed to query database Sep 4 11:31:20 : WARNING: topos [tps_storage.c:400]: tps_storage_record(): no local address - do record routing for all initial requests Sep 4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 kamailio[26608]: WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 kamailio[26608]: WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 : ERROR: db_postgres [km_dbase.c:267]: db_postgres_submit_query(): 0x2b11c92b8b18 PQsendQuery Error: Query: insert into topos_d (rectime,a_callid,a_uuid,b_uuid,a_contact,b_contact,as_contact,bs_contact,a_tag,b_tag,a_rr,b_rr,s_rr,iflags,a_uri,b_uri,r_uri,a_srcaddr,b_srcaddr,s_method,s_cseq ) values ('2018-09-04 11:31:20','1ff8d1d7606f7416-26611(a)192.168.70.106 ','','','','','','','ae86e22a93159b5c6ac75234cdf26c1b-44e5','','','','',0,'','','','','','OPTIONS','10') Sep 4 11:31:20 kamailio[26608]: WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 : ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query Sep 4 11:31:20 kamailio[26608]: ERROR: db_postgres [km_dbase.c:267]: db_postgres_submit_query(): 0x2b11c92b8b18 PQsendQuery Error: Query: select rectime,a_callid,a_uuid,b_uuid,direction,x_via,x_vbranch,x_rr,y_rr,s_rr,x_uri,x_tag,s_method,s_cseq,a_contact,b_contact,as_contact,bs_contact,a_tag,b_tag from topos_t where x_vbranch='z9hG4bK86fa.424ded00000000000000000000000000.0' Sep 4 11:31:20 kamailio[26608]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Sep 4 11:31:20 : ERROR: db_postgres [km_dbase.c:559]: db_postgres_store_result(): invalid query, execution aborted Sep 4 11:31:20 kamailio[26608]: ERROR: topos [tps_storage.c:961]: tps_db_load_branch(): failed to query database Sep 4 11:31:20 : ERROR: db_postgres [km_dbase.c:561]: db_postgres_store_result(): driver error: PGRES_FATAL_ERROR, Sep 4 11:31:20 : WARNING: db_postgres [km_dbase.c:609]: db_postgres_insert(): unexpected result returned Sep 4 11:31:20 : ERROR: topos [tps_storage.c:599]: tps_db_insert_dialog(): failed to store message Sep 4 11:31:20 : ERROR: topos [tps_storage.c:412]: tps_storage_record(): failed to store Sep 4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 : ERROR: db_postgres [km_dbase.c:267]: db_postgres_submit_query(): 0x2b11c92b8b18 PQsendQuery Error: Query: select rectime,a_callid,a_uuid,b_uuid,direction,x_via,x_vbranch,x_rr,y_rr,s_rr,x_uri,x_tag,s_method,s_cseq,a_contact,b_contact,as_contact,bs_contact,a_tag,b_tag from topos_t where x_vbranch='z9hG4bK76fa.d33cc801000000000000000000000000.0' Sep 4 11:31:20 : ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Sep 4 11:31:20 : ERROR: topos [tps_storage.c:961]: tps_db_load_branch(): failed to query database Sep 4 11:31:20 : WARNING: topos [tps_storage.c:400]: tps_storage_record(): no local address - do record routing for all initial requests Sep 4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 : WARNING: db_postgres [km_dbase.c:259]: db_postgres_submit_query(): postgres query command failed, connection status 1, error [no connection to the server#012] Sep 4 11:31:20 : ERROR: db_postgres [km_dbase.c:267]: db_postgres_submit_query(): 0x2b11c92b8b18 PQsendQuery Error: Query: insert into topos_d (rectime,a_callid,a_uuid,b_uuid,a_contact,b_contact,as_contact,bs_contact,a_tag,b_tag,a_rr,b_rr,s_rr,iflags,a_uri,b_uri,r_uri,a_srcaddr,b_srcaddr,s_method,s_cseq ) values ('2018-09-04 11:31:20','1ff8d1d7606f7417-26611(a)192.168.70.106 ','','','','','','','ae86e22a93159b5c6ac75234cdf26c1b-917f','','','','',0,'','','','','','OPTIONS','10') Sep 4 11:31:20 : ERROR: <core> [db_query.c:235]: db_do_insert_cmd(): error while submitting query Sep 4 11:31:20 : ERROR: db_postgres [km_dbase.c:559]: db_postgres_store_result(): invalid query, execution aborted Sep 4 11:31:20 : ERROR: db_postgres [km_dbase.c:561]: db_postgres_store_result(): driver error: PGRES_FATAL_ERROR,

5 years, 10 months

DMQ mem leak issues

by Rogelio Perez

Hello, We're running three instances of Kamailo v5.14 as registrars handling registrations from ~2000 SIP clients, with one instance being primary and the other two as backups. The three of them are using the dmq and dmq_usrloc modules to synchronize user locations, however after a couple of days of operation the two failover instances show memory leak behaviors, with mem usage assigned to the core taking all available resources. When this happens we've noticed that: - The shared memory used by the function "sip_msg_shm_clone" spikes (from 1kb to 1.5GB). - The shared memory used by the function "dmq:worker.c:job_queue_push" also increases, but not as much (from 1kb to 1MB) - DMQ request are not being answered (with a 200 OK) by the affected instance during this memory leak, which make us think that DMQ module becomes unresponsive. A few more notes: - The failover instances are doing nothing except receiving replicated contacts. - The shared memory grows at the same rate on both instances, but the critical behavior never happens at the same time. - We are allocating 1GB memory on startup to each instance. - We store the location DB in a psql DB and we load it at startup. - We didn't find any errors in syslog, even at debug level. Has anyone experienced a similar issue who can suggest a possible solution? Thanks, Rogelio Perez Telnyx

5 years, 10 months

Ipv6_to_ipv4

by Karlheinz Knapp

i have tested the sample config from: https://kb.asipto.com/kamailio:kamailio-mixed-ipv4-ipv6 i found that i can register with v4 to kamailio and to the provider if i user ipv6 to kamailio and ipv4 to provider i can´t register. the packet from the provider contain a via entry which is missing from kamailio to my phone. Someone have a solution ?

5 years, 10 months

event_route [tcp:closed] not executed

by Juha Heinanen

Based on comment: https://github.com/kamailio/kamailio/issues/171#issuecomment-418175840 I gave event_route [tcp:closed] a try: event_route [tcp:closed] { # Handle TCP connection close xlog("L_INFO", "$proto connection closed ($conid)\n"); } Nothing comes to syslog when I quit my baresip UA that according to wireshark closes its TCP connection after un-registration (fin - fin - ack). I have not set closed_event param, because according to README, it defaults to 1.

5 years, 10 months

dispatcher probe

by volga629＠networklab.ca

Hello Everyone, Is possible access OPTIONS packet generated by dispatcher probe ? I am trying insert something like this. if(is_method("OPTIONS") && $hdr(User-Agent)=~"kamailio") { append_hf("X-Node-ID: $avp(node_id)\r\n"); } volga629

5 years, 10 months

Can't connect to local MySQL server (13 "Permission denied")

by Ginhoux, Patrick

Hi, In a previous post ([SR-Users] Questions about changes between 5.0.1 and 5.0.7 <https://lists.kamailio.org/pipermail/sr-users/2018-August/102442.html> ), I reported problem to upgrade my kamailio from 5.0.1 to 5.0.7-7 level. With help from some people, it was finally fixed on my test server in my lab. Now I was expecting to do the same upgrade on a real server using these packages: kamailio-5.0.7-7.el7.x86_64.rpm kamailio-ims-5.0.7-7.el7.x86_64.rpm kamailio-mysql-5.0.7-7.el7.x86_64.rpm kamailio-perl-5.0.7-7.el7.x86_64.rpm kamailio-snmpstats-5.0.7-7.el7.x86_64.rpm But kamailio failed to connect the local MySQL server : Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]: DEBUG: <core> [db.c:209]: db_bind_mod(): using db bind api for db_mysql Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]: DEBUG: <core> [db.c:314]: db_do_init2(): connection 0x7fef779958f8 not found in pool Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]: DEBUG: db_mysql [km_my_con.c:98]: db_mysql_new_connection(): opening connection: mysql://xxxx:xxxx@localhost/siprouter Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]: ERROR: db_mysql [km_my_con.c:129]: db_mysql_new_connection(): driver error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13 "Permission denied") Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]: ERROR: <core> [db.c:318]: db_do_init2(): could not add connection to the pool Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]: ERROR: htable [ht_db.c:92]: ht_db_open_con(): failed to connect to the database Aug 31 08:16:20 in52inmvt2router1-mvt-tpm-sipr /usr/sbin/kamailio[6365]: ERROR: <core> [core/sr_module.c:974]: init_mod(): Error while initializing module htable (/usr/lib64/kamailio/modules/htable.so) My "kamailio.cfg" contains the following command: modparam("htable", "db_url", "mysql://siprouter:password@localhost/siprouter") The service unit : "/usr/lib/systemd/system/kamailio.service" content is : [Unit] Description=Kamailio (OpenSER) - the Open Source SIP Server After=network.target mysql.service [Service] Type=simple User=kamailio Group=kamailio Environment='CFGFILE=/etc/kamailio/kamailio.cfg' Environment='SHM_MEMORY=1024' Environment='PKG_MEMORY=8' EnvironmentFile=-/etc/sysconfig/kamailio ExecStart=/usr/sbin/kamailio -DD -P /var/run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY Restart=on-failure [Install] WantedBy=multi-user.target The "/etc/sysconfig/kamailio" content is : # # Kamailio startup options # # # Kamailio startup options # # Set to yes to enable kamailio, once configured properly. RUN_KAMAILIO=yes # User to run as USER=kamailio # Group to run as GROUP=kamailio # Amount of shared memory to allocate for the running Kamailio server (in Mb) SHM_MEMORY=1024 # Amount of per-process (package) memory to allocate for Kamailio (in Mb) PKG_MEMORY=8 Below the existing user in mysql : mysql:root:(none)> use mysql; Database changed mysql:root:mysql> select user,host from user; +-----------+-----------+ | user | host | +-----------+-----------+ | myadmin | % | | siprouter | % | | kamailio | localhost | | root | localhost | +-----------+-----------+ I have a symlink to locate the my.cnf : ln -s /myqdata/mysiprdb/data/my.cnf /etc/my.cnf And also this link to fix a htable reload problem : ln -s /myqdata/mysiprdb/data/mysiprdb.sock /var/lib/mysql/mysql.sock I don't find what the problem is this time. So if there is people that could help on the issue, thanks in advance. Cordialement. Patrick GINHOUX

5 years, 10 months

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 September 2018