For a lot of offices, Microsoft Teams is where the working day happens: chat, meetings, files. The phone system has usually lived next to it, in its own app. Yeastar's P-Series Cloud Edition 84.15.0.74, released on 17 July 2024, narrows that gap. It upgraded the Microsoft Teams integration so people can place and handle business calls without leaving Teams.
Here's what the release contains, how the Teams calling works, and what it means if you run a Yeastar P-Series Cloud PBX today.
What's new in Yeastar 84.15.0.74
According to Yeastar's release notes, this release brought:
- Calling from inside Microsoft Teams. Users can make, receive and control calls in the Teams interface. The calling endpoint is Linkus Web, Linkus Desktop or an IP phone.
- A prefix for emergency numbers. The PBX can add a prefix automatically when someone dials an emergency number.
- Control Linkus Desktop from Linkus Web. The web client can act as a control panel for a connected desktop client.
- Smaller fixes and tweaks. Message text in omnichannel conversations now wraps at word boundaries, the
call/play_promptAPI returns acall_id, and a Grandstream auto-provisioning template no longer reverts to an older version after a reboot.
How Microsoft Teams calling works with Yeastar
The important idea is the split between interface and endpoint.
Teams becomes the place where your users see and control calls. The call itself still runs on your Yeastar P-Series PBX and is carried by a Yeastar endpoint: Linkus Web, Linkus Desktop or a desk phone. That means:
- Your extensions, numbers and SIP trunk stay on the PBX.
- Your call routing — IVR, ring groups, queues, business hours — keeps working as before.
- Your users get one place to work, instead of switching between Teams and a separate phone app all day.
Which endpoint should you use?
| Endpoint | Good for |
|---|---|
| Linkus Web | People who work in the browser and don't want to install anything |
| Linkus Desktop | Heavy phone users who want a dedicated client on their computer |
| IP phone | Reception, shared desks, or anyone who prefers a handset |
You can mix them across your team. The right choice is mostly about where people sit and how much time they spend on the phone.
Emergency number prefix: why it matters
Some carriers expect a prefix in front of emergency calls so they route correctly. With 84.15.0.74, an admin can set this once — under Call Control, Emergency Number, Outbound Rules — and the PBX adds the prefix automatically whenever someone dials an emergency number.
Nobody has to remember a special dialling rule in a stressful moment. If your SIP trunk provider asks for a prefix on emergency calls, this is where it goes.
Controlling Linkus Desktop from Linkus Web
The release also added a CTI-style link between the two Linkus clients. Linkus Web acts as a visual control panel, while the call is actually placed and received on the connected Linkus Desktop client.
That helps people who keep a browser tab open all day but want audio handled by the desktop app — for example, with a headset that works best with the desktop client.
What came after: Teams in later Yeastar releases
The Teams story didn't stop in 2024. Later Yeastar releases built on it:
- 84.18.0.102 (March 2025) made Teams presence sync configurable in either direction or both, including statuses like "In a Meeting" and "Presenting". See our post on CRM templates, LDAP and call notes.
- 84.20.0.128 (October 2025) stopped Teams presence from overriding an extension's status while it's ringing or busy.
- V25.3 (October 2026) added the Yeastar for Teams Desktop Plugin, so Teams users can make and receive calls without Linkus or a SIP device as the endpoint. More in our post on Message Flow Designer and the Teams Desktop Plugin.
Setting up the Teams integration
The Teams integration is set up in your PBX's own admin panel, where it connects to your company's Microsoft 365. Yeastar's documentation walks through it step by step, and it's the best place to start.
A few practical tips before you begin:
- Decide the endpoint per person before you roll it out, so nobody ends up with Teams calling and no audio device.
- Test with two or three people first, including one who works mostly from a mobile or laptop.
- Keep your routing as it is. The Teams integration changes where people click, not how calls reach them.
On PBXfactory
If you run a Yeastar P-Series Cloud PBX from PBXfactory, Yeastar's firmware and security updates are applied for you — routine ones in announced maintenance windows, urgent security fixes sooner. You don't install anything.
Configuring the Teams integration itself is PBX configuration, which isn't part of our included support. Yeastar's documentation covers it well; if you'd rather have help, your IT partner or one of our support packages can do it with you.