sr-users August 2019

sr-users@lists.kamailio.org

65 participants
100 discussions

Re: [SR-Users] Wildcarded IMPU
by Henning Westerholt 17 Aug '19

17 Aug '19

Hello Maryam, (please keep the list in CC) understand. There is work ongoing to update the IMS modules (e.g. refer to https://www.kamailio.org/wiki/features/new-in-devel). I don't know about a current effort to add wildcarded AVPs to them, though. If you like to implement something in this regards, it is always good to announce it quickly on the developer list sr-dev to get some feedback and to to synchronize with other developers. Cheers, Henning Am 17.08.19 um 08:04 schrieb Maryam Baghdadi: Hello Henning, Thank you for your response . I read all ETSI‌ standards , latest version of standards are according to Release15 IMS but IMS modules in kamailio support Release 7 IMS. for example there is Wildcarded_IMPU AVP in AUR in R15 IMS which isn't implemented in IMS_icscf module in kamailio . I know all AVP lists are exist in kamailio and I can add my requirements to modules code . I just wanted to know ims modules in kamailio will be updated or not? On Wed, Aug 14, 2019 at 11:55 PM Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> wrote: Hello Maryam, Kamailio supports AVPs and also an extended version called XAVP. About your question - I quickly looked into ETSI TS 129 329 and TS 129 229 but they did not define how this actually works.. Can you elaborate what you actually are looking for? Cheers, Henning Am 05.08.19 um 12:41 schrieb Maryam Baghdadi: hello, I need to know wildcarde_IMPU feature support in kamailio or not? I use kamailio as scscf and need to have support of wildcarded_impu in my scscf. is there any implementation of AVP_Wildcarded_IMPU in kamailio ? thanks _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services

1 0

uac_replace_from() and multiple branches
by John Quick 16 Aug '19

16 Aug '19

v5.2.3 of Kamailio. Serial forking is used to route calls to a multiple destinations as described in documentation for the TM module. Also using the DIALOG module - my script calls dlg_manage() before loading the serialised branches. I need to be able to substitute the username part of the From header and have been trying this with calls to uac_replace_from(). modparam("uac", "restore_mode", "auto") modparam("uac", "restore_dlg", 1) There is no problem if all branches use one substituted From username, in which case my script calls uac_replace_from() in the main route. uac_replace_from("sip:" + $avp(route:src) + "@" + $fd); However, I may need to substitute a different value for each branch. Can this be done? I tried moving the call to uac_replace_from() into the branch route, but then I get an error when the final BYE is received: ERROR: uac [replace.c:281]: replace_uri(): decline FROM replacing in sequential request in auto mode (has TO tag) Is there a simple solution to this please? Hoping I can still use UAC auto restore mode because manual restore looks quite tedious/complex. Thanks. John Quick Smartvox Limited www.smartvox.co.uk

3 3

pike parameters doup when have dinamyc ip clients and scanners
by PICCORO McKAY Lenz 15 Aug '19

15 Aug '19

I read documentation for pike usage.. and have a doub.. what it's the best for very dinamyc ip of my devices.. i mean, i'm just curious of that very ironic and problematic scenario: for the scanners i setup fail2ban but only when the scaning are detecte.. but if i have the pike option how this: # this it's my setup for pike due the dinamyc ip and devices over the internet: modparam("pike", "sampling_time_unit", 4) modparam("pike", "reqs_density_per_unit", 80) modparam("pike", "remove_latency", 60) ... route { if (!pike_check_req()) { xlog("L_ALERT","ALERT: pike block $rm from $fu (IP:$si:$sp)\n"); exit; } ... } I put the remove latency in 60, so then due are dinamycally must remian in memory more (due any one will be a possible clilent), just ban if there are 180 (60*3) request each 4 seconds, it's a good configuration or maybe i'm wrong please help me! -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com

3 6

RFC 3860 support - Kamailio is sending SUBSCRIBE back with extra Via header
by Praveen Vatti 15 Aug '19

15 Aug '19

Hi Kamailio support, Basically, I am looking for RFC3860 support - i.e., accept SUBSCRIBE for reg event and send 200OK, NOTIFY to client. With some browsing on Internet I came across Kamailio, which is supporting RFC3860. I have installed and attached is my CFG file. I am sending a SUBSCRIBE request with reg event to Kamailio and it is sending back the same request with extra Via header. Via now contains Kamailio system IP and the source of SUBSCRIBE IP. Please help me in resolving this issue. I have loaded db_mysql, dialplan, tm, sl, presence, presence_reginfo modules. Thanks, Praveen

2 6

Wildcarded IMPU
by Maryam Baghdadi 14 Aug '19

14 Aug '19

hello, I need to know wildcarde_IMPU feature support in kamailio or not? I use kamailio as scscf and need to have support of wildcarded_impu in my scscf. is there any implementation of AVP_Wildcarded_IMPU in kamailio ? thanks

2 1

Uac_replace for header's parameters
by Duarte Rocha 14 Aug '19

14 Aug '19

Greetings, I'm using uac_replace_to() and uac_replace_from() to do some number manipulations. It allows me to modify and automatically restore Display Number and URI. This works nicely, however it only allows to manipulate URI's parameter. Is there any method to the same and include the Header's parameters too? Best regards, Duarte Rocha

2 1

Question regarding Dispatcher + ds_default_socket() modparam + Call-ID generation
by Joel Serrano 14 Aug '19

14 Aug '19

Hello, Simple doubt regarding dispatcher module when you have the ds_default_socket() modparam set: Say you have 2 kamailio boxes, active + passive, one shared IP via keepalived.... On the actrive node, you have dispatcher.send_ping to 1, and the passive has it set to 0. So far OK, only the active box is sending out probing OPTIONS requests, and it's using as outbound socket the virtual IP out of all the available ones (as defined with ds_default_socket() modparam) I have seen in a capture that the outbound OPTIONS look like: OPTIONS sip:190.14.203.219:5060 SIP/2.0 Via: SIP/2.0/UDP A.B.C.180 ;branch=z9hG4bK7abb.6fbaccc1000000000000000000000000.0 To: <sip:190.14.203.219:5060> From: <sip:dspinger@my.domain>;tag=e2bdd495733c59fd91487a137fccad4e-8a73 CSeq: 10 OPTIONS Call-ID: 2019f8491329c382-31419(a)A.B.C.181 Max-Forwards: 70 Content-Length: 0 A.B.C.180 -> VRRP A.B.C.181 -> Physical IP of the box My doubt is, shouldn't ds_default_socket also update the IP used to generate the Call-ID used in the OPTIONS request? Currently, I believe it's using the first defined listen= IP from config script as I switched the order the listen= are defined and I get the desired result: OPTIONS sip:186.188.220.174:5060 SIP/2.0 Via: SIP/2.0/UDP A.B.C.180 ;branch=z9hG4bKc97e.a8d9e1c2000000000000000000000000.0 To: <sip:186.188.220.174:5060> From: <sip:dspinger@my.domain>;tag=5e2e1773f812f6a7e4085c5d036e29d8-d323 CSeq: 10 OPTIONS Call-ID: 7d9a92c218fc1ba0-32111(a)A.B.C.180 Max-Forwards: 70 Content-Length: 0 Is this expected? Cheers, Joel.

3 4

Kamailio/Freeswitch auth user and UserID
by Petarr Jones 14 Aug '19

14 Aug '19

Hi I am new to Kamailio and would like some guidance on linking up with Freeswitch. I have an exiting hosted Asterisk PBX that uses a combination of extension and pbx username (eg 1001-126252581276) and I want to move it over to Kamailio/Freeswitch without re-configuring the SIP phones. I have tried Freeswitch "number-alias" but it does not seem like a good fit due to things like BLF not working and the added overhead etc. Is there a way to configure Kamailio to authenticate a user based on the above username and then send an extension to Freeswitch as the UserID instead, thereby separating the Kamailio authentication from the Freeswitch UserID? As I don't yet have a full understanding of the Kamailio/Freeswitch interaction, I don't know whether this will cause other issues? Thanks in advance Petarr

2 8

Re: [SR-Users] Dispatcher round-robin problems in 5.2
by JR Richardson 14 Aug '19

14 Aug '19

Hey Alex, After I recently upgraded, I had to include more response codes, 5.2 by default only 200 OK is accepted. I had some upstream carriers sending 405 and were taken off-line as a result until I added that code in modparm: modparam("dispatcher", "ds_ping_reply_codes", "class=2;code=405") Not sure if this applies to what you are doing, but my dispatcher round robin distribution acts as it did prior to upgrade to 5.2, pretty even, no anomalies with any nodes getting more calls than any other. JR JR Richardson Engineering for the Masses Chasing the Azeotrope Hi, I've got a proxy that does very basic round-robin distribution of calls to an elastic pool of servers, defined in a simple SQLite database with equal priorities. Nothing too complicated, just a vanilla `ds_select_domain("1", "4")`. The only complication is that seldom are most of the gateways enabled. Probing stuff was turned on, but didn't do quite what was desired, so it was replaced with a system that manages activation and deactivation of the gateways externally. Nevertheless, these are the left-over probing settings: modparam("dispatcher", "ds_ping_method", "OPTIONS") modparam("dispatcher", "ds_ping_from", "sip:pinger@domain") modparam("dispatcher", "ds_ping_interval", 15) modparam("dispatcher", "ds_probing_threshold", 256) modparam("dispatcher", "ds_inactive_threshold", 1) modparam("dispatcher", "ds_probing_mode", 0) After an upgrade from 5.1 to 5.2.3 (009f62), the round-robin has become extremely "sticky" and tendentious. That is to say, it directs _almost_ all calls to a single gateway -- the first gateway in the table -- though not 100%. There is also a marked tendency to send lots of consecutive calls to the same gateway, even if it's not the first one, though most of the time it is. Has anyone experienced similar upon upgrading to 5.2? Thanks much! -- Alex

2 2

Wrong Record-Route and Via header fields when TCP is used
by Leonid Fainshtein 14 Aug '19

14 Aug '19

Hi, Kamailio server has two legs that are connected to different networks. I'm using Kamailio v.5.2.3 and the "enable_double_rr" is implicitly set to "1". The leg "A" IP address is 10.159.65.1 The leg "B" IP address is 192.168.0.31 The call is initiated from 10.159.65.18 According to the "rr" module documentation, function record_route() should insert two "Record_Route" header fields when a request is accepted on one leg is should go out via the second leg. This works as expected in case of UDP protocol: INVITE sip:2000@192.168.6.106:5460;transport=UDP SIP/2.0 Record-Route: <sip:192.168.0.31;r2=on;lr;did=e2c.a191> Record-Route: <sip:10.159.65.1;r2=on;lr;did=e2c.a191> Via: SIP/2.0/UDP 192.168.0.31;branch=z9hG4bKcfa5.d64ecbd87d5315b5993c4ccf16f86537.0 Via: SIP/2.0/UDP 10.159.65.18:5060;rport=5060;branch=z9hG4bK3a9e9a4d But when the TCP protocol is used then the outbound message looks like this: INVITE sip:2005@192.168.0.178:35058;transport=tcp SIP/2.0 Record-Route: <sip:10.159.65.1;transport=tcp;lr;did=bb6.7dc1> Via: SIP/2.0/TCP 10.159.65.1;branch=z9hG4bKc85a.14afc3867dd3220826f9b9940f78168f.0;i=3 Via: SIP/2.0/TCP 10.159.65.18:5060;rport=58616;branch=z9hG4bK1469331f There are two problems there: a) only one Record-Route with leg is inserted b) the added "Via" header field contains the leg "A" IP address instead of expected leg "B" IP address (192.168.0.31). In the LAN trace I see that in reality the message was sent from leg "B". Is it a bug? Best regards, Leonid Fainshtein

2 13

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2026

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 August 2019