Installation guide

Prerequisites and Deployment Overview
Acano solution: Deployment Guide R1.2 76-1006-06-K
Page 13
Both internal and external Acano clients use ICE/TURN to find suitable candidates for
connectivity and choose the best: in the case of internal clients this will always be the local host
candidates on the internal network.
The necessary ports need to be open on the firewall between Core and Edge components to
allow the media UDP traffic to pass (UDP ports 32768 - 65535) and the control link between the
XMPP server and the Call Bridge (port 5223). The Web Bridge uses port 443 (and optionally
port 80).
Another deployment option for the Edge server/virtualized server is to enable the XMPP server
on a second interface and connect that interface to the private network. Then internal clients
can connect directly to the XMPP server and not have to traverse the internal firewall. Separate
internal and external SRV records for the XMPP service need to be configured, directed to the
two interfaces on the Core server/virtualized server that the XMPP server is listening on. The
Call Bridge to XMPP connection should also use the XMPP server’s internal address in this
case, avoiding the need to open port 5223 through the firewall.
2.2.9 Acano Web Bridge
If you are using the Acano Web Client you will need to enable and configure the Acano Web
Bridge, refer to section 4.8 and section 9.
Acano Web Client works on HTML5-compliant browsers and uses the WebRTC standard for
video and audio. For a list of tested devices see the Acano solution Support FAQs document.
2.2.10 Acano TURN Server
To use Acano clients from outside of your organization you will need to enable the TURN server,
refer to section 4.9 and section 10. The TURN server allows you to use the built-in firewall
traversal technology when traversing a firewall or NAT. If you are unfamiliar with TURN servers,
ICE and STUN, see http://en.wikipedia.org/wiki/Traversal_Using_Relay_NAT and the figure in
section 2.2.8.
2.2.11 Split deployment considerations
This Deployment Guide should be followed in order if you are setting up a one Acano Server
deployment or a one virtualized server solution; however, this section describes the few
differences that you must remember when following this Deployment Guide if you are installing
and configuring a two-Acano Server deployment such as the example configuration in the
figures or the virtual equivalent. The figure below shows the TURN server, XMPP server and
Web Bridge on one physical Acano Server, and the Call Bridge on the second. (Comparing
figure 3 to figure 1, you see that there are very few differences because the Acano solution was
designed for flexible deployment.)
Note: The installation file is the same for both single and split deployments: you install all the
software on both servers/virtualized servers, but every component is disabled by default.
Therefore you only configure and enable the relevant components on each server/virtualized
server, in our example deployment:
 Edge server/virtualized server: XMPP server, TURN server, Web Bridge
 Core server/virtualized server: Call Bridge, Web Admin Interface