sr-users

sr-users@lists.kamailio.org

37 participants
37511 discussions

Start a nNew thread

KAZOO module on quorum queues
by David VILLAUME 13 Jun '22

13 Jun '22

Hello, Did any of you had any success with Kazoo module with RabbitMq quorum queues ? Regards, David

1 0

Get all contacts by domain
by Jose Fco. Irles Durá 13 Jun '22

13 Jun '22

Hi, I'm running a cloud infrastructure with multiple sip domains and I have some kamailio's as registrars with dmq for usrloc replication. The kamailio registrars are configured without db, so the aors are in ram. For some gui's I need to get all aors for one sip domain, If I execute ul.dump I get all aors, but I want only a few. In my situation it would be perfect to get all registrations for one sip domain in one request (memory, performance, cache at gui...) I thought I could save the registers with save("$rd") but ul.dump doesn't allow any parameter that restricts the "location" domain. Is there any solution for this? Best regards -- Jose Fco. Irles Durá

3 4

problem getting the rtp packet source port
by hamed r 12 Jun '22

12 Jun '22

hello i have problem on receive source port rtp packet client-ip = 5.202.105.250 server-ip = 194.5.205.33 client2-ip = 188.212.241.46 In the 200 ok packet from client2 ,The value 4002 is set in the audio port [image: invite.jpg] I expect rtp packets to be sent to me from source port 4002, but these packets are sent to me from another source , which is port 55755 in the image below, and I just opened this port(4002) in the firewall. If I turn on my firewall service, all packets will be dropped. I have to have this firewall [image: rtp.jpg] thanks for help me

1 0

Use of interface name or listening socket name as DMQ server_socket
by Ben Kaufman 10 Jun '22

10 Jun '22

Kamailio allows the use of an interface name (eth0 for example), as the identifier for the listen directive. Additionally it allows assignment of a name to be used as an identifier. This can be used, as indicated in the documentation: A unique name can be set for sockets to simplify the selection of the socket for sending out. For example, the rr and path modules can use the socket name to advertise it in header URI parameter and use it as a shortcut to select the corresponding socket for routing subsequent requests. I'm wondering if there is a way to get allow either of these parameters to be used to define DMQ's server_socket parameter. This would be useful in containerization situations where the local IP address is assigned dynamically. Here's what I'm attempting: #!KAMAILIO loadmodule "tm" loadmodule "sl" loadmodule "dmq" loadmodule "textops" listen=udp:eth0:5060 name "sip5060" listen=udp:eth0:5090 name "sip5090" modparam("dmq", "server_address", "sip:dmq_quicktest:5090") modparam("dmq", "notification_address", "sip:dmq-bus:5090") modparam("dmq", "server_socket", "sip5090" ) ## Above line doesn't work, neither does the line below: #modparam("dmq", "server_socket", "udp:eth0:5090" ) modparam("dmq", "multi_notify", 1) modparam("dmq", "num_workers", 3) modparam("dmq", "ping_interval", 30) request_route { exit; } I get the following error during startup: 0(1) ERROR: dmq [dmq.c:241]: mod_init(): server_uri is not a socket the proxy is listening on Thoughts? I realize that I can configure and pass static networking with the containers, but I'm looking for a way to have this set on the fly - especially when testing, etc. Ben Kaufman

2 1

SIP trunk challange
by Mihai 10 Jun '22

10 Jun '22

Hello ! I have this issue with the telco provider they give the sip trunk on a private conection with private ips, the problem is that i am trying to relocate the sip trunk in remote server and I've tried though basic networking/tunnels/vpn and no go; their sbc is dropping requests and rejects if they are more via headers, they force me to use that conection and the ip allocated. The challenge is how to this is in kamailio, basically i just want to transport the trunk (similiar to a reverse proxy for web) to its new destination and from there handle everything. Any hints on how to achieve this?

2 1

Kamailio vs FreeSWITCH as SBC
by Unai Rodriguez 09 Jun '22

09 Jun '22

Dear List, I’m looking at using Kamailio as SBC. This would replace our current FreeSWITCH-based SBCs. What are your thoughts on this move? Would there be any known reasons why Kamailio would be superior to FreeSWITCH as an SBC? Thank you so much Unai Rodriguez

3 3

t_drop_replies can't be used on a route?
by David Villasmil 09 Jun '22

09 Jun '22

Hello guys, I have a failure route which calls another route, and on this route I need to t_drop_replies(); But i'm getting: [core/cfg.y:3510]: yyerror_at(): parse error in config file /etc/kamailio/include/relay_routes.cfg, line 143, column 20: Command cannot be used in the block Any way to fix this without me having to use it in the failure_route? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

1 0

remove header in async processing (e.g. by http_async_client)
by Henning Westerholt 09 Jun '22

09 Jun '22

Hello, I'd like to remove headers during async processing e.g. in a route called from http_async_client(..). The usual textops functions are not working here. Adding headers could be done using something like rtjson, but it do not offer a remove header function. I could of course loop the request locally, but this is not that "nice". Any other suggestions for this case? Or just the rtjson module needs some extensions? Thank you, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/>

1 1

Siremis startup helper service for systemd
by Joseph Goettgens 09 Jun '22

09 Jun '22

Hi, I had some difficulties getting Siremis 5.3 to run under Debian 11 Bullseye. It turned out that the problem was the creation of the Siremis socket: <UnixSockLocal name="unixsocklocal" address="/run/siremis/siremis_rpc.sock" timeout="3.0"/> There is a warning in siremisJRCommands.xml that points out that systemd has to be reconfigured as sockets in /tmp are no longer shared (PrivateTmp setting). By the same token, /run/siremis/siremis_rpc.sock cannot be created as the httpd server is not allowed to write to /run, i.e. it can neither create the socket nor the siremis directory. The permanent creation of the siremis directory with suitable access rights is also not possible, since /run is mounted as tmpfs in the default configuration. At least the directory has to be created at boot time, which can be done with a small helper service. This is working for me (siremis-helper.service): [Unit] Description=Siremis Helper Service After=network.target [Service] Type=oneshot ExecStartPre=/usr/bin/mkdir /var/run/siremis ExecStart=/usr/bin/chown www-data:www-data /var/run/siremis [Install] WantedBy=multi-user.target It is enabled the usual way with systemctl "systemctl start --now siremis-helper". Siremis now works with jsonrpc commands and the procedure would mean that installing Siremis on a newer Debian system would definitely require some attention. Does anyone have any objections to the above procedure?

1 0

Re-establishment of a closed TCP connection
by Vitalii Krutsitskyi 09 Jun '22

09 Jun '22

Hello General overview of the infrastructure: Client (Cisco Hardware) ---> AWS NLB ---> Kamailio Instances The client has a time limit for the opened TCP connections - 10 minutes. This is a hardcoded value that can't not be changed. Regardless of the traffic that flows through the connection, it is closed after 10 minutes. Problem: in case of long-running calls above 10 minutes it is not possible for Kamailio to send back SIP traffic back to the client using the original TCP connection. The client has been asked to either increase the time limit or send SIP reinvites - none of that is possible due to some client's infrastructure limitations. Question: is it possible to force Kamailio to open a new TCP connection and associate it with the call? Client has a 5060 port always opened which can accept incoming connections.

3 2

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