Installation guide

Prerequisites and Deployment Overview
Acano solution: Deployment Guide R1.2 76-1006-06-K
Page 7
2 Prerequisites and Deployment Overview
2.1 Prerequisites
The list of items you need prior to installing and configuring the Acano solution in a typical
customer environment is given below; some of these items can be configured beforehand:
 A fully qualified Doman Name for the Acano solution. The name of this domain should be set
up in advance of the installation. See Appendix A for a summary of DNS records that you
may need to create and be sure that the ones not for an Acano solution component (e.g. the
Web Bridge) are already in place
 Firewall configuration – see Appendix B for a summary of the firewall changes you may
need to make
 Installation of a Syslog server to capture logs. Instructions for configuring the Acano solution
to use this Syslog server are given in in this document. The Syslog is essential for most
troubleshooting
 Access to at least one NTP server. Instructions for configuring the Acano solution to use this
NTP server are given in in this document.
 Decision on a dial plan to use to reach calls hosted on the Acano solution. . Instructions for
deploying this dial plan are given in this document
 Generating the security certificate for the Web Admin Interface, Call Bridge, Web Bridge and
XMPP server
Instructions for generating self-signed certificates using the Acano solution’s internal
commands are given in this document. These are useful for testing. However, if you are
using certificates signed by a Certificate Authority, they are a pre-requisite and must be
available before deployment starts. You can use the openssl commands given in Appendix
C to generate a certificate signing request to do this before installing and deploying the
Acano Server. (After installation, you can also use the Acano solution’s internal commands
as given in Appendix D.)
 Access to a SIP Call Control platform (for example, Cisco VCS) to make dial plan
configuration changes. . The changes required are given in this document
 If deploying in a Lync environment, access to the Lync Front End Server to make dial plan
configuration changes there. The changes required are given in this document
 Read-only access to the Active Directory server in order to import users
 Access to SIP endpoints and/or Acano clients to test the solution
 Access to a PBX for voice calls
 Hostname set for the server using the MMP command:
hostname <name>
hostname mybox.mydomain
reboot
Note: A reboot is required after issuing this command.