sr-users

sr-users@lists.kamailio.org

47 participants
37554 discussions

JS Kemi TypeError: undefined not callable (property 'ifdef' of [object Object])
by Huseyin Kaan Koyukan 18 Jan '22

18 Jan '22

Hello Everyone, First of all, this is my first ever e-mail to the group so I'd like to thank all the developers who built this great product and thank everyone for the kind and helpful community. I've been using Kamailio for the past 8 months, I've had lots of fun with it. My issue is I'm trying to set-up JS Kemi interpreter for my Kamailio-Asterisk box. I translated the config file to JS kemi, which wasn't too bad but I'm getting a type error for the "KSR.kx.ifdef("WITH_ASTERISK")" statement that I used. Jan 17 15:11:26 anayurt kamailio[8261]: 0(8261) DEBUG: app_jsdt [app_jsdt_api.c:1478]: dukopen_KSR(): module 'KSR' has been initialized Jan 17 15:11:26 anayurt kamailio[8261]: 0(8261) DEBUG: app_jsdt [app_jsdt_api.c:473]: jsdt_sr_init_child(): loading js script file: /usr/local/etc/kamailio/kamailio-basic-kemi-jsdt.js Jan 17 15:11:26 anayurt kamailio[8261]: 0(8261) ERROR: app_jsdt [app_jsdt_api.c:447]: jsdt_kemi_load_script(): failed running: TypeError: undefined not callable (property 'ifdef' of [object Object]) Jan 17 15:11:26 anayurt kamailio[8261]: 0(8261) ERROR: <core> [core/sr_module.c:865]: init_mod_child(): error while initializing module app_jsdt (/usr/local/lib64/kamailio/modules/app_jsdt.so) (idx: 0 rank: -127 desc: [main]) Jan 17 15:11:26 anayurt kamailio[8261]: 0(8261) ERROR: <core> [main.c:1671]: main_loop(): error in init_child(PROC_INT) -- exiting In syslog I can see that kex.so module is loaded successfully and 'KSR' has been initialized. I don't know what I'm doing wrong. A few sample JS Kemi code that I could find did not use the kx.ifdef function. Was this a new addition to the interpreter? Perhaps my Kamailio version (kamailio 5.5.0 x86_64/linux) does not support it? Thank you all in advance. Kaan.

1 0

Help with rewriting headers for NAT manually
by Chad 17 Jan '22

17 Jan '22

We are looking for some help (possibly a paid consultant) to help us with our Kamailio setup. To keep this as short as possible: we use Kamailio as a NAT proxy to bridge our external IP and our private IP asterisk servers (via dispatcher). However both the external IP and the internal IP that the Kamailio server uses are virtual IPs created by keepalived. Because of that neither mhomed nor fix_nated_contact work, and we use force_send_socket to direct the traffic. We run linux Debian 10 for the OS. Also we do not use a DB at all, everything is done with local config files. The problem is that when traffic goes out the Contact header has a private IP in it, like: Contact: <sip:##########@10.10.10.###]:5060> There are 2 possible solutions to this: 1. Make changes to linux, keepalived and/or Kamailio so that Kamailio recognize the virtual IPs so that mhomed and fix_nated_contact work as usual. 2. Create a manual header rewrite system. If solution #2: What we need to do is create a way to rewrite the contact header to the external IP on the way out, and on the way back rewrite it back to the internal server that the call is already connected to. Not sure if we will need to store those paths on the server or if we can do some kind of cheat with another persistant header like P-Preferred-Identity or P-Asserted-Identity (i.e. store the internal IP in the name field or something). If anyone out there know of a way to do this or wants to give it a try please reach out to me. Thank you all for your time. -- ^C Chad

5 27

Alternate to FoHSS for Kamailio IMS?
by Simon,Benjamin T 17 Jan '22

17 Jan '22

Hello, We are attempting to setup an instance of Kamailio to serve as an IMS for a test setup of 4G/5G NSA with Open5GS. The instructions on the Kamailio wiki and provided by Open5GS currently specify to use FoHSS as the HSS solution for Kamailio IMS. As this HSS solution has not seen significant development in a few years we are reticent to deploy it on our implementation. Is there an alternative open source HSS which can be deployed to serve as the HSS for Kamailio instead of FoHSS, and would there need to be any adjustments to Kamailio to reflect the deployment of this HSS instead of FoHSS? Thank you, Benjamin Simon Research Assistant Florida Institute for Cybersecurity Research, University of Florida Email: bsimon4(a)ufl.edu Disclaimer: Florida has a very broad public records law. As a result, any written communication created or received by the University of Florida will be made available to the public and media, upon request, unless otherwise exempt. Under Florida law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public records request, do not send electronic mail to this address. Instead, contact by phone or in writing.

2 2

RR balance kamailio
by Gokan Atmaca 16 Jan '22

16 Jan '22

Hello I installed kamailio on Ubuntu. The version information is as follows. (0) I added two dispatcher sip servers. (1) When I enter the parameter as below in the configuration file , I get an error as follows. (2) I am getting RR module not available error. Packages installed are "kamailio-berkeley-modules, kamailio-tls-modules, kamailio-presence-modules" How can I solve the problem? (0) version: version: kamailio 5.5.3 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 9.3.0 (1) Dispatcher list: { NRSETS: 1 RECORDS: { SET: { ID: 1 TARGETS: { DEST: { URI: sip:X.X.X.X FLAGS: AP PRIORITY: 0 LATENCY: { AVG: 0.000000 STD: 0.000000 EST: 0.000000 MAX: 0 TIMEOUT: 0 } } DEST: { URI: sip:Y.Y.Y.Y FLAGS: AP PRIORITY: 0 LATENCY: { AVG: 0.000000 STD: 0.000000 EST: 0.000000 MAX: 0 TIMEOUT: 0 } } } } } } (2) if ( method=="INVITE" ) { ds_select_dst("1","4"); sl_send_reply("100","Trying"); forward(); exit(); } Err_log: Jan 12 12:15:11 kamailio /usr/sbin/kamailio[21241]: INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded Jan 12 12:15:11 kamailio /usr/sbin/kamailio[21241]: INFO: rr [rr_mod.c:188]: mod_init(): outbound module not available -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄⠀⠀⠀⠀

2 3

Mid-dialog failover without virtual IP
by Muhammad Danish Moosa 14 Jan '22

14 Jan '22

Hi, I have a pair of kamailio stateful proxies and am trying to achieve Active-Passive failover model with DMQ dialog replication. Primary Proxy is working in the middle of 2 SBCs and all nodes are within the same network so NATing is NOT involved ;secondary proxy is accessible through VPN. It's pretty simple configuration, proxy is just adding and removing headers in the middle. So if I stop the kamailio service on primary IP , SBCs blacklist that and start sending new invites to secondary IP. That's all good. But if I reproduce this failover during a connected session , SBCs do not send mid-dialog requests/responses to failover IP. I can see they still try to send messages to primary SBC which obviously end up with timeout. I understand the most natural solution is HA with Virual IP but it's not possible because secondary IP is accessible through VPN. I tried to use DNS SRV record with priorities but that also does not work with mid-dialog messages, I also have tried to change record-route/via header to fqdn through advertise_address. Its not changing record-route but via only but I am still not getting expected results. Any guidance of possible solution(s) here will be appreciated. -- Muhammad Danish Moosa " The core of mans' spirit comes from new experiences. "___ Christopher McCandless

3 2

Massive uploading of aliases through a dbtext
by Denys Pozniak 14 Jan '22

14 Jan '22

Hello! I need help uploading a list of aliases through a dbtext to use them via myself. It is likely that there is some configuration problem: *loadmodule "db_text.so"* *modparam("db_text", "db_mode", 1)modparam("db_text", "emptystring", 1)* *loadmodule "alias_db.so"modparam("alias_db", "db_url", "text:///etc/kamailio/dbtext")* *[root@kamailio]$ cat dbtext/dbaliasesid(int,auto) alias_username(string) alias_domain(string) username(string) domain(string)1::sip.test.local::* *[root@kamailio]$ kamcmd core.aliases_list{ myself_callbacks: yes aliases: { }}* If done through a script (alias=sip.test.local), then everything works fine: *[root@kamailio]$ kamcmd core.aliases_list{ myself_callbacks: yes aliases: { alias: { proto: * address: sip.test.local port: * } }}* -- BR, Denys Pozniak

2 4

Retrieve last via IP from SIP MEssage
by Adarsh Chauhan 14 Jan '22

14 Jan '22

Hi All, I have tried couple of methods to retrieve last via IP of SIP message but failed to retrieve it, trying to retrieve the source - @hf_value.via[-1].host, it simply prints the exact text back @hf_value.via[-1].host - $sel((a)hf_value.via[-1]) it doest give the IP but the entire via value SIP/2.0/TCP 172.31.30.144;branch=z9hG4bKf8bd.753341d2000000000000000000000000.0.host @via[-1].host it also simply prints the exact text back @via[-1].host Regards, Adarsh Chauha

2 1

EVAPI workload allocation across processes
by Alex Balashov 13 Jan '22

13 Jan '22

Hi, Given several EVAPI worker processes: modparam("evapi", "workers", 4) # kamcmd -s /run/kamailio/kamailio_ctl ps | fgrep -i evapi 539257 EvAPI Dispatcher 539258 EvAPI Worker 539259 EvAPI Worker 539260 EvAPI Worker 539261 EvAPI Worker How should one understand the way that the EVAPI workload is allocated among them? My best guess is that the EvAPI dispatcher process is the sole accept()or of client connections and the place where all relaying to client connections is done, regardless of their number, and that the ‘workers’ represent an async pool of processes in which TM transactions can be resumed or other work can be done when an outside caller sends a message to the dispatcher. However, the documentation[1] is a little vague on the meaning of the ‘workers’ modparam: "Number of worker processes to be started to handle incoming messages from remote applications.” Or maybe it’s not. Just wanted to confirm that my understanding is correct. Thanks! — Alex [1] https://kamailio.org/docs/modules/5.5.x/modules/evapi.html#evapi.p.workers -- 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/

2 3

Reverse Kamailio Dispatcher order
by Adarsh Chauhan 12 Jan '22

12 Jan '22

Hi All, I was looking for a way where i could reverse the order of priority set on destinations in dispatcher file. for eg: if i have the following file: 1 sip:10.252.168.41:5060;transport=tcp 0 5 # (US) 1 sip:10.252.168.42:5060;transport=tcp 0 4 # (US) 1 sip:10.252.168.43:5060;transport=tcp 0 3 # (EU) 1 sip:10.252.168.44:5060;transport=tcp 0 2 # (EU) I wanted to use top to bottom when in US region and bottom to top when in EU region. One option is to make another set, however that will force Kamailio to send ping (OPTIONS) twice when probing. Regards, Adarsh Chauhan

4 4

Suggestion on receiving AAR
by Jyoti Bansal 10 Jan '22

10 Jan '22

Hello all, We are trying to connect kamailio ims to a pcrf, connection is successful. Whenever we register through bhoghe client , we receive AAR on pcrf from kamailio ims(pcscf), so just need a suggestion can we disable that till we receive invite from the soft phone? Can anyone help on this? Thanks, Jyoti bansal -- Confidentiality Notice and Disclaimer: This email (including any attachments) contains information that may be confidential, privileged and/or copyrighted. If you are not the intended recipient, please notify the sender immediately and destroy this email. Any unauthorized use of the contents of this email in any manner whatsoever, is strictly prohibited. If improper activity is suspected, all available information may be used by the sender for possible disciplinary action, prosecution, civil claim or any remedy or lawful purpose. Email transmission cannot be guaranteed to be secure or error-free, as information could be intercepted, lost, arrive late, or contain viruses. The sender is not liable whatsoever for damage resulting from the opening of this message and/or the use of the information contained in this message and/or attachments. Expressions in this email cannot be treated as opined by the sender company management – they are solely expressed by the sender unless authorized.

2 1

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