sr-users August 2021

sr-users@lists.kamailio.org

49 participants
51 discussions

Start a nNew thread

no transaction found so that cant step into route-block

by fran.interpla.56906

2 years, 8 months

no transaction found so that cant step into route-block

by fran.interpla.56906

2 years, 8 months

Kamailio v5.5.2 Released

by Daniel-Constantin Mierla

Hello, Kamailio SIP Server v5.5.2 stable release is out. This is a maintenance release of the latest stable branch, 5.5, that includes fixes since the release of v5.5.1. 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.2. For more details about version 5.5.2 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2021/08/kamailio-v5-5-2-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

2 years, 8 months

MS Teams outbound calls. Called number normalization

by Володимир Іванець

Hello all! I'm testing integration with MS Teams. I treat calls from Teams to the phone system the same way as calls from phones. And would like to ask if someone has already dealt with this. My test account location is set to the United States. When I make a call to "200", an INVITE request from Teams to Kamailio will have "+1200" in the To URI user. I could just strip "+1" but when I make a call to "100", Teams sends "+100". So in this case I need to strip only one character. The problem is that I don't know when I need to remove one or two characters. And it gets more complicated when I change my test account location. For some countries, Teams prepend 3 characters. What do to make sure phone numbers are consistent? I thought this behavior could be disabled in Teams but could not find anything related yet. Thank you! Regards, Volodymyr Ivanets

2 years, 8 months

Releasing Kamailio v5.5.2

by Daniel-Constantin Mierla

Hello, I am considering to release Kamailio v5.5.2 sometime next week, likely on Wednesday (August 25, 2021). 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

2 years, 8 months

[VoLTE] 401 unauthorized error

by 오택경

Hi. I am implementing the VoLTE setup with the dockerized project (https://github.com/herlesupreeth/docker_open5gs https://github.com/herlesupreeth/docker_open5gs). I have almost done to run the VoLTE service, but 401 unauthorized error in sip and auth-pending error in fhoss have occured. How can I fix this problem? I will share the discussion note in which I tried to solve some problems including the above one. : https://github.com/herlesupreeth/docker_open5gs/issues/55 https://github.com/herlesupreeth/docker_open5gs/issues/55 Very thanks, Taekkyung Oh.

2 years, 8 months

Race conditions upon quick reinvite

by David VILLAUME

Hello, We encounter sometimes reinvite from some provider really quickly after 200 OK ACK so sometime there a race conditions where the re-invite exits Kamailio before the ACK leading to some Freeswitch “500 Overlapping Requests”. [cid:image001.png@01D798FA.6F5B9D80] I tried to catch the 500 on failure-route unsuccessfully as transaction is already established. Do you have any idea on how I could deal with this behavour ? Running 5.3.6 with 8 childs modules used :(tm + dialog) No costly action performed on ack that can explain slowliness. Regards, David

2 years, 8 months

kazoo error

by 崔群

Dear sir: I have some problems。the kamailio version is 5.3.0. My linux version is centos 7. the kamailio log: ERROR: kazoo [kz_amqp.c:2238]: kz_amqp_send_ex(): Failed to publish -9 : a socket error occurred ERROR: kazoo [kz_amqp.c:2707]: kz_amqp_publisher_send(): error sending publish to zone : local , connection id : 1, uri : amqp://admin The connection between kamailio and rabbitmq was interrupted, which caused the queue of MQ to be blocked and the message could not be consumed。

2 years, 8 months

Some questions about drouting module

by Андрей Яри н

Hello! I test module on Centos 7, kamailio version 5.5 and found some strange things: 1) Definition of table dr_gateways at https://kamailio.org/docs/modules/5.5.x/modules/drouting.html#idm98 - in DB there is field 'attrs' and only notice about it is module param 3.8. attrs_avp but it doesnt describe table field. In OpenSIPS docs i found description * attributes (not used by DR engine, but only pushed to script level when routing to this GW) In kamailio this field is deprecated or its only docs misses param? 2) Previous moment was found when i try to resolve: WARNING: drouting [dr_load.c:529]: dr_load_routing_info(): route <1> does not exist "Definition of dr_rules table" says that field has type of integer, but realy in database its varchar and i think its old docs. But i use KEMI question is - how i can tell module that it must be called in KEMI, not in native? 3) Every time when i call 'kamcmd drouting.reload' i get message CRITICAL: <core> [core/mem/q_malloc.c:502]: qm_free(): BUG: bad pointer 0x7f3e4cea04c0 (out of memory block!) called from core: core/utils/tmrec.c: tmrec_free(393) - ignoring I rollback to 5.4 and still get this error. As i understand its old module and its can be internal error - how critical this error can be? 4) Also planned commands like drouting.dump gws|gw_lists|rules? -- С уважением, Ярин Андрей Анатольевич инженер, группы управления телефонией Группа компаний «Интерсвязь» e-mail: yarin-aa(a)intersvyaz.net

2 years, 8 months

Kamailio as basic dispatcher for load balancing

by Philipp Trenz

Hey there, I’m Philipp, an IT Systems Engineer from Potsdam, Germany and want to deepen my knowledge in SIP communication on scale. Currently, my setup is quite simple: A single stateless Asterisk instance, fully managed via ARI, which registers to multiple VoIP providers, only processes incoming calls to play audio files (no outgoing or conference calls). Now, with growing load on the single Asterisk instance, I would like to have one or two Kamailio instances, which will balance the load of incoming calls to multiple Asterisk instances. On which Asterisk instance they end up is irrelevant for me, as the calls can be processed on every instance. I looked into some Kamailio and Astricon conference speeches and checked out some tutorials. But still I’m not quite sure where to start. So here are some basic questions which would really help me out to get going: As I don’t want to have registrations of all my Asterisk instances at the VoIP providers, I should use the UAC module to let Kamailio do the registering to the VoIP providers and register my Asterisk instances to Kamailio, right? Will Kamailio automatically apply new outbound registrations when added to the database or do I have to trigger that manually? Should I use one or two instances of Kamailio, how hard is it to configure them fail-safe? For writing my first config file, should I start blank or from the standard config, what’s best practice? Thanks in advance, looking forward to your replies! Philipp

2 years, 8 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 August 2021