Yeastar P-Series Cloud Edition 84.19.0.22
Release date: May 8, 2025
New features
- Dynamics 365 CRM Integration
- Yeastar P-Series Cloud Edition supports deep integration with Microsoft
Dynamics 365 CRM. After integrating the PBX system into Dynamics 365,
users can directly make and receive calls, manage call activities, and
more within the Dynamics 365 CRM interface via the embedded 'Linkus for
Dynamics 365' plugin, streamlining their workflow. Key features of the
integration include:
- Click-to-call
- Call pop-up
- Dynamics contact creation
- Phone call activity logging
- Access to call recordings
- Google Workspace Integration
- By integrating Yeastar P-Series Cloud Edition with Google Workspace, you can synchronize Google Workspace users to PBX, and enable the synced users to log in to Linkus UC clients by their Google accounts with Single Sign-on (SSO).
Improvement and bug fixes
- User Role
- Optimized the permission control of Call
Reports:
- Added support for configuring operation permissions for a role,
including report downloading and access to Rate
settings.
- Added support for granular access control, allowing you to
specify accessible report types and data scopes.
- Added support for configuring operation permissions for a role,
including report downloading and access to Rate
settings.
- Auto Provisioning
-
- Added support for auto provisioning the following IP phones:
Vendor Phone Model Snom - D710, D712, D715
- D720, D725
- Fixed the following auto provisioning issues:
- IP phones failed to retrieve the PBX time zone during auto provisioning.
- When add multiple IP phones for bulk auto provisioning, only the last phone was successfully provisioned.
- Added support for auto provisioning the following IP phones:
- Inbound Route
- Optimized the DID pattern setting: When DID Matching Mode is set to Match DID Range to Extension Range or DID Number to Specific Extension, you can directly select the desired DID number(s) from a list of DIDs configured on trunks, eliminating the need for manual input.
- Active Directory Integration
-
-
Optimized the following synchronization features:
- Optimized User Synchronization settings:
Added a Map
setting,
allowing for user field mapping between PBX and AD
user attributes, ensuring seamless synchronization
of specified user data.
- Optimized Organizational Unit
Synchronization setting: Added a
synchronization method Read Specific
Property Value, allows synchronization
of Organizational Units (OUs) using a specific
property, ensuring more flexible and precise mapping
of organizational structures.
For more information, see Active Directory Integration Guide.
- Optimized User Synchronization settings:
Added a Map
setting,
allowing for user field mapping between PBX and AD
user attributes, ensuring seamless synchronization
of specified user data.
- Fixed the following synchronization issues:
- Specified users were not fully synchronized to the PBX, and the web page displayed a "Network Request Error."
- After performing data synchronization, the webpage remained stuck in the loading state.
-
- Microsoft Entra ID (Azure Active Directory) Integration
-
- Optimized User Synchronization settings: Added a
Map
setting,
allowing for user field mapping between PBX and
Entra
ID user's attributes, ensuring seamless
synchronization of specified user data.
For more information, see Microsoft Entra ID (Azure Active Directory) Integration Guide.
- Fixed the Teams user presence synchronization issue: Teams presence status changes were not synchronized with the PBX extension.
- Optimized User Synchronization settings: Added a
Map
setting,
allowing for user field mapping between PBX and
Entra
ID user's attributes, ensuring seamless
synchronization of specified user data.
- Omnichannel messaging
-
- Added support for the SMS messaging integration with Apidaze,
which allows business to set up SMS messaging channels for the
Service Provider on Yeastar P-Series Cloud Edition.
For more information, see Set up an SMS Channel for Apidaze.
- Simplified the authentication process for messaging integration
via SMS API.
If the Service Provider does not require authentication, the following information and configurations can be skipped:
- HTTPS REST API for verifying authentication: PBX does not need to send the API request with an API key to Service Provider for identity verification.
- Secret for webhook request verification: PBX does not need to perform signature verification using the secret for webhook requests received from the Service Provider.
- Added support for the SMS messaging integration with Apidaze,
which allows business to set up SMS messaging channels for the
Service Provider on Yeastar P-Series Cloud Edition.
- CDR
-
- Added a DID filter, which allows you to filter call
detail records by DID number.
- Fixed the CDR issue: When All Busy Mode for Endpoints was enabled for an extension, and the extension received a call during an ongoing call, the CDR of the new call was displayed incorrectly.
- Added a DID filter, which allows you to filter call
detail records by DID number.
- API
- Optimized the following CDR API interfaces:
- 'Yeastar Linkus for Google' Chrome extension
- Fixed the display issue: When dialing a number starting with
#
, the character was incorrectly displayed as%23
. - Linkus Web Client
-
- Added support for logging in to Linkus Web Client with Google
account. Note: This feature is supported only when you have integrated the PBX with Google Workspace and enabled Single Sign-on (SSO) feature.
- Added support for creating up to 3,000 personal contacts.
- Optimized Caller ID Name display in Call Logs, Voicemails, and Recordings: When a caller number doesn't match any extensions or contacts, its associated Caller ID Name will be displayed, if any.
- Optimized Queue Panel: Added support for monitoring statistics
and managing calls of multiple queues in a single pane within
Queue Panel. Users can create a group
to customize the call queues to be displayed together.
- Added support for logging in to Linkus Web Client with Google
account.
- Call issue
- Fixed the call transfer
issues:
- After a call was transferred, the caller ID name was not updated to reflect the original caller.
- When a ring group member transferred a call to an external number, the call was immediately disconnected, and the call transfer failed.
- Extension
- Fixed the extension issue: The Accept calls from Ring Group option was disabled by default when importing extensions.
- Trunk
- Fixed the following trunk issues:
- When the PBX was connected to the Yeastar TA100 FXS gateway via sip trunk, sending a fax using an extension registered on the FXS port of the gateway failed.
- After an outbound call was made through a trunk, placing a second outbound call through the same trunk would cause the first call to be unexpectedly dropped.
- Outbound Route
- Fixed the outbound route issue: After setting a PIN list in an outbound route, the list was not displayed upon reopening, and the PINs did not work when used for outbound calls.
- CRM Integration
-
- Fixed the CRM template issue: A custom CRM template configured with API key authentication could be saved successfully, but displayed an error message when reopened.
- Fixed the Zoho CRM integration issue: The integration with Zoho CRM via PhoneBridge failed to work properly after a PBX restart, resulting in issues with call log and recording synchronization.
- Zoho Desk Integration
- Fixed the Zoho Desk user list issue: The PBX only retrieved 10 Zoho Desk users.