MiCloud Business Partner Built MiCC Deployment Best Practices

INFORMATION

When deploying MiContact Center in a MiCloud Business partner built environment, it is important to follow the appropriate best practices.  Failure to comply with the best practices will prevent automated usage reports from being generated and your operations will have to manually supply usage information for monthly billing.  Specifically, when adding additional systems and/or virtual instances to support additional customers then the following must be observed: 
 
For Virtual Machine deployments:

• Do NOT clone the virtual image if you already have installed MiContact Center Business on the server and SQL server is also running locally on the same server.
• Do NOT install\use the MiCC 7.1 OVA. An 8.1.1.0 OVA available and that is what everyone should be using as it does not ship with a database already created.

 
For Physical Machine OR Virtual Machine case:

• Do NOT restore the same MiCC backup onto another system for two different customers.

 
With the introduction of automated service provider service usage reporting for MiCC, failure to follow these best practices will result in inaccurate usage reports.   The automated service usage reporting relies on unique identifiers in the CCMData database and cloning or restoring databases results in the creation of non-unique identifiers.
 
If these practices have not been followed for existing deployed systems, then please contact Mitel Product Support so that we can identify corrective measures that can be taken to re-establish unique identifiers and ensure the service usage reports are being accurately generated.
 

APPLIES TO

MiContact Center Version 8 or newer