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?
Thanks Karsten. The setup consists of client connecting to kamailio over WS
(10.0.0.14). Kamailio needs to proxy the requests to SIP server
(10.0.0.100) over TLS. As per your suggestion, I modified the dispatch list
as below
# setid(integer) destination(sip uri) flags (integer, optional),
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} ***
Please post the config around the ds_select
What that’s saying is basically it could not find a destination for the set
you are asking for.
Either because the setid you provide with the function doesn’t exist, or
the destination is not responding to the pings.
On Sat, 9 Nov 2019 at 10:33,
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
Is kamailio listening in that socket?
On Sat, 9 Nov 2019 at 17:34, sthustfo wrote:
> 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
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
Please paste the “listen” parameters from the config.
On Sat, 9 Nov 2019 at 18:04, David Villasmil
wrote:
> Is kamailio listening in that socket?
>
> On Sat, 9 Nov 2019 at 17:34, sthustfo wrote:
>
>> Thanks Karsten. Instead of SIP server, I ran a simple socket listener
>> program to see if
Greetings,
I'm trying to configure kamailio to get OPTIONS response, but it does
not working properly.
After a successful REGISTER, I send OPTIONS first time, get Proxy-
Authenticate header to calculate Proxy-Authorization, and resend
OPTIONS with Proxy-Authenticate header, but server follows
You need to have a TLS listen like
https://kamailio.org/docs/tls-1.3.x.html#AEN192
On Sun, 10 Nov 2019 at 00:32, David Villasmil <
david.villasmil.w...@gmail.com> wrote:
> From what you paste, 8080 is not TLS
>
> On Sat, 9 Nov 2019 at 23:29, sthustfo wrote:
>
>> Kamailio listening on WS only
Well, I was hoping there was a way to proxy from non secure (WS) to secure
one (TLS) upstream.
On Sun, Nov 10, 2019 at 6:12 AM David Villasmil <
david.villasmil.w...@gmail.com> wrote:
> You need to have a TLS listen like
>
> https://kamailio.org/docs/tls-1.3.x.html#AEN192
>
>
> On Sun, 10 Nov
>From what you paste, 8080 is not TLS
On Sat, 9 Nov 2019 at 23:29, sthustfo wrote:
> Kamailio listening on WS only as seen from below log snippet. As I
> mentioned earlier, talks pure WS (no WSS) with the clients, and TLS towards
> the SIP server.
>
> 0(3268) INFO: [core/sctp_core.c:74]:
Kamailio listening on WS only as seen from below log snippet. As I
mentioned earlier, talks pure WS (no WSS) with the clients, and TLS towards
the SIP server.
0(3268) INFO: [core/sctp_core.c:74]: sctp_core_check_support():
SCTP API not enabled - if you want to use it, load sctp module
Listening
13 matches
Mail list logo
