sr-users September 2018

sr-users@lists.kamailio.org

72 participants
127 discussions

Ipv6_to_ipv4
by Karlheinz Knapp 04 Sep '18

04 Sep '18

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 ?

1 0

event_route [tcp:closed] not executed
by Juha Heinanen 04 Sep '18

04 Sep '18

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.

2 10

dispatcher probe
by volga629＠networklab.ca 04 Sep '18

04 Sep '18

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

3 4

Can't connect to local MySQL server (13 "Permission denied")
by Ginhoux, Patrick 04 Sep '18

04 Sep '18

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

3 6

load-balance to registered trunks?
by David Villasmil 03 Sep '18

03 Sep '18

Hello guys, I've got this scenario where some gateways will register on my kamailio and i need to send them calls on a load-balance fashion. is this possible? Thanks! Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337 ᐧ

4 6

Dispatcher question
by Igor Olhovskiy 03 Sep '18

03 Sep '18

Hi! I’m having some issues with dispatcher and cannot get why it’s not working Idea is to use ds_next_dst right after ds_select_dst I’m having it like this modparam("dispatcher", "list_file", "/tmp/dispatcher.list") modparam("dispatcher", "flags", 2) # Enable dispather failover modparam("dispatcher", "xavp_dst", "_dispacher_dst_list_") … ds_select_dst(«1», «0»); … # Some extra check on $du here … ds_next_dst(); But get in logs WARNING: dispatcher [dispatch.c:2285]: ds_update_dst(): no xavp uri field in next destination record But contents of /tmp/dispatcher.list is 1 sip:172.28.0.12:5060 1 sip:172.28.0.19:5060 Can I somehow dump xavp_dst var to check if ds_select_dst is correct? kamailio 5.2.0-dev6 Regards, Igor

5 17

handle_ruri_alias() question or issue?
by Wilkins, Steve 02 Sep '18

02 Sep '18

Good Morning All, The following Incoming request came in => SIP Incoming Request: [[BYE sip:2406506175@20.20.20.20:5060;alias=10.10.10.5~55157~2 SIP/2.0 I called handle_ruri_alias(), and expected the destination and port to be set to 10.10.10.5:55157, but it was not. It was left 20.20.20.20:5060. Is my thinking correct or is there another way to set the destination and port to the alias? Thanks All!, -Steve

3 9

2026

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