- sr-users - kamailio.org

double_rr issues
by Roman Dissauer 28 Feb '19

28 Feb '19

I’m experiencing issues with kamailio 5.1 in multihomed config: two machines, latest debian stretch, latest kamailio 5.1, exactly same config (verified with diff) both machines have an internal and an external network interface. Only thing different is that they are in different datacenters. on one machine everything works perfect, on outgoning calls rr parameters are added perfectly right: Record-Route: <sip:yy.yy.yy.yy;transport=tcp;r2=on;lr;nat=yes> Record-Route: <sip:xx.xx.xx.xx;transport=tcp;r2=on;lr;nat=yes> where yy.yy.yy.yy is the external ip and xx.xx.xx.xx is the internal IP on the other machine I only get: Record-Route: <sip:xx.xx.xx.xx;transport=tcp;lr;nat=yes> even if I set enable_double_rr to 2 I get: Record-Route: <sip:xx.xx.xx.xx;transport=tcp;r2=on;lr;nat=yes> Record-Route: <sip:xx.xx.xx.xx;transport=tcp;r2=on;lr;nat=yes> I already checked with traceroute that the routing to the destination IP Adresses are going through the external interface. maybe someone has a hint for me. Thank you all in advance! Roman

3 3

TLS reload
by Patrick Wakano 27 Feb '19

27 Feb '19

Hi list, I've seen the TLS documentation ( https://www.kamailio.org/docs/modules/5.2.x/modules/tls.html#tls.known_limi…) where it states that TLS specific config reloading is not safe, so for now better don't use it, especially under heavy traffic. This note is there since version 3.0 and in 2013 there was some discussion about it but wthout anything conclusive.... What I would like to know if this is still the case. Is anyone running the TLS reload for certificate renovation for example, or is it better to restart Kamailio? Thanks, Kind regards, Patrick Wakano

4 5

SQlite in memory
by Duarte Rocha 27 Feb '19

27 Feb '19

Greetings, I'm trying to use SQlite as my engine in order to improve performance. I would like to have my Database stored in memory for faster access. I see that Kamailio can open the SQlite database as Read-Only, but i can't find a way to open it in memory. Is this possible using Kamailio? What's the best way to do this? Best Regards, Duarte Rocha

4 11

Dispatcher with parameter use_default=1
by Denys Pozniak 27 Feb '19

27 Feb '19

Hello! I use dispatcher with algorithm=1 (hashing over from URI) with module parameter use_default=1. So I am expecting that last string in dispatcher.list for specific set will be the "last hope" for call routing. dispatcher.list .. 4 sip:10.6.3.122:5060 4 sip:10.6.3.1:5060 4 sip:10.6.3.2:5060 4 sip:10.6.3.3:5060 4 sip:10.6.3.4:5060 4 sip:10.6.3.5:5060 But as I see from logs dispatcher module takes first string as the "last hope": xlog("L_WARN", "TEST-- $(avp(AVP_DST)[0]) $(avp(AVP_DST)[1]) $(avp(AVP_DST)[2]) $(avp(AVP_DST)[3]) $(avp(AVP_DST)[4]) $(avp(AVP_DST)[5]) $(avp(AVP_DST)[6]) \n"); Feb 26 16:11:39 kamailio-2 /usr/sbin/kamailio[28156]: WARNING: <script>: TEST-- sip:10.6.3.4:5060 sip:10.6.3.3:5060 sip:10.6.3.2:5060 sip: 10.6.3.1:5060 sip:10.6.3.5:5060 sip:10.6.3.122:5060 <null> Feb 26 16:11:58 kamailio-2 /usr/sbin/kamailio[28156]: WARNING: <script>: TEST-- sip:10.6.3.3:5060 sip:10.6.3.2:5060 sip:10.6.3.1:5060 sip: 10.6.3.5:5060 sip:10.6.3.4:5060 sip:10.6.3.122:5060 <null> Feb 26 16:11:59 kamailio-2 /usr/sbin/kamailio[28156]: WARNING: <script>: TEST-- sip:10.6.3.2:5060 sip:10.6.3.1:5060 sip:10.6.3.5:5060 sip: 10.6.3.4:5060 sip:10.6.3.3:5060 sip:10.6.3.122:5060 <null> Feb 26 16:12:08 kamailio-2 /usr/sbin/kamailio[28156]: WARNING: <script>: TEST-- sip:10.6.3.1:5060 sip:10.6.3.5:5060 sip:10.6.3.4:5060 sip: 10.6.3.3:5060 sip:10.6.3.2:5060 sip:10.6.3.122:5060 <null> According to the module explanation it should be "the last address in destination set is used as a final option to send the request to" version: kamailio 4.4.2 (x86_64/linux) 892ad6 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, 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: 892ad6 compiled on 12:58:38 Aug 28 2017 with gcc 4.8.5 -- BR, Denys Pozniak

2 4

auth_ephemeral too noisy
by Juha Heinanen 27 Feb '19

27 Feb '19

I did some tests with auth_ephemeral. When timestamp has expired, I get to syslog Feb 23 03:53:05 char /usr/bin/sip-proxy[31758]: WARNING: auth_ephemeral [authorize.c:205]: autheph_verify_timestamp(): username has expired Feb 23 03:53:05 char /usr/bin/sip-proxy[31758]: ERROR: auth_ephemeral [authorize.c:260]: digest_authenticate(): invalid timestamp in username In my opinion, the WARNING is enough and the ERROR message should be removed. ERROR is when an error happens. There is no error here, just an expired timestamp. -- Juha

2 2

Using the avp [*] index with jansson module functions
by Enrico Bandiera 26 Feb '19

26 Feb '19

Hello, I would like to use the [*] index for the avps (to overwrite instead of adding to the stack) when passing the variable to jansson module functions. When trying to do so I get this error: 9(35) ERROR: jansson [jansson_funcs.c:219]: janssonmod_set(): result has json error at line 1: end of file expected near ',' I suppose this is unsupported but maybe I'm doing something wrong, any suggestions? Thanks, Enrico.

1 0

How can I put updated sdp body to message in kemi
by Yuriy Gorlichenko 26 Feb '19

26 Feb '19

Hi. On the original config to set body with New data I used set_body() function, exported from sdpops module. But for kamailio 5.1 I can't find something same in case of using kemi Is There is some additional way to do this?

2 2

bad transport for sips uri?
by David Cunningham 26 Feb '19

26 Feb '19

Hello all, We're having an issue with Kamailio not processing an ACK and hope someone can help. A PCAP shows that Kamailio is receiving the ACK, and we believe these log messages are directly related to it: Feb 21 10:54:01 hostname /sbin/kamailio[15854]: ERROR: tm [ut.h:279]: uri2dst2(): ERROR: uri2dst: bad transport for sips uri: 1 Feb 21 10:54:01 hostname /sbin/kamailio[15854]: ERROR: tm [t_fwd.c:1777]: t_forward_nonack(): ERROR: t_forward_nonack: failure to add branches Feb 21 10:54:01 hostname /sbin/kamailio[15854]: ERROR: sl [sl_funcs.c:387]: sl_reply_error(): ERROR: sl_reply_error used: Unresolvable destination (478/SL) The ACK is as follows. It's from telephone 111111 which is using TLS, which Kamailio listens for on port 5061. Does anyone know which URI has the bad transport as per the error above? Might it be the From URI "sips:111111@es8.example.com" because it doesn't specify port 5061? Thank you in advance. Session Initiation Protocol (ACK) Request-Line: ACK sips:105@70.42.xx.xx:5070 SIP/2.0 Message Header Via: SIP/2.0/TLS 50.78.yy.yy:5061;branch=z9hG4bK741961203 Route: <sips:70.42.xx.xx:5061;transport=tls;r2=on;lr=on> Route: <sips:70.42.xx.xx;r2=on;lr=on> From: ES8 Test 102 <sips:111111@es8.example.com >;tag=Nf5GG!Orq!MSmGfeu66F03F2114df82b To: <sips:105@es8.example.com:5061>;tag=as7a72b209 Call-ID: 222222(a)50.78.yy.yy CSeq: 94679 ACK Contact: <sips:111111@50.78.yy.yy:5061;transport=tls> Max-Forwards: 70 User-Agent: ewb2bua/15.3.0 Content-Length: 0 -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

3 8

Dialog - Kamailio 5.2
by Nicolas Breuer 25 Feb '19

25 Feb '19

Hello the world, Can you give more informations about the new features of Dialog in K5.2 ? https://www.kamailio.org/w/kamailio-v5-2-0-release-notes/ * ability to load dialog records from database on demand * ability to load dialog records from database if they are not yet in memory cache Indeed in 5.1, restart Kamailio doesn't load the dialog data from database but we can see https://www.kamailio.org/docs/modules/5.1.x/modules/dialog.html#dialog.p.db… there is a function : Set db_skip_load to 1, to skip the loading of dialog data from the database. If on restart, the dialogs are not loaded, what this "db skip load " does ?

2 2

Kamailio with oracle database
by eyas barhouk 25 Feb '19

25 Feb '19

Hello community I'm trying to run kamailio with oracle 11g database and applying the needed querys by using Sqlops modules after applying the needed configuration i didn't find any Syntex to execute Oracle function from kamailio sqlops module . So is there any way to execute oracle function from kamailio ?? Best regards

3 3

Kamailio Module Phonenum
by Nicolas Breuer 25 Feb '19

25 Feb '19

Hello, Trying to find the module phonenum using the Kamailio repository but didn't find it. How can I active this module ? Thanks

2 3

How to easily remove top most header and set destination uri
by YASIN CANER 25 Feb '19

25 Feb '19

Hello, I have trouble with REFER method that has to-tag and Route header , more than one. When it pass loose_route() method , loose_route function remove all route headar then sets RURI with top most Route. Is there a function that removing own route header and sets destination uri ($du) with top most uri. Best Regards. Yasin CANER https://tools.ietf.org/html/rfc3515 2.6<https://tools.ietf.org/html/rfc3515#section-2.6> Behavior of SIP Proxies SIP proxies do not require modification to support the REFER method. Specifically, as required by [1<https://tools.ietf.org/html/rfc3515#ref-1>], a proxy should process a REFER request the same way it processes an OPTIONS request. For example, ---------->mykamailio(a)test2.test----------->>nextroute(a)test3.test------> 1 -- REFER : sip:alice@test.test ... Route:<sip:mykamailio-local@test2.test;lr>,<sip:nextroute@test3.test;lr>,<sip:nextroute2@test4.test> To: <>;tag=asdads From:<>;tag=asd123 --- 2 - After Kamailio Process --- REFER : sip:alice@test.test ... <sip:nextroute@test3.test>,<sip:nextroute2@test4.test> To: <>;tag=asdads From:<>;tag=asd123

2 3

Rows return in sql_xquery()
by Duarte Rocha 25 Feb '19

25 Feb '19

Greetings, If I do a query using sql_query() method I can see the number of rows returned with $dbr(ra=>rows). Is there a return with this info using sql_xquery ? Best Regards, Duarte Rocha

1 0

create own packages for some modules
by Sergey Safarov 22 Feb '19

22 Feb '19

Current kamailio package (checked via RPM) is contains lot of modules. Some of this is not important to include in every kamailio installation. May be create own packages for this modules and other in next 5.3 branch? Modules examples: benchmark.so db_cluster.so db_text.so rtpengine.so rtpproxy.so sipcapture.so siptrace.so sipt.so sms.so smsops.so ss7ops.so https://github.com/kamailio/kamailio/issues/1862

4 6

Is DMQ now the recommended way to do things?
by Canuck . 21 Feb '19

21 Feb '19

Before DMQ there were other ways to do similar things. Is DMQ now considered the best way? Assuming I am using recent stable? Are there any good guides on clustering Kamailio? I am not finding a lot of good info on that subject. Specifically, for multi datacenter active active where things like floating IP's and keepalived are not really an option.

5 7

Not able to connect kamailio via SIP Client
by Prabhat Kumar 21 Feb '19

21 Feb '19

hi, I have setup everything in kamailio and i also added dispatcher in my kamailio config. When i try to login via SIP Client(zoiper) i am getting the following error. Feb 21 11:20:26 ip-10-0-0-121 /usr/local/sbin/kamailio[21131]: INFO: <core> [core/parser/parse_fline.c:144]: parse_first_line(): ERROR:parse_first_line: method not followed by SP Feb 21 11:20:26 ip-10-0-0-121 /usr/local/sbin/kamailio[21131]: ERROR: <core> [core/parser/parse_fline.c:257]: parse_first_line(): parse_first_line: bad message (offset: 0) Feb 21 11:20:26 ip-10-0-0-121 /usr/local/sbin/kamailio[21131]: ERROR: <core> [core/parser/msg_parser.c:675]: parse_msg(): ERROR: parse_msg: message=<�#007�> Feb 21 11:20:26 ip-10-0-0-121 /usr/local/sbin/kamailio[21131]: ERROR: <core> [core/receive.c:199]: receive_msg(): core parsing of SIP message failed (114.241.140.68:4569/1) How can i fix this problem? Thanks. Prabhat

3 2

Parallel Forking
by Jan-Hendrik Dörner 21 Feb '19

21 Feb '19

Hello, I would like to get parallel forking working on my Kamailio installation, but I have trouble to accomplish that. I am running Kamailio 5.1.4 and follow the example in the tm-module as given in https://www.kamailio.org/docs/modules/5.1.x/modules/tm.html#tm.serial_forki… <https://www.kamailio.org/docs/modules/5.1.x/modules/tm.html#tm.serial_forki…> If I run this example nothing is happening, except that I can see that the „t_on_branch“ is executed when stated, but no calls are routed to the destinations appended. (No phones are actually ringing ...) What am I missing / should do to get actual calls routed? (I am getting the seturi- phone to ring, if I remove the break statement, so that the call can get routed „all the way“.) Is there any working Kamailio example-config, where I can actual see the parallel forking working? Regards Jan-Hendrik

2 1

BUG: Error While installing websocket
by Prabhat Kumar 21 Feb '19

21 Feb '19

I am getting the following error while installing websocket modules in kamailio. make -C src/ install-modules-all make[1]: Entering directory '/usr/local/src/kamailio-5.1/kamailio/src' CC (gcc) [M websocket.so] ws_frame.o ws_frame.c:32:10: fatal error: unistr.h: No such file or directory #include <unistr.h> ^~~~~~~~~~ compilation terminated. ../../Makefile.rules:100: recipe for target 'ws_frame.o' failed make[2]: *** [ws_frame.o] Error 1 Makefile:511: recipe for target 'install-modules' failed make[1]: *** [install-modules] Error 1 make[1]: Leaving directory '/usr/local/src/kamailio-5.1/kamailio/src' Makefile:27: recipe for target 'install-modules-all' failed make: *** [install-modules-all] Error 2 *Is this a bug?? How can i fix this problem?* Thanks,

2 1

Regex issue with subst_body
by Kristijan Vrban 21 Feb '19

21 Feb '19

Hi, in a sdp i need to rewrite a a=sendrecv to a=sendonly but onyl for the for the video stream. I made a regex like this: (?<=m=video)(?s)(.*)(a=sendrecv) Full version here: https://regex101.com/r/rovecJ/1 But if have problems to translate this into kamailio config via subst_body function. I always end with ERROR: fix_actions(): fixing failed (code=-3) Somebody sees the mistake? Kristijan

3 2

Default Modules while installing kamailio
by Prabhat Kumar 21 Feb '19

21 Feb '19

Hi, I am installing kamailio from source on my ubuntu 16.04 server. *How would i know the default modules installing automatically with kamailio?* *Also How can i install all modules(if i want to) with kamailio 5.1?* Thanks, Prabhat Kumar

2 1

kamailio-sipcapture-daemon-config package not found for CentOS7
by Patrick Wakano 20 Feb '19

20 Feb '19

Hello list, I was trying to yum install Kamailio 5.2.1 on a CentOS 7 from the http://download.opensuse.org/repositories/home:/kamailio:/v5.2.x-rpms/CentO… repo, but the kamailio-sipcapture-daemon-config can't be installed because it depends on the kamailio-sipcapture package, which can't be found... Is anyone aware of that? Thank you, Kind regards, Patrick Wakano # yum install kamailio-sipcapture-daemon-config Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.optus.net * epel: mirror.optus.net * extras: mirror.intergrid.com.au * updates: mirror.intergrid.com.au Resolving Dependencies --> Running transaction check ---> Package kamailio-sipcapture-daemon-config.x86_64 0:5.2.1-1.el7.centos will be installed --> Processing Dependency: kamailio-sipcapture = 5.2.1 for package: kamailio-sipcapture-daemon-config-5.2.1-1.el7.centos.x86_64 --> Finished Dependency Resolution Error: Package: kamailio-sipcapture-daemon-config-5.2.1-1.el7.centos.x86_64 (home_kamailio_v5.2.x-rpms) Requires: kamailio-sipcapture = 5.2.1 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest # yum deplist kamailio-sipcapture-daemon-config Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.optus.net * epel: mirror.optus.net * extras: mirror.intergrid.com.au * updates: mirror.intergrid.com.au package: kamailio-sipcapture-daemon-config.x86_64 5.2.1-1.el7.centos dependency: /bin/sh provider: bash.x86_64 4.2.46-31.el7 dependency: kamailio-sipcapture = 5.2.1 Unsatisfied dependency

2 2

Topoh disabling
by Nicolas Breuer 20 Feb '19

20 Feb '19

Hello, Using this event route (see doc) event_route[topoh:msg-outgoing] { if($sndto(ip)=="10.1.1.10") { drop; } } Cause Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16417]: ERROR: <core> [core/parser/parse_via.c:2051]: parse_via(): bad char <´> on state 100 Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16417]: ERROR: <core> [core/parser/parse_via.c:2704]: parse_via(): parsing via on: <´#037#027#015#012X> Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16417]: ERROR: <core> [core/parser/parse_via.c:2710]: parse_via(): via parse error Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16417]: ERROR: topoh [th_msg.c:454]: th_unmask_via(): cannot find cookie in via2 Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16416]: ERROR: <core> [core/parser/parse_via.c:2051]: parse_via(): bad char <´> on state 100 Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16416]: ERROR: <core> [core/parser/parse_via.c:2704]: parse_via(): parsing via on: <´#037#027#015#012X> Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16416]: ERROR: <core> [core/parser/parse_via.c:2710]: parse_via(): via parse error Feb 20 21:02:22 proxy2 /usr/sbin/kamailio[16416]: ERROR: topoh [th_msg.c:454]: th_unmask_via(): cannot find cookie in via2 Kamailio 5.1.7

2 2

Kamailio Asterisk Retransmitting problem
by Techinnovation 20 Feb '19

20 Feb '19

Hello, Could you please help me correctly to configure Kamailio with load balancing between two asterisk servers and topology hidding with topoh module. In attach sip trace from kamailio and my config. Currently my problem is that after call UP on Asterisk side, Asterisk send 10 times Retransmitting to <-------------> Retransmitting #5 (no NAT) to 37.148.171.162:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 37.148.171.162;branch=z9hG4bKf534.157d7d1321019895cc6ba367dd3ae94c.0;received=37.148.171.162 Via: SIP/2.0/UDP 37.148.171.162;branch=z9hG4bKsr-mDYdVEts1x8-yJc91MhEVMtOVMhC6pni1uai1uSAQiytLvyKkMqHB5JsSg98PMYayEyHzESE1gdA6E9C From: "testaccount" <sip:37125511039@213.21.197.50>;tag=as7abbf1f1 To: <sip:100@37.148.171.162:5060>;tag=as143173ac Call-ID: !!:1MeMfMhpfGtgfo6MQu6HfMNH1v-515SC1omDQocT1Efc1MhEVMtOVMhC6pni1uai1uSA CSeq: 102 INVITE Server: Asterisk PBX GIT-master-c83a44c Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces, timer Session-Expires: 1800;refresher=uas Contact: <sip:100@37.148.171.164:5060> Content-Type: application/sdp Require: timer Content-Length: 267 v=0 o=root 1502512559 1502512559 IN IP4 37.148.171.164 s=Asterisk PBX GIT-master-c83a44c c=IN IP4 37.148.171.164 t=0 0 m=audio 19658 RTP/AVP 8 101 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=maxptime:150 a=sendrecv And no ACK answer from Kamailio. After 32 sec call drops. I have call flow: Provider 213.21.197.50 -> Kamailio 37.148.171.162 -> Asterisk 37.148.171.163. kamailio -v version: kamailio 5.2.0 (x86_64/linux) 535e13 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 535e13 compiled on 01:27:51 Dec 16 2018 with gcc 4.8.5 On Asterisk side I have config [general] language=en maxexpirey=3600 defaultexpirey=3600 bindport=5060 subscribecontext=lab allowsubscribe=yes limitonpeers=yes notifyringing=yes notifyhold=yes disallow=all alwaysauthreject=yes allowguest=no allow=alaw bindaddr=37.148.171.163 t38pt_udptl=yes,redundancy faxdetect=yes directmedia=no rtptimeout=60 rtpholdtimeout=300 [kamailio] type=friend host=37.148.171.162 port=5060 nat=no qualify=no canreinvite=yes insecure=invite context=from-pstn ;directmedia=yes Many thanks ! BR, Alex -- Best regards, Techinnovation mailto:techinnovation@inbox.lv

2 2

Installing and setup of RTP engine on kamailio
by Prabhat Kumar 20 Feb '19

20 Feb '19

Hi, How can i install and setup RTP-Engine on ubuntu server? Regards, Prabhat Kumar

3 3

Gracefully dropping all branches
by Andreas Granig 20 Feb '19

20 Feb '19

Hi all, I’ve a scenario where after lookup() I get multiple branches, and I want to drop some or all of them based on some filter criteria in a branch route before sending requests out. Problem is that if all branches are dropped, kamailio replies with some implicitly generated 500 server error since there are no more branches, but I want to send a 404 or 480 instead. Is there a way to determine if I’m processing the last active branch (so all others have been dropped already), so I can send a graceful reply like 404 or 480 instead of dropping this last branch as well if I decide I have to filter that one too? I’m thinking of a hash table table or something to track and decrease the number of branches for a call, and based on a flag (whether one of the previous branches has been sent out or all have been dropped so far) either drop the last branch or reply with an error. However I’m wondering if kamailio comes with a mechanism to determine the branch state out of the box? Thanks, Andreas

2 2

How to setup Kamailio to dispatch SIP client requests to WebRTC enabled Asterisk
by Adesh Pandey 20 Feb '19

20 Feb '19

Hi Guys, I have recently setup a Kamailio server which can accept SIP or WebSocket connections but voice is not coming in the case of SIP client. I have no idea to change avp in the incoming request, please advise how to proceed.

3 3

Topos and subst_hf
by Igor Olhovskiy 19 Feb '19

19 Feb '19

Hi! I'm using subst_hf to add some extra info to contact subst_hf("Contact", "/^(.*)sip:(.*)@(.*)$/\1sip:encei$var(extra_info)-\2@\3/i", "f"); With combination of topos it's giving me strange results like 2(26) WARNING: sanity [sanity.c:282]: check_ruri_scheme(): failed to parse request uri [sip:encei302e3734-btpsh-5c6c00ac-2e-f@172.28.0.74><sip:encei302e3734-btpsh-5c6c00ac-2e-f@172.28.0.74] Seems, it's doubling R-URI on in-dialog requests. If I'm disabling topos - all is ok. What is interesting - this can't be reproduced with remove_hf/append_hf mechanisms.

1 1

Problem with requests routing when topoh is enabled
by Leonid Fainshtein 19 Feb '19

19 Feb '19

Hi, I have Kamailio 5.1 and I'm using the topology hiding module (topoh) that is configured as the following: modparam("topoh", "mask_key", "...") modparam("topoh", "uparam_name", "....") modparam("topoh", "uri_prefix_checks", 0) Unfortunately Fanvil SIP phone modifies the remote party Contact's URI before it puts it as R-URI in the re-INVITE request. For example, The remote party Contact header: Contact: <sip:127.0.0.8;tr=sr-O2Sdn60d3qrt3otz3o7L.6pF.6mUr6lF3qpd> The re-INVITE request line: INVITE sip:127.0.0.8;tr=sr-O2Sdn60d3qrt3otz3o7L.6pF.6mUr6lF3qpd;user=phone SIP/2.0 As you can see, ";user=phone" was added. As result of that Kamailio tries to send the request to 127.0.0.8. If I disable sending 'user=phone' in Fanvil configuration then everything works well. I assumed that if uri_prefix_checks=0 then the topoh module should take rid of such URI modifications. Am I wrong? Is there any way to solve the problem except to modify the endpoint configuration? Best regards, Leonid Fainshtein

1 0

How can i send presence status from Asterisk 13 to kamailio presence module
by PICCORO McKAY Lenz 19 Feb '19

19 Feb '19

i have followed the guie in https://kb.asipto.com/kamailio:presence:k43-blf and asterisk are working (due we connnect the phones directly to asterisk and works) but when connect the phones to the kamailio the led in phones does not work! ther's some info missing or what? Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com

1 0

Re: [SR-Users] TM Module - Unfortunately error on sending to next hop occurred (477/TM)
by Ilie Soltanici 19 Feb '19

19 Feb '19

Hi, Looks that space comes from copy/paste or page formatting - in the log file there is no space within this variable. Thank's

2 3

Detecting end of DNS failover in tm:branch-failure
by Ivan Ribakov 19 Feb '19

19 Feb '19

Hi all, I have a custom routing logic implemented in my module. This routing logic may return a list of 2 or more endpoints where INVITE should be attempted to be routed. Since endpoint URI can contain domain names, I’m also trying to take care of DNS resolution. Based on the documentation found in https://github.com/kamailio/kamailio/blob/master/doc/tutorials/dns.txt <https://github.com/kamailio/kamailio/blob/master/doc/tutorials/dns.txt> current DNS resolver/failover logic takes good care of RFC3263. To support switching between various endpoints returned by custom routing logic I have been using “tm:branch-failure” routing blocks. Problem I’m facing right now is that I am unable to distinguish between a DNS failover branch failure that has more SRV records to try and the “final” DNS failover branch failure (at which point I should be switching to another endpoint). I’ve tried monitoring $T_reply_code values, but it is “408” in both cases. Any ideas on how “final” and “non-final” DNS failover branch failures can be distinguished? Regards, Ivan

1 0

Re: [SR-Users] Issue with UAC restore_mode when restore_dlg is enabled
by Daniel-Constantin Mierla 19 Feb '19

19 Feb '19

Can you check via rpc and looking at database tables if dialog record is there? Cheers, Daniel On Tue, 19 Feb 2019, 08:44 <jenus(a)cyberchaos.nl wrote: > Daniel, > > Yes the uac_replace_from is called from a branch route. > > Jan > > Daniel-Constantin Mierla schreef op 2019-02-19 08:26: > > I do not recall any relevant changes recently in this part of the code, > > so likely to be same result for 5.2. > > > > With restore_dlg set to 1, dialog variables are used for storing the > > headers. When do you call uac_replace_from()/_to()? Is it in a > > branch_route? > > > > Cheers, > > Daniel > > > > On 19.02.19 08:07, jenus(a)cyberchaos.nl wrote: > >> Forgot to mention, i'm running kamailio 5.1.7, did not test yet with > >> the latest 5.2 release. > >> > >> Jan > >> > >> > >> jenus(a)cyberchaos.nl schreef op 2019-02-18 15:22: > >>> Hello, > >>> > >>> I'm running into a issue with restore_mode auto when i enable > >>> restore_dlg in the uac module. I have a feature where i reroute calls > >>> for a subscriber when it is offline. When routing calls to the > >>> subscriber i check the exit status of "lookup("location")" and > >>> re-route the call. This works fine. It seems to fail when i hit the > >>> failure route (subscriber has a usrloc entry but does not respond). > >>> In > >>> the failure route i append_branch and reroute the call. > >>> > >>> The rerouting works fine, but when i receive the ACK on the 200OK on > >>> the re-routed call the "restore" feature seems to fail and i end up > >>> with a header like: > >>> > >>> To: > >>> <sip:+<null>@voip-dev.domain.nl > >;tag=5B8ABC8A-5C6ABE83000EBF35-AB202700 > >>> in the ACK. > >>> > >>> If i disable restore_dlg feature from the UAC module it adds the > >>> vsf/vst to the Record-Route header and all works fine. > >>> > >>> Do i need to do something special when i create a new branch and use > >>> the restore_dlg feature? > >>> > >>> > >>> Thanks, > >>> > >>> Jan Hazenberg > >>> > >>> _______________________________________________ > >>> Kamailio (SER) - Users Mailing List > >>> sr-users(a)lists.kamailio.org > >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >> > >> > >> _______________________________________________ > >> Kamailio (SER) - Users Mailing List > >> sr-users(a)lists.kamailio.org > >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > >

2 2

Issue with UAC restore_mode when restore_dlg is enabled
by jenus＠cyberchaos.nl 19 Feb '19

19 Feb '19

Hello, I'm running into a issue with restore_mode auto when i enable restore_dlg in the uac module. I have a feature where i reroute calls for a subscriber when it is offline. When routing calls to the subscriber i check the exit status of "lookup("location")" and re-route the call. This works fine. It seems to fail when i hit the failure route (subscriber has a usrloc entry but does not respond). In the failure route i append_branch and reroute the call. The rerouting works fine, but when i receive the ACK on the 200OK on the re-routed call the "restore" feature seems to fail and i end up with a header like: To: <sip:+<null>@voip-dev.domain.nl>;tag=5B8ABC8A-5C6ABE83000EBF35-AB202700 in the ACK. If i disable restore_dlg feature from the UAC module it adds the vsf/vst to the Record-Route header and all works fine. Do i need to do something special when i create a new branch and use the restore_dlg feature? Thanks, Jan Hazenberg

2 3

Presence module with external MWI
by Trevor Peirce 19 Feb '19

19 Feb '19

Hello, Looking for pointers as to what I'm missing here. I'm using the presence module to allow UAs to subscribe to message-summary events. I can see the entries appearing in the active_watchers table and I see subscription renewals increment the cseq columns so I'm satisfied this part is working well. I'm having trouble finding out how to tell Kamailio about a change to the message-summary so that it can notify the watchers. The pua module seems to provide a way but it doesn't seem to work with the subscriptions set up by the presence module. The presence module itself does not seem to offer any RPCs capable of doing this. Appreciate any pointers! Thanks, -- Trevor Peirce AcroVoice Solutions Inc

4 5

Integration with mobile oprators
by sina yazdanian 18 Feb '19

18 Feb '19

Dear Kamailio Technical team I’m Sina from a small software development company in Middle-East. We are interested in your product. For R&D research we need some documents about your product. Your support would be appreciated in case of sharing document. We need document about* SIP server integration with Mobile operator*. I would be grateful if you support me and the team to complete research. Best Regards Sina Yazdanian

2 1

how to see banned address after rule it
by PICCORO McKAY Lenz 18 Feb '19

18 Feb '19

i configure rules for routing banned ip and i want to see where i can autdit this issues.. i mean where i can automatically define a cron setup that grep those logs definitios.. where are loggin those all? my rules are: define at begining of kamailio.cfg "#!WITH_ANTIFLOOD", later add: #!ifdef WITH_ANTIFLOOD loadmodule "htable.so" loadmodule "pike.so" modparam("pike", "sampling_time_unit", 2) modparam("pike", "reqs_density_per_unit", 16) modparam("pike", "remove_latency", 4) modparam("htable", "htable", "ipban=>size=8;autoexpire=300;") #!endif later routing definitions: route[REQINIT] { if(src_ip!=myself) { if($sht(ipban=>$si)!=$null) { 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; } } if($ua =~ "friendly-scanner|sipcli|VaxSIPUserAgent") { xlog("L_ALERT","ALERT: friendly canings from $fu (IP:$si:$sp)\n"); 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; } } Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com

3 3

Dispatcher No destinations available
by Cristian Livadaru 18 Feb '19

18 Feb '19

Hi, I have a Kamailio running as Load Balancer and it works great but since a couple of weeks I kept noticing 404s in Homer and when looked into it they came from Kamailio. ``` route[LOADBALANCE] { #ds_select_dst(destination_set, algorithm) function chooses the destination for the call. For this it can use a lot of algorithms. #Alg. 0 is the default one that does the the choosing over the call ID hash #Alg. 4 is a Round-Robin #Alg. 10 is the one that chooses the destination based on the minimum load of all destinations if(!ds_select_dst("1", "4")) { #if we are here that means no destination is available. We notify the user by 404 and exit the script. xlog("L_NOTICE", "No destination available!"); send_reply("404", "No destination"); exit; } xlog("L_NOTICE", "Routing call to <$ru> via <$du>\n"); #set the no_reply_recieved timeout to 2 second ... adjust the value to your need #note: The first value "0" is invite timeout .. we do not need to change it #This means that is the selected media server fails to respond within 2 seconds the failure_route "MANAGE_FAILURE" is called #note: this implies that ale the signaling from media servers on the way back to the user goes through the proxy as well t_set_fr(0,2000); t_on_failure("MANAGE_FAILURE"); return; } ``` The two asterisks behind it seem fine and I can’t really see why this started happening. Also I thing that returning 404 might be misleading, wouldn’t it be better if I would return 503 instead? I enabled debugging in Kamailio but can’t really seem to notice anything wrong here: ``` Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/udp_server.c:491]: udp_rcv_loop(): received on udp socket: (106/100/1104) [[INVITE sip:431230123@213.137.140.230:5060 SIP/2.0 0D 0A Via: SIP/2.0/UDP 196.27.235.76:5060;branch=z9h]] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:604]: parse_msg(): SIP Request: Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:606]: parse_msg(): method: <INVITE> Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:608]: parse_msg(): uri: <sip:431230123@213.137.140.230:5060> Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:610]: parse_msg(): version: <SIP/2.0> Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK0080827005DD9C0D8E963B2EA293>; state=16 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of header reached, state=5 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:492]: parse_headers(): Via found, flags=2 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:494]: parse_headers(): this is the first via Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=10 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To> [52]; uri=[sip:431230123@213.137.140.230] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:172]: get_hdr_field(): to body ["431230123" <sip:431230123@213.137.140.230> Feb 15 09:50:28 wlb kamailio[6659]: ] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq <CSeq>: <36825> <INVITE> Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/receive.c:200]: receive_msg(): --- received sip message - request - call-id: [2610e00004f5-5c66843f-6400386f-2c1b8100-6c4782(a)127.0.0.1] - cseq: [36825 INVITE] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/receive.c:248]: receive_msg(): preparing to run routing scripts... Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_addr_spec.c:185]: parse_to_param(): add param: tag=0080827005DD9C0D8E96C55CF6CD Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/parse_addr_spec.c:864]: parse_addr_spec(): end of header reached, state=29 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siptrace [siptrace.c:507]: sip_trace_store_db(): database connection not initialized Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siptrace [siptrace_hep.c:498]: pipport2su(): the port string is 5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siptrace [siptrace_hep.c:498]: pipport2su(): the port string is 5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/proxy.c:264]: mk_proxy(): doing DNS lookup... Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siptrace [siptrace_hep.c:302]: trace_send_hep2_duplicate(): setting up the socket_info Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) NOTICE: <script>: Tracing 6(6668) DEBUG: maxfwd [mf_funcs.c:74]: is_maxfwd_present(): value = 70 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:183]: get_hdr_field(): content_length=355 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found end of header Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: sanity [sanity_mod.c:256]: w_sanity_check(): sanity checks result: 1 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/socket_info.c:559]: grep_sock_info(): checking if host==us: 14==9 && [213.137.140.230] == [127.0.0.1] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/socket_info.c:566]: grep_sock_info(): checking if port 5060 (advertise 0) matches port 5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/socket_info.c:559]: grep_sock_info(): checking if host==us: 14==14 && [213.137.140.230] == [213.137.140.230] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: <core> [core/socket_info.c:566]: grep_sock_info(): checking if port 5060 (advertise 0) matches port 5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) NOTICE: <script>: OPTIONS from 196.27.235.76:5060 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: siputils [checks.c:120]: has_totag(): no totag Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:1018]: t_check_msg(): msg (0x7f7e7edd3be8) id=6845 global id=6844 T start=(nil) Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:476]: t_lookup_request(): start searching: hash=29308, isACK=0 Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:435]: matching_3261(): RFC3261 transaction matching failed Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:659]: t_lookup_request(): no transaction found Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: tm [t_lookup.c:1087]: t_check_msg(): msg (0x7f7e7edd3be8) id=6845 global id=6845 T end=(nil) Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: rr [loose.c:1209]: is_direction(): param ftag not found Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: dispatcher [dispatch.c:1832]: ds_select_dst_limit(): set [1] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) DEBUG: dispatcher [dispatch.c:1935]: ds_select_dst_limit(): alg hash [1] Feb 15 09:50:28 wlb kamailio[6659]: 6(6668) NOTICE: <script>: No destination available! 6(6668) DEBUG: sl [sl.c:282]: send_reply(): reply in stateless mode (sl) ``` My kamailio.cfg ``` #!KAMAILIO # # sample config file for dispatcher module # - load balancing of VoIP calls with round robin # - no TPC listening # - don't dispatch REGISTER and presence requests # # Kamailio (OpenSER) SIP Server v3.2 # - web: http://www.kamailio.org # - git: http://sip-router.org # # Direct your questions about this file to: sr-users(a)lists.sip-router.org # # Refer to the Core CookBook at http://www.kamailio.org/dokuwiki/doku.php # for an explanation of possible statements, functions and parameters. # # Several features can be enabled using '#!define WITH_FEATURE' directives: # # *** To run in debug mode: # - define WITH_DEBUG # ####### Global Parameters ######### #!define WITH_HOMER #!define WITH_DEBUG #!ifdef WITH_DEBUG debug=4 log_stderror=yes #!else debug=2 log_stderror=no #!endif memdbg=5 memlog=5 log_facility=LOG_LOCAL0 fork=yes children=4 /* comment the next line to enable TCP */ disable_tcp=yes /* uncomment the next line to disable the auto discovery of local aliases based on revers DNS on IPs (default on) */ auto_aliases=yes /* add local domain aliases */ port=5060 /* 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:127.0.0.1:5060 sip_warning=no ####### Modules Section ######## #set module path mpath="/usr/lib/x86_64-linux-gnu/kamailio/modules/" # loadmodule "db_mysql.so" # loadmodule "mi_fifo.so" 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" loadmodule "dispatcher.so" #!ifdef WITH_HOMER loadmodule "siptrace.so" #!endif #loadmodule "kex.so" #loadmodule "tm.so" #loadmodule "tmx.so" #loadmodule "sl.so" #loadmodule "rr.so" #loadmodule "pv.so" #loadmodule "maxfwd.so" #loadmodule "textops.so" #loadmodule "siputils.so" #loadmodule "xlog.so" #loadmodule "sanity.so" ## loadmodule "ctl.so" #loadmodule "mi_rpc.so" #loadmodule "acc.so" # ----- acc params ----- modparam("acc", "log_flag", 1) modparam("acc", "failed_transaction_flag", 3) modparam("acc", "log_extra", "src_user=$fU;src_domain=$fd;dst_ouser=$tU;dst_user=$rU;dst_domain=$rd;src_ip=$si") #!ifdef WITH_HOMER # check IP and port of your capture node modparam("siptrace", "duplicate_uri", "sip:213.136.47.31:9060") modparam("siptrace", "hep_mode_on", 1) modparam("siptrace", "trace_to_database", 0) modparam("siptrace", "trace_flag", 22) modparam("siptrace", "trace_on", 1) #!endif # ----------------- setting module-specific parameters --------------- # modparam("dispatcher", "db_url", DBURL) modparam("dispatcher", "table_name", "dispatcher") modparam("dispatcher", "flags", 2) modparam("dispatcher", "dst_avp", "$avp(AVP_DST)") modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)") modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)") modparam("dispatcher", "sock_avp", "$avp(dssocket)") modparam("dispatcher", "attrs_avp", "$avp(dsattrs)") #set next two parameters if you want to enable balance alg. no. 10 #modparam("dispatcher", "dstid_avp", "$avp(dsdstid)") #modparam("dispatcher", "ds_hash_size", 8) modparam("dispatcher", "ds_ping_interval", 20) modparam("dispatcher", "ds_ping_from", "sip:kamailio@example.com") #modparam("dispatcher", "ds_ping_method", "INFO") modparam("dispatcher", "ds_probing_mode", 1) modparam("dispatcher", "ds_probing_threshold", 1) #configure codes or classes of SIP replies to list only allowed replies (i.e. when temporarily unavailable=480) modparam("dispatcher", "ds_ping_reply_codes", "class=2;code=480;code=404") ####### Routing Logic ######## # main request routing logic route { #!ifdef WITH_HOMER #start duplicate the SIP message now sip_trace(); setflag(22); xlog("L_NOTICE","Tracing"); #!endif # per request initial checks route(REQINIT); # handle requests within SIP dialogs route(WITHINDLG); # CANCEL processing if (is_method("CANCEL")) { if (t_check_trans()) t_relay(); exit; } t_check_trans(); # record routing for dialog forming requests (in case they are routed) # - remove preloaded route headers remove_hf("Route"); if (is_method("INVITE|SUBSCRIBE")) record_route(); #if (is_method("INVITE")) #{ # ds_select_domain("1","4"); # #sl_send_reply("300","Redirect"); # #t_relay(); # exit; #} # account only INVITEs if (is_method("INVITE")) { setflag(1); # do accounting } # handle presence related requests route(PRESENCE); # handle registrations route(REGISTRAR); if ($rU==$null) { # request with no Username in RURI sl_send_reply("484","Address Incomplete"); exit; } route(LOADBALANCE); route(RELAY); } # Per SIP request initial checks route[REQINIT] { if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; } if(!sanity_check("1511", "7")) { xlog("Malformed SIP message from $si:$sp\n"); exit; } # Reply to options if (uri==myself) { xlog("L_NOTICE","OPTIONS from $si:$sp\n"); if ((method==OPTIONS) && (! uri=~"sip:.*[@]+.*")) { xlog("L_NOTICE","answering options $si:$sp\n"); options_reply(); } } } # Handle requests within SIP dialogs route[WITHINDLG] { if (has_totag()) { # sequential request withing a dialog should # take the path determined by record-routing if (loose_route()) { if (is_method("BYE")) { setflag(1); # do accounting ... setflag(3); # ... even if the transaction fails } route(RELAY); } else { if (is_method("SUBSCRIBE") && uri == myself) { # in-dialog subscribe requests route(PRESENCE); exit; } if ( is_method("ACK") ) { if ( t_check_trans() ) { # non loose-route, but stateful ACK; # must be ACK after a 487 or e.g. 404 from upstream server t_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; #sl_send_reply("404", "No registrar"); #t_relay(); if(!ds_select_dst("1", "4")) { sl_send_reply("404", "No registrar"); exit; } forward(); exit; } # Presence server route route[PRESENCE] { if(!is_method("PUBLISH|SUBSCRIBE")) return; sl_send_reply("404", "Not here"); exit; } route[LOADBALANCE] { #ds_select_dst(destination_set, algorithm) function chooses the destination for the call. For this it can use a lot of algorithms. #Alg. 0 is the default one that does the the choosing over the call ID hash #Alg. 4 is a Round-Robin #Alg. 10 is the one that chooses the destination based on the minimum load of all destinations if(!ds_select_dst("1", "4")) { #if we are here that means no destination is available. We notify the user by 404 and exit the script. xlog("L_NOTICE", "No destination available!"); send_reply("404", "No destination"); exit; } xlog("L_NOTICE", "Routing call to <$ru> via <$du>\n"); #set the no_reply_recieved timeout to 2 second ... adjust the value to your need #note: The first value "0" is invite timeout .. we do not need to change it #This means that is the selected media server fails to respond within 2 seconds the failure_route "MANAGE_FAILURE" is called #note: this implies that ale the signaling from media servers on the way back to the user goes through the proxy as well t_set_fr(0,2000); t_on_failure("MANAGE_FAILURE"); return; } # manage failure routing cases failure_route[MANAGE_FAILURE] { # route(NATMANAGE); if (t_is_canceled()) { exit; } xlog("L_NOTICE", "Media server $du failed to answer, selecting other one!"); # next DST - only for 500 reply or local timeout (set by t_set_fr()) if (t_check_status("500") || t_branch_timeout() || !t_branch_replied()) { #we mark the destination Inactive and Probing ds_mark_dst("ip"); #select the new destination if(ds_next_dst()) { #again set local timeout for reply t_set_fr(0,2000); t_on_failure("MANAGE_FAILURE"); route(RELAY); exit; } else { #last available node failed to reply, no other destinations available send_reply("404", "No destination"); exit; } } } route[RELAY] { xlog("L_NOTICE", "going to <$ru> via <$du>"); if (!t_relay()) { sl_reply_error(); } exit; } ``` and my dispatcher.list ``` # line format # id(int,auto) setid(int) destination(string) flags(int) priority(int) attrs(string) description(string) 1 sip:196.27.235.76:5060 1 sip:213.137.140.230:5060 ``` any help to understand these issues would be greatly appreciated. Cris --- Cristian Livadaru LcX IT Solutions Web: http://lcx.at/ Tel: +43 1 37 37 37 Fax: +43 1 37 37 37 - 25 **24/7 Support: 0900 474 455** (1,81€/Min)

2 3

Info: Kamailio World 2019 - First group of speakers
by Daniel-Constantin Mierla 18 Feb '19

18 Feb '19

Hello, a short note to let everybody know that we have published the details for the first group of speakers at Kamailio World 2019 (May 6-8, in Berlin) - you can read more about at: * https://www.kamailioworld.com/k07/2019/02/kamailio-world-2019-first-group-o… * https://www.kamailioworld.com/k07/speakers/ The target is to finish the review of the speaking proposals by end of the month, then start working on the schedule. We received a lot more than it can be accommodated, but we will try to select all that are very interesting by having several short sessions/lightning talks. There will be few new concepts, trying to engage more the participants as well as use better the evening time for social networking with a boat trip at the end of first day, in addition to the cocktail party on the second day. Hoping to meet many of you in Berlin at Kamailio World 2019! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com

1 0

Branches Routes
by Nicolas Breuer 18 Feb '19

18 Feb '19

Hello, We have a main route where we try multiple destinations (SIP Providers) one by one in case of failure. We modify the $ru in branch routes. I have to manipulate the $rU in the main route (adding 000 and strip 000) to create the second branch. Otherwise I have an error in Kamailio , is it expected ?? Feb 16 10:29:13 proxy2 /usr/sbin/kamailio[3837]: NOTICE: RU => 0003280033800 (Branch 0) * Adding 000 in main route Feb 16 10:29:13 proxy2 /usr/sbin/kamailio[3837]: NOTICE: RU => 3280033800 (Branch 0) * Strip "000" in main route * Timeout of first provider (going to main route again with an other branch) Feb 16 10:29:15 proxy2 /usr/sbin/kamailio[3840]: NOTICE: RU => 0003280033800 (Branch 1) Feb 16 10:29:15 proxy2 /usr/sbin/kamailio[3840]: NOTICE: RU => 3280033800 (Branch 1) * Call OK I will now remove the prefix & strip command in main route Feb 16 10:32:11 proxy2 /usr/sbin/kamailio[3951]: NOTICE: RU => 3280033800 (Branch 0) Feb 16 10:32:11 proxy2 /usr/sbin/kamailio[3951]: NOTICE: RU => 3280033800 (Branch 0) Feb 16 10:32:11 proxy2 /usr/sbin/kamailio[3951]: NOTICE: Branch to sip:3280033800@XXXXXXXXXXX * Timeout Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: NOTICE: RU => 3280033800 (Branch 1) Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: NOTICE: RU => 3280033800 (Branch 1) Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: ERROR: tm [t_fwd.c:1728]: t_forward_nonack(): no branches for forwarding Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: ERROR: tm [tm.c:1548]: _w_t_relay_to(): t_forward_noack failed Feb 16 10:32:13 proxy2 /usr/sbin/kamailio[3955]: ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (6/SL) Any suggestions ?

3 4

kamailio with oracle database
by eyas barhouk 17 Feb '19

17 Feb '19

hello dears i'm trying to run kamailio 5.1.7 with Oracle database and after building it from source with the needed module and installing Oracle Instant Client when i'm trying to run kamailio i get the following Error : ERROR: <core> [core/sr_module.c:498]: load_module(): could not open module </usr/local/lib64/kamailio/modules/db_oracle.so>: libclntsh.so.12.1: cannot open shared object file: No such file or directory so is there any way to make the libclntsh.so.12.1 open shared object ?? best regards Eyas

2 2

Re. SRTP configuration Rtpengine
by vinod mn 16 Feb '19

16 Feb '19

Hi I am not able to do SRTP configuration properly this the kamailio configuration *route[NATMANAGE] {* *rtpengine_manage("replace-origin replace-session-connection RTP/SAVP");}* I can see in SDP RTP/SAVP but still the packets are RTP. clients used linphone-android (media-encryption is SRTP ) and 3cx-windows-client

2 1

Log/Alerts Volume
by Daniel Greenwald 15 Feb '19

15 Feb '19

Curious how other folks are dealing with the volume of logs that Kamailio generates. We are currently sending them to syslog and alerting on WARN and above but the amount of alert noise is unbearable. For example (there are many variations): ERROR: <core> [core/tcp_read.c:297]: tcp_read_data(): error reading: Connection reset by peer INVITE:WARNING: sanity [sanity.c:776]: check_parse_uris(): failed to parse >From header INVITE:ERROR: <core> [core/parser/parse_from.c:75]: parse_from_header(): b ad From header The fact that these are WARN/ERROR level and from core makes me wonder how we can possibly make alerts relevant. Any input would be appreciated. Thanks, Daniel G

3 3

Memory allocator was called from cdp: diameter_avp.c:365
by Denys Pozniak 15 Feb '19

15 Feb '19

Hello! I have faced with Kamailio (5.1.7) crashes, probably it is connected to cdp module, please check the source of issue: 14(5649) INFO: cdp [receiver.c:455]: receiver_process(): receiver_process(): [diameter1.dev] Receiver process doing init on new process... 14(5649) INFO: cdp [receiver.c:188]: add_serviced_peer(): add_serviced_peer(): Adding serviced_peer_t to receiver for peer [diameter1.dev] 14(5649) INFO: cdp [receiver.c:460]: receiver_process(): receiver_process(): [diameter1.dev] Receiver process starting up... 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: -1 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: -1 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 16(5651) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 16 rank 1001: cdp [cdp_timer] 16(5651) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 16 rank 1001: cdp_avp [cdp_timer] 16(5651) DEBUG: cdp_avp [cdp_avp_mod.c:211]: cdp_avp_child_init(): Initializing child in module cdp_avp for rank [1001] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: acc [cdp_acceptor] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: uac [cdp_acceptor] 16(5651) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 16 rank 1001: ims_charging [cdp_timer] 16(5651) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 16 rank 1001: ims_dialog [cdp_timer] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: htable [cdp_acceptor] 15(5650) DEBUG: htable [htable.c:236]: child_init(): rank is (1000) 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: carrierroute [cdp_acceptor] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: dispatcher [cdp_acceptor] 16(5651) INFO: cdp [timer.c:205]: timer_process(): Timer process starting up... 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: cdp [cdp_acceptor] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: cdp_avp [cdp_acceptor] 15(5650) DEBUG: cdp_avp [cdp_avp_mod.c:211]: cdp_avp_child_init(): Initializing child in module cdp_avp for rank [1000] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: ims_charging [cdp_acceptor] 15(5650) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 15 rank 1000: ims_dialog [cdp_acceptor] 15(5650) INFO: cdp [acceptor.c:81]: acceptor_process(): Acceptor process starting up... 15(5650) DEBUG: cdp [tcp_accept.c:114]: create_socket(): create_sockets: create socket and bind for IPv4... 15(5650) WARNING: cdp [tcp_accept.c:121]: create_socket(): create_socket(): Trying to open/bind/listen on 10.10.10.10 port 38680 15(5650) WARNING: cdp [tcp_accept.c:146]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.10.10.10 port 38680 15(5650) INFO: cdp [acceptor.c:95]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... [root@10-10-10-10 kamailio]# 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: kex [tcp main process] 17(5652) DEBUG: kex [kex_mod.c:157]: child_init(): rank is (-4) 17(5652) DEBUG: <core> [sruid.c:106]: sruid_init(): root for sruid is [srid-5c658bbb-1614-] (0 / 19) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: corex [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: tm [tcp main process] 17(5652) DEBUG: tm [callid.c:137]: child_init_callid(): callid: ' 46ac84cd57961b27-5652(a)10.10.10.10' 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: tmx [tcp main process] 17(5652) DEBUG: tmx [tmx_mod.c:261]: child_init(): rank is (-4) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: sl [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: usrloc [tcp main process] 17(5652) DEBUG: <core> [sruid.c:106]: sruid_init(): root for sruid is [ulcx-5c658bbb-1614-] (0 / 19) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: registrar [tcp main process] 17(5652) DEBUG: <core> [sruid.c:106]: sruid_init(): root for sruid is [uloc-5c658bbb-1614-] (0 / 19) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: ctl [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: acc [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: uac [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: htable [tcp main process] 17(5652) DEBUG: htable [htable.c:236]: child_init(): rank is (-4) 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: carrierroute [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: dispatcher [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: cdp [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: cdp_avp [tcp main process] 17(5652) DEBUG: cdp_avp [cdp_avp_mod.c:211]: cdp_avp_child_init(): Initializing child in module cdp_avp for rank [-4] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: ims_charging [tcp main process] 17(5652) DEBUG: <core> [core/sr_module.c:942]: init_mod_child(): idx 17 rank -4: ims_dialog [tcp main process] 17(5652) DEBUG: <core> [core/local_timer.c:61]: init_local_timer(): timer_list between 0xa6e0a8 and 0xab20a8 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 7, 4, 0x7fbdd97d7bec), fd_no=0 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 8, 4, 0x7fbdd97d7c78), fd_no=1 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 9, 4, 0x7fbdd97d7d04), fd_no=2 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 10, 4, 0x7fbdd97d7d90), fd_no=3 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 11, 4, 0x7fbdd97d7e1c), fd_no=4 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 12, 4, 0x7fbdd97d7ea8), fd_no=5 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 13, 4, 0x7fbdd97d7f34), fd_no=6 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 15, 4, 0x7fbdd97d7fc0), fd_no=7 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 4, 4, 0x7fbdd97d804c), fd_no=8 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 16, 4, 0x7fbdd97d80d8), fd_no=9 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 17, 4, 0x7fbdd97d8164), fd_no=10 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 18, 4, 0x7fbdd97d81f0), fd_no=11 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 23, 4, 0x7fbdd97d827c), fd_no=12 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 24, 4, 0x7fbdd97d8308), fd_no=13 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 25, 4, 0x7fbdd97d8394), fd_no=14 17(5652) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa6dee0, 26, 4, 0x7fbdd97d8420), fd_no=15 5(5640) DEBUG: ims_charging [ro_timer.c:252]: ro_timer_routine(): getting expired ro-sessions 5(5640) DEBUG: ims_charging [ro_timer.c:211]: get_expired_ro_sessions(): my ticks are [32829471] 13(5648) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp receiver peer unknown Serviced Peers: --- 13(5648) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 16(5651) DEBUG: cdp [peermanager.c:263]: peer_timer(): peer_timer(): taking care of peers... 16(5651) DEBUG: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer diameter1.dev State 0 16(5651) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer diameter1.dev State Closed Event Start 16(5651) INFO: cdp [peerstatemachine.c:525]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer diameter1.dev 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: -1 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 16(5651) INFO: cdp [receiver.c:875]: peer_connect(): peer_connect(): Trying to connect to 10.10.10.20 port 3868 16(5651) INFO: cdp [receiver.c:954]: peer_connect(): peer_connect(): Peer diameter1.dev:3868 connected 14(5649) DEBUG: cdp [receiver.c:702]: receive_loop(): select_recv(): There is something on the fd exchange pipe 14(5649) DEBUG: cdp [receiver.c:711]: receive_loop(): select_recv(): fd exchange pipe says fd [8] for peer 0x7fbdd979e368:[diameter1.dev] 14(5649) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer diameter1.dev State Wait_Conn_Ack Event I_Rcv_Conn_Ack 14(5649) DEBUG: cdp [diameter_msg.c:184]: AAANewMessage(): AAANewMessage: param session received null and it's a request!! 14(5649) ERROR: cdp [peerstatemachine.c:634]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket 14(5649) DEBUG: cdp [diameter_msg.c:81]: AAABuildMsgBuffer(): AAABuildMsgBuffer(): len=184 14(5649) DEBUG: cdp [receiver.c:1013]: peer_send_msg(): peer_send_msg(): Pipe push [0x7fbdd97e0788] 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: 8 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 14(5649) DEBUG: cdp [receiver.c:756]: receive_loop(): select_recv(): There is something on the send pipe 14(5649) DEBUG: cdp [receiver.c:769]: receive_loop(): select_recv(): Send pipe says [0x7fbdd97e0788] 8 14(5649) DEBUG: cdp [diameter_msg.c:410]: AAAFreeMessage(): AAAFreeMessage: Freeing message (0x7fbdd97e0788) 257 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: 8 Recv.State: 0 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 16(5651) DEBUG: cdp [peermanager.c:143]: log_peer_list(): --- Peer List: --- 16(5651) DEBUG: cdp [peermanager.c:145]: log_peer_list(): State of peer: Wait_I_CEA FQDN: diameter1.dev Port: 3868 Is dynamic 16(5651) DEBUG: cdp [peermanager.c:149]: log_peer_list(): ------------------ 16(5651) DEBUG: cdp [session.c:396]: cdp_sessions_log(): ------- CDP Sessions ---------------- 16(5651) DEBUG: cdp [session.c:431]: cdp_sessions_log(): ------------------------------------- 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: 8 Recv.State: 1 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 14(5649) DEBUG: cdp [receiver.c:579]: do_receive(): receive_loop(): [diameter1.dev] Recv Version 1 Length 172 14(5649) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp_receiver_peer=diameter1.dev Serviced Peers: --- 14(5649) DEBUG: cdp [receiver.c:112]: log_serviced_peers(): Peer: diameter1.dev TCP Socket: 8 Recv.State: 2 14(5649) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 14(5649) DEBUG: cdp [receiver.c:1107]: receive_message(): receive_message(): [diameter1.dev] Recv msg 257 14(5649) DEBUG: cdp [peerstatemachine.c:90]: sm_process(): sm_process(): Peer diameter1.dev State Wait_I_CEA Event I_Rcv_CEA 14(5649) DEBUG: cdp [peerstatemachine.c:698]: count_Supported_Vendor_Id_AVPS(): Found 1 Supported_Vendor AVPS14(5649) DEBUG: cdp [peerstatemachine.c:681]: add_peer_application(): Application 0 of maximum 1 14(5649) DEBUG: cdp [peerstatemachine.c:750]: save_peer_applications(): Found Supported Vendor for Application 0: 10415 14(5649) DEBUG: cdp [peerstatemachine.c:681]: add_peer_application(): Application 1 of maximum 1 14(5649) DEBUG: cdp [diameter_msg.c:410]: AAAFreeMessage(): AAAFreeMessage: Freeing message (0x7fbdd97e0788) 257 14(5649) CRITICAL: <core> [core/mem/q_malloc.c:149]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten(28af, abcdefed)[0x7fbdd97e0c98:0x7fbdd97e0cd0]! Memory allocator was called from cdp: diameter_avp.c:365. Fragment marked by cdp: diameter_avp.c:142. Exec from core/mem/q_malloc.c:504. 5(5640) DEBUG: ims_charging [ro_timer.c:252]: ro_timer_routine(): getting expired ro-sessions 5(5640) DEBUG: ims_charging [ro_timer.c:211]: get_expired_ro_sessions(): my ticks are [32829472] 13(5648) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp receiver peer unknown Serviced Peers: --- 13(5648) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 15(5650) DEBUG: cdp [tcp_accept.c:221]: accept_loop(): accept_loop(): No connection attempts 5(5640) DEBUG: ims_charging [ro_timer.c:252]: ro_timer_routine(): getting expired ro-sessions 5(5640) DEBUG: ims_charging [ro_timer.c:211]: get_expired_ro_sessions(): my ticks are [32829473] 13(5648) DEBUG: cdp [receiver.c:106]: log_serviced_peers(): --- Receiver cdp receiver peer unknown Serviced Peers: --- 13(5648) DEBUG: cdp [receiver.c:114]: log_serviced_peers(): -------------------------------------------------------- 17(5652) CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 24 17(5652) DEBUG: <core> [core/tcp_main.c:3513]: handle_ser_child(): dead child 14, pid 5649 (shutting down?) 17(5652) DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa6dee0, 24, -1, 0x0) fd_no=16 called 0(5635) ALERT: <core> [main.c:739]: handle_sigs(): child process 5649 exited by a signal 6 0(5635) ALERT: <core> [main.c:742]: handle_sigs(): core was generated 0(5635) INFO: <core> [main.c:764]: handle_sigs(): terminating due to SIGCHLD 0(5635) DEBUG: <core> [main.c:766]: handle_sigs(): terminating due to SIGCHLD 16(5651) INFO: <core> [main.c:819]: sig_usr(): signal 15 received GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-114.el7 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html > This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/sbin/kamailio...Reading symbols from /usr/lib/debug/usr/sbin/kamailio.debug...done. done. [New LWP 5649] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `kamailio -f kamailio.cfg -E'. Program terminated with signal 6, Aborted. #0 0x00007fbde6015207 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install glibc-2.17-260.el7_6.3.x86_64 keyutils-libs-1.5.8-3.el7.x86_64 krb5-libs-1.15.1-37.el7_6.x86_64 libcom_err-1.42.9-13.el7.x86_64 libgcc-4.8.5-36.el7.x86_64 libselinux-2.5-14.1.el7.x86_64 libstdc++-4.8.5-36.el7.x86_64 libxml2-2.9.1-6.el7_2.3.x86_64 mariadb-libs-5.5.60-1.el7_5.x86_64 openssl-libs-1.0.2k-16.el7.x86_64 pcre-8.32-17.el7.x86_64 xz-libs-5.2.2-1.el7.x86_64 zlib-1.2.7-18.el7.x86_64 (gdb) bt full #0 0x00007fbde6015207 in raise () from /lib64/libc.so.6 No symbol table info available. #1 0x00007fbde60168f8 in abort () from /lib64/libc.so.6 No symbol table info available. #2 0x0000000000673469 in qm_debug_check_frag (qm=0x7fbdd94fd000, f=0x7fbdd97e0c98, file=0x7fbdde6bb992 "cdp: diameter_avp.c", line=365, efile=0x7dc6b7 "core/mem/q_malloc.c", eline=504) at core/mem/q_malloc.c:151 __FUNCTION__ = "qm_debug_check_frag" #3 0x00000000006765ec in qm_free (qmp=0x7fbdd94fd000, p=0x7fbdd97e0cd0, file=0x7fbdde6bb992 "cdp: diameter_avp.c", func=0x7fbdde6bd478 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7fbdde6bb7c0 "cdp") at core/mem/q_malloc.c:504 qm = 0x7fbdd94fd000 f = 0x7fbdd97e0c98 size = 140730526467984 next = 0x7a8db8 prev = 0x7a8db8 __FUNCTION__ = "qm_free" #4 0x0000000000680148 in qm_shm_free (qmp=0x7fbdd94fd000, p=0x7fbdd97e0cd0, file=0x7fbdde6bb992 "cdp: diameter_avp.c", func=0x7fbdde6bd478 <__FUNCTION__.7016> "AAAFreeAVP", line=365, mname=0x7fbdde6bb7c0 "cdp") at core/mem/q_malloc.c:1268 No locals. #5 0x00007fbdde696e61 in AAAFreeAVP (avp=0x7ffe610a0860) at diameter_avp.c:365 __FUNCTION__ = "AAAFreeAVP" #6 0x00007fbdde65c88f in AAAFreeAVPList (avpList=0x7fbdd97e07d8) at diameter_msg.c:396 avp_t = 0x7fbdd97e0cd0 avp = 0x7fbdd97e0bb8 #7 0x00007fbdde65cc4c in AAAFreeMessage (msg=0x7ffe610a0910) at diameter_msg.c:416 __FUNCTION__ = "AAAFreeMessage" #8 0x00007fbdde63f05e in Process_CEA (p=0x7fbdd979e368, cea=0x7fbdd97e0788) at peerstatemachine.c:804 avp = 0x7fbdd97e10b0 #9 0x00007fbdde638223 in sm_process (p=0x7fbdd979e368, event=I_Rcv_CEA, msg=0x7fbdd97e0788, peer_locked=0, sock=8) at peerstatemachine.c:166 result_code = -563425872 next_event = 32701 msg_received = 0 __FUNCTION__ = "sm_process" #10 0x00007fbdde6874be in receive_message (msg=0x7fbdd97e0788, sp=0x7fbde59538b0) at receiver.c:1147 avp1 = 0xde6b2c50 avp2 = 0x7fbdd97e0990 __FUNCTION__ = "receive_message" #11 0x00007fbdde67c5bb in do_receive (sp=0x7fbde59538b0) at receiver.c:598 cnt = 152 n = 152 version = 1 dst = 0x7fbdd97e1164 "" dmsg = 0x7fbdd97e0788 __FUNCTION__ = "do_receive" #12 0x00007fbdde68038e in receive_loop (original_peer=0x7fbdd979e368) at receiver.c:805 rfds = {__fds_bits = {256, 0 <repeats 15 times>}} efds = {__fds_bits = {0 <repeats 16 times>}} tv = {tv_sec = 0, tv_usec = 999998} n = 1 max = 21 cnt = 1 msg = 0x0 sp = 0x7fbde59538b0 sp2 = 0x7fbde59538b0 p = 0x7fbdd979e368 fd = 8 fd_exchange_pipe_local = 21 __FUNCTION__ = "receive_loop" #13 0x00007fbdde679aec in receiver_process (p=0x7fbdd979e368) at receiver.c:464 ---Type <return> to continue, or q <return> to quit--- __FUNCTION__ = "receiver_process" #14 0x00007fbdde62a7d5 in diameter_peer_start (blocking=0) at diameter_peer.c:289 pid = 0 k = -1 p = 0x7fbdd979e368 __FUNCTION__ = "diameter_peer_start" #15 0x00007fbdde61c9a8 in cdp_child_init (rank=0) at cdp_mod.c:243 __FUNCTION__ = "cdp_child_init" #16 0x000000000053b6b1 in init_mod_child (m=0x7fbde5885150, rank=0) at core/sr_module.c:943 __FUNCTION__ = "init_mod_child" #17 0x000000000053b353 in init_mod_child (m=0x7fbde5885dc8, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #18 0x000000000053b353 in init_mod_child (m=0x7fbde5886190, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #19 0x000000000053b353 in init_mod_child (m=0x7fbde58865d0, rank=0) at core/sr_module.c:939 __FUNCTION__ = "init_mod_child" #20 0x000000000053ba85 in init_child (rank=0) at core/sr_module.c:970 No locals. #21 0x0000000000424fe5 in main_loop () at main.c:1701 i = 4 pid = 5641 si = 0x0 si_desc = "udp receiver child=3 sock=10.10.10.10:5060\000\275\177\000\000\300\023\na\376\177\000\000\022\000\000\000\000\000\000\000\000\000\000\004\000\000\000\000\000\000\200\000\000\000\000\000\263\215z", '\000' <repeats 13 times>, "\220\026\na\376\177\000\000\207\"\003\346\275\177\000\000\260yw\000\000\000\000\000\060;\223\345\275\177\000" nrprocs = 4 woneinit = 1 __FUNCTION__ = "main_loop" #22 0x000000000042b994 in main (argc=4, argv=0x7ffe610a1778) at main.c:2642 cfg_stream = 0x103a020 c = -1 r = 0 tmp = 0x0 tmp_len = 0 port = 0 proto = 0 options = 0x758c10 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 1364069336 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x0 p = 0x0 st = {st_dev = 19, st_ino = 68292, st_nlink = 2, st_mode = 16832, st_uid = 995, st_gid = 994, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1550156643, tv_nsec = 630000000}, st_mtim = {tv_sec = 1550158563, tv_nsec = 502470819}, st_ctim = {tv_sec = 1550158563, tv_nsec = 502470819}, __unused = {0, 0, 0}} __FUNCTION__ = "main" (gdb) version: kamailio 5.1.7 (x86_64/linux) 567df3 flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, 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_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 567df3 compiled on 02:06:09 Feb 2 2019 with gcc 4.8.5 -- BR, Denys Pozniak

2 2

Assemble struct sip_uri back to string?
by Ivan Ribakov 15 Feb '19

15 Feb '19

Hi all, does anyone know if there is a C function available in some module/header that assembles parsed sip_uri struct back into a single buffer? I’ve been looking at msg_parser.h (where sip_uri struct is defined) and parse_uri.h, but I can’t see anything of that kind. Thanks in advance, Ivan

3 3

Fwd: pv_buffer_size config value actually ignored?
by Enrico Bandiera 14 Feb '19

14 Feb '19

---------- Forwarded message --------- From: Enrico Bandiera <enrico.bandiera(a)cloud.timenet.it> Date: mer 13 feb 2019 alle ore 09:18 Subject: Re: [SR-Users] pv_buffer_size config value actually ignored? To: Daniel-Constantin Mierla <miconda(a)gmail.com> Hello Daniel, yes we do use that $avp for a log line which is actually a big json, the $avp is composed by multiple jansson_append calls and at the end an xlog() calls prints it Could it also be that I'm miscalculating because of the encoding? 4K utf8 characters could be more than 4K (but I don't think there are so many multibytes characters to let it reach the 8K limit) Il giorno mer 13 feb 2019 alle ore 09:15 Daniel-Constantin Mierla < miconda(a)gmail.com> ha scritto: > Hello, > > where do you use that avp, because for the avp value itself, that buffer > is not used -- avp values are stored in shared memory. > > Do you use that avp in xlog() or other functions parameters? > > Cheers, > Daniel > On 13.02.19 09:10, Enrico Bandiera wrote: > > Hi, I'm having some strange issues with a somewhat big $avp value, when it > reaches a size of about 4K I get this error: > > 29(47) ERROR: <core> [core/pvapi.c:1452]: pv_printf(): no more space for > spec value > 29(47) ERROR: <core> [core/pvapi.c:1461]: pv_printf(): buffer overflow – > increase the buffer size... > > In the docs I read that the default pv_buffer_size is 8K, I still tried to > enforce it to something bigger and checked the logs to be sure it was set: > > 0(384) DEBUG: <core> [core/pvapi.c:2062]: pv_init_buffer(): PV print > buffer initialized to [40][16384] > > But still when reaching the 4K size inside the $avp that error comes out, > is there any limit I'm not aware of? > > Thanks, > Enrico. > > _______________________________________________ > Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com > Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC, USA -- www.asipto.com > >

2 6

TM Module - Unfortunately error on sending to next hop occurred (477/TM)
by Ilie Soltanici 14 Feb '19

14 Feb '19

Hi List, Can someone give a hint related to this issue, please? On other messages, I found that this problem may happen why variable $du is empty, but in my case looks that it's present: Config File: if (!t_relay()) { switch ($retcode) { case -1: xlogl("L_ERR", "[$cfg(route)] Generic Internal Error\n"); xlogl("L_ERR", "[$cfg(route)] | $du/$ru |\n"); break; Log File: [RELAY] Generic Internal Error [RELAY] | sip:192.168.180.23:15109/sip:1003@ 192.168.180.23:15109 | sl [sl_funcs.c:372]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (1/SL) Also, as I understand this may happen when there is a problem on the physical network, i'm not sure that is my case - because kamailio and asterisk are 2 VM's running on the same Physical Server, and both their interfaces are connected to the same Virtual Switch. There is no firewalls/selinux on those servers. Can someone help please?

2 1

Kamailio/Dispatcher failure routing to SRV record
by Jesse Strahn 13 Feb '19

13 Feb '19

Hi all, I'm hoping someone can help me with this as I am baffled. I have a server running Kamailio with dispatcher. I am trying to direct calls from kamailio to an SRV record but am receiving a 404 error on the calls. If I instead place one of the hostnames from the SRV record in my dispatcher.list, the call completes fine. Contents of dispatcher.list look like: 1 sip:bvr.production.instance:5060 Nslookup from the Kamailio server for SRV record: nslookup -type=SRV _sip._udp.bvr.production.instance Server: 10.0.0.2 Address: 10.0.0.2#53 Non-authoritative answer: _sip._udp.bvr.production.instance service = 1 10 5060 ip-10-100-79-143.production.instance. _sip._udp.bvr.production.instance service = 1 10 5060 ip-10-100-96-92.production.instance. Again, if I put 1 sip: ip-10-100-96-92.production.instance:5060 into the dispatcher.list, the call routes fine. Is there some configuration within Kamailio required to route to an SRV record in this way? I haven't found anything indicating that is the case. Any help is greatly appreciated. Thanks, Jesse

2 2

Mysql to hastable conversion
by Duarte Rocha 13 Feb '19

13 Feb '19

Greetings, I have Kamailio has an SBC and i'm using a MySQL database to store all the relevant configurations and settings regarding the NAP's, Users, Numbers, etc. That being said, i'm having lots of of performance issues originated by the queries. In order to solve that i think the best way to proceed would be to implement hashtables. However, i would like to keep Sql DB's for easier configuration and having them automatically transformed into hashtables. Is there a simple way to do this? As i see, the htable module is able to load from a DB, but i understand it, the table should be already in "hashtable form". Does kamailio has any way to solve this or should i use external tools? Best Regards, Duarte Rocha

2 1

kamailio with oracle data base
by eyas barhouk 13 Feb '19

13 Feb '19

Hello Community i'm trying to build kamailio on top of oracle D.B so is there any way to configure kamailio to deal with Oracle D.B and call functions from it ? Thanks in advance. Regards Eyas

4 9

Cannot get message routing for websockets "invalid" URI
by Sergey Safarov 13 Feb '19

13 Feb '19

I have configured websocket usage using this module description https://kamailio.org/docs/modules/devel/modules/websocket.html Added registrar and usrloc modules Registration saved using this block route[REGISTRAR] { if(!is_method("REGISTER")) return; if (!save("location")) { xlog("L_INFO", "Location save error\n"); sl_reply_error(); } } Now in database i can see WebRTC client registration { "jsonrpc": "2.0", "result": { "Domains": [{ "Domain": { "Domain": "location", "Size": 1024, "AoRs": [{ "Info": { "AoR": "1000", "HashID": 924766747, "Contacts": [{ "Contact": { "Address": "sips:1000@df7jal23ls0d.invalid ;rtcweb-breaker=no;transport=wss", "Expires": 155, "Q": -1, "Call-ID": "0c818ac1-5e77-bd4c-b7fe-a135d6c6a4bf", "CSeq": 61442, "User-Agent": "IM-client/OMA1.0 sipML5-v1.2016.03.04", "Received": "[not set]", "Path": "[not set]", "State": "CS_SYNC", "Flags": 0, "CFlags": 0, "Socket": "tls:192.168.2.10:7443", "Methods": -1, "Ruid": "uloc-5c643a67-4b56-1", "Instance": "[not set]", "Reg-Id": 0, "Server-Id": 0, "Tcpconn-Id": 2, "Keepalive": 0, "Last-Keepalive": 1550074434, "Last-Modified": 1550074434 } }] } } ], "Stats": { "Records": 1, "Max-Slots": 1 } } }] }, "id": 19493 } Now I try deliver call to WebRTC client. Kamailio receives message INVITE sip:1001@192.168.30.2 SIP/2.0 Via: SIP/2.0/UDP 192.168.30.2:45060;rport;branch=z9hG4bK5gaK3B38egZQH Route: <sip:192.168.2.10> Max-Forwards: 70 From: "" <sip:0000000000@192.168.30.2>;tag=8e7Za8pD6pcKg To: <sip:1001@192.168.30.2> Call-ID: 989274f0-aa4d-1237-08a1-94b86deaeed5 CSeq: 483510 INVITE Contact: <sip:mod_sofia@192.168.30.2:45060> User-Agent: FreeSWITCH-mod_sofia/1.8.4+git-20181228T070140Z~a0377e9677~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, path, replaces Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Content-Type: application/sdp Content-Disposition: session Content-Length: 621 X-FS-Support: update_display,send_info Remote-Party-ID: <sip:0000000000@192.168.30.2 >;party=calling;screen=yes;privacy=off Expected that Kamailio using follow config block route message to WEbRTC client via websocket. route[FROM_FS] { record_route(); if (!lookup("location")) { $var(rc) = $rc; t_newtran(); switch ($var(rc)) { case -1: case -3: send_reply("404", "Not Found"); exit; case -2: send_reply("405", "Method Not Allowed"); exit; } } route(RELAY); exit; } But really Kamailio try resolve "sips:1000@df7jal23ls0d.invalid" URI via DNS and deliver for non locally connected device 3(19341) exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=238 a=16 n=if 3(19341) exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=231 a=41 n=isflagset 3(19341) exec: *** cfgtrace:request_route=[DEFAULT_ROUTE] c=[/usr/local/etc/kamailio/kamailio.cfg] l=232 a=5 n=route 3(19341) exec: *** cfgtrace:request_route=[FROM_FS] c=[/usr/local/etc/kamailio/kamailio.cfg] l=266 a=24 n=record_route 3(19341) exec: *** cfgtrace:request_route=[FROM_FS] c=[/usr/local/etc/kamailio/kamailio.cfg] l=281 a=16 n=if 3(19341) exec: *** cfgtrace:request_route=[FROM_FS] c=[/usr/local/etc/kamailio/kamailio.cfg] l=267 a=25 n=lookup 3(19341) DEBUG: registrar [lookup.c:255]: lookup_helper(): contact for [1000] found by address 3(19341) exec: *** cfgtrace:request_route=[FROM_FS] c=[/usr/local/etc/kamailio/kamailio.cfg] l=281 a=5 n=route 3(19341) exec: *** cfgtrace:request_route=[RELAY] c=[/usr/local/etc/kamailio/kamailio.cfg] l=289 a=16 n=if 3(19341) exec: *** cfgtrace:request_route=[RELAY] c=[/usr/local/etc/kamailio/kamailio.cfg] l=286 a=24 n=t_relay 3(19341) DEBUG: tm [t_lookup.c:1326]: t_newtran(): msg id=2 , global msg id=2 , T on entrance=0 3(19341) DEBUG: tm [t_lookup.c:483]: t_lookup_request(): start searching: hash=7468, isACK=0 3(19341) DEBUG: tm [t_lookup.c:441]: matching_3261(): RFC3261 transaction matching failed - via branch [z9hG4bK72v4614F91BXr] 3(19341) DEBUG: tm [t_lookup.c:666]: t_lookup_request(): no transaction found 3(19341) DEBUG: tm [t_hooks.c:348]: run_reqin_callbacks_internal(): trans=0x7fbb0b1d0d40, callback type 1, id 0 entered 3(19341) DEBUG: <core> [core/md5utils.c:67]: MD5StringArray(): MD5 calculated: 07ad473ba02a6d3a4f8753a378c102e8 3(19341) DEBUG: tm [t_funcs.c:324]: t_relay_to(): new INVITE 3(19341) DEBUG: tm [t_reply.c:596]: _reply_light(): reply sent out. buf=0x7fbb0f256750: SIP/2.0 100 trying -..., shmem=0x7fbb0b1e75d8: SIP/2.0 100 trying - 3(19341) DEBUG: tm [t_reply.c:607]: _reply_light(): finished 3(19341) DEBUG: <core> [core/dns_cache.c:527]: _dns_hash_find(): (_sips._tcp.df7jal23ls0d.invalid(31), 33), h=232 3(19341) DEBUG: <core> [core/resolve.c:967]: get_record(): skipping 1 NS (p=0x561007b83e71, end=0x561007b83ebc) 3(19341) DEBUG: <core> [core/resolve.c:980]: get_record(): parsing 0 ARs (p=0x561007b83ebc, end=0x561007b83ebc) 3(19341) DEBUG: <core> [core/dns_cache.c:761]: dns_cache_mk_bad_entry(): (_sips._tcp.df7jal23ls0d.invalid, 33, 60, 1) 3(19341) DEBUG: <core> [core/dns_cache.c:701]: dns_cache_add(): adding _sips._tcp.df7jal23ls0d.invalid(31) 33 (flags=1) at 232 3(19341) DEBUG: <core> [core/dns_cache.c:527]: _dns_hash_find(): (df7jal23ls0d.invalid(20), 1), h=139 3(19341) DEBUG: <core> [core/resolve.c:967]: get_record(): skipping 1 NS (p=0x561007b83e66, end=0x561007b83eb1) 3(19341) DEBUG: <core> [core/resolve.c:980]: get_record(): parsing 0 ARs (p=0x561007b83eb1, end=0x561007b83eb1) 3(19341) DEBUG: <core> [core/dns_cache.c:761]: dns_cache_mk_bad_entry(): (df7jal23ls0d.invalid, 1, 60, 1) 3(19341) DEBUG: <core> [core/dns_cache.c:701]: dns_cache_add(): adding df7jal23ls0d.invalid(20) 1 (flags=1) at 139 3(19341) ERROR: <core> [core/resolve.c:1698]: sip_hostport2su(): could not resolve hostname: "df7jal23ls0d.invalid" 3(19341) ERROR: tm [ut.h:309]: uri2dst2(): failed to resolve "df7jal23ls0d.invalid" 3(19341) ERROR: tm [t_fwd.c:1735]: t_forward_nonack(): failure to add branches 3(19341) DEBUG: tm [t_funcs.c:334]: t_relay_to(): t_forward_nonack returned error -478 (-478) 3(19341) DEBUG: tm [t_funcs.c:352]: t_relay_to(): -478 error reply generation delayed 3(19341) exec: *** cfgtrace:request_route=[RELAY] c=[/usr/local/etc/kamailio/kamailio.cfg] l=287 a=24 n=sl_reply_error 3(19341) ERROR: sl [sl_funcs.c:372]: sl_reply_error(): stateless error reply used: Unresolvable destination (478/SL) 3(19341) exec: *** cfgtrace:request_route=[RELAY] c=[/usr/local/etc/kamailio/kamailio.cfg] l=289 a=2 n=exit 3(19341) DEBUG: <core> [core/receive.c:353]: receive_msg(): request-route executed in: 12632 usec 3(19341) DEBUG: tm [t_lookup.c:1490]: t_unref(): delayed error reply generation(-478) 3(19341) DEBUG: tm [t_reply.c:1650]: cleanup_uac_timers(): RETR/FR timers reset 3(19341) DEBUG: tm [t_reply.c:596]: _reply_light(): reply sent out. buf=0x7fbb0f2571f0: SIP/2.0 478 Unresolv..., shmem=0x7fbb0b1e7860: SIP/2.0 478 Unresolv 3(19341) DEBUG: tm [t_reply.c:607]: _reply_light(): finished Looks I missed some thing in message routing, But cannot find what. Please point me how to properly route call for this case.

1 0

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