Coming off of our last partner training in Chicago we came away with many really good questions. One question we want to highlight here is what would prompt a private cloud deployment over public cloud with BVoIP?
Things to consider:
- Private cloud deployments are dedicated enviroments with a dedicated firewall and blade just for that end customer.
- In Public cloud deploymets, while each customer is segregated, it is more of a multi-tenanted shared infrastructure.
- Public Cloud deploys scale up to a certain size and then larger instances require dedicated resources anyway.
- Heavily security conscious end users
- Customers who require point-to-point or MPLS circuits
- Customers who want to deploy site-to-site VPN to encrypt PBX traffic or in general lock down access
- Larger deployments which require dedicated resources
- High Availability needs
- Ability to control their own maintenance windows for operational purposes
- Need to stack multiple locations from a core pbx deployment rather than multiple instances one per site.
Gotchas
- If your customer has different sites in different time zones please note that the PBX only runs on one time zone for time stamps for things like call history, logs, etc
- If your customer requires different muic on hold per location the PBX only allows for one core music on hold option system wide but does have options for different park and call queue settings on the same PBX.
- If your customer requires different language prompts while you can custom record greetings each PBX can only have one core langauge promptset for system messages.
Do you have particular project that you want to talk about? Let us know.
