Installation guide
Prerequisites and Deployment Overview
Acano solution: Deployment Guide R1.2 76-1006-06-K
Page 9
2.2.1 Management and network interfaces
There are two layers to the Acano solution: a Platform and an Application.
The Platform is configured through the Mainboard Management Processor (MMP). The
MMP is used for low level bootstrapping and configuration. It presents a command line
interface.
Note: On the Acano Server the MMP can be accessed via the serial Console port or SSH
on the Ethernet interface labeled Admin. In the virtualized deployment the MMP is
accessed on virtual interface A.
The Application runs on this managed platform with configuration interfaces of its own.
These are sometimes referred to as “the media interfaces”. The application level
administration (call and media management) is done via the Web Admin Interface which can
be configured to run on any one of the Ethernet interfaces.
Note: On the Acano Server there are five physical Ethernet interfaces labeled Admin, A, B
C and D. In the virtualized deployment one Ethernet interface (A) is created but up to three
more can be added (B, C and D).
There is no physical separation between the media interfaces A-D but the Admin interface
is physically separate. Each interface is configured independently of the others at the IP
level. IP forwarding is not enabled in either the Admin or host IP stack.
See the appropriate Installation Guide for details.
2.2.2 DNS configuration
The Acano solution will need to be provided with a fully-qualified DNS record. Acano requests
that the name of this domain is decided and set up in advance of the installation. See Appendix
A for a full list of DNS requirements which you may want to request now.
2.2.3 Security certificates
You will need to generate and install security certificates. This needs to be done on the domain
that will be used. The Acano solution follows the X.509 standard for certificates which is a
standard for:
Servers to identify themselves: the Acano solution’s name to which communications are
routed i.e. FQDN.
TLS connectivity on SIP trunks and secure HTTP (HTTPS), which also uses TLS
For example, so that the Lync Server will trust the Acano solution (see Figure 1 below).
2.2.4 SIP trunks and routing changes
SIP trunks will need to be set up between your SIP Call Control, Voice Call Control and Lync
Front End Server components to the Acano solution. Changes will also need to be made to the
call routing configuration on these devices to route calls to the Acano solution that require the
Acano Edge software for interoperability. See the diagram below.