3Com BETA, Getting Started Manual

Page: 66 / 70

Chapter 7. Firewall and Client Configuration
•
Let through TCP traffic between the Internet (all high ports) and the Telecommuting Mod-
ule (ports 1024-32767). You must allow traffic in both directions.
•
Let through TCP traffic between the internal networks (all high ports) and the Telecom-
muting Module (ports 1024-32767). You must allow traffic in both directions.
•
Let through UDP traffic between the Internet (all high ports) and the Telecommuting
Module (the port interval for media streams which was set on the
Basic Settings page).
You must allow traffic in both directions.
•
Let through UDP traffic between the internal networks (all high ports) and the Telecom-
muting Module (the port interval for media streams which was set on the
Basic Settings
page). You must allow traffic in both directions.
•
Let through UDP traffic between the Telecommuting Module (all high ports) and the In-
ternet (port 53). You must allow traffic in both directions. This enables the Telecommuting
Module to make DNS queries to DNS servers on the Internet. If the DNS server is located
on the same network as the Telecommuting Module, you don’t have to do this step.
•
NAT between the Telecommuting Module and the Internet must not be used.
•
NAT between the Telecommuting Module and the internal networks must not be used.
The SIP clients
SIP clients will use the Telecommuting Module as their outgoing SIP proxy and as their
registrar (if they can’t be configured with the domain only). If you don’t want to use the
Telecommuting Module as the registrar, you should point the clients to the SIP registrar you
want to use.
Other
The DNS server used must have a record for the SIP domain, which states that the Telecom-
muting Module handles the domain, or many SIP clients won’t be able to use it (if you don’t
use plain IP addresses as domains).
The DMZ/LAN type
Using the DMZ/LAN type, the network configuration should look like this:
58