- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
11-27-2015 04:28 AM
Hi,
I have a voice/visioconference system available on the internet (via NAT-ed IP) using H323. So of course the port 1720 is open and reachable from outside, without restriction on IP addresses because users must be able to reach the system from their smartphone App.
My problem is that sometimes, some traffic on port 1720 (shown as H.225 in the logs) is making the system ringing because a few packets go through the firewall even if it's not legitimate call signaling.
Because the incoming traffic is matching a policy on the firewall my Zone Protection Profile does not block.
How can I better protect this port? Any suggestions?
Thank you for helping,
Regards,
Nicolas.
11-27-2015 05:42 AM
Check logs if those "bad" calls come from same country where "good" calls.
Maybe you can block based on source country.
You use application based rules right (not port based)?
12-06-2015 11:24 PM
Hi,
Yes I'm using Application-based Rules, and it is recognized as valid h.225 application.
I already limited the source IPs to some Countries, but I still have the same issue.
Because of the mobile Users I can't be to restrictive on souce IP addresses.
I think I will force the mobile users to use SSL VPN to access the Visioconf System and for the other office I can restrict the Access to a few well-known public IP.
Regards,
Nicolas.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!