Trunks
Trunk status tracked continuously and shown as a ratio of trunks up to trunks configured, so a single failed provider trunk is obvious at a glance.

Trunks, extensions, firmware and uptime, checked continuously and judged against thresholds set for Yeastar rather than borrowed from somewhere else.
Yeastar systems appear in their own monitor list, with their own status thresholds, and feed the same alerts, incidents and status pages as everything else you monitor.
Trunk status tracked continuously and shown as a ratio of trunks up to trunks configured, so a single failed provider trunk is obvious at a glance.
Extension registration tracked the same way, so you can see how much of the office is actually reachable.
The firmware each Yeastar system is running, recorded on the monitor list so systems left behind on an old build stand out.
System uptime tracked from the moment monitoring starts, alongside the up and down history.
Yeastar systems are scored on their own thresholds rather than the 3CX ones, because the two behave differently. Yeastar uptime is calculated from trunks and extensions.
| Healthy (green) | The uptime percentage at or above which a Yeastar system is considered healthy. |
|---|---|
| Critical (red) | The uptime percentage at or below which a Yeastar system is considered critical. |
| Degraded (orange) | Applies automatically between the two thresholds above. |
Alerts are delivered to your global alert email addresses and SMS numbers, or to addresses set for an individual system.
Adding a Yeastar system works the same way as everything else in the portal.
In the portal, go to Yeastar Servers under Monitor and choose Add Yeastar Server.
Give the system a name and its URL, along with the credentials the monitor should use.
Set the healthy and critical uptime percentages under Settings, in the Yeastar Status Thresholds section.
Alerts go to your global alert emails and SMS numbers, or to addresses you set for this system.
Yeastar systems appear under PBX incidents alongside 3CX, and can be published on a public status page like any other monitor.
Yeastar systems reachable over HTTPS from the monitoring server, including the P-Series. If you are unsure whether yours will work, ask us before you subscribe.
Yeastar uptime is calculated from trunks and extensions only, so applying the 3CX scoring would misjudge it. Setting them separately keeps both accurate.
Yes. Email and SMS alerts, incident records and public status pages all behave exactly as they do for every other monitor type.
The trial covers 15 servers, 15 webpages, 15 SSL certificates and 10 phone systems — the full feature set, at no cost.