Datasheet

Acano X Series Server and Virtualized Deployments
Acano Solution R1.6: Support FAQs 76-1022-08-K
Page 26
How do I set the default layout for every coSpace?
Set the defaultLayout in a callLegProfile and apply that callLegProfile at the system (global)
level. Note that this default layout will only apply if the setting is not overwritten by a layout
setting at a lower level e.g. per coSpace.
What information is included in the email invitation?
If you invite a participant from an Acano client, either from the coSpace information panel or
when in a call, only the details displayed in the coSpace’s information panel are included in the
email. Any calling details in an access method on the coSpace are not included.
What does "RTCP unprotect authentication failure" in the event log mean?
RTCP unprotect authentication failures aren't anything to worry about on their own; they are the
result of authentication failures on incoming RTCP, which is mostly due to 3rd party endpoints
not following the specifiction for this correctly.
How do I move the master database?
This FAQ applies to Acano solution R1.6 onwards only.
The master database in a cluster will move automatically if the current master goes down, but
you cannot control which of the previous standby databases will become the new master
database for the cluster. The following procedure should only be used if you want to move the
master database to a particular host server; but of course the master database will move again
automatically if this server goes down.
Note: The process to move the master database described below causes all active calls hosted
on Call Bridges connected to the database cluster to drop; therefore only perform this
procedure during a scheduled down time.
1. Check that the status of all the standby databases in the cluster is “In sync” by running the
following MMP command on all servers hosting one of these databases.
dbcluster status
2. Uncluster all the databases by running the following MMP command on all servers including
that hosting the master database.
dbcluster disable
Note: All active calls will drop.
3. On the server with the database that you want to be the master, initialize the database by
running the following MMP command:
dbcluster initialise
4. Attach the other databases to the master by running the following MMP command:
dbcluster attach <master hostname/IP>
5. Check the status of the new cluster to make sure that all the databases are in sync and to
check which is the master database.
dbcluster status