sr-users

sr-users@lists.kamailio.org

28 participants
37382 discussions

Re: sr-users Digest, Vol 213, Issue 52
by Mohamed SADIK 08 Mar '23

08 Mar '23

Hello, Thank you for your reply! I've used your suggestion to accomplish some amazing things. However, I'm having an issue when calling the *"sl.stats"* or any other procedures. I've noticed that the number of "200" responses gets incremented by 2, which is not the case when using the `*kamcmd*` tool. I suspect that this may be due to jsonrpc using *http/https*, which is causing Kamailio to treat it as a "200" response code. Could you advise on how to avoid this issue? Is there any further configuration that needs to be done? Best regards. On Sat, Feb 25, 2023 at 12:00 PM <sr-users-request(a)lists.kamailio.org> wrote: > Send sr-users mailing list submissions to > sr-users(a)lists.kamailio.org > > To subscribe or unsubscribe via email, send a message with subject or > body 'help' to > sr-users-request(a)lists.kamailio.org > > You can reach the person managing the list at > sr-users-owner(a)lists.kamailio.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sr-users digest..."Today's Topics: > > 1. Kamailio RPC configuration (sadik.oualla.mohamed(a)gmail.com) > 2. Re: Kamailio RPC configuration (Alex Balashov) > > > > ---------- Forwarded message ---------- > From: sadik.oualla.mohamed(a)gmail.com > To: sr-users(a)lists.kamailio.org > Cc: > Bcc: > Date: Fri, 24 Feb 2023 17:07:33 -0000 > Subject: [SR-Users] Kamailio RPC configuration > Dear Kamailio community, > > I am a newbie in Kamailio and I am currently working on a project that > involves communicating with Kamailio using Python. I have been exploring > the Kamailio documentation and I have come across RPC, JSONRPCS..., which I > believe can help me achieve my goal. > > However, I am not sure about the steps to follow in the Kamailio > configuration file to create my own script to communicate with Kamailio > using Python (the script is on an other machine on the same LAN). I would > be grateful if someone could guide me through the process. > > I have already set up Kamailio (builed it from the source code 5.5.5) and > Python on my machines and I have basic knowledge of Kamailio configuration. > I just need some guidance on how to set up the RPC module in Kamailio and > how to create a Python script to communicate with it. I found that I can > use RPyC library of python. > > I would appreciate any help or suggestions from the Kamailio community. > Thank you in advance for your time and assistance. > > Best regards, > Wild Coder. > > > > ---------- Forwarded message ---------- > From: Alex Balashov <abalashov(a)evaristesys.com> > To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> > Cc: > Bcc: > Date: Fri, 24 Feb 2023 13:22:16 -0500 > Subject: [SR-Users] Re: Kamailio RPC configuration > Hi, > > The easiest way to communicate with the JSONRPCS module is probably to use > HTTP, in the form of the `xhttp` module: > > https://kamailio.org/docs/modules/5.6.x/modules/xhttp.html > > You will need... > > 1) To enable the HTTP transport in the `jsonrpcs` module; > > 2) A TCP or TLS listener (listen= config directive) to accept the traffic; > > 3) An xhttp `event_route[xhttp:request]` route, as detailed in that > module's docs: > > > https://kamailio.org/docs/modules/5.6.x/modules/xhttp.html#xhttp.f.xhttp_re… > > 4) Probably some measure of security / authentication for #3. > > The example from jsonrpc_dispatch() is perfectly sufficient to get you > started: > > > https://kamailio.org/docs/modules/5.6.x/modules/jsonrpcs.html#jsonrpcs.f.js… > > You should then be able to do things like: > > # curl \ > -X POST \ > -d '{"jsonrpc": "2.0", "id": "abc123", "method": "ul.dump"}' \ > http://${KAMAILIO_IP}:5060/RPC <http://${kamailio_ip}:5060/RPC> > > -- Alex > > > On Feb 24, 2023, at 12:07 PM, sadik.oualla.mohamed(a)gmail.com wrote: > > > > Dear Kamailio community, > > > > I am a newbie in Kamailio and I am currently working on a project that > involves communicating with Kamailio using Python. I have been exploring > the Kamailio documentation and I have come across RPC, JSONRPCS..., which I > believe can help me achieve my goal. > > > > However, I am not sure about the steps to follow in the Kamailio > configuration file to create my own script to communicate with Kamailio > using Python (the script is on an other machine on the same LAN). I would > be grateful if someone could guide me through the process. > > > > I have already set up Kamailio (builed it from the source code 5.5.5) > and Python on my machines and I have basic knowledge of Kamailio > configuration. I just need some guidance on how to set up the RPC module in > Kamailio and how to create a Python script to communicate with it. I found > that I can use RPyC library of python. > > > > I would appreciate any help or suggestions from the Kamailio community. > Thank you in advance for your time and assistance. > > > > Best regards, > > Wild Coder. > > __________________________________________________________ > > Kamailio - Users Mailing List - Non Commercial Discussions > > To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org > > Important: keep the mailing list in the recipients, do not reply only to > the sender! > > Edit mailing list options or unsubscribe: > > -- > Alex Balashov > Principal Consultant > Evariste Systems LLC > Web: https://evaristesys.com > Tel: +1-706-510-6800 e > > _______________________________________________ > sr-users mailing list -- sr-users(a)lists.kamailio.org > To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org >

1 0

Using jsonrpc_dispatch in xhttp:request - is it possible to restrict the RPC that can be invoked ?
by Chaigneau, Nicolas 07 Mar '23

07 Mar '23

Hello, I'm using jsonrpc_dispatch in a "xhttp:request" section (with xhttp and jsonrpcs modules), e.g.: event_route[xhttp:request] { if ($hu =~ "^/RPC") { jsonrpc_dispatch(); exit; } xhttp_reply("404", "Not Found", "", ""); exit; } This works, but I would like to restrict the RPC functions that can be invoked this way. Any advice on how I could do that ? The xhttp module provides "url_skip" and "url_match" but this is not useful because in the URL I only have something like "RPC". And the method is in the JSON body. I could parse the JSON body before calling jsonrpc_dispatch, but it's a bit complicated (I don't know if it's feasible in Kamailio script ?), and seems redundant because jsonrpc_dispatch already does that... Maybe somehow this could be checked from the "void *" second argument passed to the RPC function ? Thanks. Regards, Nicolas. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

2 4

Info: Kamailio World 2023 - Announcing First Group Of Speakers
by Daniel-Constantin Mierla 06 Mar '23

06 Mar '23

Hello, it's now like 3 months till the start of the next Kamailio World Conference (taking place in Berlin, Germany, during June 5-8, 2023) and the first group of speakers has just been published, the details are available at: - https://www.kamailioworld.com/k2023/speakers/ Not all proposals were reviewed and Call for Speakers is still open, therefore if you want to share your interesting experiences or knowledge in the RTC space, submit it via: - https://www.kamailioworld.com/k2023/call-for-speakers/ All together, expect another edition of Kamailio World conference with great content covering topics such as RTC scalability, security, cloud-based deployments and elasticity, NG112/911, IoT, WebRTC, VoLTE and 4G/5G. Looking forward to meeting many of you in Berlin! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com Kamailio Advanced Training - Online - March 27-30, 2023 - www.asipto.com

1 0

Remove silo extra_hdrs before store
by Dr. Barabás Péter 06 Mar '23

06 Mar '23

Hi, I’m using kamailio’s silo module to store offline messages in it. I set extra_hdrs modparam to e.g. : ‘Resent-from-silo’ so the clients get information that the message has arrived directly (immediatelly) from the sender or it was stored offline and comes from silo. So the problem is the following: * if receiver’s socket is broken (e.g. airplane mode on mobile) and kamailio ‘thinks’ it is registered, server tries to send the message * message will be timed out and based on config it will be stored in silo. * the next step is to check if receiver is registered or not (since the client can re-register during 30sec until the message has timed out) * If client is registered, kamailio tries to send the message immediately with m_dump(). * If the receiver’s connection is still broken, the message will be timed out and store in silo. * In every store, a new ‘resent’ extra_hdrs value is appended. When extra_hdrs length reaches 1024 bytes, the m_dump will fail and it blocks the dumping of messages to the given receiver. Question: can extra_hdrs value be removed before store? Or what can be the solution not to duplicate the extra_hdrs value in some bad network situation? Peter

1 0

How to access rtpengine rtcp-metrics?
by Benoit Panizzon 06 Mar '23

06 Mar '23

Hi all I'm trying to incorporate rtcp data from rtpengine into our CDRS. So trying with the first interesting value, the average mos. modparam("rtpengine", "mos_average_pv", "$avp(mos_average)") If I understood right, to get this variable set, I need to call rtpengine_manage() on the message that terminates the call. So on an established call, that is either BYE or the 200 OK to the BYE. Right? if ($rm == "BYE") { rtpengine_manage(); xlog("L_INFO", "$cfg(route): $rm: MOSS: $avp(mos_average)\n"); } onreply_route[MANAGE_REPLY] { [...] rtpengine_manage(); xlog("L_INFO", "$cfg(route): $rm reply MOS: $avp(mos_average)\n"); } Messages pass those blocks, $avp(mos_average) is 'null' no mater what. What am I missing? In the syslog output of rtpengine I see there is rtcp data. Mit freundlichen Grüssen -Benoît Panizzon- -- 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 2

tcp_set_connection_lifetime => in respect to 'idle' connection?
by Benoit Panizzon 06 Mar '23

06 Mar '23

Hi List Digging further into my tcp/tls issues... Upon successful authentication I call: tcp_keepalive_enable("60", "5", "5"); tcp_set_connection_lifetime("120"); I tought, this would do to keep the connection alive. I noticed, despite keepalive packets being exchanged, kamailio is closing the connection after a bit more than 2 minutes. I am right at assuming, that tcp_set_connection_lifetime is not related to how long the connection is idle, but is counted from the SYN, no matter if keepalives were successfully exchanged? Does calling tcp_set_connection_lifetime() again restart the lifetime like for 2 more minutes like in this example? Or would I have to keep increase the value of the lifetime on each successful re-register to keep it open? Mit freundlichen Grüssen -Benoît Panizzon- -- 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 ______________________________________________________

1 0

Kamailio v5.6.3 Released
by Daniel-Constantin Mierla 05 Mar '23

05 Mar '23

Hello, Kamailio SIP Server v5.6.3 stable release is out. This is a maintenance release of the latest stable branch, 5.6, that includes fixes since the release of v5.6.2. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.6.x. Deployments running previous v5.6.x versions are strongly recommended to be upgraded to v5.6.3. For more details about version 5.6.3 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2023/01/kamailio-v5-6-3-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 - June 5-7, 2023 - www.kamailioworld.com

5 10

Kamailio v5.5.6 Released
by Daniel-Constantin Mierla 02 Mar '23

02 Mar '23

Hello, Kamailio SIP Server v5.5.6 stable release is out. This is a maintenance release of the stable branch 5.5 that includes fixes since the release of v5.5.5. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.5.x. Deployments running previous v5.5.x versions are strongly recommended to be upgraded to v5.5.6. Note that 5.5 is the second last stable branch, still officially maintained by Kamailio development team. The latest stable branch is 5.6, with v5.6.4 being release out of it. For more details about version 5.5.6 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2023/03/kamailio-v5-5-6-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 - June 5-7, 2023 - www.kamailioworld.com Kamailio Advanced Training - Online - March 27-30, 2023 - www.asipto.com

1 0

Releasing Kamailio v5.5.6
by Daniel-Constantin Mierla 02 Mar '23

02 Mar '23

Hello, I am considering to release Kamailio v5.5.6 soon, branch on branch 5.5, likely on Thursday or Wednesday next week (Mar 2/3, 2023). This is the usual heads up notification to see if anyone is aware of issues not yet reported to bug tracker and if yes, do it as soon as possible to give them a chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com Kamailio Advanced Training - Online - March 27-30, 2023 - www.asipto.com

1 1

Websocket closing
by David Villasmil 01 Mar '23

01 Mar '23

Hello guys, We're seeing corner cases where the following happens: On proxy-ws - IP1:PORT1 connects via websocket from Client1 - Registration happens on an upstream kamailio - for any reason, the TCP socket closes or times out. - IP1:PORT1 (same IP:PORT combination) connects via websocket from Client2 - Registration happens on an upstream kamailio Now a call comes in to Client1. Because the first connection was never cleaned up, it is sent to the proxy-ws and the proxy will send it to the IP1:PORT1 where Client2 is connected. Short story, proxy-ws doesn't check the IP1:PORT1 where it is sending the INVITE is the actual client it is supposed to be sending... It seems that when a socket is closed, the mapping IP:PORT to Address (i.e.: sip:d4f27e34@994f31243be9.invalid;transport=ws) doesn't seem to be cleared... is this by design? Thanks! Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 6

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