TLS/SSL enable not working

[Hamed-Ramezani]

Hello guys!

I've installed captegent from master repository with param --enable-ssl and --enable-tls and the installation has completed without any errors. I also configured XML files as you describe in the WIKI.

Build directory............. :
Installation prefix......... : /usr/local/captagent
HEP Compression............. : no
IPv6 support.................: no
HEP SSL/TLS................. : yes
Flex........................ : flex
Bison....................... : bison -y

Build with REDIS............ : no
Build with MySQL............ : no
Build with PCRE............. : no
Build with LibUV............ : yes
Build with EPAN............. : no
Build with TLS.............. : yes

UDP traffic is sending to the heplify server correctly but It does send the TLS ( webrtc) traffic. I saw this line in the logs:
captagent[27570]: [ERR] protocol_tls.c:269 TLS has been not enabled. Please reconfigure captagent with param --enable-ssl and --enable-tls

[lmangani]

Even if you provide the requirement for compiling it, that's likely not going to work with TLS unless you're using obsolete RSA encryption. You should use a different methohd but since you didn't specify what is the webrtc handler we can't make any suggestions. feel free to expand on the big picture.

[Hamed-Ramezani]

I'm using Asterisk 16 as WebRTC handler and the client app is vicidial viciphone.
The RSA Private key is 2048 bit

[kYroL01]

@Hamed-Ramezani please check this https://github.com/sipcapture/captagent/wiki/TLS
This is the only method that worked at the time, but it has many limitations, as you can imagine, plus is insecure nowadays.
Feel free to test it, but the best method is to send plain TCP traffic to Captagent after you pass the TLS to a proxy.

[Hamed-Ramezani]

Thank you for your response

…

On Thu, 7 Aug 2025, 11:02 Michele Campus, ***@***.***> wrote: *kYroL01* left a comment (sipcapture/captagent#286) <#286 (comment)> @Hamed-Ramezani <https://github.com/Hamed-Ramezani> please check this https://github.com/sipcapture/captagent/wiki/TLS This is the only method that worked at the time, but it has many limitations, as you can imagine, plus is insecure nowadays. Feel free to test it, but the best method is to send plain TCP traffic to Captagent after you pass the TLS to a proxy. — Reply to this email directly, view it on GitHub <#286 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BMN3LCRC3CVLGAYVMERRJDL3ML6HJAVCNFSM6AAAAACDHQ7GOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNRSHA4DCMBYG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>