PBXfactory

Yeastar V24.3: call quality monitoring

Published July 20, 20263 min readby The PBXfactory team

Yeastar P-Series Cloud V24.3 (firmware 84.23.0.123) adds call quality monitoring: live quality data for an extension's calls, a report after each call and an alert when quality is poor. The AI Receptionist gains custom tools — HTTP requests it can make mid-call to check an order or book an appointment.

Yeastar made P-Series V24.3 generally available for the Cloud Edition on 20 July 2026, as firmware 84.23.0.123. The features came with the beta on 29 June; the GA build adds one fix to call pop-ups. Two things stand out: a way to see — and prove — how good your calls sound, and an AI Receptionist that can act on information from your other systems. Details below, from Yeastar's release notes.

Why call quality monitoring matters

"The line was choppy" is one of the hardest complaints to chase. Voice over the internet depends on the caller's network, your office network, the SIP trunk and the PBX, and a problem in any one of them sounds the same. Without data, everyone points at someone else.

What Yeastar call quality monitoring does

V24.3 adds Call Quality Monitoring for extensions:

  • Live monitoring of an extension's call quality while calls are in progress.
  • Call performance reports after each call, with detailed metrics meant to help support staff troubleshoot.
  • A "Poor Call Quality" reminder — a new event notification that fires when a monitored call is rated as poor overall.
  • API support: you can switch monitoring on per extension, set when it ends, and read call scores and network data from the call report API.

The release notes don't list the exact metrics or the thresholds behind a "poor" rating. On the client side, Linkus Desktop 1.24.2 brings live call-quality data and post-call reports to the desktop app.

How to use it in practice

Monitoring is set per extension, with an end time. That suits the usual pattern: someone complains, you switch monitoring on for their extension for a few days, and you look at the reports. If quality drops on all their calls, look at their network or device first. If it drops only on calls over one trunk, talk to that SIP provider. The data turns a guess into a conversation with evidence.

AI Receptionist custom tools

The AI Receptionist could already answer questions from a knowledge base and route calls. With custom tools, it can now do things:

  • You define tools based on HTTP requests — calls to your own systems or online services — and assign them to an AI receptionist.
  • During a call, the receptionist uses them when the conversation needs it. The notes give checking an order status and booking an appointment as examples.
  • Every tool call is logged in the call records with the tool name, status, request parameters and response.

That log matters. When an AI takes actions on your behalf, you want to be able to see exactly what it asked and what came back.

What to think about before you connect a tool

  • Give each tool the least access it needs. Reading an order status is low risk; changing an order is not.
  • Make sure the system behind the tool can take the load and returns clear errors.
  • Test with real questions before you put it in front of callers.

Other changes in V24.3

  • Bandwidth SMS switches to OAuth 2.0 (client ID and secret). Existing integrations must be updated with the "Update Authentication" button before 2 December 2026 — no other reconfiguration needed.
  • Voicemail: a "No Greeting" option for extension, group and global voicemail.
  • CDR: column filters for source trunk, destination trunk and DID/DDI.
  • CRM and helpdesk templates: a connection keepalive check, up to 10 custom fields for OAuth2 templates, and a choice of POST or PUT for call journals.
  • Microsoft Entra ID: several sync fixes, including one for high CPU when switching on Teams presence sync for more than 200 extensions at once.
  • Web interface: Catalan and Hungarian.
  • AI Transcription: usage is now shown correctly (it was counted in seconds but labelled as minutes).
  • API: CDR query interfaces under openapi v2.0.

What this means for you

On a Yeastar P-Series Cloud PBX from PBXfactory, Yeastar's updates are applied for you in announced maintenance windows, and urgent security fixes sooner.

Call quality monitoring is a useful tool when you raise a ticket: if your PBX isn't reachable, that's ours to fix; if one office's calls sound poor, the reports help you and your IT partner find where. AI Receptionist minutes beyond the included free ones are a paid Yeastar add-on — ask our support whether it's available for your PBX. Building custom tools is PBX configuration; Yeastar's documentation or our support packages can help.

Questions and answers

What does call quality monitoring show in V24.3?
Real-time quality data for an extension's calls, a performance report after each call, and a 'Poor Call Quality' reminder when a monitored call is rated poor. The release notes don't list the exact metrics or thresholds.
What are AI Receptionist custom tools?
HTTP requests you define and assign to an AI receptionist. During a call it uses them when needed, for example to check an order status or book an appointment, and each use is logged in the call records.
I use Bandwidth for SMS. Do I need to do anything?
Yes. Bandwidth SMS now authenticates with OAuth 2.0. Yeastar's notes say existing integrations must be updated with the 'Update Authentication' button before 2 December 2026.
Where are Yeastar's release notes for V24.3?
In Yeastar's release notes for 84.23.0.123.