Yeastar P-Series Software Edition 83.21.0.66

• Extension users can easily send the call information via email on their Linkus Web Client / Desktop Client.

  Location	Illustration
  Call window
  Post-call pop-up
  Call log

• By default, the call information email is sent using the default email client on the extension users' computer, the users can also select their preferred email client for email sending using the newly added configuration item Choose Email Client on Linkus Web Client / Desktop Client (Path: Preferences > Features > Call Follow-Up Via Email).

  

• Added an email template Call Follow-Up Template Via Email in the PBX system (Path: System > Email > Email Templates). This template contains call information for a 1:1 call and is used when extension users click to send call details via email during a call or after calls.

• Fixed the extension import issue: When adding extensions in bulk via CSV importing, the default setting of Play Ringtone on the extensions' Linkus clients was incorrect.
• Fixed the time-based presence auto switch issue:
  • When an extension's presence status was switched automatically based on the time-based presence auto switch rules, the Accept Push Notifications setting did not update to the value set in the new presence.
  • After bulk-configuring time-based presence auto switch rules, some extensions did not update their presence status as scheduled.

• Fixed the Microsoft SQL Integration issue: When using the format {server address}\{instance name} to connect to a specific named instance in a Microsoft SQL server, the connection failed.
• Fixed the LDAP contact synchronization issue: PBX failed to synchronize all specified contacts from the LDAP server.

• Added support for auto provisioning the following Akuvox IP phones.
  • R20A
  • E16C V2.0
  • S562W
  • S563W
  • X912K
• Added support for uploading phone images in .dob format (Path: Auto Provisioning > Resource Repository).
• Optimized the parameter import compatibility: When adding phones in bulk via CSV import, PBX automatically ignores the setting of the Authentication First-time parameter for phone models that do not support this feature, ensuring successful bulk imports and thus improving deployment efficiency.

For example, user A and user B are in a call, when user A transfers the call to user C via blind transfer, user C will then see the number and/or name of user B.

• Optimized the recording feature setting: Added a configuration item Delete the recording file when deleting the CDR (Path: Call Features > Recording), which allows you to decide whether to delete or retain the corresponding recording files when manually deleting a CDR.
  Note: This feature only applies to manually deleted CDRs. For files deleted by the Auto Cleanup, CDRs and recording files are cleaned up independently based on their respective retention policies.

  

• Optimized the recording file management (Path: Reports and Recordings > Recording Files):
  • Added a filter setting File Location, which allows you to search specific recording files based on the storage location.

    

  • Added a File Location column in the recording file list, which intuitively display the current storage location of each file.

    

    Tip: You can hover over the icon to view the full storage path and click to copy.

    

    File Location	Description
    Archived ()	The recording file has been archived to an external archive server.
    Local ()	The recording file is stored on PBX-attached storage.

• Added support for the MS-CHAP v2 authentication protocol for PPPoE connection. When obtaining an IP address from a PPPoE client, PBX is compatible with ISPs or network providers that require this protocol, ensuring successful connection and IP assignment.
• Fixed the audio issue: Calls had no audio when the PBX NAT type was set to the External Host.

• Added a server type SharePoint (Path: System > Archive > Archive Task > Archive Server), which allows you to add Microsoft SharePoint as an archive server and schedule tasks to archive PBX's call recordings and backup files to your SharePoint container.

  For more information, see Archive Files to Microsoft SharePoint.

• Optimized the archive server setting for S3.
  • Renamed the server type Amazon S3 to S3, which allows you to connect to any S3-compatible object storage services.
  • Added configuration items Endpoint and Region, which requires you to specify the service URL and the bucket region to ensure a successful connection.
  For more information, see Archive Files to S3-Compatible Object Storage.
• Added the following settings for recording archiving tasks.

  Setting	Description
  Recording File Format	This setting can be used to specify the format for the archived recording files. Note: This option appears only when the stereo-separated recording feature is enabled (Path: Call Features > Recording > Support generating stereo-separated recording files (left/right channel)).
  Skip archived files	When enabled, the system skips recording files that have already been archived. Note: Repeated archiving will update the file's storage location, but will not delete files already archived to the archive server.
  Delete local files after archiving	When enabled, the system removes the local recording file after a successful archive. Note: After deletion, playback and download for the archived recording files are still supported from the PBX server and Linkus clients. However, playback/download from third-party platforms or Dynamics 365 will no longer be supported.

• Optimized archival logs: Added support for checking the archiving details of an archive task.

  

• Fixed the FTP archiving issue: After setting a recurring task to periodically archive recording files to an FTP server, the task failed at the second execution.

• Optimized the call journaling feature for the CRM/Helpdesk integration: Added a configuration item Disable Display Missed Call Records in Unanswered Agents. If enabled, for queue and ring group calls, the PBX will only synchronize the call logs to the CRM of the agent who answers the call, while missed call logs for the same call are not synchronized to the CRM of agents who did not answer.
  Note: The supported platforms include Bitrix24, HubSpot, Oddo, Salesforce, Zoho, Zoho Desk.
• Optimized the following features for the CRM/Helpdesk integration template.

  Feature	Description
  Authentication Method	Added a configuration item Content Type (Path: Request Configuration > Authentication Method). When the authentication method is set to OAuth2 or Bearer Token, this configuration item can be used to set the content type of the token retrieval request.
  Follow-up Request	Added support for adding follow-up requests (Path: Request Configuration > Follow-up Requests). You can configure up to 10 follow-up requests, which will be automatically triggered upon the completion of a specified operation (such as token retrieval or token refresh), and their response data can be extracted and stored in global variables for reuse elsewhere in the integration.
  Call Journaling	Added a configuration item Disable Display Missed Call Records in Unanswered Agents (Path: Call Journal). If enabled, the corresponding setting will be available to configure in the integration. This can be used to determine whether call logs for queue and ring group calls are synchronized only to the CRM/Helpdesk of the agent who answered the call, while missed call logs for the same call are not synchronized to the CRM/Helpdesk of agents who did not answer.

  For more information, see Add a CRM Integration Template and Add a Helpdesk Integration Template.

• Added support for Swedish interface language.

• Added support for call parking via a dedicated button. By clicking the Park button on the call window, extension users can park an active call to a system-assigned or manually-selected parking number.

  

• Added compatibility with the following system-level configurations:
  • Caller ID name display rules: Depending on the rules configured on the PBX, Linkus Web Client may display the matched contact name, the caller ID name carried by the caller, or both.
  • Login restriction: If the PBX is integrated with Microsoft Entra ID (Azure AD), Active Directory, Google Workspace, or Red Hat SSO, and the login method is configured to Enforce SSO login only, extension users must log in to Linkus using their account from the integrated third-party platform.