sr-users

sr-users@lists.kamailio.org

42 participants
37518 discussions

Failed AKAv1-MD5 authentication with Boghe
by Bao, Yin 18 Oct '19

18 Oct '19

I have a Boghe (v2.0.153.836) working fine with Kamailio with MD5 algorithm however fails to authenticate if I configure S-CSCF to use AKAv1-MD5. We have the same configuration on private user identity in FHoSS on both the succ MD5 run and failed AKAv1-MD5 run. I wonder if anyone has faced this issue before. Here are some details on message exchanges: * S-CSCF included the challenge in 401 Unauthorized – Challenging the UE: WWW-Authenticate: Digest realm="example.example.org", nonce="rzGnTBGPw3hE+mDPHrZ1PAAAAAAApAAAmfftHqYUuUA=", algorithm=AKAv1-MD5, ck="629d6d9a6a6befa509b1a9bb17a9c2a3", ik="32fcd14a102279de2e38200a2257efcb", qop="auth,auth-int"\r\n * The same header was seen when 401 Unauth travelled through I-CSCF and P-CSCF (shouldn’t P-CSCF strips out the ck and ik fields before sending to UE?) * UE responded with another register with response: Authorization: Digest username="bob(a)example.example.org",realm="example.example.org",nonce="rzGnTBGPw3hE+mDPHrZ1PAAAAAAApAAAmfftHqYUuUA=",uri="sip:example.example.org",response="6445f9df2b785eab3fa461849880b48d",algorithm=AKAv1-MD5,cnonce="34baf441e99a23e0fcb2bc001355c4bf",qop=auth-int,nc=00000001\r\n * S-CSCF failed the calculation and sent back 403 Authentication Failed I tried AKAv2-MD5 setting as default algorithm on S-CSCF and the result is the same as above. It seems that only MD5 works on my setup. What are the different configs in HSS (or other places) AKAv1-MD5 need? I checked the AMF/OP on both HSS and Boghe and they match. Boghe does not have SQN setting but I set HSS to start with 0. Any pointers are appreciated! Yin

2 1

IMC through HTTP
by Péter Barabás 18 Oct '19

18 Oct '19

Hi, I want to implement conference messaging functionality into a client. IMC module seems perfect. In our scenario, the rooms and members are managed in a different server bacause of other user management functionalities and the kamailio only uses the rooms to broadcast messages to members. Is it possible anyway to create rooms and join members from a separate server like through http protocol with XHTTP module? The idea is: 1. Create a room on server A with adding members. Server A store the room data. 2. Server A sends http message to kamailio with proper format, like POST .../createRoom with jsonBody { name: „room1” } 3. Kamailio receives the http request and process it with creating a room ’room1’. 4. Server A sends members of room like POST .../addMembers with json body { room: „room1”, members: [ username: „user1”, username: „user2” ] } 5. Kamailio receives the https request and process it with joining memers into room All commands should have the belonging http request. Is it possible? Regards, Peter

2 2

MySQL vs MariaDB support
by Sergey Safarov 18 Oct '19

18 Oct '19

At present time we create RPM packages using MySQL libs. May be need switch to MariaDB libs. What you think about it?

2 1

Need to suppress "200 cancelling" in kamailio
by amit Kumar 18 Oct '19

18 Oct '19

Hi All, As per our requirement, when A party send a cancel to B party we do not want "200 cancelling" message from Kamailio.We try to find any high-level flag to disable it. but could not able to find. Can you please help us on how to achieve this. A Party Kamailio B Party ---------------->INVITE------------------------> <---------180 Ringing<------------------------ ------------>CANCEL--------------------------> <---------200 canceling [we want to suppress this message and do not want kamialio to inform A party about progress status of cancel] <------------OK----------------------------------- Thanks, Amit

2 1

Need to suppress "200 cancelling" in kamailio
by amit Kumar 18 Oct '19

18 Oct '19

Hi All, As per our requirement, when A party send a cancel to B party we do not want "200 cancelling" message from Kamailio. We try to find any high-level flag to disable it. but could not able to find it. Can you please help us on how to achieve this. A Party Kamailio B Party ---------------->INVITE------------------------> <---------180 Ringing<------------------------ ------------>CANCEL--------------------------> <---------200 canceling [we want to suppress this message and do not want kamialio to inform A party about progress status of cancel] <------------OK----------------------------------- Thanks, Amit

1 0

Kamailio v5.3.0 Released - new major version is out
by Daniel-Constantin Mierla 17 Oct '19

17 Oct '19

Kamailio v5.3.0 is out – it comes with 6 new modules and a considerable set of improvements touching more than 100 existing modules. You can read detailed release notes at: * https://www.kamailio.org/w/kamailio-v5-3-0-release-notes/ Many thanks to all developers and community members that made possible this release. v5.3.0 brings more flexibility and optimizations for KEMI interpreters, enhancements to load balancer, dialog tracking, uac remote registration and tls with libssl 1.1.x implementations, new variables, transformations and plenty of other new features. Enjoy Kamailio v5.3.0! Thank you for flying Kamailio! Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 1

Releasing Kamailio v5.3.0
by Daniel-Constantin Mierla 17 Oct '19

17 Oct '19

Hello, if there are no known major issues that need longer time to take care of them, in my opinion we could consider releasing the next major version 5.3.0 next week, for me Thursday, October 10 seems to work the best, still allowing a bit more than one week for testing. Any other suggestions? Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat

3 4

catching tls errors
by Juha Heinanen 17 Oct '19

17 Oct '19

Sometimes I see in syslog errors like this: Oct 15 16:44:57 salmon /usr/bin/sip-proxy[2064]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417C086:SSL routines:tls_process_client_certificate:certificate verify failed Is it possible somehow to catch the error in config file, for example, to figure out from which IP address the connection attempt came from? -- Juha

3 6

Kamailio weighted dispatch problems
by Jasen Hall 17 Oct '19

17 Oct '19

I am trying to change our request dispatching from round-robin to a weight-based method (ds_select_dst() algorithm 9 vs. algorithm 4) and am having a hard time getting an asymmetrical dispatch pattern enabled. In testing, I'm dispatching to two Ringswitch servers and trying to send three times the traffic to one instance. My destinations list file previously set both endpoints in the same group and simply provided the SIP URI for each. My new list file adds the attribute `weight` to each endpoint and looks like this: >1 sip:10.0.0.1:5060 weight=3 >1 sip:10.0.0.2:5060 weight=1 However, when I throw a couple thousand calls at Kamailio, I always end up with an almost perfect split of calls to both ringswitches. Regardless of the weights I choose, I never see variation in the dispatched load. Does anyone have experience with this issue and have some guidance? Thanks in advance. -- Jasen Hall | Invoca *Site Reliability Engineer* www.invoca.com [image: See the list] <https://invoca.sigstr.net/uc/5cba111d3527a200469b9afd>

3 4

IMS Kamailio Diameter Charging Server
by Jack R 14 Oct '19

14 Oct '19

Hi All, We have installed Kamailio as IMS setup pcscf icscf scscf - 3 instances running on Ubuntu.. Referring to the link below, it mentioned about Diameter based Kamailio Charging Server. https://www.kamailio.org/events/2016-KamailioWorld/Day2/15-Carsten.Bock-Dia… Where to find it? How to install it? to make it work in Kamailio IMS set up as per below articles: https://www.kamailio.org/docs/modules/stable/modules/ims_charging.html https://kamailio.org/docs/modules/devel/modules/ims_ocs.html Regards, Jack.

2 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