Firewall Settings for RingCentral VoIP Released by Calyptix Firewall Settings for RingCentral VoIP Released by Calyptix

Firewall Settings for RingCentral VoIP Released by Calyptix

by Calyptix, July 13, 2018

Charlotte, NC – Calyptix Security today added another voice-over-IP (VoIP) phone service to the list of those supported by the company’s flagship product, AccessEnforcer UTM Firewall.

RingCentral is the latest VoIP system to join the list. While AccessEnforcer supported RingCentral before today’s announcement, Calyptix has now released configuration guidelines for administrators wishing to deploy the phones on an AccessEnforcer network.

AccessEnforcer is compatible with most VoIP phone services, including those provided by:

  • RingCentral
  • Vonage
  • Mitel
  • Nextivia
  • 3CX
  • 8×8
  • Asterisk (PBX)
  • FreedomVoice
  • Many others

Calyptix publishes recommended configuration settings for many of the VoIP systems supported by their firewall. The tutorials are available from the company’s web portal, which is available for free to Calyptix reseller partners.

The recommended configuration settings on AccessEnforcer for RingCentral VoIP phones include the following:

  • Adding a list of IP address ranges to the AccessEnforcer Static Whitelist
  • Adding a list of domains to the device’s whitelist, if Web Filtering is enabled
  • Two new rules for Web Filter exemptions
  • QoS rules to optimize the phones’ network bandwidth

AccessEnforcer includes many features that make deploying VoIP phones easier and safer for network and administrators and businesses alike.

One such feature is Quality of Service (QoS) – a bandwidth management feature that allows administrators to allocate or limit network bandwidth for any traffic source or destination, including both external and internal hosts. Administrators can even allow hosts to “borrow” spare bandwidth from non-critical systems and prioritize certain packets to ensure they are always processed first.

The Intrusion Prevention System (IDS/IPS) in AccessEnforcer also protects against a wide variety of cyber attacks, including protocol-specific attacks against VoIP services.

SIP Proxy is another feature of AccessEnforcer designed for use with certain VoIP systems. The feature is analogous to features such as SIP Application-level Gateway (SIP ALG) found on other devices.

SIP Proxy makes it unnecessary to set explicit port-forwarding rules for the VoIP service. Instead, AccessEnforcer detects and stores the each device’s SIP address and routes incoming calls to the appropriate devices automatically.

Trivial File Transfer Protocol (TFTP) is another service required by some VoIP systems, and support for this protocol is available on AccessEnforcer. The feature is disabled by default, though administrators need only select a checkbox to activate it through the device’s simple point-and-click interface.

Static IP addresses can also be used for some or all outbound traffic on AccessEnforcer. This can be helpful when configuring some VoIP phone services that require a static port for operation. Administrators can specify the use of a static port on the firewall’s Outbound Filtering page (the ports are randomized by default).

Additional information about AccessEnforcer and VoIP phone services is available on the Calyptix website.

 

About Calyptix Security

Calyptix Security helps small and medium-size businesses secure their networks so they can raise profits, protect investments, and control technology. The company’s flagship product, AccessEnforcer UTM Firewall, makes it easy to protect SMB networks so companies can forget about security and focus on winning. Developed, built, and serviced in the U.S., AccessEnforcer is a flexible solution for MSPs and VARs to deliver security that keeps clients safe and saves time.

 

 

No Comments


    Leave a Reply

    Your email address will not be published Required fields are marked *

    You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

    *