Show\Hide Navigation Manager: Configuration Settings
Up Down Back Forwards Print Synch Bookmark and Share Bookmark and Share

Firewall Profile Settings

icon large firewall

The IP Office can act as a firewall, allowing only specific types of data traffic to start a session across the firewall and controlling in which direction such sessions can be started.

•Static NAT
IP Office 4.2+ adds support for Static NAT address translation by IP Office Firewall Profiles. If the Firewall Profile contains any Static NAT entries, all packets received by the firewall must match one of those static NAT entries to not be blocked.

IP Office firewall profiles can be applied in the following areas of IP Office operation.

•icon large system System
A firewall profile can be selected to be applied to traffic between LAN1 and LAN2.
•icon large user User
Users can be used as the destination of incoming RAS calls. For those users a firewall profile can be selected on the user's Dial In tab.
•icon large service Service
Services are used as the destination for IP routes connection to off-switch data services such as the internet. A Firewall Profile can be selected for use with a service.
•icon medium logical lan Logical LAN
Where a logical LAN is created for use as an IP Route destination, a Firewall Profile can be selected for use with the logical LAN.

 

If Network Address Translation (NAT) is used with the firewall (which it typically is), then you must also configure a Primary Incoming Translation Address (see IP tab of the Service configuration form) if you wish sessions to be started into your site (typically for SMTP) from the Internet.

 

 

© 2009 AVAYA
15-601011 Issue 23.p.-
07:06, 30 October 2009
(firewall_profile_settings.htm)

Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by (R) or TM are registered trademarks or trademarks respectively of Avaya Inc. All other trademarks are the property of their respective owners.

Last Modified: 06/03/2008