Deployment Preparation for Remote Management

Yeastar Central Management supports remote management for on-premises P-Series PBX and Yeastar TA gateways. This topic provides the prerequisites and server requirements for Remote Management service.

Prerequisites

To work properly with the Remote Management service, ensure the following servers in your system are running the required firmware versions:
Server Requirement
YCM Server 87.15.0.83 or later
SBC / SBC Proxy Server 86.15.0.70 or later
PBXHub Server 85.15.0.70 or later
P-Series PBX System
  • P-Series Appliance Edition: 37.19.0.110 or later
  • P-Series Software Edition: 83.19.0.110 or later
TA Gateway
  • TA1600/TA2400/TA3200: V3 or later
  • TA1610: V3 or later

Usage Scenarios

The Remote Management service supports the following two management scopes. Choose one based on your needs and complete the corresponding preparations.
  • Scenario 1: Manage P-Series PBXs only
    If your want to remotely manage on-premises P-Series PBX systems only, complete the following preparations:
    1. Change the domain and certificate for your existing YCM server. For more information, see Modifications required on YCM Server.

    2. Contact Yeastar to provide the environment information and request for deployment.

  • Scenario 2: Manage both P-Series PBXs and TA gateways
    If you want to remotely manage both on-premises P-Series PBX systems and Yeastar TA gateways, complete the following preparations:
    1. Change the domain and certificate for your existing YCM server. For more information, see Modifications required on YCM Server.
    2. Prepare a dedicated management server for TA gateway remote management. For more information, see Requirements for dedicated remote management server.

    3. Contact Yeastar to provide the environment information and request for deployment.

Modifications required on YCM Server

To enable remote management, you must perform the following modifications on your existing YCM server.

Item Description
Domain name
  • Change the YCM server's single domain name to a wildcard domain.

    For example, if the YCM server domain name is ycm.example.com, change it to a wildcard domain name *.ycm.example.com.

  • Update your DNS records to resolve this wildcard domain to the public IP address of your YCM server.
    Important: If you want to remotely management both P-Series devices and TA gateways, ensure your DNS supports individual (single) domain records and does not rely solely on a wildcard domain. This is essential to ensure proper remote connectivity for TA gateways.
Certificate Prepare an SSL certificate and private key files, which is mandatory to establish secure, encrypted remote connections and to prevent browser security warnings.

Requirements for dedicated remote management server

To extend remote management capabilities to TA gateways, you must provision a separate server that meets the following specifications.

Hardware requirements
Resource Requirement
CPU Intel brand, 4 vCPU (thread), 3 GHz
Memory 8 GB
Storage 200 GB
Important: Minimum 150MB/s read speed and 150MB/s write speed.
Operating system requirements
Item Requirement
Version Ubuntu 24.04 LTS (64-bit)
Language English
Important: The default operating system language MUST be set to English to ensure the proper operation of the server.
Network requirements
Item Requirement
Deployment Location The server must reside within the same VPC (Virtual Private Cloud) as the other servers of the system to ensure internal communication between the components.
Public Access Assign an public IP address to the server.
Domain name Prepare a wildcard domain name (e.g. *.mgt.example.com) and the relevant certificate for the server.
Network port requirements
To ensure seamless communication between servers as well as the connectivity with endpoint devices, expose the required server ports according to the table below.
Port Protocol Purpose
22 TCP TA gateway connection
80 TCP YCM interface request
443 TCP
10001-10997 TCP TA gateway remote access