Sophos Central Endpoint and SEC: Computers fail/hang on boot after the Microsoft Windows April 9, 2019 update. Please follow knowledge base article 133945
Learn about the Benefits of Multi-Factor Authentication (MFA). Turn your MFA on now!
We'd love to hear about it! Click here to go to the product suggestion community
Our 3cx phone system could not negiciate port 5060. The rules are fine and working on 17.1 MR 3. Updating to the beta had numberous issues.
SIP failures and ports not working.
DNS failures (related to phone system only)
Rolled back (as you do) no issues with 17.1.MR3.
Still testing on my Sophos SG135W.
Have you checked UDP port for 5060 permited in firewall rule .
In reply to VishvasChitale:
Like I said
I have a set of working rules, inclusive of port 5060 UPD.
It works on 17.1 MR3.
It does not work on 17.5 Beta.
In reply to DomusRegis:
Have you made sure to unload the SIP helpers?
I've just noticed that my SIP helper was unloaded but is now showing as loaded again. Will do some testing.
To disable, log on via SSH, Option 4 for Device Console and run the following command: system system_modules sip unload
Before you roll forwards to v17.5, check to make sure they are unloaded using command: system system_modules show
Then once you roll forward and check again.
In reply to EmileBelcourt:
SIP Loaded (just to try it) on 17.5 Beta 2
Reverted back to 17.1 RM3
if a separate firewall rule is created with the sip server network(s) as destination with logging enabled is anything informative logged?
any difference with that firewall rule allowing all traffic to the sip server network(s) as a test?
Thank you for the feedback. Contacting you on PM for further details