From khorsmann@gmail.com Sat Nov 9 19:06:36 2019 From: Karsten Horsmann To: sr-users@lists.kamailio.org Subject: Re: [SR-Users] dispatch REGISTER over TLS Date: Sat, 09 Nov 2019 19:06:18 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1171330716==" --===============1171330716== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, For example you can use the controllflag -c and -f path/to/kamailio.cfg to see on what ports and technologies your Kamailio is listing. Here you see an test instance only with udp and tcp (no tls). So if I would try your dispatcher config it wouldn't work (and of course the ips don't match). BTW for debugging purpose maybe starting with tcp is easier and if that works you can attach tls to your config. k1:~# kamailio -c -f /etc/kamailio/kamailio.cfg 0(15313) INFO: [core/sctp_core.c:74]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: 10.10.10.1 [10.10.10.1]:5060 udp: 10.10.10.1 [10.10.10.1]:5062 udp: 192.168.122.100 [192.168.122.100]:5060 tcp: 10.10.10.1 [10.10.10.1]:5060 tcp: 192.168.122.100 [192.168.122.100]:5060 sthustfo schrieb am Sa., 9. Nov. 2019, 18:34: > Thanks Karsten. Instead of SIP server, I ran a simple socket listener > program to see if dispatcher is attempting to connect to it or not. But it > did not receive any client connection attempts. So after looking at the > logs, I found below log statements. Any idea why this might have happened? > > 0(3004) ERROR: dispatcher [dispatch.c:411]: pack_dest(): non-local socket > > 0(3004) WARNING: dispatcher [dispatch.c:816]: ds_load_list(): unable to > add destination sip:10.0.0.100:5061;transport=3Dtls to set 1007 -- skipping > > dispatcher.list file pasted below contains the address. Why would this be > an error? > > # setid(integer) destination(sip uri) flags (integer, optional), > priority(int,opt), attrs (str,optional) > 1007 sip:10.0.0.100:5061;transport=3Dtls 0 3 socket=3Dtls:10.0.0.14:5061; > ping_from=3Dsip:10.0.0.14 > > > On Sat, Nov 9, 2019 at 9:35 PM Karsten Horsmann > wrote: > >> Hi, >> >> I guess the dispatcher is not able to get an 200 okay from your upstream >> tls / sipserver. And so the dispatcher did his job. Find no active >> dispatcher targets, then told you that. >> >> You find more about the dispatcher state with kamctl dispatcher dump or >> kamcmd dispatcher.list >> >> And read the module docu of dispatcher, they explain you the states of >> the commands above. >> >> Hints here: >> >> Reading dispatcher docu, understand the states, read tls (maybe that's >> your root cause). >> >> >> Cheers >> Karsten >> >> sthustfo schrieb am Sa., 9. Nov. 2019, 14:56: >> >>> Thanks David. You are right, ds_select_dst() is failing and error log is >>> shown. >>> >>> 9(2528) ERROR: {1 9733 REGISTER e4rvba563tlnj0i3a906qa} dispatcher >>> [dispatch.c:2032]: ds_manage_routes(): no destination sets >>> 9(2528) exec: {1 9733 REGISTER e4rvba563tlnj0i3a906qa} *** >>> cfgtrace:request_route=3D[DISPATCH] c=3D[/etc/kamailio/kamailio.cfg] l=3D= 970 a=3D25 >>> n=3Dxdbg >>> 9(2528) DEBUG: {1 9733 REGISTER e4rvba563tlnj0i3a906qa}