- sr-users - kamailio.org

Docker image for 5.2.4
by Colin, Andrew 22 Aug '19

22 Aug '19

Hey All Who updates the images on https://hub.docker.com/r/kamailio/kamailio/tags i dont see the latest image kamailio:5.2.4-stretch --

1 0

{param.count,delimiter} issue
by Juha Heinanen 20 Aug '19

20 Aug '19

Looks like there is bug in {param.count,delimiter} transformation: $var(test) = "a=1;b=2"; xinfo("param count = $(var(test){param.count,;})\n"); $var(test) = "a=1,b=2"; xinfo("param count = $(var(test){param.count,,})\n"); syslog: Aug 19 11:27:27 salmon /usr/bin/sip-proxy[26513]: INFO: param count = 2 Aug 19 11:27:27 salmon /usr/bin/sip-proxy[26513]: INFO: param count = 1 -- Juha

3 10

Slowly increasing PKG memory usage
by Andrew White 20 Aug '19

20 Aug '19

Hi all, I had a Kamailio crash the other day, and some debugging showed I ran out of PKG memory. Since then I’ve run a simple bash script to compile the amount of memory used by all child processes, effective /usr/local/sbin/kamcmd pkg.stats | grep real_used summed together. I’ve graphed out the data, and there’s a clear growth of PKG memory going on, mostly increasing during our busier daytime hours. https://i.imgur.com/UTzx2k1.png Based on this, I suspect either a module loaded or something within my app_ruby conf is leaking memory. I’ve been reading through https://www.kamailio.org/wiki/tutorials/troubleshooting/memory <https://www.kamailio.org/wiki/tutorials/troubleshooting/memory>, but I’m a bit nervous, as I’m not really a C/deep memory type of guy. I can see a GDB script I can attach to Kamailio, but is that going to use significant resources to run or impact the running process? Is there a newer/better/alternative way to do this, and to help me break this down? Thanks! Andrew

3 17

Evapi dispatcher is consuming all the private memory
by José Seabra 20 Aug '19

20 Aug '19

Hello there, I'm using kamailio 5.2.1 with evapi module to send and receive events from an external application. During my stress tests to kamailio i have been noticing that at some point kamailio is getting out of memory: edge-sip-proxy[20565]ERROR: ESP_LOG: <null>: <core> [core/mem/q_malloc.c:291]: qm_find_free(): qm_find_free(0x7fb8730b6010, 64); Free fragment not found! edge-sip-proxy[20565]: ERROR: ESP_LOG: <null>: <core> [core/mem/q_malloc.c:425]: qm_malloc(): qm_malloc(0x7fb8730b6010, 64) called from core: core/parser/msg_parser.c: parse_headers(325), module: core; Free fragment not found! edge-sip-proxy[20565]: ERROR: ESP_LOG: <null>: <core> [core/parser/msg_parser.c:328]: parse_headers(): memory allocation error edge-sip-proxy[20565]: ERROR: ESP_LOG: <null>: pv [pv_core.c:704]: pv_get_callid(): cannot parse Call-Id header edge-sip-proxy[20565]: INFO: ESP_LOG: <null>: [evapi:connection-received] EVAPI msg received -> {"aor":"sip:FUZECI1-x1516@uc.fuze.domain ","contact":"<sip:FUZECI1-x1516@10.225.121.206:5060;transport=UDP>"} edge-sip-proxy[20565]: ERROR: ESP_LOG: <null>: <core> [core/mem/q_malloc.c:291]: qm_find_free(): qm_find_free(0x7fb8730b6010, 64); Free fragment not found! edge-sip-proxy[20565]: ERROR: ESP_LOG: <null>: <core> [core/mem/q_malloc.c:425]: qm_malloc(): qm_malloc(0x7fb8730b6010, 64) called from core: core/parser/msg_parser.c: parse_headers(325), module: core; Free fragment not found! The process id 20565 is running out of memory as you can see bellow: output of kamcmd pkg.stats entry: 14 pid: rank: -2 used: 6058696 free: 824 real_used: 8387784 total_size: 8388608 total_frags: 30 This process ID is related with Evapi Dispatcher kamcmd ps | grep 20565 20565 EvAPI Dispatcher After stop the sipp that was generating traffic to kamailio the evapi process still have all the memory consumed Can it be some memory leak in Evapi module? Best Regards José Seabra -- Cumprimentos José Seabra

2 12

HSS download - open source
by Jack R 20 Aug '19

20 Aug '19

Please could you advise where can I get open source HSS that works with latest Kamailio 5.2 release for OS: ubuntu18-04:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic If possible please share the steps to integrate with Kamailio. The link in this article for FHoSS repository is not working: https://www.kamailio.org/wiki/tutorials/ims/installation-howto If not Open source then maybe an evaluation software. Please advise. Thanks and Regards.

2 1

kamailio doesn't reply on internal interface
by Zhan Bazarov 19 Aug '19

19 Aug '19

Hello, we have interesting issue... Some time kamailio comes unreachable on private interface for asterisk, but port checked via telnet and everything is ok... ps. connection via public ip works good root@kamailio:/usr/local/etc/kamailio# lsof -i :5068 | grep LISTEN kamailio 6014 root 13u IPv4 8341589 0t0 TCP kamailio.local.ip:5068 (LISTEN) kamailio 6014 root 14u IPv4 8341590 0t0 TCP kamailio.public.ip:5068 (LISTEN) root@kamailio:/usr/local/etc/kamailio# telnet from asterisk machine: root@asterisk:/etc/asterisk# telnet kamailio.local.ip 5068 Trying kamailio.local.ip... Connected to kamailio.local.ip. Escape character is '^]'. But peer is unreachable in asterisk... More than, kamailio comes reachable when I change transport from TCP to UDP, or when I restart kamailio daemon(but it situation repeats every day).. Any ideas how I can fix it? thanks!

2 1

set_rtpengine_set(set1, set2) issue
by Juha Heinanen 19 Aug '19

19 Aug '19

My sip proxy has two rtpengine sets: # sip-proxy_ctl rtpengine.show all { url: udp:192.26.134.1:6050 set: 0 index: 0 weight: 1 disabled: 0 recheck_ticks: 0 } { url: udp:192.26.134.40:6050 set: 1 index: 1 weight: 1 disabled: 0 recheck_ticks: 0 } Config makes callBefore calling rtpengine_offer(), config calls set_rtpengine_set("1", "0"); rtpengine_offer("..."); As result, debug shows that sip proxy sends TWO offer commands to the rtpproxy in set 1 and NONE to the rtpproxy in set 0. Debug at set 1 engine: Aug 19 18:06:08 buster-10-0 rtpengine[1314]: NOTICE: [5e1407211cc50fd9]: Creating new call Aug 19 18:06:08 buster-10-0 rtpengine[1314]: INFO: [5e1407211cc50fd9]: Replying to 'offer' from 192.26.134.1:33284 (elapsed time 0.000812 sec) Aug 19 18:06:08 buster-10-0 rtpengine[1314]: INFO: [5e1407211cc50fd9]: Received command 'offer' from 192.26.134.1:33284 Aug 19 18:06:08 buster-10-0 rtpengine[1314]: INFO: [5e1407211cc50fd9]: Replying to 'offer' from 192.26.134.1:33284 (elapsed time 0.005247 sec) I haven't been able to figure out, why that is the case. It is a bug, or am I missing something? I added INFO call to set_rtpengine_set_f(): INFO("set1/set2 = %u/%u\n", selected_rtpp_set_1->id_set, selected_rtpp_set_2->id_set); return 1; and it correctly printed: Aug 19 18:06:08 salmon /usr/bin/sip-proxy[26911]: INFO: rtpengine [rtpengine.c:3574]: set_rtpengine_set_f(): set1/set2 = 1/0 Any ideas? -- Juha

1 0

MOH setup
by Maryam Baghdadi 19 Aug '19

19 Aug '19

Hello everyone, I need to setup Music on hold feature and I did all modifications in configuration file and did all steps for setup: 1- load MOH and all requirement modules . 2- rtpproxy setups and works correctly 3- mohqueue and mohqcalls tables created. 4- audio file with type index (novanet.8) exists 5- parameters of MOH module setup and mohq_process() function called in request_route()‌. 6- table mohqueue initiated like this‌: +----+------+----------------------------+-------------------+---------+-------+ | id | name | uri | mohdir | mohfile | debug | +----+------+----------------------------+-------------------+---------+-------+ | 1 | main | sip:main at 191.38.245.2 | /var/kamailio/MOH | novanet | 1 | +----+------+----------------------------+-------------------+---------+-------+ Kamailio starts successfully and no error appears , call setup but on hold doesn't work and no audio file plays. I review all previous mailing lists responses but no one answers completely and before me others had this problem.

4 5

Replacing Caller ID
by Pete Kay 18 Aug '19

18 Aug '19

Hi Could anyone tell me if there is a module for replacing the caller ID in the SIP messages? I need to replace the caller ID when the call comes in and leaves Kamailio. When the egress sends back any response, I need to revert the caller ID back to its normal form. I have a long list of numbers to be used as caller-ID, and I need to keep modifying them without having to restart Kamailio. Do I need to write my own modules for maintaining the list of numbers to be used as caller-id? I am running at 2000 CPS, so I think I need to implement some sort of hash table in order for the caller id to be retrieved in round roubin fashion very quickly. Is there any modules for this purpose or I need to write a cusom one? Pete

2 1

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

Kamailio v5.2.4 Released
by Daniel-Constantin Mierla 14 Aug '19

14 Aug '19

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

1 0

Planning the release of Kamailio v5.2.4
by Daniel-Constantin Mierla 14 Aug '19

14 Aug '19

Hello, I am considering to do soon a new release out of branch 5.2, respectively v5.2.4. I am aiming for August 12 or August 14, a matter of how backporting is finished, given that next week some devs travel to ClueCon. As usual, if you are aware of issues not reported yet on bug tracker or fixes not yet backported to branch 5.2, act during the next days to have enough time to approach them. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 3

Strange behavior for unregister() function. Wrong docs? Bug?
by Joel Serrano 13 Aug '19

13 Aug '19

Hello, I'm playing around with the unregister() function from the registrar module: https://www.kamailio.org/docs/modules/devel/modules/registrar.html#registra… Docs say that that it can be used in REQUEST_ROUTE or FAILURE_ROUTE. I needed it in REPLY_ROUTE, and before reading the docs I tried it and got this error: Aug 12 15:52:44 csbc01 kamailio: CRITICAL: <core> [core/cfg.y:3526]: yyerror_at(): parse error in config file /etc/kamailio/csbc/reply_routes.cfg, line 27, column 71: Command cannot be used in the block#012 Aug 12 15:52:44 csbc01 kamailio[12737]: ERROR: bad config file (1 errors) But, I have this working on another setup, I compared, and my difference is that I'm running unregister() inside a route, and calling that route from reply_route, and that works (and by works, I mean it also does what it is supposed to do, which is unregister the AoR). So this doesn't work: ... onreply_route[MANAGE_REG_REPLY] { if(status=~"2[0-9][0-9]") { if(($sel(contact.expires)==0) || ($hdr(Expires)==0)){ if (unregister("location", "$sht(sipserver=>$fU::contact)")) { xlog("L_NOTICE", "[usrloc] removed user location\n"); } route(DEL_SIPSERVER); } ... But this works: ... onreply_route[MANAGE_REG_REPLY] { if(status=~"2[0-9][0-9]") { if(($sel(contact.expires)==0) || ($hdr(Expires)==0)){ route(UNREG_CUSTOMER); route(DEL_SIPSERVER); } ... ... route[UNREG_CUSTOMER] { if (unregister("location", "$sht(sipserver=>$fU::contact)")) { xlog("L_NOTICE", "[usrloc] removed user location\n"); } } ... So I'm in no-mans-land right now, docs say it's not allowed in REPLY_ROUTE, and if I try it it will fail, but if I try it inside a route, it woks (hack?). What is the correct approach here? Should unregister() be valid in reply_route (like other similar functions, for example: save()) and therefor docs should be updated and the error in the logs should also be updated, or if it's really not supported, shouldn't Kamailio not let me use it anywhere that a ends up being called from reply_route? I hope I have explained myself correctly. As always, please let me know if this should be a GH issue instead and I'll happily create it. Thanks, Joel.

3 5

Dispatcher round-robin problems in 5.2
by Alex Balashov 12 Aug '19

12 Aug '19

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 -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

3 4

Kamailio DRA - Unable to get diameter_request() function to send
by Nick Jones 10 Aug '19

10 Aug '19

Hi Kamailio users, I'm trying to setup Kamailio as a Diameter Routing Agent, but I just can't seem to get the diameter_request() function to actually send a diameter request, I just get a warning about no JSON Response: *WARNING: ims_diameter_server [avp_helper.c:341]: addAVPsfromJSON(): No JSON Response* Inside my event route I've got one line to send the data to the peer "ims-hss.localdomain": *event_route[diameter:request]{ diameter_request("ims-hss.localdomain", $diameter_application, $diameter_command, $diameter_request); xlog("Forwarded Diameter Request");}* Hard as I try I can't seem to get this request forwarded to this peer and see that next xlog() line. In the config file I've included the cdp_check_peer & cdp_has_app checks to confirm the peer is up, and able to accept the request, (full config in pastebin below) I've defined the peers in the diametercfg.xml config file, and they're all showing as online when I do a "kamcmd cdp.list_peers": * FQDN: ims-hss.localdomain Details: { State: I_Open Disabled: False Last used: 0 Applications: { appid:vendorid: 16777216:10415 appid:vendorid: 16777216:4491 appid:vendorid: 16777216:13019 appid:vendorid: 16777216:0 appid:vendorid: 16777217:10415 appid:vendorid: 16777221:10415 } }* The source of avp_helper.c shows the warning is called if the length of the JSON is <= 0, but as I'm feeding back out what I've received it's not 0, an no recent major changes to the source, so I'm stumped as to why it's catching this. I'm running Kamailio 5.1.2 on Ubuntu 18.04 installed from Repos. Full Kamailio Config: https://pastebin.com/afgqUfWr Diameter CDP Config XML: https://pastebin.com/bVrBG8mG Relevant Syslog: https://pastebin.com/ZY8z2kd4 Kamcmd cdp.list_peers: https://pastebin.com/cKi4JAHC Any ideas as to what am I missing? Thanks in advance! Nick

1 0

need to Configure S-CSCF, I-CSCF and P-SCF
by ganesh nanaiah 10 Aug '19

10 Aug '19

Hi how do we configure the S-CSCF, I-CSCF and P-CSCF in kamalio 5.2.3 to authenicate with the HSS/PCRF, please point us to document to configure the IMS modules regards Ganesh

3 2

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