In this blog article I will provide some best practices for deployment planning that our UC platform will need, to work as expected.
When a new UC system is installed, users will need to spend a considerable amount of time and resources learning how it works. It is crucial to reduce the impact of adopting any new technologies by avoiding user problems.
The most common issues I have witnessed are “regressions” in how the system works, particularly when compared to the previous system. Some examples include:
- Missing features (especially telephonic ones)
- Poor audio quality
- Fax machines not working reliably
- PoS connections not working reliably
A Unified Communication solution can be deployed either in an environment controlled by the customer, as a corporate data center, or in a third-party data center. Let’s review such deployment scenarios in more detail.
In most scenarios, a solution deployed in a cloud environment (such as Amazon AWS) offers the best overall conditions including easy redundancy, by relying on different physical data centers, and better connectivity, by providing worldwide data centers.
However, there are scenarios where an in-house UC platform can offer advantages over a cloud solution. When the UC services are accessed mostly by local users and using local PSTN trunking, a local deployment is the best solution. Another scenario might be a site with poor Internet connectivity where phone services must be provided.