Hello - I have FreePBX on Raspberry Pi (raspbx) with latest upgrades using PJSIP. The device is a Yealink SIP-T40G set up for encrypted communications (TLS and SRTP). The wireshark shows what appears to be a successful TLS handshake. After but then the the FreePBX sends TLS “Finished” message it then sends TCP FIN and appears to end the connection.
One known issue with my setup is that the framework module is disabled. I am having difficulty getting it upgraded and I am hoping it is not the source of the problem.
I have rechecked many points of my SIP and TLS configuration. I am not seeing any error messages or any useful log data. Can someone please steer me at some first steps at finding where the failure is?
How about a proper Asterisk level debug to see what is happening. The pcap shows that the handshake happened but since Asterisk is running over TLS that means it happened by Asterisk. So do you see REGISTER messages happen in the Asterisk console with the proper driver debug/logger on?
Is this a case of Asterisk not getting it, not replying to it, not sending a proper message back? Sending back a valid error because of an issue with the packet or request?
PJSIP logging is enabled and shows no SIP messages of any type reaching Asterisk. The wireshark shows none either.
From the wireshark it appears that the FreePBX chooses to close the connection immediately after the TLS handshake. I am hoping someone can steer me toward whatever linux logs would show any error messages resulting from the TLS handshake.
If I understand you, an address book request from the Yealink to the FreePBX would get the same TLS stacks talking to each other as if it were a SIP message. And the web servers on each side might provide some useful error messages?