[ASTPPCOM-520] SIP TLS doen't work in ASTPP 4.0 even after "tls = true" in SIP profile Created: 09/Jun/19  Updated: 22/Jul/20  Resolved: 27/Oct/19

Status: Closed
Project: ASTPP Community
Component/s: None
Affects Version/s: None
Fix Version/s: v4.0.2

Type: Bug
Reporter: timur-v Assignee: (Community) DN (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

I tried to use TLS encryption, so I edited SIP profile "default" (Switch -> SIP Profiles -> default) and changed the value "tls" to "true". Then I restarted freeswitch service and could see that it listened for port 5061 TCP. But that port remained unavailable from outside the server, so TLS auth didn't work.
I found that it was due to firewall rules which were set up by ASTPP installation script. They denied all the ports except 5060, 80, 443 and some other. Port 5061 left closed.
Solution for that is
firewall-cmd --permanent --zone=public —add-port=5061/tcp
firewall-cmd --reload
I hope developers will add this in further releases.



 Comments   
Comment by hemdip [ 13/Jun/19 ]

That was the issue, it will be fixed in upcoming release

Comment by Samir Doshi [ 27/Oct/19 ]

This is not an issue. You will need to open relevant port in your firewall and that needs to be done manually. 

Generated at Sat Feb 10 07:17:54 CET 2024 using Jira 8.13.3#813003-sha1:22ebedbb75c99b147c66f14e031dd8a2d214753a.