sr-users

sr-users@lists.kamailio.org

27 participants
37381 discussions

Finding a way to gracefully restart kamailio with dialog module enabled and DMQ sync
by Benoît Panizzon 07 Jul '23

07 Jul '23

Hi Gang We are still having massive issues on how to safely reload kamailio after config changes when using the dialog module and DMQ. If there are active dialogues, kamailio corrupts them on a restart even when using MySQL as dialog backend. As we use two core nodes for redundancy, I am looking for a way to gracefully restart kamailio. I am considering adding some key in a hash table or anything else I can reload on runtime to indicate to kamailio not to accept any new calls (effectively rejecting Invites without To-Tag with 503 causing the registrar or IC peer to hopefully resend the invite to the other node). Then wait, until no more dialogues are active, so kamailio can safely be restarted. My Issue now: How can I find out, one specific node does not have any active dialogues? 'kamcmd dlg.stats_active' returns the count of all DMQ synced nodes, not of the local one. And suggestions or any other ideas how I can 'reload' the kamailio config without disrupting active dialogues? My last resort would be to look into the database: modparam("dialog", "h_id_start", -1) # Use server_id modparam("dialog", "h_id_step", 2) So odd/even H_ID should tell me the number per node. But I see a lot of orphan dialogues hanging around in the database not being cleaned so I guess that will not be reliable at all. Yes, I know I will get the question: 'Why do you need to restart kamailio that often'. We have started production on our kamailio based TSP platform. And of course, despite a LOT of testing beforehand, there is always some issue that pops up. At the moment, I have to implement a config change about once or twice a week to fix some new minor issues. I hope, somewhen in the future we will hopefully have a stable config which will last for several months, but at the moment this is the situation. -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

3 4

Randomize calling number
by Ali Taher 06 Jul '23

06 Jul '23

Hello, What is the best way to change the calling number to a random number (based on specific pattern, like number of digits for example) in an invite packet without using a database. So the scenario is : * receive an invite packet from certain source * change the calling number * send back the invite packet including the new calling number to the original source. Regards, Ali Taher

3 7

302 Handling issue in failure route
by Devang Dhandhalya 05 Jul '23

05 Jul '23

Hello All I am handling 302 response in the failure route and when receiving 302 response in kamailio, it's not going into the failure route , kamailio just executing the onreply route when 302 response are received. A few days ago the same code with failure route worked but now it does not. i dont know why kamailio is not executing a failure route from where we can redirect calls to another server. code snippet route[RELAY]{ t_on_reply("MANAGE_REPLY"); t_on_failure("MANAGE_FAILURE"); t_on_branch("MANAGE_BRANCH"); if (!t_relay()) { sl_reply_error(); } exit; } failure_route[MANAGE_FAILURE] { if (t_is_canceled()) { exit; } if (t_check_status("302")){ get_redirects("*"); $ru= $T_rpl($sel(contact.uri)); route(RELAY); } } kamailio version : 5.6.4 Please suggest if I am doing anything wrong. -- Regards, *Devang Dhandhalya* -- *Disclaimer* In addition to generic Disclaimer which you have agreed on our website, any views or opinions presented in this email are solely those of the originator and do not necessarily represent those of the Company or its sister concerns. Any liability (in negligence, contract or otherwise) arising from any third party taking any action, or refraining from taking any action on the basis of any of the information contained in this email is hereby excluded. *Confidentiality* This communication (including any attachment/s) is intended only for the use of the addressee(s) and contains information that is PRIVILEGED AND CONFIDENTIAL. Unauthorized reading, dissemination, distribution, or copying of this communication is prohibited. Please inform originator if you have received it in error. *Caution for viruses, malware etc.* This communication, including any attachments, may not be free of viruses, trojans, similar or new contaminants/malware, interceptions or interference, and may not be compatible with your systems. You shall carry out virus/malware scanning on your own before opening any attachment to this e-mail. The sender of this e-mail and Company including its sister concerns shall not be liable for any damage that may incur to you as a result of viruses, incompleteness of this message, a delay in receipt of this message or any other computer problems.

3 3

SL absorbed ACK is counted as dropped by core.drop_requests
by Kaufman 03 Jul '23

03 Jul '23

Just checking to see if this is the designed behavior. The SL module will attempt to match ACKs for stateless replies and handle them (absorb them?). The question I have is that it looks as though this ACK gets counted as dropped by the core.drop_requests from the KEX module. Tested using this config: #!KAMAILIO loadmodule "pv" loadmodule "sl" loadmodule "xlog" loadmodule "kex" loadmodule "corex" loadmodule "ctl" modparam("sl", "bind_tm", 0) route { xinfo("[$ci] $rm Request. Src:[$si:$sp] RURI:[$ru] To:[$tu] From:[$fu]\n"); sl_send_reply("404", "Not Found"); } event_route[sl:filtered-ack] { xnotice("sl:filtered-ack ACK [$ci] to local reply absorbed\n"); } Then validate by kamcmd stats.fetch core:drop_requests Is this the designed and "correct" behavior? Kaufman

3 4

Kamailio v5.7.1 Released
by Daniel-Constantin Mierla 28 Jun '23

28 Jun '23

Hello, Kamailio SIP Server v5.7.1 stable release is out. This is a maintenance release of the latest stable branch, 5.7, that includes fixes since the release of v5.7.0. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.7.x. Deployments running previous v5.7.x versions are strongly recommended to be upgraded to v5.7.1. For more details about version 5.7.1 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2023/06/kamailio-v5-7-1-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.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - www.kamailioworld.com

1 0

Forward Registration
by nutxase 28 Jun '23

28 Jun '23

Hi All I have setup kamailio using websockets(wss) i am trying to forward any registration that comes to kamailio to go to asterisk, so in theory kamailio is a registration proxy i have set rewritehostport("xxx.xxx.xxx[:5080](http://node3.sipalto.com:5080)"); the registration forwards fine but the contact on asterisk side shows as sip:xxx:kamailioip.xxxx.invalid so therefore asterisk sees the sip peer as offline what am i missing :( Sent with [Proton Mail](https://proton.me/) secure email.

1 0

Releasing v5.7.1
by Daniel-Constantin Mierla 28 Jun '23

28 Jun '23

Hello, I am considering to release Kamailio v5.7.1 (out of branch 5.7) this week (likely on Wednesday or Thursday, Jun 28/29, 2023). If anyone is aware of issues not yet on the bug tracker, report them there asap in order to have a better chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - www.kamailioworld.com

1 1

Matching the From Username in LCR rule table
by harneet singh 27 Jun '23

27 Jun '23

Hi Experts, We wished to used the LCR Module to be able to select the Gateway(s) to send the calls to based on the From(Caller) Username. Based on the LCR Documentation, the usage of other fields like request URI or prefix etc is pretty clear. But for the From Usename I am having certain trouble understanding the same. It refers to some mtree. Excerpt below: "A gateway matches a request if user part of Request-URI matches "prefix", caller URI matches "from_uri" pattern,* caller URI userpart matches mtree with "mt_value"*, and callee URI matches "request_uri" pattern in a tuple that is associated with the gateway." Can someone explain/ share a sample lcr_rule table entries for the From Username that can be matched against the incoming sip message for gw selection? Do we need to manually create an mtree by the name "*lcr*". Asking based on the below section in LCR documentation? Any pointers are highly appreciated. 3.35. mtree (string) Name of mtree to which load_gws() matches caller URI userpart. *Default value is "lcr".* Regards, Harneet Singh -- "Once you eliminate the impossible, whatever remains, no matter how improbable, must be the truth" - Sir Arthur Conan Doyle

2 3

uac_replace() and uac_restore debug help
by Duarte Rocha 24 Jun '23

24 Jun '23

Hello, I'm currently experiencing some odd behaviours when using these functions and I need some help debugging to find the root of the issue. I receive a call from a client and do some changes to the To and From header using auto mode with password. Encrypted info goes on the Record-Route header parameters (vsf\vst) normally. 1 - On subsequent requests sent by the originating client, domains on To and From header are different from the ones sent in the first INVITE. In this scenario, somehow the automatic modifying has errors on the end result. Can the different domains affect the end result of the automatic modifying or only the vsf\vst parameters and password are needed to the auto replace\restore? 2 - How can I decrypt the info on vsf and vst parameters in order to verify the info sent and the encryption? Cheers, Duarte Rocha

2 1

uac_restore behaviour question
by Duarte Rocha 22 Jun '23

22 Jun '23

Hello, I have some questions regarding uac_replace methods. When I receive the first INVITE from someone I change To and From using uac_replace_to() and uac_replace_from(). I do this only on first INVITES. In order to restore them I use the "auto" so the changes are restored automatically in replies or requests sent to the call originator.. In the case of subsequent requests from the originator kamailio still changes To and From without me using uac_replace functions. Is this caused by the auto restore? Does it work for both sides and is this is the intended behaviour? Cheers

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