Additional notes with ubuntu 18.04
Thought i would try compiling against openssl 1.0.2u to see what effect that
had. Although open ssl would compile correctly, tlsa would complain when
trying to link against 1.02u.
Solution was to re-rerun the openssl ./config script with the suggested
@miconda Agreed, have opened an issue in the ruxc repo, was more of an interim
fix, but i think it makes absolute sense to have it at lib level
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Just had a bash at adding this myself, and it seems to work nicely for my
usecase...
Adding this changing calls to post or get, and defining a parameter for retry
attempts
```
ruxc_http_get(_http_request, _http_response);
//Retry enabled, either have a server error code or a connection
### Description
Could a module parameter be added to retry a request _n_ number of times in the
event of a connection or server failure, without having to write a tedious bit
of boiler plate config to catch failure response codes and retry.
### Expected behavior
A http(s) post or get is
### Description
Would it be possible to have the debug messages from libruxc entered into the
kamailio logs, as thats much more useful than -1 for diagnosing connection
failures, as well as the uri of the failing request?
### Expected behavior
Some diagnostic data passed up from libruxc
Unfortunatly the additional switches made no effect, i have however found a
work around...
If you set the `LIBSSL_STATIC_SRCLIB` to yes, and alter the path to where
ubuntu stores the static libs from packages it compiles with no warnings and
loads as expected.
```
# set to yes when wanting to
### Description
Building TLSA module on ubuntu 18.04 results in a compiler warning and an
undefined symbol error when attempting to load module.
### Troubleshooting
Reproduction
Make module and attempt to load it
Debugging Data
```
N/A
```
Log Messages
Compiler output
```
@miconda it was a very naïve modification so it just created a new connection
and never reused which was a horrible solution
Re-reading through tcp_main.c I had a spark of inspiration when I noticed that
`tcpconn_rm` checked if `c->extra_data` had a value other than 0 to determine
if
I would agree its a connection reuse issue, #1107 is probably a more relevant
discussion to have.
As an experiment I tried a modified version of tcp_main.c with the connection
lookup modified to not return an existing connection and the expected behaviour
was observed.
Thinking the further
Debug output attached, in the full version from about line 8050 is the
dispatcher activity
[kamailio-debug-dispatcher-sni-full.log](https://github.com/kamailio/kamailio/files/6623779/kamailio-debug-dispatcher-sni-full.log)
Certainly, i spent yesterday debugging and going through the logs and im
thinking the issue may be the (ab)use of dispatcher to ping the same
destination presenting as different domains. The destinations are intentially
the same in the sample dispatcher.list in the first post
```1
@arkadiam Pretty sure we are both trying to do same thing judging by your
dispatcher and routing config, multi domain telephony integration with a cloud
comms platform?
Its frustrating that SNI is being flakey as it works very nicely if you have a
single cert with multiple SAN's defined but
I was half way through writing a less detailed version of a very similar issue
i am having too, having to send options presenting a specific servername and
cert
same environment as well (ubuntu 18.04, kam 5.5.0)
I have noticed that the xavp sni settings seems to only work on one thread as
No afraid not, I need to send all traffic to a destination using a specific tls
client config, including dispatcher pings, that only sets the from header of
the options message, in a request route I just set the tls xavp with suitable
values to force a specific tls client profile.
--
You are
Is it possible to specify a specific server name/server id for dispatcher to
use to send pings with (and in outgoing requests)
It seems I can't (or haven't noticed in the docs) an event route I could use to
set the xavp, as tm:local-request happens to late to use there. As an aside
why isn't
Originally i had everything being backed by ODBC tables, but could never get
the hangs to stop, usually presenting it self as an inability to auth
registrations randomly. I think i also stumbled upon some hard coded MySQL
syntax specific queries in various modules typically using the MySQL
I worked around this issue (it's more a sql azure thing than kamailio) by
creating a user on the dB and setting default language, db and schema on the
login that was enough to get it to connect.
Be warned though using sql azure with either freetds or the ms Linux driver I
experienced random
Hi
Is there any mechanism to add a contact and rr headers to the option messages
generated by dispatcher?
I have a need for both headers to be present otherwise the message gets
rejected at the proxy im trying to connect to, the content of the headers in
my use case is the from address, so
18 matches
Mail list logo
