Deploy Yeastar P-Series Cloud PBX in Data Center (HA)

This topic describes how to deploy Yeastar P-Series Cloud PBX in High Availability (HA) in your own data center.

Supported virtualization platforms

You can deploy Yeastar P-Series Cloud PBX on the following VM platforms to save hardware costs:
  • Microsoft Hyper-v
  • KVM
  • VMware
Note: Bochs is not supported.

Prerequisites

Before you begin, complete the following operations:

Understand the architecture
Learn about the High Availability (HA) deployment architecture for Yeastar P-Series Cloud PBX.
Plan resource
Learn about the system requirements for the required servers.
Tip: We provide a server calculator to help you calculate the required server configurations for the entire deployment of Yeastar P-Series Cloud PBX. For more information, see Server Calculator.
Configure router settings
Configure the following settings on the gateway router / firewall in the network where the SBC Server and SBC Proxy Server reside.
  • Allow PING requests from the LAN (Local Area Network) to ensure that the SBC Server and SBC Proxy Server can PING the gateway for connectivity checks.
  • Disable SIP ALG (Application Layer Gateway) to avoid potential issues with VoIP calls.

Procedures

Deploy servers for the complete High Availability architecture, or choose to implement high availability for specific components based on your requirements.
Important:
  • All the servers use SINGLE Ethernet port.
  • For private IP address of servers, avoid the 172.17.x.x and 172.19.x.x IP ranges.
  • Make sure that all the servers can communicate with each other in both private network and public Internet.
Deploy and configure YCM server
  1. Deploy one YCM server.
  2. Set up a data disk for the server.
  3. On the gateway router/firewall, configure NAT policies to enable bidirectional Internet access for the YCM server, ensuring the same public IP address is used for both inbound and outbound traffic.
Deploy and configure SBC server cluster
Note: To implement high availability for SBC servers, the following firmware requirements should be met.
  • YCM Server: 87.15.0.24 or later
  • SBC Server: 86.15.0.70 or later
  • PBXHub Server: 85.15.0.36 or later
  1. Deploy one Yeastar Load Balancer, and at least two SBC servers with identical hardware configurations.
    • The Yeastar Load Balancer and SBC servers must reside on the same network segment to ensure seamless communication and proper functioning of the network services.
    • Policy-based routing support is required between the load balancer and SBC servers. For confirmation regarding your specific environment's support for policy-based routing, consult with your network support team or provide the load balancer to Yeastar to confirm.
    • Configure the network bandwidth for the Yeastar Load Balancer server according to your communication requirements.
      Numbers of Extensions Minimum Upstream/Downstream Bandwidth
      10,000 60 Mbps
      40,000 240 Mbps
      60,000 360 Mbps
      80,000 480 Mbps
  2. Set up a data disk for the server.
  3. On the gateway router/firewall, configure NAT policies to enable bidirectional Internet access for the Yeastar Load Balancer and SBC servers, ensuring the same public IP address is used for both inbound and outbound traffic.
Deploy and configure SBC Proxy server cluster
Note: To implement high availability for SBC Proxy servers, the following firmware requirements should be met.
  • SBC Proxy Server: 86.15.0.105 or later
  • P-Series Cloud Edition: 84.19.0.110 or later (Required for maintaining continuous shared trunk availability during failover.)
  1. Deploy two SBC Proxy servers with identical hardware configurations.
  2. Set up a data disk for the server.
  3. Prepare an available private virtual IP (VIP) and a public IP address. The Virtual IP must reside within the same subnet as the SBC Proxy server's private IP address.
    Note: In the scenario where you are upgrading an existing SBC Proxy server to a High Availability architecture, you can directly use its current public IP address.
  4. On the gateway router/firewall, configure NAT and routing policies:
    Important: In the scenario where you are upgrading an existing environment to a High Availability architecture, these changes will interrupts external calls until the configuration is completed and all Cloud PBXs have been restarted. Plan a maintenance window accordingly to minimize server impact.

    • The SBC Proxy servers must have outbound internet access.

    • Add a NAT rule to map the Virtual IP (VIP) address to the public IP address.
      Note: If upgrading an existing environment to a High Availability architecture, first remove the original NAT rule that maps the SBC Proxy server's private IP address to the public IP address.
    • Update the routing policies:
      • Block the SBC Proxy servers' private IP address from accessing the Internet directly.
      • Ensure all outbound internet traffic from the SBC Proxy servers is routed through the VIP using the public IP address.
Deploy and configure PBXHub server cluster
  1. Deploy two PBXHub Servers
  2. Set up data disk for the servers.
    Note: You need to mount 2 additional data disks per PBXHub Server for the storage of CloudPBX system data and recording files respectively.
  3. On the gateway router/firewall, configure NAT policies to permit outbound connections only and block all inbound connections initiated from the Internet.

What to do next

Submit your information of the deployment environment to Yeastar.