Networking
Web Conferencing
Web Conferencing
Benefits
Gives users across geographic boundaries the ability to do audio and web conferencing on
demand. This is helpful for purposes of collaboration in distributed team environments; attendees
from different locations can view and work on the same information in real time by using features
such as desktop and document sharing.
Requirements
• Within the Firewall and the NAT router at the main office, the following ports need to be
opened and forwarded, in order for a participant to access the IPedge Meeting conferences:
• Admin – TCP 80
• Secure Admin – TCP 8444
• Web conferencing – TCP 443
• Data port for desktop screen sharing service – TCP (1935, 1945)
• DNS Server Configuration – In order for the IPedge Meeting service to be easily and publicly
(from the WAN) accessible, a couple of fully qualified domain names (FQDNs) need to be
created. These FQDNs need to be mapped via the DNS service to the IP address of the IPedge
Server. FQDN mappings within the DNS service (server) need to be created for:
• Meeting administration service
• Meeting web conferencing service
Note
If the IPedge server is deployed behind a NAT firewall, the DNS service would need to be
configured to map the FQDNs to the NAT public IP address instead.
Interactions
In some IT environments, public facing services and servers are configured in the DMZ. If that is
the case in a customer deployment, firewall and NAT rules will need to be configured for IPedge
meeting services to be accessible from both the WAN and the LAN.
56
IPedge General Description
03/16