[SR-Users] RTP Engine early media issue one to many
Hi everyone, in my environment (kamailio - http API for retrieve destinations - rtpengine) it is used a lot parallel forking, the flow is as follows: A -> INVITE -> Kamailio -> http API/rtjson / t_relay -> Kamailio -> client B / C / D (only one accepting the call) Kamailio loops to itself to have a parallel forking, it involves rtpengine correctly. Both audio and video work during call. The issue comes with one of destinations sending 183 with SDP, the caller will send then a video preview as early media before call is established. I noticed that only the first one "asking" for early media is receiving this video preview (sometimes none of clients requesting it), all others are ignored by caller. This is a case of 1-to-many, I searched a lot about this but it seems at least not working or not supported, could you confirm that there is no configuration trick possible to make work this early media to many destinations? Another issue in above call flow, is that if client B is receiving correctly this early media video and client C answers the call (200OK) client C does not see any video, audio working and video is completely missing from rtp, only a reinvite makes possible to see video. Is this a client side only issue (so only solution is the reinvite) or there is something missing on my kamailio configuration? Thanks Filippo __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] reinvite with 2 video lines in SDP
Hello, thanks for replay. I will check how to make the script as per your suggestion, many thanks for it. Filippo Il giorno lun 21 feb 2022 alle ore 16:15 Daniel-Constantin Mierla < mico...@gmail.com> ha scritto: > Hello, > > if you want to run kamailio development branch, then you should be able > to do it with the body line iterator: > > * > > https://www.kamailio.org/docs/modules/devel/modules/textopsx.html#textopsx.f.bl_iterator_start > > For stable branches at this moment I would run some inline > Lua/Python/JavaScript/... script that builds the new body as wanted and > then use KSR.textops.set_body(...) function. > > If you use rtpengine/rtpproxy, then you should also do msg_apply_changes(). > > Cheers, > Daniel > > On 21.02.22 15:55, Filippo Graziola wrote: > > Hi all, I'm facing a strange behaviour from a client (iOS application > > based on pjsip library) which is doing as follow when receiving a call > > (on phone locked): > > - accept the call rejecting video (m=video 0...) in SDP > > - reinvite to negotiate again video media > > > > Specifically the reinvite passing through kamailio (+rtpengine) has > > this SDP body after rtpengine offer (the client use TLS so I can't see > > the original message): > > > > v=0 > > o=- 3854443139 3854443142 IN IP4 PUBLIC_RTP_ENGINE_IP > > s=pjmedia > > b=AS:386 > > t=0 0 > > a=X-nat:0 > > m=audio 46734 RTP/AVP 8 101 > > c=IN IP4 PUBLIC_RTP_ENGINE_IP > > b=TIAS:96000 > > a=ssrc:1456418416 cname:441b90ac6db72f22 > > a=rtpmap:8 PCMA/8000 > > a=rtpmap:101 telephone-event/8000 > > a=fmtp:101 0-16 > > a=sendrecv > > a=rtcp:46735 > > m=video 0 RTP/AVP 96 > > c=IN IP4 PUBLIC_RTP_ENGINE_IP > > b=TIAS:256000 > > m=video 46776 RTP/AVP 98 > > c=IN IP4 PUBLIC_RTP_ENGINE_IP > > b=TIAS:256000 > > a=rtpmap:98 H264/9 > > a=fmtp:98 profile-level-id=42e01e; packetization-mode=1 > > a=sendrecv > > a=rtcp:46777 > > > > from this I can understand that the client is doing something strange, > > because there is still the rejection line (I know that this question > > should go to the pjsip guys) but I would also like to know if it is > > possible to "clean" this sdp by kamailio. > > A few clients receiving this sdp are answering with only audio. > > Reading the docs, sdpops/textops modules allow modifying lines by > > prefix or media, but till now I have no luck to exclude only the line > > "m=video 0 RTP/AVP 96" and his attributes without touching the correct > > video request. Could someone please give me some hints on it? > > > > __ > > Kamailio - Users Mailing List - Non Commercial Discussions > > * sr-users@lists.kamailio.org > > Important: keep the mailing list in the recipients, do not reply only to > the sender! > > Edit mailing list options or unsubscribe: > > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > -- > Daniel-Constantin Mierla -- www.asipto.com > www.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio Advanced Training - Online > Feb 21-24, 2022 (America Timezone) > * https://www.asipto.com/sw/kamailio-advanced-training-online/ > > __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] reinvite with 2 video lines in SDP
Hi all, I'm facing a strange behaviour from a client (iOS application based on pjsip library) which is doing as follow when receiving a call (on phone locked): - accept the call rejecting video (m=video 0...) in SDP - reinvite to negotiate again video media Specifically the reinvite passing through kamailio (+rtpengine) has this SDP body after rtpengine offer (the client use TLS so I can't see the original message): v=0 o=- 3854443139 3854443142 IN IP4 PUBLIC_RTP_ENGINE_IP s=pjmedia b=AS:386 t=0 0 a=X-nat:0 m=audio 46734 RTP/AVP 8 101 c=IN IP4 PUBLIC_RTP_ENGINE_IP b=TIAS:96000 a=ssrc:1456418416 cname:441b90ac6db72f22 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv a=rtcp:46735 m=video 0 RTP/AVP 96 c=IN IP4 PUBLIC_RTP_ENGINE_IP b=TIAS:256000 m=video 46776 RTP/AVP 98 c=IN IP4 PUBLIC_RTP_ENGINE_IP b=TIAS:256000 a=rtpmap:98 H264/9 a=fmtp:98 profile-level-id=42e01e; packetization-mode=1 a=sendrecv a=rtcp:46777 from this I can understand that the client is doing something strange, because there is still the rejection line (I know that this question should go to the pjsip guys) but I would also like to know if it is possible to "clean" this sdp by kamailio. A few clients receiving this sdp are answering with only audio. Reading the docs, sdpops/textops modules allow modifying lines by prefix or media, but till now I have no luck to exclude only the line "m=video 0 RTP/AVP 96" and his attributes without touching the correct video request. Could someone please give me some hints on it? __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] serial forking kamailio - twilio
Hi, thanks for answering. Based on your answer I was able to move the call sequence to Twilio instead of handling in kamailio, now I send the INVITE from kamailio to Twilio and in Twilio make a request to my own API endpoint to create the call sequence and call logs. thanks Filippo I think what you’re asking is: if a call is answered and hung up, can Kamailio make another call to somewhere else? If so, the answer is no; proxies just can’t do that. Forking deals with the management early-stage requests during their pendency. Once a final dispositive reply for a request is received from the upstream UA, the transaction is finished. Kamailio cannot initiate new transactions in that sense. So, to roll over to another route after an answer+hangup, you’d need to implement this on the calling UA side. Is that an accurate understanding of your question? Il giorno lun 19 lug 2021 alle ore 18:18 Filippo Graziola < filippo.grazi...@gmail.com> ha scritto: > Hi all, > > I have a question for my kamailio configuration which works like this: > > - INVITE arrives to kamailio > - HTTP async request to API endpoint > - Resume, use of rtjson module for parallel forking and loop to kamailio > itself > - One of the invite is "transformed" in serial forking with rtjson module > and it is sent with a delay to TWILIO SIP Domain (landline/mobile phone > numbers) > > Twilio is giving me some troubles because it answers with a 200 OK but the > call it is still in establishing/ringing on the "landline" side and as > expected when reaching the timeout (no answer from phone number on TWILIO > side) kamailio is receiving a BYE. > > Now the question, how to handle next number to call through Twilio? > I was thinking of using rtjson_next_route() when handling the in-dialog > BYE but as it is not a failure route so it does not work, or I'm doing it > wrong. > > Thanks in advance for any help/hint. > > Filippo > > __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] serial forking kamailio - twilio
Hi all, I have a question for my kamailio configuration which works like this: - INVITE arrives to kamailio - HTTP async request to API endpoint - Resume, use of rtjson module for parallel forking and loop to kamailio itself - One of the invite is "transformed" in serial forking with rtjson module and it is sent with a delay to TWILIO SIP Domain (landline/mobile phone numbers) Twilio is giving me some troubles because it answers with a 200 OK but the call it is still in establishing/ringing on the "landline" side and as expected when reaching the timeout (no answer from phone number on TWILIO side) kamailio is receiving a BYE. Now the question, how to handle next number to call through Twilio? I was thinking of using rtjson_next_route() when handling the in-dialog BYE but as it is not a failure route so it does not work, or I'm doing it wrong. Thanks in advance for any help/hint. Filippo __ Kamailio - Users Mailing List - Non Commercial Discussions * sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] kamailio 5.4.3 ubuntu 20.04 tls - http_async_client
Hello, here are the results for ssl packages (dpkg -l | grep ssl): ii libcrypt-openssl-bignum-perl 0.09-1build3 amd64Perl module to access OpenSSL multiprecision integer arithmetic libraries ii libcrypt-openssl-random-perl 0.15-1build2 amd64module to access the OpenSSL pseudo-random number generator ii libcrypt-openssl-rsa-perl0.31-1build1 amd64module for RSA encryption using OpenSSL ii libevent-openssl-2.1-7:amd64 2.1.11-stable-1 amd64Asynchronous event notification library (openssl) ii libgnutls-openssl27:amd643.6.13-2ubuntu1.3 amd64GNU TLS library - OpenSSL wrapper ii libssl-dev:amd64 1.1.1f-1ubuntu2.1 amd64Secure Sockets Layer toolkit - development files ii libssl1.1:amd64 1.1.1f-1ubuntu2.1 amd64Secure Sockets Layer toolkit - shared libraries ii libwavpack1:amd645.2.0-1ubuntu0.1 amd64audio codec (lossy and lossless) - library ii libxmlsec1-openssl:amd64 1.2.28-2 amd64Openssl engine for the XML security library ii libzstd1:amd64 1.4.4+dfsg-3 amd64fast lossless compression algorithm ii openssl 1.1.1f-1ubuntu2.1 amd64Secure Sockets Layer toolkit - cryptographic utility ii perl-openssl-defaults:amd64 4 amd64version compatibility baseline for Perl OpenSSL packages ii python3-openssl 19.0.0-1build1 all Python 3 wrapper around the OpenSSL library ii ssl-cert 1.0.39 all simple debconf wrapper for OpenSSL here is the result of ldd on tls.so: linux-vdso.so.1 (0x7ffd687d6000) libssl.so.1.1 => /lib/x86_64-linux-gnu/libssl.so.1.1 (0x7f9feaf1c000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f9feaef9000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f9fead07000) libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x7f9feaa31000) /lib64/ld-linux-x86-64.so.2 (0x7f9feb071000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f9feaa2b000) thanks Filippo Il giorno mer 27 gen 2021 alle ore 13:11 Daniel-Constantin Mierla < mico...@gmail.com> ha scritto: > Hello, > > can you give more details about libssl on Ubuntu 20.04? The version (apt > show libssl, or apt search libssl, ...), eventually the ldd over the tls.so > kamailio module. > > Cheers, > Daniel > On 26.01.21 16:10, Filippo Graziola wrote: > > Hello, > > thanks for the fast reply, I just tried kamailio (5.4.3) from kamailio > repo on debian buster, self-signed certificates, same minimal > configuration. No error on start, so it seems specific for ubuntu. > > Il giorno mar 26 gen 2021 alle ore 15:39 Daniel-Constantin Mierla < > mico...@gmail.com> ha scritto: > >> Hello, >> >> would you be able to test on Debian 10 (maybe using docker or virtual >> machine/virtualbox) and see if you get the same issue? >> >> I do not have Ubuntu 20.04 at hand and I haven't encountered any issue >> lately with tls on Debian 10. In this way we can rule out if it is specific >> to Ubuntu version of the libraries or not. >> >> Cheers, >> Daniel >> On 26.01.21 15:06, Filippo Graziola wrote: >> >> Hi all, >> I have an issue related (my guess) to tls and http_async_client module >> that result in a segmentation fault and a not correct handle of tls >> connections. >> >> First with only tls module loaded, not forked: >> >> 0(1021) INFO: [core/tcp_main.c:4983]: init_tcp(): using epoll_lt >> as the io watch method (auto detected) >> 0(1021) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import >> bind_ob - maybe module is not loaded >> 0(1021) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not >> available >> 0(1021) INFO: tls [tls_mod.c:389]: mod_init(): With ECDH-Support! >> 0(1021) INFO: tls [tls_mod.c:392]: mod_init(): With Diffie Hellman >> 0(1021) WARNING: tls [tls_init.c:784]: tls_h_mod_init_f(): openssl bug >> #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls >> operations will fail preemptively) with free memory thresholds 4718592 and >> 2359296 bytes >> 0(1021) INFO: [core/cfg/cfg_ctx.c:595]: cfg_set_now(): >> tls.low_mem_threshold1 has been changed to 4718592 >> 0(1021) INFO: [core/cfg/cfg_ctx.c:595]: cfg_set_now(): >> tls.low_mem_threshold2 has been changed to 2359296 >> 0(1021) INFO: [main.c:2833]: main(): processes (at least): 9 - >> shm size: 67108864 - pkg size: 67108864 >> 0(1021) INFO: [core/udp_server.c:154]: >> probe_max_receive_buffer(): SO_RCVBUF is initially 212992 >&g
Re: [SR-Users] kamailio 5.4.3 ubuntu 20.04 tls - http_async_client
Hello, thanks for the fast reply, I just tried kamailio (5.4.3) from kamailio repo on debian buster, self-signed certificates, same minimal configuration. No error on start, so it seems specific for ubuntu. Il giorno mar 26 gen 2021 alle ore 15:39 Daniel-Constantin Mierla < mico...@gmail.com> ha scritto: > Hello, > > would you be able to test on Debian 10 (maybe using docker or virtual > machine/virtualbox) and see if you get the same issue? > > I do not have Ubuntu 20.04 at hand and I haven't encountered any issue > lately with tls on Debian 10. In this way we can rule out if it is specific > to Ubuntu version of the libraries or not. > > Cheers, > Daniel > On 26.01.21 15:06, Filippo Graziola wrote: > > Hi all, > I have an issue related (my guess) to tls and http_async_client module > that result in a segmentation fault and a not correct handle of tls > connections. > > First with only tls module loaded, not forked: > > 0(1021) INFO: [core/tcp_main.c:4983]: init_tcp(): using epoll_lt > as the io watch method (auto detected) > 0(1021) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import > bind_ob - maybe module is not loaded > 0(1021) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available > 0(1021) INFO: tls [tls_mod.c:389]: mod_init(): With ECDH-Support! > 0(1021) INFO: tls [tls_mod.c:392]: mod_init(): With Diffie Hellman > 0(1021) WARNING: tls [tls_init.c:784]: tls_h_mod_init_f(): openssl bug > #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls > operations will fail preemptively) with free memory thresholds 4718592 and > 2359296 bytes > 0(1021) INFO: [core/cfg/cfg_ctx.c:595]: cfg_set_now(): > tls.low_mem_threshold1 has been changed to 4718592 > 0(1021) INFO: [core/cfg/cfg_ctx.c:595]: cfg_set_now(): > tls.low_mem_threshold2 has been changed to 2359296 > 0(1021) INFO: [main.c:2833]: main(): processes (at least): 9 - shm > size: 67108864 - pkg size: 67108864 > 0(1021) INFO: [core/udp_server.c:154]: probe_max_receive_buffer(): > SO_RCVBUF is initially 212992 > 0(1021) INFO: [core/udp_server.c:206]: probe_max_receive_buffer(): > SO_RCVBUF is finally 425984 > 0(1021) INFO: tls [tls_domain.c:305]: ksr_tls_fill_missing(): > TLSs: tls_method=12 > 0(1021) INFO: tls [tls_domain.c:317]: ksr_tls_fill_missing(): > TLSs: certificate='/etc/kamailio/fullchain.pem' > 0(1021) INFO: tls [tls_domain.c:324]: ksr_tls_fill_missing(): > TLSs: ca_list='(null)' > 0(1021) INFO: tls [tls_domain.c:331]: ksr_tls_fill_missing(): > TLSs: crl='(null)' > 0(1021) INFO: tls [tls_domain.c:334]: ksr_tls_fill_missing(): > TLSs: require_certificate=0 > 0(1021) INFO: tls [tls_domain.c:342]: ksr_tls_fill_missing(): > TLSs: cipher_list='(null)' > 0(1021) INFO: tls [tls_domain.c:349]: ksr_tls_fill_missing(): > TLSs: private_key='/etc/kamailio/privkey.pem' > 0(1021) INFO: tls [tls_domain.c:352]: ksr_tls_fill_missing(): > TLSs: verify_certificate=0 > 0(1021) INFO: tls [tls_domain.c:356]: ksr_tls_fill_missing(): > TLSs: verify_depth=9 > 0(1021) INFO: tls [tls_domain.c:359]: ksr_tls_fill_missing(): > TLSs: verify_client=0 > 0(1021) NOTICE: tls [tls_domain.c:1105]: ksr_tls_fix_domain(): registered > server_name callback handler for socket [:0], server_name='' ... > 0(1021) INFO: tls [tls_domain.c:711]: set_verification(): TLSs: > No client certificate required and no checks performed > 0(1021) INFO: tls [tls_domain.c:305]: ksr_tls_fill_missing(): > TLSc: tls_method=20 > 0(1021) INFO: tls [tls_domain.c:317]: ksr_tls_fill_missing(): > TLSc: certificate='(null)' > 0(1021) INFO: tls [tls_domain.c:324]: ksr_tls_fill_missing(): > TLSc: ca_list='(null)' > 0(1021) INFO: tls [tls_domain.c:331]: ksr_tls_fill_missing(): > TLSc: crl='(null)' > 0(1021) INFO: tls [tls_domain.c:334]: ksr_tls_fill_missing(): > TLSc: require_certificate=0 > 0(1021) INFO: tls [tls_domain.c:342]: ksr_tls_fill_missing(): > TLSc: cipher_list='(null)' > 0(1021) INFO: tls [tls_domain.c:349]: ksr_tls_fill_missing(): > TLSc: private_key='(null)' > 0(1021) INFO: tls [tls_domain.c:352]: ksr_tls_fill_missing(): > TLSc: verify_certificate=0 > 0(1021) INFO: tls [tls_domain.c:356]: ksr_tls_fill_missing(): > TLSc: verify_depth=9 > 0(1021) INFO: tls [tls_domain.c:359]: ksr_tls_fill_missing(): > TLSc: verify_client=0 > 0(1021) INFO: tls [tls_domain.c:714]: set_verification(): TLSc: > Server MAY present invalid certificate > 6(1027) ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level > error > 6(1027) ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS > accept:error:141FC044:SSL routines:tls_setup_handshake:internal error > 6(1027) ERROR: tls [tls_server.c:1287]: tls_h_read_f(): source IP: > XXX > 6(1027)
[SR-Users] kamailio 5.4.3 ubuntu 20.04 tls - http_async_client
Hi all, I have an issue related (my guess) to tls and http_async_client module that result in a segmentation fault and a not correct handle of tls connections. First with only tls module loaded, not forked: 0(1021) INFO: [core/tcp_main.c:4983]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1021) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1021) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1021) INFO: tls [tls_mod.c:389]: mod_init(): With ECDH-Support! 0(1021) INFO: tls [tls_mod.c:392]: mod_init(): With Diffie Hellman 0(1021) WARNING: tls [tls_init.c:784]: tls_h_mod_init_f(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 4718592 and 2359296 bytes 0(1021) INFO: [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold1 has been changed to 4718592 0(1021) INFO: [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold2 has been changed to 2359296 0(1021) INFO: [main.c:2833]: main(): processes (at least): 9 - shm size: 67108864 - pkg size: 67108864 0(1021) INFO: [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1021) INFO: [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1021) INFO: tls [tls_domain.c:305]: ksr_tls_fill_missing(): TLSs: tls_method=12 0(1021) INFO: tls [tls_domain.c:317]: ksr_tls_fill_missing(): TLSs: certificate='/etc/kamailio/fullchain.pem' 0(1021) INFO: tls [tls_domain.c:324]: ksr_tls_fill_missing(): TLSs: ca_list='(null)' 0(1021) INFO: tls [tls_domain.c:331]: ksr_tls_fill_missing(): TLSs: crl='(null)' 0(1021) INFO: tls [tls_domain.c:334]: ksr_tls_fill_missing(): TLSs: require_certificate=0 0(1021) INFO: tls [tls_domain.c:342]: ksr_tls_fill_missing(): TLSs: cipher_list='(null)' 0(1021) INFO: tls [tls_domain.c:349]: ksr_tls_fill_missing(): TLSs: private_key='/etc/kamailio/privkey.pem' 0(1021) INFO: tls [tls_domain.c:352]: ksr_tls_fill_missing(): TLSs: verify_certificate=0 0(1021) INFO: tls [tls_domain.c:356]: ksr_tls_fill_missing(): TLSs: verify_depth=9 0(1021) INFO: tls [tls_domain.c:359]: ksr_tls_fill_missing(): TLSs: verify_client=0 0(1021) NOTICE: tls [tls_domain.c:1105]: ksr_tls_fix_domain(): registered server_name callback handler for socket [:0], server_name='' ... 0(1021) INFO: tls [tls_domain.c:711]: set_verification(): TLSs: No client certificate required and no checks performed 0(1021) INFO: tls [tls_domain.c:305]: ksr_tls_fill_missing(): TLSc: tls_method=20 0(1021) INFO: tls [tls_domain.c:317]: ksr_tls_fill_missing(): TLSc: certificate='(null)' 0(1021) INFO: tls [tls_domain.c:324]: ksr_tls_fill_missing(): TLSc: ca_list='(null)' 0(1021) INFO: tls [tls_domain.c:331]: ksr_tls_fill_missing(): TLSc: crl='(null)' 0(1021) INFO: tls [tls_domain.c:334]: ksr_tls_fill_missing(): TLSc: require_certificate=0 0(1021) INFO: tls [tls_domain.c:342]: ksr_tls_fill_missing(): TLSc: cipher_list='(null)' 0(1021) INFO: tls [tls_domain.c:349]: ksr_tls_fill_missing(): TLSc: private_key='(null)' 0(1021) INFO: tls [tls_domain.c:352]: ksr_tls_fill_missing(): TLSc: verify_certificate=0 0(1021) INFO: tls [tls_domain.c:356]: ksr_tls_fill_missing(): TLSc: verify_depth=9 0(1021) INFO: tls [tls_domain.c:359]: ksr_tls_fill_missing(): TLSc: verify_client=0 0(1021) INFO: tls [tls_domain.c:714]: set_verification(): TLSc: Server MAY present invalid certificate 6(1027) ERROR: tls [tls_server.c:1283]: tls_h_read_f(): protocol level error 6(1027) ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:141FC044:SSL routines:tls_setup_handshake:internal error 6(1027) ERROR: tls [tls_server.c:1287]: tls_h_read_f(): source IP: XXX 6(1027) ERROR: tls [tls_server.c:1290]: tls_h_read_f(): destination IP: XX 6(1027) ERROR: [core/tcp_read.c:1498]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f2cbc1b3948 r: 0x7f2cbc1b3a70 (-1) so no segmentation fault but error in handling. Second one also with http_async_client loaded: 0(1059) INFO: [core/tcp_main.c:4983]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1061) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1061) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1061) INFO: tls [tls_mod.c:389]: mod_init(): With ECDH-Support! 0(1061) INFO: tls [tls_mod.c:392]: mod_init(): With Diffie Hellman 0(1061) INFO: http_async_client [http_async_client_mod.c:222]: mod_init(): Initializing Http Async module 0(1061) WARNING: tls [tls_init.c:784]: tls_h_mod_init_f(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 5242880 and 2621440 bytes 0(1061) INFO: [core/cfg/cfg_ctx.c:595]: cfg_set_now(): tls.low_mem_threshold1 has
