|
|
This page describes general routing requirements for the e/pop web conferencing server, and thereafter, covers the most typical customer configurations.
When considering where to place the e/pop Web Conferencing server, it’s important to note that the Host, Presenter and all Participants must have IP routing to the Server. This is true whether you are restricting the server to internal-only Participants, or using it for general purpose web conferencing over the Internet.
The e/pop Web Conferencing software requires port 80 to be open and dedicated to the conferencing application. The conferencing server defaults to a short list of additional ports, and listens to them all. WiredRed strongly recommends leaving the default port settings as is (especially for trial purposes). Please contact WiredRed for assistance with adding ports (for production conferencing servers).
For customers that place the conferencing server behind a firewall, the port(s) mentioned above must be open. The firewall settings must allow inbound and outbound traffic, and must allow ActiveX. In addition, the firewall must be configured to allow TCP sockets to stay active long enough for the 'keep alive' packets to reset the timer in the firewall. Note: customers take special care when making these settings, to that they apply to the conferencing server IP address and ports only, thereby protecting the integrity of their border security policies.
Please contact WiredRed for assistance with routing requirements, firewall settings, and add-on options for pure html conferencing clients.
Below are some common physical configurations for the e/pop Web Conferencing application.
Behind
Firewall
(No Open
Ports)
In this
configuration,
only
internal
users
have
“routing”
access
to the
e/pop
Web
Conferencing
Server. |
 |
Advantages:
- MOST SECURE
- Traffic stays within the corporate network
- No 3rd party access to server logs
|
Behind Firewall (Open
Ports Only To Conference
Server)
In this configuration,
the conferencing server
is behind the firewall,
port 80 and (optionally)
a short list of
additional ports (see
admin console) are open
to/from the conference
server.
|
Advantages:
- Easy
to
configure
- Secure
- Only external traffic goes over the internet
- No 3rd party access to server logs
|
In a DMZ
Installations that plan to host the e/pop Web Conferencing server in their environment may consider placing the server in a DMZ, so it does not violate the security policy of the corporate network. In this scenario, the employees are routed to the conferencing server via a private IP address, while external participants a public address.
|
Advantages: |
- Most popular and best configuration for compliance with border security policies
- Secure
- Only external traffic goes over the internet
- Often used in retail, retail banking, transportation, healthcare and government, where employees do NOT have general Internet access, but CAN access the web conferencing server
- No 3rd party access to server logs
|
|
Co-Location /
Hosting
This is
configuration is
a popular choice
for customers
that do not have
the IT staff or
infrastructure
to implement one
of the
configurations
listed above;
already have
servers at a
co-location
facility; and/or
intend to have
large recurring
conferences and
need more
bandwidth at the
conferencing
server (than is
available
in-house).
|
Advantages: |
- An easy choice for customers with servers already hosted at a co-location facility
- A good choice for customers hosting large meetings with mostly external users
- You can evaluate and monitor your co-location security much easier than a distant online service provider
|
|
|
