Smart Technologies Smart Bridgit 4.5 - Manual (Page 16)

l
Firewalls for the client should allow outbound communication from the client on all specified
ports.
For best performance, allow inbound TCP and UDP traffic to the server on the default ports specified
in the following table.
Default
ports
Type/protocol Use
80 TCP/HTTP
l
Initial connection to the SMART Bridgit server to
display the web page from which the users download
the SMART Bridgit client.
l
Initial connection to the SMART Bridgit server from
the SMART Bridgit client when looking for meetings
to join or when creating new meetings.
l
Fallback communication method for all other
SMART Bridgit functions when other ports are
unavailable (lower performance than other ports).
80 TCP/SMART Bridgit
l
Primary port for data, screen viewing and webcam
traffic for SMART Bridgit meetings.
l
If this port is limited to only HTTP, SMART Bridgit
conferencing software attempts to use the
secondary port (9933) for this traffic.
l
If this port is blocked or unavailable, SMART Bridgit
conferencing software uses the HTTP on the primary
port, which can affect performance.
9933 TCP/SMART Bridgit Secondary port for data, screen viewing and webcam traffic
for SMART Bridgit meetings.
9901 to
9920
UDP/SMART Bridgit l
Primary port range for VoIP audio traffic for
SMART Bridgit meetings.
l
If these ports are blocked or unavailable,
SMART Bridgit conferencing software falls to TCP or
HTTP on the primary or secondary port, which can
negatively affect performance.
Configuring proxy servers
You can configure your SMART Bridgit server software to work with any proxy server that adheres to
the RFC 2068 HTTP standard. If you install your SMART Bridgit server software behind a proxy
server, you must create access policy rules for inbound and outbound traffic on that proxy server. You
can further enhance your network security by enabling authentication, such as basic, digest or NT
LAN Manager (NTLM) authentication.
C H A P T E R 2
Installing SMART Bridgit software
12