Overview
The Yeastar Cloud Manager Basic Collector retrieves Cloud PBX instance allocation data from the Yeastar Central Management (YCM) platform using the YCM Open API.
This collector provides visibility into active Cloud PBX instances and their associated capacity allocations — including extension counts, concurrent call capacity, and call recording capacity — enabling organisations to validate subscriptions and allocate costs within Varibill.
The collector retrieves unrated allocation data, meaning no monetary values are supplied by the source system. Pricing and billing calculations are applied within Varibill based on configured contracts and pricing rules.
This is a point-in-time collector, meaning each execution retrieves the current state of PBX instances and their capacity allocations at the time of collection.
For general instructions on creating and running Source Collectors, see: Varibill Cloud Source Collectors – Setup and Configuration Guide
Collector Summary
| Field | Value |
|---|---|
| Source Collector Name | Yeastar Central Management – Version 6.0 |
| Collection Behavior | Point in Time |
| Rating Model | Unrated |
| Vendor Name | Yeastar |
| Product | Yeastar Central Management (YCM) – Cloud PBX |
| Purpose | Retrieves Cloud PBX instance capacity allocation data from Yeastar Central Management for billing and validation within Varibill |
About Yeastar Central Management
Yeastar Central Management (YCM) is a cloud-hosted platform used by service providers and resellers to deploy, manage, and monitor Yeastar Cloud PBX instances across their customer base.
Each Cloud PBX instance (also referred to as a PBX instance) represents an individual customer’s hosted phone system. YCM tracks each instance’s plan, extension capacity, concurrent call capacity, and call recording capacity.
Service providers use YCM to centrally manage their entire Cloud PBX portfolio, giving them visibility into customer subscriptions, capacity allocations, and instance status from a single administrative portal.
Note: Yeastar documentation for the YCM Open API is available via the Yeastar Central Management Developer Guide.
Data Collected
The YCMBasic 6.0 collector retrieves unrated Cloud PBX instance allocation data from Yeastar Central Management. The data collected depends on which collection switches are enabled in the collector configuration.
The following allocation types can be collected:
| Record Type | Description | Controlled By |
|---|---|---|
| Plan | The plan assigned to the PBX instance (quantity always 1) | Collect Plans |
| Extensions | The total extension capacity of the PBX instance | Collect Extensions |
| Included concurrent calls | The number of concurrent calls included with the plan (calculated as 1 per 4 extensions) | Collect Free Concurrent Call Capacity |
| Excess concurrent calls | Concurrent calls exceeding the included allowance | Collect Excess Concurrent Call Capacity |
| Call recording capacity | The total call recording capacity of the PBX instance | Collect All Recordings |
| Included call recording | The call recording capacity included with the plan | Collect Free Recordings |
| Additional call recording | Call recording capacity exceeding the included allowance | Collect Excess Recordings |
Important: The YCMBasic 6.0 collector reflects the state of Yeastar Central Management at the time it runs. More frequent execution improves billing accuracy for environments with frequent plan or capacity changes.
Note: Only PBX instances with a status of Running are included in the collected data. Instances in other states (for example, suspended or stopped) are excluded.
Prerequisites
Before configuring this collector, ensure that:
- You have administrator access to the Yeastar Central Management portal
- The YCM API feature has been enabled in System > API within the YCM portal
- You have copied the Client ID and Client Secret values from System > API
- You have noted the host URL of your YCM portal (for example,
https://ycm.example.com) - You have access to the Varibill Source Collector configuration screen
Tip: Client ID and Client Secret are read-only values generated by YCM. If your Client Secret is compromised, you can regenerate it from System > API in the YCM portal. Regenerating the secret will invalidate any existing access tokens.
Note: For full instructions on enabling the YCM API, see Enable YCM API in the Yeastar documentation.
Configuration Parameters
The parameters below are entered when configuring the collector in Varibill. They are grouped by function.
Connection Parameters
These parameters identify and authenticate against your Yeastar Central Management instance.
| Parameter | What it is | Format | Example | Required |
|---|---|---|---|---|
| YCM Host | The base URL of your Yeastar Central Management portal | URL (include https://, no trailing slash) |
https://ycm.example.com |
Yes |
| YCM Client ID | The Client ID generated in the YCM API settings | Alphanumeric string | 08xAgJUJ9TfTYnTmIczdu1VDJiXBeHy8 |
Yes |
| YCM Client Secret | The Client Secret generated in the YCM API settings | Alphanumeric string | (copy from YCM portal) | Yes |
Tip: Find your Client ID and Client Secret by logging in to the YCM portal and navigating to System > API. See Enable YCM API for step-by-step instructions.
Warning! The YCM Client Secret grants API access to your Yeastar environment. Store it securely and do not share it. If the secret is exposed, regenerate it immediately from the YCM portal.
Collection Switches
These parameters control which types of allocation data are collected
from each PBX instance. Set each switch to true to collect
that data type, or false to skip it.
| Parameter | What it controls | Default |
|---|---|---|
| Collect Reseller | When set to true, includes PBX instances created by
resellers (those with a creator role of Hosting User). When set
to false, only direct customer instances are
collected. |
false |
| Collect Plans | Collects the plan assigned to each PBX instance (quantity 1 per instance) | false |
| Collect Extensions | Collects the total extension capacity of each PBX instance | false |
| Collect Free Concurrent Call Capacity | Collects the number of concurrent calls included with the plan (1 per 4 extensions) | false |
| Collect Excess Concurrent Call Capacity | Collects concurrent call capacity exceeding the included allowance | false |
| Collect All Recordings | Collects the total call recording capacity of each PBX instance | false |
| Collect Free Recordings | Collects the call recording capacity included with the plan | false |
| Collect Excess Recordings | Collects call recording capacity exceeding the included allowance | false |
Note: All collection switches default to false. You must
explicitly enable the data types relevant to your billing
configuration.
Product Identifier Parameters
These parameters define the Product Identifier (PI) prefix applied to each allocation record submitted to Varibill. The values must match the product codes configured in your Varibill billing setup.
| Parameter | What it is | Example |
|---|---|---|
| Plan Code Product Identifier | Product Identifier prefix for plan allocation records | YCMPlan |
| Extension Code Product Identifier | Product Identifier prefix for extension allocation records | YCMExt |
| Free Concurrent Capacity Product Identifier | Product Identifier prefix for included concurrent call records | YCMFreeConcurrent |
| Excess Concurrent Capacity Product Identifier | Product Identifier prefix for excess concurrent call records | YCMExcessConcurrent |
| Recording Code Product Identifier | Product Identifier prefix for total recording capacity records | YCMRecording |
| Free Recording Code Product Identifier | Product Identifier prefix for included recording capacity records | YCMFreeRecording |
| Excess Recording Code Product Identifier | Product Identifier prefix for additional recording capacity records | YCMExcessRecording |
Note: The Product Identifier submitted to Varibill is constructed by appending the instance’s activation status and trial flag to the PI prefix. For plan records, the plan name is also included. Ensure your Varibill product configuration accounts for this format.
Operational Parameters
These parameters control collection and file management behaviour.
| Parameter | What it is | Format | Default |
|---|---|---|---|
| Delete data files older than | The number of days after which locally stored collection files are automatically deleted | Integer (days) | 62 |
| Maximum number of records per file | The maximum number of records written to a single output file before a new file is started. Must be between 1,000 and 50,000. | Integer | 10000 |
Configuration Steps
Step 1: Prepare Yeastar Central Management
- Log in to the YCM portal as an administrator.
- Navigate to System > API.
- Enable the API by turning on the API toggle.
- Copy the Client ID value.
- Copy the Client Secret value.
- Note the host URL of your YCM portal.
Step 2: Configure the Collector in Varibill
In the Varibill User Interface, open the Source Collector configuration screen.
Enter the required field values under the Details tab:
- Hosting Provider: Select Varibill Cloud
- Source Collector Name: Select Yeastar Central Management
Enter the connection parameters:
- YCM Host: The base URL of your YCM portal (for
example,
https://ycm.example.com) - YCM Client ID: The Client ID from the YCM API settings
- YCM Client Secret: The Client Secret from the YCM API settings
- YCM Host: The base URL of your YCM portal (for
example,
Configure the collection switches. Set each switch to
truefor the data types you want to collect.Enter the Product Identifier prefix for each enabled data type. Ensure the values match your Varibill product configuration.
Save the collector configuration.
Step 3: Run the Collector
Run or schedule the collector according to your standard Source Collector execution process.
For detailed instructions, see: Varibill Cloud Source Collectors – Setup and Configuration Guide
Troubleshooting
If the collector fails to connect to Yeastar Central Management, verify that:
- The YCM Host URL is correct and includes
https://with no trailing slash. - The Client ID is correct.
- The Client Secret is valid and has not been regenerated since it was last copied.
- The YCM API feature is enabled in System > API within the YCM portal.
- No IP restriction rules in the YCM API settings are blocking the Varibill collector’s IP address.
If no data is returned despite a successful connection, verify that:
- At least one collection switch is set to
true. - There are active PBX instances with a status of Running in your YCM environment.
Yeastar References
The following resources may assist with locating values or configuring your Yeastar Central Management API access.
Yeastar Documentation (External)
Note: Yeastar documentation is provided for reference. Steps and interface labels may vary depending on your YCM version and account permissions.
Related Documentation
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article