Basic Architecture of Yeastar P-Series Cloud PBX

Before you start to deploy Yeastar P-Series Cloud PBX, you need to learn about the basic architecture of Yeastar P-Series Cloud PBX.

Architecture

The figure below shows the most basic architecture of Yeastar P-Series Cloud PBX, which means there is only one server in each component of the system.

Note: If you would like to deploy more than one server to implement High Availability performance, see High Availability Architecture of Yeastar P-Series Cloud PBX.

The foundational architecture of Yeastar P-Series Cloud PBX includes the following components:
Important: Make sure that the SBC Server, SBC Proxy Server, and PBXHub Server can communicate with each other internally.
Note: For security purpose, we recommend that you set up a security group for all the servers of Yeastar P-Series Cloud PBX, and set up the security group rule to open an SSH port 1022 and allow instance access from known IP addresses only; Contact Yeastar to obtain the IP allowlist.

YCM Server

YCM Server is the server that hosts a centralized platform, namely Yeastar Central Management platform. Through the graphical user interface presented on this server, you can implement the following features:

  • Create and manage Yeastar P-Series Cloud PBXs.
  • Monitor the status of all the servers (SBC Server, SBC Proxy Server, and PBXHub Server).

For more supported features of YCM Server, see Yeastar Central Management Administrator Guide.

SBC Server

SBC Server is a server that works as a security component of Yeastar P-Series Cloud PBX.

When the domain name of a Cloud PBX is resolved, it will point to the SBC Server, through which the traffic flow is sent to the PBX residing behind. In this way, the detailed network topology of Cloud PBX won't be exposed to the public Internet, greatly improving security performance.

Note: The SBC Server is embedded with default security rules to protect the P-Series Cloud PBX instances from malicious attack.

The data packet of the following services are transferred through an SBC Server:

  • PBX web access
  • Account trunk
  • SIP extension registration
  • Linkus clients login and registration

SBC Proxy Server

SBC Proxy Server is a server that provides extra security for Yeastar P-Series Cloud PBX.

The PBX services listed below go through the SBC Proxy Server. In this way, the PBX location can be hided, thus protecting the PBX from internet threats.

An SBC Proxy Server deals with the following PBX services:

  • LDAP/LDAPs
  • Register Trunk
  • Port-based Peer Trunk
  • DID-based Peer Trunk
  • Outbound service port assignment, including ports for SSH connection, AMI integration, and database grant.

PBXHub Server

PBXHub Server is the server where the Yeastar P-Series Cloud PBX instances are launched. The server is located in private subnet, which needs to be associated with a NAT gateway to ensure outbound Internet connectivity.

A PBXHub Server provides the following services for the Cloud PBX:
PBX instance launching

When you create Yeastar P-Series Cloud PBXs on the YCM Server for customers in different regions, the PBX instances are launched in the PBXHub Server. Customers can then log in and manage their own Cloud PBX.

Storage
In a PBXHub Server, you need to set up two additional storage disks.
  • Data storage disk: This storage disk is used to store the system data of all the Cloud PBXs in the PBXHub Server.
  • Recording storage disk: This storage disk is used to store the recording files of all the Cloud PBXs in the PBXHub Server.
Port assignment for Peer Trunk (Private Network)

When PBX administrator set up a Peer Trunk based on private network, PBXHub Server will provide a virtual IP address and a SIP registration port for the Cloud PBX.