- sr-users - kamailio.org

TLS in-dialog set_forward_no_connect()and upstream TLS LCR gateway
by Anthony Joseph Messina 21 Sep '19

21 Sep '19

In preparation for the 5.3 release, I've been testing the following configuration change for TCP/TLS connections: https://github.com/kamailio/kamailio/commit/ 8bba208fe6ae7ccb4c92362b8c33f1530b9f56da route[REQINIT] { # no connect for sending replies set_reply_no_connect(); if(has_totag()) { # no connect for requests within dialog set_forward_no_connect(); } This change creates issues when a UAC TLS INVITE routes to an upstream gateway using TLS to port 5061 (via the LCR module). Kamailio sends the initial outbound TLS connection from a local ephemeral port. The TCPOPS tcp_keepalive_enable function issues keepalives from the local ephemeral port to the gateway port 5061: https://kamailio.org/docs/modules/stable/modules/ tcpops#tcpops.f.tcp_keepalive_enable Even so, the TLS connection eventually times out, after which in-dialog requests from the UAC are no longer able to reach the upstream gateway. ERROR: tm [../../core/forward.h:293]: msg_send_buffer(): tcp_send failed WARNING: tm [t_fwd.c:1570]: t_send_branch(): sending request on branch 0 failed ERROR: sl [sl_funcs.c:372]: sl_reply_error(): stateless error reply used: Unfortunately error on sending to next hop occurred (477/SL) I figure I must be doing something wrong with my TCPOPS here. Is a TLS connection to an upstream gateway supposed to be maintained throughout the duration of a call? -- Anthony - https://messinet.com F9B6 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6

2 6

Info: initialization of libssl 1.1.+ with PTHREAD_PROCESS_SHARED attribute for pthread mutex and rwlock
by Daniel-Constantin Mierla 21 Sep '19

21 Sep '19

Hello, after couple of months waiting for feedback about the workaround with the preloaded shared library to set the PTHREAD_PROCESS_SHARED attribute for pthread mutex/rwlock in order to avoid deadlocks and as it seems to be the solution, I just pushed a few commits to move that code in the core of kamailio. It this way the initialization with the PTHREAD_PROCESS_SHARED attribute is done by default when libssl v1.1 is detected at compile time, without the need of using the approach with a preloaded library. The shared library is still kept in the tls module: * https://github.com/kamailio/kamailio/tree/master/src/modules/tls/utils/open… Probably is going to be removed in the near future. I am asking the community members that use Kamailio on systems with libssl v1.1+ to test the master branch and give feedback. The master branch is anyhow in testing phase for preparing the next major release v5.3.0, so it will help for that as well. If no issue is going to be reported soon, the commits will be backported to stable branches, to re-enable smooth use of Kamailio with libssl v1.1+. When libssl v1.1+ is detected, the core links with pthread, but that was already present in the Makefiles.defs for different compile options. The pthread more or less a default library on linuxes/unixes, so this should not introduce any major dependency to the Kamailio core. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

6 21

Possible locking issue in usrloc module in file udomain.c
by Rupesh Kumar 18 Sep '19

18 Sep '19

Hi , Currently I am running kamailio 4.2 and now upgrading to kamailio 5.2 and was just going thru the changes. In the file modules/usrloc/udomain.c inside the function free_udomain( ) , it appears that we are not protecting via lock_ulslot and unlock_ulslot doing free. Could it cause some race condition ? May be its intentional but going thru the github history its there since day 1. I checked all branches in kamailio 4.x and we have the protection. In 4.x void free_udomain(udomain_t* _d) { int i; if (_d->table) { for(i = 0; i < _d->size; i++) { lock_ulslot(_d, i); deinit_slot(_d->table + i); unlock_ulslot(_d, i); } shm_free(_d->table); } shm_free(_d); } In 5.x void free_udomain(udomain_t* _d) { int i; if (_d->table) { for(i = 0; i < _d->size; i++) { deinit_slot(_d->table + i); } shm_free(_d->table); } shm_free(_d); }

2 2

How to distinguish is from Asterisk or from the client
by przeqpiciel 18 Sep '19

18 Sep '19

Hi, I looking information how to distinguish whether the packet is directed to the Astersik (my platform) or to the customer (softphone / sip client ).

5 5

NAT problem
by Arnout Van Den Kieboom 18 Sep '19

18 Sep '19

Hi, First of all, I'm really new to Kamailio. So sorry if I ask a stupid question, or perhaps a really weird one. I started using kamailio in a test environment about a week ago. for setup i have the situation for inbound calls: Carrier --> FW (NAT) --> Kamailio for outbound to an asterisk box i have: Kamailio --> FW (NAT) --> Asterisk for outbound to users i have: Kamailio --> FW (NAT) --> sip-phone (yealink) or grandstream During that time i was able to : Set up calls to users, Use the dispatcher module use the avpops module to do data lookups. Get calls from asterisk to kamailio user to work. Also calls between users (even though behind nat) are having good audio. I have installed rtpproxy and it works nicely. There is just one situation where it fails: Carrier --> FW (NAT) Kamailio --> asterisk There is only one way audio (from asterisk to carrier) but not from carrier to asterisk. I believe I need to do something with the rtp proxy module ... and tried different things (forcing the r flag, forcing the w flag) Any idea where I might need to start looking? It's been driving me crazy... Thanks Pemp

4 7

app_lua: invalid Lua environment attributes or parameters
by Yuriy Gorlichenko 18 Sep '19

18 Sep '19

Hi! Im using kamailio 5.1.8 with app_lua and getting this message during startup of kamailio. Looks like I forgot to add something at the module setup, but cant figure out what is wrong. My setup of app_lua is: modparam("app_lua", "load", "/etc/kamailio/extended/main.lua") modparam("app_lua","reload",1) modparam("app_lua","register","textops") app_lua [app_lua_sr.c:1599]: sr_kemi_lua_exec_func_ex(): invalid Lua environment attributes or parameters starting kamailio service with kamailio -f /etc/kamailio/extended/main.lua Also here is little bit confusing me that in case of use "KSR" everywhere I'm getting message about "sr"... Thx in advice

2 5

dedicated bearer - Kamailio settings
by Jack R 18 Sep '19

18 Sep '19

Hi, We have installed Kamailio as IMS setup pcscf icscf scscf - 3 instances running on Ubuntu. I have done the attached (image) settings to create dedicated bearer in nextepc as advised by this link: https://github.com/open5gs/nextepc/issues/180 Do I need to do some setting in Kamailio server side (maybe in pcscf cfg files etc.to take some information from PCRF) to make dedicated bearer work end to end or that is all (just configure the new apn in the phone) rest will be taken care itself? Thanks and Regards, Jack.

2 1

core dump if silo table > ~5000 records
by David Villasmil 18 Sep '19

18 Sep '19

Hello guys, i've got a kamailo: version: kamailio 5.0.0 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, 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_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, 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 on 19:50:58 Mar 28 2017 with gcc 4.9.2 which was core dumping every 20 seconds and we had no idea why. We emptied out the silo table, which had: mysql> select count(*) from silobackup; +----------+ | count(*) | +----------+ | 5240 | +----------+ records. Once we truncated it, kamailio started working again. Is there a limit to how many records msilo can handle? I will look into the data in the table, but in case there's a limit, i'd like to know. core available on request. Thanks Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 3

Kamailio+B2BUA on IPv4-only and NAT64 Apple app store tests
by Anthony Alba 17 Sep '19

17 Sep '19

Hi folks, I'm wondering what you do to pass Apple app store tests (IPv6-only NAT64/DNS64 scenario) with the iOS app likely to put IPv6 addresses in the SDP, when Kamailio and your B2BUA(Asterisk, FreeSWITCH,...) are IPv4-only endpoints. By "pass" I mean media flowing + SIP working - not sure the app store gatekeepers would actually test media, but it would be nice to have a robust solution. Strictly speaking, this is not a Kamailio's problem but a media SDP/<your-rtp-proxy-of-choice> problem. But since everything is so closely intertwined I'm wondering where you choose to the location the "solution". I have noticed that if Kamailio is IPv4-only and it "sees" IPv6-addresses(Contact, Via headers??) it will try to resolve the IPv6-address as a DNS name! The Wikipedia article on NAT64 mentions 464XLAT(RFC 6877) and Port Control Protocol (RFC 7225), but those seem to be deep rabbit-holes... Cheers Anthony Alba

4 5

Kamailio merchandising shop
by Henning Westerholt 16 Sep '19

16 Sep '19

Hello, there is now a Kamailio merchandising shop available: https://skalatan.de/merchandising/ You find there many options e.g. different Kamailio T-Shirts, Hoodies, Bags, Caps, Mugs, etc.. It provides shipping in many countries world-wide (based from Europe and also USA). Feedback via (direct) e-mail welcome. Best regards, Henning

1 1

3GPP compliance
by Tihomir Culjaga 15 Sep '19

15 Sep '19

Hi, is there any 3GPP compliance list for Kamailio IMS ? Regards, Tihomir.

2 1

RUN kamailio in kubernetes
by Gaurav Bmotra 14 Sep '19

14 Sep '19

hi i want to run kamailio in kubernetes deployment and i want to run this kamailio/kamailio-ci:5.2 image in to the kubernetse .. can anyone help thank you -- *Regards:* Gaurav Kumar

5 6

Problem with incoming audio from Asterisk
by przeqpiciel 14 Sep '19

14 Sep '19

Hi, After a month of fight with SIP signalling I made it but now I have problem with incoming audio from Asterisk. Kamailio and Asterisk are their own public IPs I dont use rtpproxy. When Asterisk sends rtp I'm able to see RTP on my router but it not going to my computer. Maybe somebody have idea why ?

2 1

Using $shv within current call only
by Zhan Bazarov 13 Sep '19

13 Sep '19

Hello, we ran into a trouble with sharing variable into reply route... We are going to match asterisk's uniqueid with rtpengine records like this: route[from_asterisk]{ $var(UniqueId)=$hdr(X-UniqueId); $var(rtp_flags) = $var(rtp_flags) + " label={uid:$var(UniqueId),stream:outgoing} record-call=on"; rtpengine_manage($var(rtp_flags)); } it nicely work for outgoing request, but doesn't for reply.... reply_route[from_pstn]{ rtpengine_manage("replace-origin replace-session-connection ICE=remove RTP/AVP rtcp-mux-demux label={uid:$var(UniqueId),stream:outgoing"); } and it doesn't work... The one possible way what we found its using $shv instead of $var/$avp... But its unsecure way, cuz it may confus our bussines logic... Do you have any idea how to implement this, how we can assign $shv within current call only? Many thanks!

3 2

Issue with <null> and 0 when comparing vars
by Joel Serrano 13 Sep '19

13 Sep '19

Hello, I'm running into what I believe a weird situation when comparing <null> to 0. I have the following lines: xlog("L_NOTICE", "DEBUG: sel(contact.expires)=$sel(contact.expires) - hdr(Expires)=$hdr(Expires)\n"); if ($hdr(Expires)==0 || $sel(contact.expires)==0) { xlog("L_NOTICE", "[end] removed user location\n"); } else { xlog("L_NOTICE", "[end] saved user location\n"); } I registered with 3 devices, one sends expires as header, another as contact param, and the last uses both header AND contact param. My surprise was this: 1- Both header and contact param: Sep 12 19:37:48 csbc01 csbc[8036]: NOTICE: {1 4 REGISTER 02c3ea6ee623916d37532188031017c9@0:0:0:0:0:0:0:0} <script>: DEBUG: sel(contact.expires)=600 - hdr(Expires)=600 Sep 12 19:37:48 csbc01 csbc[8036]: NOTICE: {1 4 REGISTER 02c3ea6ee623916d37532188031017c9@0:0:0:0:0:0:0:0} <script>: [end] saved user location 2- Only contact param: Sep 12 19:36:15 csbc01 csbc[8035]: NOTICE: {1 40629 REGISTER f2cbaa53-eabfd633(a)84.121.150.224} <script>: DEBUG: sel(contact.expires)=600 - hdr(Expires)=<null> Sep 12 19:36:15 csbc01 csbc[8035]: NOTICE: {1 40629 REGISTER f2cbaa53-eabfd633(a)84.121.150.224} <script>: [end] removed user location 2- Only header: Sep 12 19:29:33 csbc01 csbc[8033]: NOTICE: {1 402 REGISTER 2_1804628355(a)192.168.30.31} <script>: DEBUG: sel(contact.expires)=<null> - hdr(Expires)=3600 Sep 12 19:29:33 csbc01 csbc[8033]: NOTICE: {1 402 REGISTER 2_1804628355(a)192.168.30.31} <script>: [end] removed user location I can workaround the header by using is_present_hf() before comparing, I can also probably parse the $ct to see if it has some Expires in it, but I really want to know if my understanding is incorrect and I'm doing something wrong or if this is a bug? Thanks! Joel.

2 2

Testing server up with SIP OPTIONS/netcat
by Andrew White 13 Sep '19

13 Sep '19

Hi all, As part of a custom monitoring solution, I’m writing a simple script that sends an OPTIONS via netcat to a Kamailio server. However the server doesn’t appear to like it. Here’s the text - options.sip: OPTIONS sip:10.0.0.10 SIP/2.0 Via: SIP/2.0/UDP 10.0.0.20:5060 From: <sip:monitoring@10.0.0.20> To: sip:monitoring@10.0.0.10 Call-ID: monitoring(a)10.0.0.20 CSeq: 1 OPTIONS I’m running the following command from the 10.0.0.20 machine: nc -u 10.0.0.10 5060 < options.sip And I get the following error in the Kamailio logs: ERROR: <core> [core/parser/parse_cseq.c:56]: parse_cseq(): method terminated unexpectedly ERROR: <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq ERROR: <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq ERROR: <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [CSeq: 1 OPTIONS] ERROR: <core> [core/parser/parse_cseq.c:56]: parse_cseq(): method terminated unexpectedly ERROR: <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq ERROR: <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq ERROR: <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [CSeq: 1 OPTIONS] WARNING: <core> [core/receive.c:319]: receive_msg(): parsing relevant headers failed ERROR: <core> [core/parser/parse_cseq.c:56]: parse_cseq(): method terminated unexpectedly ERROR: <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq ERROR: <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq ERROR: <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [CSeq: 1 OPTIONS] ERROR: pv [pv_core.c:1893]: pv_get_hdr(): error parsing headers ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/parse_cseq.c:56]: parse_cseq(): method terminated unexpectedly ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [CSeq: 1 OPTIONS] ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/parse_cseq.c:56]: parse_cseq(): method terminated unexpectedly ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [CSeq: 1 OPTIONS] ERROR: {1 <null> monitoring(a)13.236.91.139} maxfwd [mf_funcs.c:51]: is_maxfwd_present(): parsing MAX_FORWARD header failed! ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/parse_cseq.c:56]: parse_cseq(): method terminated unexpectedly ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [CSeq: 1 OPTIONS] ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/msg_translator.c:2361]: build_res_buf_from_sip_req(): alas, parse_headers failed As far as I can see, the message itself is valid. It appears parse_cseq() is expecting a higher cseq, or more headers? I’ve looked at another OPTIONS message we get regularly from one of our upstream, and it’s almost identical to this one. Can anyone point me the right way here? Thanks! Andrew

3 2

Presence and BLF
by Bill Neely 12 Sep '19

12 Sep '19

Hi all: I am trying to set up presence and BLF notifies on Kamailo 5.2.4 I am following the instructions laid out in http://kb.asipto.com/kamailio:presence:k43-blf Don't know if these instructions are valid, but I am definitely not getting any light action (using Grandstream 2130 and Grandstream Wav for testing.) Entries in active_watchers appear to be correct. Here is my cfg file: #!KAMAILIO # # Kamailio (OpenSER) SIP Server v5.1 - default configuration script # - web: https://www.kamailio.org # - git: https://github.com/kamailio/kamailio # # Direct your questions about this file to: <sr-users(a)lists.kamailio.org> # # Refer to the Core CookBook at https://www.kamailio.org/wiki/ # for an explanation of possible statements, functions and parameters. # # Note: the comments can be: # - lines starting with #, but not the pre-processor directives, # which start with #!, like #!define, #!ifdef, #!endif, #!else, #!trydef, # #!subst, #!substdef, ... # - lines starting with // # - blocks enclosed in between /* */ # # Several features can be enabled using '#!define WITH_FEATURE' directives: # # *** To run in debug mode: # - define WITH_DEBUG # # *** To enable mysql: # - define WITH_MYSQL # # *** To enable authentication execute: # - enable mysql # - define WITH_AUTH # - add users using 'kamctl' # # *** To enable IP authentication execute: # - enable mysql # - enable authentication # - define WITH_IPAUTH # - add IP addresses with group id '1' to 'address' table # # *** To enable persistent user location execute: # - enable mysql # - define WITH_USRLOCDB # # *** To enable presence server execute: # - enable mysql # - define WITH_PRESENCE # # *** To enable nat traversal execute: # - define WITH_NAT # - install RTPProxy: http://www.rtpproxy.org # - start RTPProxy: # rtpproxy -l _your_public_ip_ -s udp:localhost:7722 # - option for NAT SIP OPTIONS keepalives: WITH_NATSIPPING # # *** To enable PSTN gateway routing execute: # - define WITH_PSTN # - set the value of pstn.gw_ip # - check route[PSTN] for regexp routing condition # # *** To enable database aliases lookup execute: # - enable mysql # - define WITH_ALIASDB # # *** To enable speed dial lookup execute: # - enable mysql # - define WITH_SPEEDDIAL # # *** To enable multi-domain support execute: # - enable mysql # - define WITH_MULTIDOMAIN # # *** To enable TLS support execute: # - adjust CFGDIR/tls.cfg as needed # - define WITH_TLS # # *** To enable XMLRPC support execute: # - define WITH_XMLRPC # - adjust route[XMLRPC] for access policy # # *** To enable anti-flood detection execute: # - adjust pike and htable=>ipban settings as needed (default is # block if more than 16 requests in 2 seconds and ban for 300 seconds) # - define WITH_ANTIFLOOD # # *** To block 3XX redirect replies execute: # - define WITH_BLOCK3XX # # *** To block 401 and 407 authentication replies execute: # - define WITH_BLOCK401407 # # *** To enable VoiceMail routing execute: # - define WITH_VOICEMAIL # - set the value of voicemail.srv_ip # - adjust the value of voicemail.srv_port # # *** To enhance accounting execute: # - enable mysql # - define WITH_ACCDB # - add following columns to database #!ifdef ACCDB_COMMENT ALTER TABLE acc ADD COLUMN src_user VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE acc ADD COLUMN src_domain VARCHAR(128) NOT NULL DEFAULT ''; ALTER TABLE acc ADD COLUMN src_ip varchar(64) NOT NULL default ''; ALTER TABLE acc ADD COLUMN dst_ouser VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE acc ADD COLUMN dst_user VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE acc ADD COLUMN dst_domain VARCHAR(128) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN src_user VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN src_domain VARCHAR(128) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN src_ip varchar(64) NOT NULL default ''; ALTER TABLE missed_calls ADD COLUMN dst_ouser VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN dst_user VARCHAR(64) NOT NULL DEFAULT ''; ALTER TABLE missed_calls ADD COLUMN dst_domain VARCHAR(128) NOT NULL DEFAULT ''; #!endif ####### Include Local Config If Exists ######### import_file "kamailio-local.cfg" #!define WITH_DEBUG #!define WITH_NAT #!define WITH_AUTH #!define WITH_MYSQL #!define WITH_USRLOCDB #!define WITH_PRESENCE ####### Defined Values ######### # *** Value defines - IDs used later in config #!ifdef WITH_MYSQL # - database URL - used to connect to database server by modules such # as: auth_db, acc, usrloc, a.s.o. #!ifndef DBURL #!define DBURL "mysql://kamailio:kamailiorw@localhost/kamailio" #!endif #!endif #!ifdef WITH_MULTIDOMAIN # - the value for 'use_domain' parameters #!define MULTIDOMAIN 1 #!else #!define MULTIDOMAIN 0 #!endif # - flags # FLT_ - per transaction (message) flags # FLB_ - per branch flags #!define FLT_ACC 1 #!define FLT_ACCMISSED 2 #!define FLT_ACCFAILED 3 #!define FLT_NATS 5 #!define FLT_DLG 9 #!define FLT_DLGINFO 10 #!define FLB_NATB 6 #!define FLB_NATSIPPING 7 ####### Global Parameters ######### ### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR #!ifdef WITH_DEBUG debug=3 log_stderror=no #!else debug=2 log_stderror=no #!endif memdbg=5 memlog=5 log_facility=LOG_LOCAL0 log_prefix="{$mt $hdr(CSeq) $ci} " /* number of SIP routing processes */ children=8 /* uncomment the next line to disable TCP (default on) */ # disable_tcp=yes /* uncomment the next line to disable the auto discovery of local aliases * based on reverse DNS on IPs (default on) */ # auto_aliases=no /* add local domain aliases */ # alias="sip.mydomain.com" /* uncomment and configure the following line if you want Kamailio to * bind on a specific interface/port/proto (default bind on all available) */ listen=udp:62.151.xx.xx:50060 # allow http requests listen=tcp:127.0.0.1:8080 tcp_accept_no_cl=yes #!ifdef WITH_TLS enable_tls=yes #!endif /* life time of TCP connection when there is no traffic * - a bit higher than registration expires to cope with UA behind NAT */ tcp_connection_lifetime=3605 ####### Custom Parameters ######### /* These parameters can be modified runtime via RPC interface * - see the documentation of 'cfg_rpc' module. * * Format: group.id = value 'desc' description * Access: $sel(cfg_get.group.id) or @cfg_get.group.id */ #!ifdef WITH_PSTN /* PSTN GW Routing * * - pstn.gw_ip: valid IP or hostname as string value, example: * pstn.gw_ip = "10.0.0.101" desc "My PSTN GW Address" * * - by default is empty to avoid misrouting */ pstn.gw_ip = "" desc "PSTN GW Address" pstn.gw_port = "" desc "PSTN GW Port" #!endif #!ifdef WITH_VOICEMAIL /* VoiceMail Routing on offline, busy or no answer * * - by default Voicemail server IP is empty to avoid misrouting */ voicemail.srv_ip = "104.192.xx.xx" desc "VoiceMail IP Address" voicemail.srv_port = "5060" desc "VoiceMail Port" #!endif ####### Modules Section ######## /* set paths to location of modules */ # mpath="/usr/lib64/kamailio/modules/" #!ifdef WITH_MYSQL loadmodule "db_mysql.so" #!endif loadmodule "jsonrpcs.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "cfg_rpc.so" loadmodule "acc.so" loadmodule "counters.so" #!ifdef WITH_AUTH loadmodule "auth.so" loadmodule "auth_db.so" #!ifdef WITH_IPAUTH loadmodule "permissions.so" #!endif #!endif #!ifdef WITH_ALIASDB loadmodule "alias_db.so" #!endif #!ifdef WITH_SPEEDDIAL loadmodule "speeddial.so" #!endif #!ifdef WITH_MULTIDOMAIN loadmodule "domain.so" #!endif #!ifdef WITH_PRESENCE loadmodule "presence.so" loadmodule "presence_xml.so" loadmodule "presence_dialoginfo.so" loadmodule "pua.so" loadmodule "pua_dialoginfo.so" #!endif #!ifdef WITH_NAT loadmodule "nathelper.so" loadmodule "rtpproxy.so" #!endif #!ifdef WITH_TLS loadmodule "tls.so" #!endif #!ifdef WITH_ANTIFLOOD loadmodule "htable.so" loadmodule "pike.so" #!endif #!ifdef WITH_XMLRPC loadmodule "xmlrpc.so" #!endif #!ifdef WITH_DEBUG loadmodule "debugger.so" #!endif # load the module loadmodule "xhttp.so" loadmodule "json.so" loadmodule "pua_json.so" loadmodule "dialog.so" # ----------------- setting module-specific parameters --------------- # ----- jsonrpcs params ----- modparam("jsonrpcs", "pretty_format", 1) /* set the path to RPC fifo control file */ # modparam("jsonrpcs", "fifo_name", "/var/run/kamailio/kamailio_rpc.fifo") /* set the path to RPC unix socket control file */ # modparam("jsonrpcs", "dgram_socket", "/var/run/kamailio/kamailio_rpc.sock") # ----- ctl params ----- /* set the path to RPC unix socket control file */ # modparam("ctl", "binrpc", "unix:/var/run/kamailio/kamailio_ctl") # ----- tm params ----- # auto-discard branches from previous serial forking leg modparam("tm", "failure_reply_mode", 3) # default retransmission timeout: 30sec modparam("tm", "fr_timer", 30000) # default invite retransmission timeout after 1xx: 120sec modparam("tm", "fr_inv_timer", 120000) # ----- rr params ----- # set next param to 1 to add value to ;lr param (helps with some UAs) modparam("rr", "enable_full_lr", 0) # do not append from tag to the RR (no need for this script) modparam("rr", "append_fromtag", 0) # ----- registrar params ----- modparam("registrar", "method_filtering", 1) /* uncomment the next line to disable parallel forking via location */ # modparam("registrar", "append_branches", 0) /* uncomment the next line not to allow more than 10 contacts per AOR */ # modparam("registrar", "max_contacts", 10) /* max value for expires of registrations */ modparam("registrar", "max_expires", 3600) /* set it to 1 to enable GRUU */ modparam("registrar", "gruu_enabled", 0) # ----- acc params ----- /* what special events should be accounted ? */ modparam("acc", "early_media", 0) modparam("acc", "report_ack", 0) modparam("acc", "report_cancels", 0) /* by default ww do not adjust the direct of the sequential requests. * if you enable this parameter, be sure the enable "append_fromtag" * in "rr" module */ modparam("acc", "detect_direction", 0) /* account triggers (flags) */ modparam("acc", "log_flag", FLT_ACC) modparam("acc", "log_missed_flag", FLT_ACCMISSED) modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") modparam("acc", "failed_transaction_flag", FLT_ACCFAILED) /* enhanced DB accounting */ #!ifdef WITH_ACCDB modparam("acc", "db_flag", FLT_ACC) modparam("acc", "db_missed_flag", FLT_ACCMISSED) modparam("acc", "db_url", DBURL) modparam("acc", "db_extra", "src_user=$fU;src_domain=$fd;src_ip=$si;" "dst_ouser=$tU;dst_user=$rU;dst_domain=$rd") #!endif # ----- usrloc params ----- /* enable DB persistency for location entries */ #!ifdef WITH_USRLOCDB modparam("usrloc", "db_url", DBURL) modparam("usrloc", "db_mode", 2) modparam("usrloc", "use_domain", MULTIDOMAIN) #!endif # ----- auth_db params ----- #!ifdef WITH_AUTH modparam("auth_db", "db_url", DBURL) modparam("auth_db", "calculate_ha1", yes) modparam("auth_db", "password_column", "password") modparam("auth_db", "load_credentials", "") modparam("auth_db", "use_domain", MULTIDOMAIN) # ----- permissions params ----- #!ifdef WITH_IPAUTH modparam("permissions", "db_url", DBURL) modparam("permissions", "db_mode", 1) #!endif #!endif # ----- alias_db params ----- #!ifdef WITH_ALIASDB modparam("alias_db", "db_url", DBURL) modparam("alias_db", "use_domain", MULTIDOMAIN) #!endif # ----- speeddial params ----- #!ifdef WITH_SPEEDDIAL modparam("speeddial", "db_url", DBURL) modparam("speeddial", "use_domain", MULTIDOMAIN) #!endif # ----- domain params ----- #!ifdef WITH_MULTIDOMAIN modparam("domain", "db_url", DBURL) /* register callback to match myself condition with domains list */ modparam("domain", "register_myself", 1) #!endif #!ifdef WITH_PRESENCE # ----- presence params ----- modparam("presence", "db_url", DBURL) modparam("presence", "server_address", "sip:62.151.xx.xx:50060" ) modparam("presence", "send_fast_notify", 0) modparam("presence", "db_update_period", 20) modparam("presence", "clean_period", 40) modparam("presence", "subs_db_mode", 2) modparam("presence", "fetch_rows", 1000) modparam("presence", "local_log_level", 3) # ----- presence_xml params ----- modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) # ----- presence_dialoginfo params ----- modparam("presence_dialoginfo", "force_single_dialog", 0) # ----- pua params ----- modparam("pua", "db_url", DBURL) modparam("pua", "db_mode", 2) modparam("pua", "update_period", 60) modparam("pua", "dlginfo_increase_version", 0) modparam("pua", "reginfo_increase_version", 0) modparam("pua", "check_remote_contact", 1) modparam("pua", "fetch_rows", 1000) # ----- pua_dialoginfo params ----- modparam("pua_dialoginfo", "include_callid", 1) modparam("pua_dialoginfo", "send_publish_flag", FLT_DLGINFO) modparam("pua_dialoginfo", "caller_confirmed", 0) modparam("pua_dialoginfo", "include_tags", 1) modparam("pua_dialoginfo", "override_lifetime", 124) #!endif # ----- dialog params ----- modparam("dialog", "db_url", DBURL) modparam("dialog", "enable_stats", 1) modparam("dialog", "db_mode", 1) modparam("dialog", "dlg_flag", FLT_DLG) #!ifdef WITH_NAT # ----- rtpproxy params ----- modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:22222") # ----- nathelper params ----- modparam("nathelper", "natping_interval", 30) modparam("nathelper", "ping_nated_only", 1) modparam("nathelper", "sipping_bflag", FLB_NATSIPPING) modparam("nathelper", "sipping_from", "sip:pinger@kamailio.org") # params needed for NAT traversal in other modules modparam("nathelper|registrar", "received_avp", "$avp(RECEIVED)") modparam("usrloc", "nat_bflag", FLB_NATB) #!endif #!ifdef WITH_TLS # ----- tls params ----- modparam("tls", "config", "/etc/kamailio/tls.cfg") #!endif #!ifdef WITH_ANTIFLOOD # ----- pike params ----- modparam("pike", "sampling_time_unit", 2) modparam("pike", "reqs_density_per_unit", 16) modparam("pike", "remove_latency", 4) # ----- htable params ----- /* ip ban htable with autoexpire after 5 minutes */ modparam("htable", "htable", "ipban=>size=8;autoexpire=300;") #!endif #!ifdef WITH_XMLRPC # ----- xmlrpc params ----- modparam("xmlrpc", "route", "XMLRPC"); modparam("xmlrpc", "url_match", "^/RPC") #!endif #!ifdef WITH_DEBUG # ----- debugger params ----- modparam("debugger", "cfgtrace", 1) modparam("debugger", "log_level_name", "exec") #!endif ####### Routing Logic ######## /* Main SIP request routing logic * - processing of any incoming SIP request starts with this route * - note: this is the same as route { ... } */ request_route { xlog("L_ALERT","ALERT: REQUEST ROUTE ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^6 $rm from $fu (IP:$si:$sp) $du\nMESSAGE BUFFER:\n$mb\n\n\nRU:$ru\n"); $var(i)=0; while($var(i)<$branch(count)) { xlog("$(branch(uri)[$var(i)])\n"); $var(i) = $var(i) + 1; } # per request initial checks route(REQINIT); # NAT detection route(NATDETECT); # handle registrations route(REGISTRAR); # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) { route(RELAY); } exit; } # handle retransmissions if (!is_method("ACK")) { if(t_precheck_trans()) { t_check_trans(); exit; } t_check_trans(); } # handle requests within SIP dialogs route(WITHINDLG); ### only initial requests (no To tag) # authentication route(AUTH); # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); xlog("L_ALERT","ALERT: line 492******************************** $rm from $fu (IP:$si:$sp)\n"); if (is_method("INVITE|SUBSCRIBE")) { xlog("L_ALERT","ALERT: line 494******************************** $rm from $fu (IP:$si:$sp)\n"); record_route(); } # account only INVITEs if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting } # dispatch requests to foreign domains route(SIPOUT); ### requests for my local domains # handle presence related requests route(PRESENCE); if ($rU==$null) { # request with no Username in RURI sl_send_reply("484","Address Incomplete"); exit; } # dispatch destinations to PSTN route(PSTN); # user location service route(LOCATION); } event_route[xhttp:request] { if ($hu != "/presence/") { xlog("L_INFO", "invalid request [$hu]"); xhttp_reply("404", "Not Found", "text/html", ""); return; } $var(call-id) = $(rb{json.parse,Call-ID}); xlog("L_INFO", "$var(call-id)|log|[$hu] payload $rb"); if ($(rb{json.parse,Event-Package}) == "dialog") { xlog("L_INFO", "$var(call-id)|log|received $(rb{json.parse,Event-Package}) update for $(rb{json.parse,From}) $rb"); pua_json_publish($rb); } xhttp_reply("200", "OK", "text/html", "$rb"); } # Wrapper for relaying requests route[RELAY] { # enable additional event routes for forwarded requests # - serial forking, RTP relaying handling, a.s.o. if (is_method("INVITE|BYE|SUBSCRIBE|UPDATE")) { if(!t_is_set("branch_route")) t_on_branch("MANAGE_BRANCH"); } if (is_method("INVITE|SUBSCRIBE|UPDATE")) { if(!t_is_set("onreply_route")) t_on_reply("MANAGE_REPLY"); } if (is_method("INVITE")) { if(!t_is_set("failure_route")) t_on_failure("MANAGE_FAILURE"); } if(is_method("INVITE|BYE|UPDATE|CANCEL|ACK")) { setflag(FLT_DLGINFO); dlg_manage(); } if (!t_relay()) { sl_reply_error(); } exit; } # Per SIP request initial checks route[REQINIT] { #!ifdef WITH_ANTIFLOOD # flood detection from same IP and traffic ban for a while # be sure you exclude checking trusted peers, such as pstn gateways # - local host excluded (e.g., loop to self) if(src_ip!=myself) { if($sht(ipban=>$si)!=$null) { # ip is already blocked xdbg("request from blocked IP - $rm from $fu (IP:$si:$sp)\n"); exit; } if (!pike_check_req()) { xlog("L_ALERT","ALERT: pike blocking $rm from $fu (IP:$si:$sp)\n"); $sht(ipban=>$si) = 1; exit; } } #!endif if($ua =~ "friendly-scanner|sipcli|VaxSIPUserAgent") { # silent drop for scanners - uncomment next line if want to reply # sl_send_reply("200", "OK"); exit; } if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } if(is_method("OPTIONS") && uri==myself && $rU==$null) { sl_send_reply("200","Keepalive"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } } # Handle requests within SIP dialogs route[WITHINDLG] { if (!has_totag()) return; # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { route(DLGURI); if (is_method("BYE")) { setflag(FLT_ACC); # do accounting ... setflag(FLT_ACCFAILED); # ... even if the transaction fails } else if ( is_method("ACK") ) { # ACK is forwarded statelessly route(NATMANAGE); } else if ( is_method("NOTIFY") ) { # Add Record-Route for in-dialog NOTIFY as per RFC 6665. record_route(); } route(RELAY); exit; } if (is_method("SUBSCRIBE") && uri == myself) { # in-dialog subscribe requests route(PRESENCE); exit; } if ( is_method("ACK") ) { if ( t_check_trans() ) { # no loose-route, but stateful ACK; # must be an ACK after a 487 # or e.g. 404 from upstream server route(RELAY); exit; } else { # ACK without matching transaction ... ignore and discard exit; } } sl_send_reply("404","Not here"); exit; } # Handle SIP registrations route[REGISTRAR] { if (!is_method("REGISTER")) return; if(isflagset(FLT_NATS)) { setbflag(FLB_NATB); #!ifdef WITH_NATSIPPING # do SIP NAT pinging setbflag(FLB_NATSIPPING); #!endif } if (!save("location")) { sl_reply_error(); } exit; } # User location service route[LOCATION] { #!ifdef WITH_SPEEDDIAL # search for short dialing - 2-digit extension if($rU=~"^[0-9][0-9]$") { if(sd_lookup("speed_dial")) { route(SIPOUT); } } #!endif #!ifdef WITH_ALIASDB # search in DB-based aliases if(alias_db_lookup("dbaliases")) { route(SIPOUT); } #!endif $avp(oexten) = $rU; if (!lookup("location")) { $var(rc) = $rc; route(TOVOICEMAIL); t_newtran(); switch ($var(rc)) { case -1: case -3: send_reply("404", "Not Found"); exit; case -2: send_reply("405", "Method Not Allowed"); exit; } } # when routing via usrloc, log the missed calls also if (is_method("INVITE")) { setflag(FLT_ACCMISSED); } route(RELAY); exit; } # Presence server processing route[PRESENCE] { if(!is_method("PUBLISH|SUBSCRIBE")) return; if(is_method("SUBSCRIBE") && $hdr(Event)=="message-summary") { route(TOVOICEMAIL); # returns here if no voicemail server is configured sl_send_reply("404", "No voicemail service"); exit; } #!ifdef WITH_PRESENCE if (!t_newtran()) { sl_reply_error(); exit; } if(is_method("PUBLISH")) { handle_publish(); t_release(); } else if(is_method("SUBSCRIBE")) { handle_subscribe(); t_release(); } exit; #!endif # if presence enabled, this part will not be executed if (is_method("PUBLISH") || $rU==$null) { sl_send_reply("404", "Not here"); exit; } return; } # IP authorization and user authentication route[AUTH] { #!ifdef WITH_AUTH #!ifdef WITH_IPAUTH if((!is_method("REGISTER")) && allow_source_address()) { # source IP allowed return; } #!endif if (is_method("REGISTER") || from_uri==myself) { # authenticate requests if (!auth_check("$fd", "subscriber", "1")) { auth_challenge("$fd", "0"); exit; } # user authenticated - remove auth header if(!is_method("REGISTER|PUBLISH")) consume_credentials(); } # if caller is not local subscriber, then check if it calls # a local destination, otherwise deny, not an open relay here if (from_uri!=myself && uri!=myself) { sl_send_reply("403","Not relaying"); exit; } #!else # authentication not enabled - do not relay at all to foreign networks if(uri!=myself) { sl_send_reply("403","Not relaying"); exit; } #!endif return; } # Caller NAT detection route[NATDETECT] { #!ifdef WITH_NAT force_rport(); if (nat_uac_test("19")) { if (is_method("REGISTER")) { fix_nated_register(); } else { if(is_first_hop()) { set_contact_alias(); } } setflag(FLT_NATS); } #!endif return; } # RTPProxy control and signaling updates for NAT traversal route[NATMANAGE] { xlog("ALERT:NATMANAGE********************* (IP:$si:$sp)\n(DEST:$du @ $di:$dp)\n"); ; #!ifdef WITH_NAT if (is_request()) { if(has_totag()) { if(check_route_param("nat=yes")) { setbflag(FLB_NATB); } } } if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB))) return; if(nat_uac_test("8")) { rtpproxy_manage("co"); } else { rtpproxy_manage("corwie"); } if (is_request()) { if (!has_totag()) { if(t_is_branch_route()) { add_rr_param(";nat=yes"); } } } if (is_reply()) { if(isbflagset(FLB_NATB)) { if(is_first_hop()) set_contact_alias(); } } #!endif return; } # URI update for dialog requests route[DLGURI] { #!ifdef WITH_NAT if(!isdsturiset()) { handle_ruri_alias(); } #!endif return; } # Routing to foreign domains # Routing to foreign domains route[SIPOUT] { xlog("ALERT: SIPOUT (IP:$si:$sp)\n(DEST:$du @ $di:$dp)\n"); ; if (uri==myself) return; append_hf("P-hint: outbound\r\n"); route(RELAY); exit; } route[TOAST] { rewritehostport("45.33.xx.xx:5060"); $fu = "sip:7028743833@62.151.182.83:5012"; append_hf("P-hint: outbound\r\n"); route(RELAY); exit; } # PSTN GW routing route[PSTN] { #!ifdef WITH_PSTN # check if PSTN GW IP is defined if (strempty($sel(cfg_get.pstn.gw_ip))) { xlog("SCRIPT: PSTN routing enabled but pstn.gw_ip not defined\n"); return; } # route to PSTN dialed numbers starting with '+' or '00' # (international format) # - update the condition to match your dialing rules for PSTN routing if(!($rU=~"^(\+|00)[1-9][0-9]{3,20}$")) return; # only local users allowed to call if(from_uri!=myself) { sl_send_reply("403", "Not Allowed"); exit; } if (strempty($sel(cfg_get.pstn.gw_port))) { $ru = "sip:" + $rU + "@" + $sel(cfg_get.pstn.gw_ip); } else { $ru = "sip:" + $rU + "@" + $sel(cfg_get.pstn.gw_ip) + ":" + $sel(cfg_get.pstn.gw_port); } route(RELAY); exit; #!endif return; } # XMLRPC routing #!ifdef WITH_XMLRPC route[XMLRPC] { # allow XMLRPC from localhost if ((method=="POST" || method=="GET") && (src_ip==127.0.0.1)) { # close connection only for xmlrpclib user agents (there is a bug in # xmlrpclib: it waits for EOF before interpreting the response). if ($hdr(User-Agent) =~ "xmlrpclib") set_reply_close(); set_reply_no_connect(); dispatch_rpc(); exit; } send_reply("403", "Forbidden"); exit; } #!endif # Routing to voicemail server route[TOVOICEMAIL] { #!ifdef WITH_VOICEMAIL if(!is_method("INVITE|SUBSCRIBE")) return; # check if VoiceMail server IP is defined if (strempty($sel(cfg_get.voicemail.srv_ip))) { xlog("SCRIPT: VoiceMail routing enabled but IP not defined\n"); return; } if(is_method("INVITE")) { if($avp(oexten)==$null) return; $ru = "sip:" + $avp(oexten) + "@" + $sel(cfg_get.voicemail.srv_ip) + ":" + $sel(cfg_get.voicemail.srv_port); } else { if($rU==$null) return; $ru = "sip:" + $rU + "@" + $sel(cfg_get.voicemail.srv_ip) + ":" + $sel(cfg_get.voicemail.srv_port); } route(RELAY); exit; #!endif return; } # Manage outgoing branches branch_route[MANAGE_BRANCH] { xdbg("new branch [$T_branch_idx] to $ru\n"); route(NATMANAGE); } # Manage incoming replies onreply_route[MANAGE_REPLY] { xdbg("incoming reply\n"); if(status=~"[12][0-9][0-9]") { route(NATMANAGE); } } # Manage failure routing cases failure_route[MANAGE_FAILURE] { route(NATMANAGE); if (t_is_canceled()) exit; #!ifdef WITH_BLOCK3XX # block call redirect based on 3xx replies. if (t_check_status("3[0-9][0-9]")) { t_reply("404","Not found"); exit; } #!endif #!ifdef WITH_BLOCK401407 # block call redirect based on 401, 407 replies. if (t_check_status("401|407")) { t_reply("404","Not found"); exit; } #!endif #!ifdef WITH_VOICEMAIL # serial forking # - route to voicemail on busy or no answer (timeout) if (t_check_status("486|408")) { $du = $null; route(TOVOICEMAIL); exit; } #!endif }

2 2

Kamailio IMS setup - user online - unable to call
by Jack R 12 Sep '19

12 Sep '19

Hi All, We have installed Kamailio as IMS setup pcscf icscf scscf - 3 instances running on Ubuntu.. Users alice and bob are online however unable to call. When we check the logs the FHoSS is hunting for values in sh_subscription table for alice / bob user. Can you please share: 1. A sample database table values to be inserted across all tables in FHoSS helpful for the call and 2, Maybe, if possible, some description to understand table structures/ importance of fields of FHoSS. Thanks and Regards, Jack.

2 1

Help with "routines:ssl3_read_bytes:sslv3 alert bad certificate" kamailio TLS error
by david＠aslo.us 12 Sep '19

12 Sep '19

Hello everyone, I am trying to configure TLS in kamailio (5.2.4) following this guide: [ http://www.kamailio.org/dokuwiki/doku.php/tls:create-certificates ]( http://www.kamailio.org/dokuwiki/doku.php/tls:create-certificates ) Modules: #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_PRESENCE #!define WITH_ALIASDB #!define WITH_IMC #!define WITH_TLS When i try to connect via command line, this is the result (just including relevant parts): $ openssl s_client -connect 192.X.X.X:5061 -tls1 CONNECTED(00000003) depth=1 C = XX, ST = XXXX, L = XXXXXX, O = XXX CA, CN = XXX CA verify error:num=19:self signed certificate in certificate chain verify return:0 --- No client certificate CA names sent --- SSL handshake has read 2550 bytes and written 336 bytes --- --- Start Time: 1567787935 Timeout : 7200 (sec) Verify return code: 19 (self signed certificate in certificate chain) --- read:errno=0 Now, when I setup my clients, they connect to the server, but they can't send messages or make calls. This is the TLS startup LOG: Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_mod.c:372]: mod_init(): With ECDH-Support! Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_mod.c:375]: mod_init(): With Diffie Hellman Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: CRITICAL: tls [tls_init.c:671]: init_tls_h(): installed openssl library version is too different from the library the kamailio tls module was compiled with: installed "OpenSSL 1.1.1 11 Sep 2018" (0x1010100f), compiled "OpenSSL 1.1.0k 28 May 2019" (0x101000bf).#012 Please make sure a compatible version is used (tls_force_run in kamailio.cfg will override this check) Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: WARNING: tls [tls_init.c:680]: init_tls_h(): tls_force_run turned on, ignoring openssl version mismatch Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: WARNING: tls [tls_init.c:778]: init_tls_h(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 12582912 and 6291456 bytes Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: <core> [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold1 has been changed to 12582912 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: <core> [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold2 has been changed to 6291456 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: <core> [main.c:2669]: main(): processes (at least): 24 - shm size: 67108864 - pkg size: 8388608 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:303]: ksr_tls_fill_missing(): TLSs<default>: tls_method=12 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:315]: ksr_tls_fill_missing(): TLSs<default>: certificate='/etc/certs/192.X.X.X/cert.pem' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:322]: ksr_tls_fill_missing(): TLSs<default>: ca_list='/etc/certs/demoCA/cert.pem' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:329]: ksr_tls_fill_missing(): TLSs<default>: crl='(null)' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:333]: ksr_tls_fill_missing(): TLSs<default>: require_certificate=0 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:340]: ksr_tls_fill_missing(): TLSs<default>: cipher_list='(null)' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:347]: ksr_tls_fill_missing(): TLSs<default>: private_key='/etc/certs/192.X.X.X/key.pem' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:351]: ksr_tls_fill_missing(): TLSs<default>: verify_certificate=0 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:354]: ksr_tls_fill_missing(): TLSs<default>: verify_depth=9 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: NOTICE: tls [tls_domain.c:1087]: ksr_tls_fix_domain(): registered server_name callback handler for socket [:0], server_name='<default>' ... Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:707]: set_verification(): TLSs<default>: No client certificate required and no checks performed Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:303]: ksr_tls_fill_missing(): TLSc<default>: tls_method=12 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:315]: ksr_tls_fill_missing(): TLSc<default>: certificate='(null)' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:322]: ksr_tls_fill_missing(): TLSc<default>: ca_list='(null)' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:329]: ksr_tls_fill_missing(): TLSc<default>: crl='(null)' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:333]: ksr_tls_fill_missing(): TLSc<default>: require_certificate=0 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:340]: ksr_tls_fill_missing(): TLSc<default>: cipher_list='(null)' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:347]: ksr_tls_fill_missing(): TLSc<default>: private_key='(null)' Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:351]: ksr_tls_fill_missing(): TLSc<default>: verify_certificate=0 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:354]: ksr_tls_fill_missing(): TLSc<default>: verify_depth=9 Sep 6 16:41:57 aslo-kamailio /usr/sbin/kamailio[5845]: INFO: tls [tls_domain.c:710]: set_verification(): TLSc<default>: Server MAY present invalid certificate Sep 6 16:41:58 aslo-kamailio /usr/sbin/kamailio[5862]: INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/5862 Sep 6 16:41:58 aslo-kamailio /usr/sbin/kamailio[5866]: INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) This is my tls.cfg file: [server:default] method = TLSv1 verify_certificate = no require_certificate = no private_key = /etc/certs/192.X.X.X/key.pem certificate = /etc/certs/192.X.X.X/cert.pem ca_list = /etc/certs/demoCA/cert.pem #crl = /etc/kamailio/tls/crl.pem # --- # This is the default client domain profile. # Settings in this domain will be used for all outgoing # TLS connections that do not match any other # client domain in this configuration file. # We require that servers present valid certificate. # [client:default] method = TLSv1 verify_certificate = no require_certificate = no These are the relevant parts of my kamailio.cfg: # alias="sip.mydomain.com" alias=192.X.X.X:5060 alias=192.X.X.X:5061 /* uncomment and configure the following line if you want Kamailio to * bind on a specific interface/port/proto (default bind on all available) */ listen=udp:192.X.X.X:5060 listen=tcp:192.X.X.X:5060 listen=tls:192.X.X.X:5061 #!ifdef WITH_TLS enable_tls=yes /* upper limit for TLS connections */ tls_max_connections=2048 #!endif #!ifdef WITH_TLS # ----- tls params ----- modparam("tls", "config", "/etc/kamailio/tls.cfg") modparam("tls", "tls_force_run", 1) #!endif These are the errors that show up everytime i try to connect with a client: Sep 6 16:53:42 aslo-kamailio /usr/sbin/kamailio[5870]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate Sep 6 16:53:42 aslo-kamailio /usr/sbin/kamailio[5870]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f7c4e3ddd00 r: 0x7f7c4e3ddd80 (-1) Sep 6 16:53:43 aslo-kamailio /usr/sbin/kamailio[5874]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate Sep 6 16:53:43 aslo-kamailio /usr/sbin/kamailio[5874]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f7c4e3ddd00 r: 0x7f7c4e3ddd80 (-1) Sep 6 16:53:44 aslo-kamailio /usr/sbin/kamailio[5875]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate Sep 6 16:53:44 aslo-kamailio /usr/sbin/kamailio[5875]: ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f7c4e3ddd00 r: 0x7f7c4e3ddd80 (-1) Any help would be greatly appreciated. Regards.

2 1

Kamailio status get Active (Exited)
by Gaurav Bmotra 11 Sep '19

11 Sep '19

hi i m using kamailio 5.1, with -m 512 -M 8 it stop registering user SIP anf in status it shows ------------------------------ ● kamailio.service - LSB: Start the Kamailio SIP proxy server Loaded: loaded (/etc/init.d/kamailio; generated) Active: active (exited) since Sat 2019-09-07 11:05:16 UTC; 3 days ago Docs: man:systemd-sysv-generator(8) Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17708]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17677]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17714]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17685]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17681]: {1 1094155754 NOTIFY TwGwmzx4wINnraJs1Gh3Kg..} INFO: <core> [main.c:819]: sig_usr(): s… received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17704]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17689]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17693]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17691]: INFO: <core> [main.c:819]: sig_usr(): signal 15 received Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17674]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized Hint: Some lines were ellipsized, use -l to show in full. --------------------------------------------------------------------- plz help thank you -- *Regards:* Gaurav Kumar

2 1

Can't connect to db
by Andrew Chen 10 Sep '19

10 Sep '19

Hi all, I just installed kamailio 5.2.4 on two separate aws instances in two separate regions. Both regions uses the same configuration template and share the same db in AWS RDS. The issue I see is this: - SJO location was able to launch fine without any issues. - ASH location could not start up kamailio process due to db connection failure: Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8043]: ERROR: db_mysql [km_my_con.c:139]: db_mysql_new_connection(): driver error: Too many connections Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8043]: ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: db_mysql [km_my_con.c:139]: db_mysql_new_connection(): driver error: Too many connections Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: carrierroute [db_carrierroute.c:141]: carrierroute_db_open(): can't connect to database. Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: <core> [core/sr_module.c:847]: init_mod_child(): error while initializing module carrierroute (/usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so) (idx: 30 rank: 18 desc: [tcp receiver (generic) child=9]) - In ASH instance, I can manually mysql to the RDS host using the credentials in the config file. - I checked db user permissions and it's opened for the subnet in our ASH location (which is also proven using manual connection). So I don't get why one works and the other doesn't Thoughts? -- Andy Chen Sr. Telephony Lead Engineer -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

2 2

LCR lcr_id short or int?
by Grant Bagdasarian 10 Sep '19

10 Sep '19

Hello, The database tables definition for 5.2.x mentions the lcr_id parameter being of unsigned short type, while in the code I only see definitions of type int. Is it safe to assume the parameter is of type int, so the database column can also be set to an integer type? Regards, Grant

2 7

Share variable into reply route.
by Zhan Bazarov 09 Sep '19

09 Sep '19

Hello, we ran into a trouble with sharing variable into reply route... We are going to match asterisk's uniqueid with rtpengine records like this: route[from_asterisk]{ $var(UniqueId)=$hdr(X-UniqueId); $var(rtp_flags) = $var(rtp_flags) + " label={uid:$var(UniqueId),stream:outgoing} record-call=on"; rtpengine_manage($var(rtp_flags)); } reply_route[from_pstn]{ rtpengine_manage("replace-origin replace-session-connection ICE=remove RTP/AVP rtcp-mux-demux label={uid:$var(UniqueId),stream:outgoing"); } and it doesn't work... The one possible way what we found its using $shv instead of $var... But its unsecure way, cuz it may confus our bussines logic... Do you have any idea how to implement this? Many thanks!

3 2

How to install kamailio symbols for debugging
by YASIN CANER 09 Sep '19

09 Sep '19

Hello, I want to debug kamailio with gdb or try to get core.dump file but i failed. GDB wants to kamailio symbols. How to install them? on Ubuntu - raspberry PI Best regards. Yasin CANER

4 3

Error Users - 604 Does not exist anywhere - HSS User Unknown
by Jack R 08 Sep '19

08 Sep '19

Hi, We have installed Kamailio as IMS setup pcscf icscf scscf - 3 instances running on Ubuntu.. 1. 2 Sip client registers successfully (shows Online) as 'bob(a)net1.test' and 'alice(a)net1.test' 2. When we check server logs: Invite request shows 'bob@IP address' i.e. ' bob(a)10.0.0.10' 3. However, in HSS it is registered as 'bob(a)net1.test'. 4. When the request from SCSCF goes to ISCSF it gives Error: Users - 604 Does not exist anywhere - HSS User Unknown. As it compares 'bob(a)10.0.0.10' with 'bob(a)net1.test'. Please help and advise how everywhere (SCSCF, PCSCF) during query/comparisons it can take 'bob(a)net1.test' and not 'bob(a)10.0.0.10' Thanks and Regards, Jack.

1 1

Kamailio - PfSense Firewall - inbound/outbound rules
by Youssef Boujraf 06 Sep '19

06 Sep '19

Dear All, I am evaluating the kamailio proxy 5.2 server with rtpproxy on an internal network. Everything are ok. Now, I would like to evalute Kamailio proxy from outside (internet) but I have some difficulties to setup my PfSense firewall to enable inbound & outbound rules, network settings and kamailio.cfg. The issues are : Setup correctly Network files : * /etc/hostname 127.0.0.1 localhost ip_private codecsip.mydomain codecsip ip_public codecsip.mydomain codecsip * /etc/hosts file codesip * dns * /etc/resolv.conf nameserver 8.8.8.8Setup /etc/kamailio/kamailio.cfg :#!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_NAT #!define WITH_TLS /* uncomment the next line to disable the auto discovery of local aliases based on reverse DNS on IPs (default on) */ #auto_aliases=no /* add local domain aliases */ alias="codecsip.mydomain" #!ifdef WITH_NAT # ----- rtpproxy params ----- # modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722") modparam("rtpproxy", "rtpproxy_sock", "unix:/var/run/rtpproxy/rtpproxy.sock") Setup etc/default/rtpproxy : CONTROL_SOCK=udp:127.0.0.1:7722 EXTRA_OPTS="-l <IP-address>" Where <IP-address> is the external IP address of your host. Regarding the firewall rules, it will be great to identify which rules I need to create : Inbound and outbound rules and NAT 1:1 ? If anyone have any information it could be great Best regards, Youssef

2 1

Kamailio HA
by Christian Attanasio 06 Sep '19

06 Sep '19

Hi everyone I use kamailio 5.1 with rtpengine and I would like to set up a simple warm standby or hot standby system for my sip server. on the web I found various discussions and posts that led me to deepen them the dispatcher, dmq, dmq_usrloc, db_cluster and p_usrloc modules. now, though, I'm a little confused: what approach do you recommend for this system? I thought of using two identical servers: Kam01 10.10.10.2 Kam02 10.10.10.3 Hostname cluster.mydomain.com each with its own mariadb and implementing data replication (with the dmq module? Or db_cluster and sqlops?). in this scenario is it necessary to also use the dispatcher module or implement a high available system with keepalives and floating ip? thanks, Christian

1 0

Kamalio & Asterisk integration erroneous behavior, setup issue
by Aristeidis Tsitras 05 Sep '19

05 Sep '19

new to the area and trying to setup Kamailio with Asterisk in a single machine. All users will register to Kamailio's port and in case of need for media, it will be forwarded to Asterisk, that is my intention. All of my work is based on the following link https://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb. Here is what i have done: - Debian 8, 64 bit machine with mysql and odbc - *root@kamast: ~ $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.11 (jessie) Release: 8.11 Codename: jessie root@kamast: ~ $ uname -a Linux kamast 3.16.0-10-amd64 #1 SMP Debian 3.16.72-1 (2019-08-13) x86_64 GNU/Linux root@kamast: ~ $ * - Kamailio 5.2 installed from Kamailio's deb repository - Asterisk 13LTS installed from source - Used the same passwords such as kamailiorw and asterisk_password, since this is a test system, for proof of concept. I did import to the mysql>asterisk database 3 users 2200, 2201 and 2202. Then created in sip.conf the same 3 users with the same credentials. Then on 3 PCs i used softphones (Jitsi, Zoiper) and registered each account to a softphone. Problems: - Cannot see the users in the Asterisk's cli, sip show peers - I can see users only in Kamailio with kamctl ul show - A call between the extensions goes to voicemail. It never reaches the other destination eg 2200 calls 2201 and in Asterisk's console i am getting a message that 2201 is absent and it goes to voicemail. The same with any other extension. Attached you can find: 1. Kamailio.cfg 2. Asterisk's sip.conf 3. Asterisk's extension.conf 4. The import that i have done to mysql for the user creation. I would appreciate if someone could point me to the error and help me fix it please?

3 7

$Au being set to $fu instead of $fU
by Joel Serrano 05 Sep '19

05 Sep '19

Hi, Testing on latest master deb nightly build from last night I've noticed that when $au is not available, $Au is being set to $fu (uri) instead of $fU (username). Docs: https://www.kamailio.org/wiki/cookbooks/devel/pseudovariables ... $Au - Acc username: username for accounting purposes. It's a selective pseudo variable (inherited from acc module). It returns auth username ($au) if exists or From username ($fU) otherwise. ... I have the following log in several places in a test box: xlog("L_NOTICE", "[DEBUG] Au=$Au au=$au aU=$aU fU=$fU fu=$fu - \n"); And when I run through them (on both request and reply routes) I get the following: Aug 8 14:37:43 csbc01 csbc[9478]: NOTICE: {1 21564 REGISTER d8df9be1-1702e20b(a)A.B.C.D} <script>: [DEBUG] Au=1002366(a)some.domain au=<null> aU=<null> fU=1002366 fu=sip:1002366@some.domain - Aug 8 14:37:43 csbc01 csbc[9479]: NOTICE: {1 21565 REGISTER d8df9be1-1702e20b(a)A.B.C.D} <script>: [DEBUG] Au=1002366(a)some.domain au=1002366 aU=1002366 fU=1002366 fu=sip:1002366@some.domain - Aug 8 14:37:43 csbc01 csbc[9484]: NOTICE: {2 21565 REGISTER d8df9be1-1702e20b(a)A.B.C.D} <script>: [DEBUG] Au=1002366(a)some.domain au=<null> aU=<null> fU=1002366 fu=sip:1002366@some.domain - Those 3 logs belong to the same flow from different places in the config script. I would expect $Au to never have a "@some.domain" in it, so I assume in some place the replacement is not being done with $fU but with $fu. @Devs: I'm happy to create a GH issue for tracking etc if required, please let me know! Cheers, Joel.

2 3

How to detect miss call and accomplished call
by Anuran Barman 05 Sep '19

05 Sep '19

Hi, I want to show call logs in my SIP app. How can I do this with Kamailio? I want to do it from the *kamailio.cfg *file. Is it possible to do it from where? I guess Dialog module should be used for this, but can not figure out how to do it. I want minimalist feature like who call whom with timestamp, thats all. How can I do this?

3 9

Kamailio-IMS system
by Hạnh Nguyễn 05 Sep '19

05 Sep '19

Dear Mrs/Mss, I am Hanh, I am from Viet Nam. I am writting this email because I have an issue when I download The log-file and the config-files on website https://www.kamailio.org/w/2016/02/kamailio-ims-getting-started-box/. When I click on https://www.dropbox.com/s/ehkzi9pbhlp7njc/Kamailio-IMS%20config-files.zip?d… to download The log-file which I really need on this time, the page displays 404 Error - Link not found. So I can not download. I hope I will receive a new link from you soon. I look forward to hearing from you. Sincerely, Hanh Nguyen

2 1

Planning the next major release - v5.3.0
by Daniel-Constantin Mierla 04 Sep '19

04 Sep '19

Hello, it's about the time to set the milestones to the next major release - v5.3.0. There are 6 new modules and many other enhancements to existing components in git master branch, also during the last irc devel meeting it was proposed to freeze after summer holidays. At this moment I would propose Wednesday, September 4, 2019 to freeze the development. Then the release should be about one month later, after testing interval. In case there are people willing a bit more time for development, we can freeze one week later, September 11, or another date -- your suggestions here. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

3 5

Using Kamailio IMS for making a call
by supreeth herle 04 Sep '19

04 Sep '19

Hello Everyone, I have successfully setup a VM in OpenStack with Kamailio IMS, rtpengine and FoHSS using the instructions mentioned in the guide which i wrote (attached to this mail), all running in the machine. I am using the existing alice and bob IMPUs created in FoHSS. But, when I try to call each other the call doesnt go through and I observe in the wireshark traces that S-CSCF is replying to I-CSCF that "403, Forbidden - Domain not served". Can somebody please tell me do I need any additional components to make a call or am i missing some configuration? It would be great if someone can help me troubleshooting this issue. I have attached the pcap file for your reference. Many thanks in advance. Regards, Supreeth

1 0

Kamailio stops processing requests over UDP
by Juha Heinanen 04 Sep '19

04 Sep '19

I'm returning to an old issue, where Kamailio stops processing incoming requests. Now it turned out that only requests over UDP are not processed. Requests over TCP work fine. Debug log doesn't show anything about the requests over UDP, but wireshark sees them coming. core.ps shows that main process - attendant and all udp receiver processes are alive. Any ideas what could cause Kamailio (5.2 version) to stop processing requests over UDP? What additional info should I try to get? -- Juha

4 21

Hello Group - I have a "challenge"
by Kevin Greene 04 Sep '19

04 Sep '19

I recently did the upgrade from v4.4 to 5.2 (via Yum). When starting Kamailio, I get these three errors. Not sure if they are related or not but I do not think so. Have spent a lot of time searching on Google for the answer and have not found the solution. [root@ids kamailio]# kamctl restart INFO: Stopping Kamailio : INFO: stopped INFO: Starting Kamailio : INFO: started (pid: 44608) [root@ids kamailio]# tail -f /var/log/sipserver.log Sep 4 00:39:06 ids /usr/sbin/kamailio[44608]: ERROR: <core> [core/pvapi.c:1119]: pv_parse_spec2(): wrong char [t/116] in [$mt] at [2 (0)] Sep 4 00:39:06 ids /usr/sbin/kamailio[44608]: ERROR: <core> [core/dprint.c:451]: log_prefix_init(): wrong format[{$mt $hdr(CSeq) $ci} ] Sep 4 00:39:06 ids /usr/sbin/kamailio[44626]: ERROR: <core> [core/receive.c:319]: receive_msg(): no request_route {...} and no other config routing engine registered The last error is repeated many times (each time a remote user tries to connect I think). I can send any additional files if needed. Thanks. I am burning out on this upgrade. Kevin

2 1

Unexpected BYEs from dialog module
by Alex Balashov 03 Sep '19

03 Sep '19

Hi, I am running 4.3.5:1b0c0a, which I am aware is an EOL'd release train, and have a problem with the dialog module I am baffled by. On many calls - I can't find any correlation to particular kinds of endpoints - I see spoofed BYEs come out of Kamailio after a minute and a half, as if the call had hit a dialog timeout or the dialog module's dead peer detection (OPTIONS pinging) kicked it out. The thing is, neither of those explanations seem to be borne out by the parameters of the calls under investigation. The dialog timeout on these calls is set to 7200, and the dialog keepalives aren't enabled in either direction. If they were, it'd be logged. Calls that are terminated in this manner also see the following log message: WARNING: dialog [dlg_req_within.c:214]: bye_reply_cb(): inconsitent dlg timer data on dlg 0x7f9997317e48 [3390:9644] with clid '1996679936_133218050(a)x.x.x.x' and tags '2bb17663-co4006-INS001' 'as7925780d' But I don't think this is unusual for a dialog-spoofed BYE; presumably this is due to a 200 OK for the BYE from both ends. So anyway, I am trying to track down anything else that could inadvertently cause dialog to hang up calls relatively quickly in that release, or inadvertently set the dialog timeout parameter to something lower than is apparent from the logging and the config. If anyone has any pointers, that would not go unappreciated! Many thanks, -- 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/

2 6

crash/mem leaks on low memory
by Gaurav Bmotra 03 Sep '19

03 Sep '19

hi i m using kamailio 5.1 on Ubuntu 18.04 i m geting this error in logs and it stop registration form soft-phone plz help me -------------------------------------------------------------------------------------------------------- WARNING: tls [tls_init.c:778]: init_tls_h(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory th -------------------------------------------------------------------------------------------------------- kamailio.service - LSB: Start the Kamailio SIP proxy server Loaded: loaded (/etc/init.d/kamailio; generated) Active: active (exited) since Tue 2019-09-03 12:09:19 UTC; 26min ago Docs: man:systemd-sysv-generator(8) Process: 27237 ExecStart=/etc/init.d/kamailio start (code=exited, status=0/SUCCESS) Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: <core> [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold2 has been changed to 7077888 Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: <core> [main.c:2636]: main(): processes (at least): 27 - shm size: 536870912 - pkg size: 8388608 Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: ERROR: dispatcher [dispatcher.c:813]: ds_warn_fixup(): failover functions used, but required AVP parameters are NULL -- feature disabled Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: <core> [core/udp_server.c:153]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: <core> [core/udp_server.c:205]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: ERROR: <core> [core/tcp_main.c:2850]: tcp_init(): bind(c, 0x7f0b41b001f4, 16) on 172.31.35.49:5091 : Address already in use Sep 03 12:09:18 talk /usr/local/sbin/kamailio[27270]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized -- thank you *Regards:* Gaurav Kumar

3 3

evapi mismatch version
by bill＠novatrope.us 02 Sep '19

02 Sep '19

Hi All Installed Kam 5.2.4, but now getting version mismatch on evapi. ERROR: <core> [core/sr_module.c:348]: version_control(): module version mismatch for /usr/lib64/kamailio/modules/evapi.so; core: kamailio 5.2.4 (x86_64/linux); module: kamailio 5.1.6 (x86_64/linux) Anybody know how to get the correct evapi version. I am running centos 7 Bill

3 2

Issue with uac_replace
by David Costa 01 Sep '19

01 Sep '19

Greetings, I have a Kamailio proxy with uac_replace for To and From Headers. So far everything has worked correctly. However, I now have a client who encodes my Calling Number too and I'm getting some issues in the restore mechanics. I have the restore setup as "auto" and it's info is stored in "vsf" and "vst" parameters of Record-Route. On replies sent by my client I have the following Record-Route and From Header (Note : My Kamailio has two IPs which makes it insert two RR headers ): Record-Route: <sip:xxx.xxx.xxx.xxx;r2=on;lr;ftag=99A730303736313103579CC4;tbk_i=1_2_Y;tbk_ o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJDndyAwMcHwIdHQsWHwUDNw--;vst=AAAAABgGBAMH DQgJDQECA3RyAwMcHwIdGgQeHAIFAnVzZXI9cGhvbmU-;did=f74.78e2> Record-Route: <sip:xxx.xxx.xxx.xxx;r2=on;lr;ftag=99A730303736313103579CC4;tbk_i=1_2_Y;tbk_ o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJDndyAwMcHwIdHQsWHwUDNw--;vst=AAAAABgGBAMH DQgJDQECA3RyAwMcHwIdGgQeHAIFAnVzZXI9cGhvbmU-;did=f74.78e2> From: "+351411110097" <sip:I2116446I_500@xxx.xxx.xxx.xxx>;tag=99A730303736313103579CC4 In this case the restore is done correctly When the client sends me a BYE request I have the following Route Header and To Header Route : <sip:xxx.xxx.xxx.xxx;r2=on;lr;ftag=99A730303736313103579CC4;tbk_i=1_2_Y;tbk_ o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJDndyAwMcHwIdHQsWHwUDNw--;vst=AAAAABgGBAMH DQgJDQECA3RyAwMcHwIdGgQeHAIFAnVzZXI9cGhvbmU-;did=f74.78e2>,<sip:xxx.xxx.xxx. xxx;r2=on;lr;ftag=99A730303736313103579CC4;tbk_i=1_2_Y;tbk_o=128_11_Y;vsf=AA AAABgGBAMDAAUBBQAJDndyAwMcHwIdHQsWHwUDNw--;vst=AAAAABgGBAMHDQgJDQECA3RyAwMcH wIdGgQeHAIFAnVzZXI9cGhvbmU-;did=f74.78e2> To : "+351411110097" <sip:I2116446I_500@xxx.xxx.xxx.xxx>;tag=99A730303736313103579CC4 In this scenario, the To after restore is : To :"+351411110097" <sip:Q4525417L_<>Gxxx.xxx.xxx.xxx>;tag=99A730303736313103579CC4, which throws an internal error on Kamailio about bad URI and also makes our MediaGateway reply with a "Bad Request". Can this error be caused by the restore of the uac_replace mechanics? Both Record Route URIs are on different headers while the both Route URIs are on the same Route header. Can this be the reason? If you need more information please let me know. Best Regards David Costa

2 1

Re: [SR-Users] controlling presence with new module `pua_json`
by Henning Westerholt 30 Aug '19

30 Aug '19

Hello Bill, (please keep the list in CC) yes, this seems to be the case. Just looked briefly to the code, it does an assignment in some cases. E.g. if no Presentity* data is given it will just use the From* information. And then it should later output an error from pua_json_update_presentity(..) if there is not the necessary data. Do you see any error message like this? Another idea - does it works if you add more "missing" data in the curl requests? Cheers, Henning Am 28.08.19 um 21:16 schrieb bill(a)novatrope.us: > Henning: Good point. > > I do see a number of errors in the log. It looks like the json routine > is looking for data that is not in the http query as specified by the > author. > > > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > Event-Name: [update] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > Event-Package: [dialog] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [Presentity] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > Presentity: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [Presentity-User] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > Presentity-User: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [Presentity-Realm] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > Presentity-Realm: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): From: > [sip:1020101@<IP of phone>] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > From-User: [1020101] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > From-Realm: [<IP of phone>] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [From-URI] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > From-URI: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): To: > [sip:1020108@<IP of server>:50060] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > To-User: [1020108] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [To-URI] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): To-URI: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > Call-ID: [1020101@<IP of phone>] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [From-Tag] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > From-Tag: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [To-Tag] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): To-Tag: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): Json-c > error - failed to extract field [Direction] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): > Direction: [] > 17(125579) DEBUG: json [json_mod.c:70]: _json_extract_field(): State: > [Confirmed] > 17(125579) DEBUG: presence [event_list.c:348]: search_event(): start > event= [dialog/5] > > On 8/28/19 12:00 PM, Henning Westerholt wrote: >> Hello Bill, >> >> just giving some generic debug pointers here: >> >> - do you see any errors in the kamailio log file? >> >> - do you see any SIP traffic (e.g. by observing with ngrep, wireshark >> etc..) to the phone after your curl command? >> >> Cheers, >> >> Henning >> >> Am 28.08.19 um 19:04 schrieb bill(a)novatrope.us: >>> Hi all: >>> >>> I am trying to use the procedure for setting BLF lights described in >>> https://blog.voipxswitch.com/2018/02/22/kamailio-controlling-presence-with-… >>> >>> >>> WIthout success. >>> >>> My configuration is 1 Grandstream GXP2130 phone behind a NAT on a >>> public IP. (IPP in example below) >>> >>> Kamailio is running on public IP (IPK in example) listening on port >>> 50060 >>> >>> The command I am sending: >>> >>> curl -d >>> '{"Call-ID":"1020101@<IPP>","Event-Category":"presence","Event-Name":"update","Event-Package":"dialog","Expires":"3600","To":"sip:1020108@<IPK>:50060","To-User":"1020108","To-Realm":"<IPK>:50060","From":"sip:1020101@<IPP>","From-User":"1020101","From-Realm":"<IPP>","State":"Confirmed"}' >>> >>> http://localhost:8080/presence/ >>> {"Call-ID":"1020101@<IPP>","Event-Category":"presence","Event-Name":"update","Event-Package":"dialog","Expires":"3600","To":"sip:1020108@<IPK>:50060","To-User":"1020108","To-Realm":"<IPK>:50060","From":"sip:1020101@<IPP>","From-User":"1020101","From-Realm":"<IPP>","State":"Confirmed"} >>> >>> >>> >>> >>> Kamailio appears to be processing the command OK, so I think I am just >>> not setting it up properly> >>> >>> Anybody having any luck with this procedure, let me know how you are >>> getting it to work. >>> >>> >>> Bill >>> >>> >>> >>> _______________________________________________ >>> Kamailio (SER) - Users Mailing List >>> sr-users(a)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

2 1

Info: Upgrading kamcli to work with Python3
by Daniel-Constantin Mierla 30 Aug '19

30 Aug '19

Hello, with the perspective that Python2 is going to be removed from the major Linux distributes starting with the beginning of next year, the work to upgrade kamcli to run with Python3 has been started. >From now on, master branch of kamcli is expected to work only with Python3: * https://github.com/kamailio/kamcli There is still work to be done to upgrade all the code, but any use of it should be done with Python3 and eventual issues to be filed on bug tracker. Of course, pull requests are welcome as always! Who wants to use the version for Python2 has to use the code from git branch v1.2-python2. That branch is probably not going to receive any new feature, it will be kept for use with older systems (as well as a running option during the upgrade period to Python3). Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 0

IMC module not sending messages to members of a conference room
by david＠aslo.us 29 Aug '19

29 Aug '19

2 1

Kamailio 5.0.8 | authentification issue only with TCP/TLS
by Laurent Schweizer 29 Aug '19

29 Aug '19

Dear all, I have a kamailio running in version 5.0.8 and since fee weeks we have an issue with different users connected in TCP or TLS, sometimes authorization like for REGISTER are rejected and after a moment (can be few minute or hours) it work again and of course no change was done in the password .... We see this issue with different device, snom swyx, ... and on UDP we have no issue. I can see that when the Register is rejected it's with the error -2, so wrong password... # Authentication route route[AUTH] { if (is_method("REGISTER")) { # authenticate requests if (!auth_check("$fd", "subscriber", "1")) { switch($retcode) { case -1: sl_send_reply("503","Service not available"); exit; case -2: xlog("L_WARN", "auth error -2 username $au - src ip: $si \n"); auth_challenge("$fd", "0"); exit; I have attached an example of a trace where we can see a first REGISTER accepted and less than 2 minutes after a new one is rejected. ( in between they is a REGISTER without any Authorization header) Any idea ? BR Laurent

2 3

Connect Kamailio to ITSPs?
by Aingaran Thirunadarajah 29 Aug '19

29 Aug '19

Hello, Newbie here! Have Kamailio set up on a 512MB VPS. Created a couple of users, registered with Zoiper and can call between them. I am looking for documentation to connect the server to other VoIP providers (Signalwire, Anveo, VOIP.ms etc.) to make & receive calls from the external network (DIDs) / PSTN Can someone point me in the right direction? Thanks in advance.

2 1

Define properly IP in record-route header
by przeqpiciel 29 Aug '19

29 Aug '19

Hi, I have some issue and dont have enought knowledge to fix it. I have simple infrastructure. Internet -> router (NAT) -> kamailio -> asterisk Kamailio and Asterisk are inside the network and Kamailio places his own private address in the "record-route" headers instead of who's public. There is configuration to said to him what IP is proper ?

3 8

kamailio+asterisk VoiceMail implementation
by Zhan Bazarov 28 Aug '19

28 Aug '19

Hello, what's best practice for VoiceMail implementation in Kamailio+Asterisk's scheme? should I forward register into asterisk? Or I can keep register on kamailio? Could you, please, shed any lights on this

2 1

Disable GW's on runtime
by Duarte Rocha 28 Aug '19

28 Aug '19

Greetings, I have two Kamailio's working on a HA scenario. Both Kamailio's have DB replication and each machine has one HA IP. In order to set this up, i have every GW on the DB duplicated, one with Socket IPA and another with socket IPB. I have both GWs in a active state configurated in the replicated DB. They also both have the same URI and the same group id Example : GW1 : Socket = IPA ; GroupID = 1 ; Uri = sip:1.1.1.1:5060 GW2 : Socket = IPB ; GroupID = 1 ; Uri = sip:1.1.1.1:5060 In order to avoid errors, i want to disable on runtime the GWs that have a socket that doesn't belong, at the moment, to that machine (GW with Socket IPB on machine with IPA). To do that i would use the dispatcher.set_state, however it works with group id and address, which in this case it is the same. Is there other method to disable the GWs on runtime using other arguments like duid or socket ? I thought about using probing for this, since it will disable automatically the GWs with non-existent socket, but not all my clients support probing, so it isn't feasible. Thanks in advance

2 5

UAC ha1 password
by Alexandru Covalschi 28 Aug '19

28 Aug '19

Hello, I'm trying to make Kamailio to SIP register on a remote server. However storing plaintext password looks very unsecure. Is there a possibility to store password for uac module using ha1 hash instead of the plaintext password? I see there's a row for it in the database, but in the source code it's not used and it seems i can't neither use it in db neither set up in-memory as avp. Maybe there's a workaround to directly access the in-memory uac registration htable? ________________________________ Regards, Alexandru Covalschi VoIP Engineer and System Administrator tel: +37367367850

3 5

controlling presence with new module `pua_json`
by bill＠novatrope.us 28 Aug '19

28 Aug '19

Hi all: I am trying to use the procedure for setting BLF lights described in https://blog.voipxswitch.com/2018/02/22/kamailio-controlling-presence-with-… WIthout success. My configuration is 1 Grandstream GXP2130 phone behind a NAT on a public IP. (IPP in example below) Kamailio is running on public IP (IPK in example) listening on port 50060 The command I am sending: curl -d '{"Call-ID":"1020101@<IPP>","Event-Category":"presence","Event-Name":"update","Event-Package":"dialog","Expires":"3600","To":"sip:1020108@<IPK>:50060","To-User":"1020108","To-Realm":"<IPK>:50060","From":"sip:1020101@<IPP>","From-User":"1020101","From-Realm":"<IPP>","State":"Confirmed"}' http://localhost:8080/presence/ {"Call-ID":"1020101@<IPP>","Event-Category":"presence","Event-Name":"update","Event-Package":"dialog","Expires":"3600","To":"sip:1020108@<IPK>:50060","To-User":"1020108","To-Realm":"<IPK>:50060","From":"sip:1020101@<IPP>","From-User":"1020101","From-Realm":"<IPP>","State":"Confirmed"} Kamailio appears to be processing the command OK, so I think I am just not setting it up properly> Anybody having any luck with this procedure, let me know how you are getting it to work. Bill

2 1

[tm-local-request] usage
by Duarte Rocha 28 Aug '19

28 Aug '19

Greetings, Does "event_route[tm:local-request]" works like onsend route ? I'm having some problems and i'm using local-request to debug and i found this on the documentation : "Executed after the tm module has sent a local generated, transaction stateful request." I'm logging all the requests that go through this route. Is this really the last place before kamailio send the request? If the request is logged here, is there anything more in kamailio that can stop the request (pipelimit, etc) ? If a packet gets logged on this route does that mean that it was already sent? Best Regards, Duarte Rocha

3 4

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