Yeastar P-Series Software Edition

Release date: May 4, 2023

New features

Two-factor Authentication (2FA)
Yeastar P-Series Software Edition supports to enable two-factor authentication (2FA) for super administrator account. With 2FA enabled, both the account password and an additional authentication code are required for login, which adds an extra layer of security to the PBX.
Authentication code can be obtained via either of the following two methods:
  • Authenticator application on mobile phone
  • Email address that is associated with the super administrator account
For more information, see Two-factor Authentication (2FA) Overview.
Note: Extension users can also enable two-factor authentication for their accounts on Linkus Web Client and Desktop Client, and the configuration will be applied to all Linkus clients.

For more information, see Two-factor Authentication (2FA) on Linkus Web Client and Two-factor Authentication (2FA) on Linkus Desktop Client.

Yeastar Global Anti-hacking IP Blocklist
Added support for Yeastar Global Anti-hacking IP Blocklist.

Yeastar provides a central database of IP addresses that have been blocked by Yeastar PBX systems worldwide or that are suspected of malicious activity or attack. You can download Yeastar Global Anti-hacking IP Blocklist to secure the connections to your PBX, reducing the risk of cyber attacks.

For more information, see Download Yeastar Global Anti-hacking IP Blocklist.

Note: If you would like to contribute to the IP blocklist, you can share with Yeastar by reporting your system's IP blocklist. For more information, see Report PBX's IP Blocklist to Yeastar Global Anti-hacking IP Blocklist.
Hot Desking
Hot Desking feature allows multiple extension users to share a single desk phone. By logging in with their extension number and voicemail PIN, users can quickly log in to the phone, and make or receive calls with their own extensions.
To use the feature, you need to set up a hot desking phone by auto provisioning, and enable hot desking for extension users. For more information, see Hot Desking Overview.
Microsoft Teams Integration
Microsoft Teams integration allows extension users to make calls right within Microsoft Teams, without the need of a Teams calling license. With the embedded Linkus app in Microsoft Teams, users can directly place calls, look up contacts, check voicemails within Teams.
For more information, see Microsoft Teams Integration Guide.
Video preview
Added support for video preview of intercom calls. You can enable video preview for the extension registered on the door station. When receiving an incoming call from the door station, users can preview the visitor's video on their Linkus Web Client and Desktop Client while ringing.
For more information, see Enable Video Preview of Intercom Calls for Extensions.
NEW Linkus Desktop Client
Yeastar releases a NEW Linkus Desktop Client dedicated for Yeastar P-Series PBX System.

With Linkus Desktop Client, users can access a full suite of telephony features as Linkus Web Client, while enjoying enhanced privacy and security, with one simple desktop app.

For more information, see Linkus Desktop Client User Guide.
Microsoft Outlook Integration
Microsoft Outlook integration allows extension users to integrate the Linkus Desktop Client with their Microsoft Outlook for Windows. With the integration, users can directly click to call their Outlook contacts, receive call popups, and check the call logs directly in Outlook.

For more information, see Microsoft Outlook Integration Guide.

Improvement and bug fixes

Web interface

Optimized the user experience of web interface.

System security
Improved system security performance.
'Yeastar Linkus for Google' Chrome extension
  • Added support for multiple interface languages, including Chinese, Italian, German, and Portuguese.
    Note: The language of the Chrome extension follows the language setting of the browser, and cannot be changed within the extension.
  • Added compatibility with the NEW Linkus Desktop Client.

    For more information, see 'Yeastar Linkus for Google' User Guide (Desktop Client).

Azure Active Directory Integration
  • Added support for Microsoft Outlook contact synchronization.
    Supported Contact types Description
    Outlook contacts Synchronize Azure AD user's personal Outlook contacts to the associated extension's Personal Contacts.
    Shared Mailbox Contacts Synchronize shared maibox contacts from users' Microsoft 365 account to the PBX's phonebook(s).
    For more information, see Synchronize Microsoft Outlook Contacts to Yeastar P-Series Software Edition.
  • Added support for Microsoft Teams user presence synchronization.

    The feature allows PBX to synchronize Microsoft Teams users' presence to that of PBX extensions. For example, when Teams user presence is "Busy", then PBX extension presence will automatically switch to corresponding presence status.

    For more information, see Enable Microsoft Teams User Presence Synchronization.

Note: If you have previously implemented Azure Active Directory integration, you need to click Authorize on the top of the integration page to re-authorize for the integration after upgrading the PBX, so as to use the new features.

  • Added support for using the trunk username as the authentication name of an account trunk.

    Important: This option is ONLY applicable to the situation that your device needs to connect with PBX via Account trunk but the device doesn't support the authentication name field. In general use, we recommend that you set a specific authentication name for the trunk.
  • Added support for customizing the SIP headers of From Host Part and To Host Part for a peer trunk (Path: Extension and Trunk > Trunk > Peer Trunk > SIP Headers > Outbound Parameter).
    After you customize these fields, all outbound calls through this SIP trunk will carry the corresponding values in the SIP INVITE header field.
    Important: You MUST set the value according to the requirements of the SIP Trunk providers. The misconfiguration will cause call issues.

  • Fixed the following trunk issues:
    • When the outbound proxy of a register trunk was enabled, inbound calls and outbound calls through the trunk all failed.

    • Failed to delete the strip of a caller ID reformatting rule.
Auto Provisioning
  • Added support for CTI feature for the following IP phones.
    Vendor Model
    • V62
    • V64
    • V65
    • V67
  • Fixed the following auto provisioning issues:
    • If multiple IP phones were assigned to the same extension, performing a reboot via auto provisioning only took effect on the most recently bound phone.
    • The changes made to the time zone when bulk editing IP phones didn't take effect.
    • Failed to add a Snom phone via RPS provisioning method.
  • Added support for Agent Auto Pause feature (Path: Call Features > Queue > Agent Options > Agent Auto Pause).
    If you enable this feature and set a threshold of missed calls, when a queue agent's consecutive missed calls reach the preset threshold, the agent will be automatically paused in the queue, and receive an email notification.
    Note: This feature takes effect only when the queue's Ring Strategy is NOT Ring All.

  • Optimized missed call log for queue calls.

    When there is a missed queue call, a "Missed call" record will be displayed in the call logs on all queue agents' Linkus web clients.

  • Fixed the wallboard issue: The answered calls and total calls displayed on wallboard were incorrect.
Email Template
Added support for Email template language of French (Path: System > Email > Email Templates > Notification Email Language).
Call issue
Fixed the following call issues:
  • When a user transferred an outbound call to another external number via blind transfer, the call was failed.
  • When users logged in to Linkus Web Client using FQDN that contained capital letters on Google Chrome, there were no sound for the calls on the Web Client.
  • There was one-way video feed during a video call on Linkus Web Client.
  • The caller ID was not displayed after the call was picked up by a user.
  • Call channels were fully occupied unexpectedly, resulting in failure of making and receiving calls.
  • After retrieving a parked call on Operator Panel, there was still a call channel occupied.
Fixed the extension presence issue: The settings of Time-conditional Presence Auto Switch didn't take effect, resulting in calls being routed to incorrect destinations.
LDAP server
Fixed the following LDAP server issues:
  • The LDAP server didn't display the LDAP credentials of newly created extensions.
  • After the company name in the Organization Management setting was changed, the company name displayed in the LDAP contact details was not updated.
Fixed the recording issue: An extension was set to be recorded, but when the extension user answered a transferred call from a ring group, the call was not recorded.
Voice Prompt
  • Fixed the Music on Hold issue: The play order of the local audio was set to play alphabetically, but the setting didn't take effect.
  • Fixed the custom prompt issue: The custom prompt uploaded in the inbound route destination setting didn't take effect.
API interface
  • Fixed the extension API interface issue: When using the extension/update interface to edit an extension, the response would report an error if the caller_id parameter was included.
  • Fixed the outbound route API interface issue: When using the outbound_route/update interface to change the caller_id of an outbound route, the API responded with a success message, but the changes didn't take effect.