Yeastar P-Series Software Edition 83.20.0.21

• Added support for WhatsApp Message Template. PBX can automatically synchronize approved message templates from the associated WhatsApp Business Account ID for a WhatsApp channel. With these message templates, users can initiate or restart conversations in a WhatsApp channel outside the 24-hour customer service time window.

  For more information, see View WhatsApp Message Templates.

• Added support for the SMS messaging integration with Skyetel and Athena, which allows you to set up SMS message channels for these Service Providers on Yeastar P-Series Software Edition.

• Added support for Do Not Call Management, which allows you to create one or more DNC lists and add contacts whose numbers should be excluded from dial list of outbound campaigns. When a campaign is initiated, the system will check dial list against the DNC list based on specified number matching rule, and skips calls to any matched DNC numbers.

  For more information, see Add a DNC List.

• Added support for Attempt Controls, which allows you to limit call attempts to a contact or phone number, by time period or in total, helping you stay compliant with local regulations on outbound calling.

  For more information, see Configure an Attempt Control Rule.

• Added support for uploading templates for unsupported phone models from Yeastar-supported vendors (Path: Auto Provisioning > Resource Repository > Custom Templates), which allows you to add these phones to the PBX system for auto provisioning.

  For more information, see Upload a Template for a Custom Phone Model.

• Added support for the following IP phone configurations (Path: Auto Provisioning > Phones > > Preference):
  • Power LED notification settings for voicemail and missed call
  • Screensaver-related settings, including backlight timeout and screensaver exit behavior
  For more information, see Configure Power Indicator Settings for a Provisioned Phone and Configure Display Settings for a Provisioned Phone.
• Added support for synchronizing contacts data to remote phonebook of Yealink DECT phones, which allows users to query and place calls to contacts from the remote phonebook.

• WhatsApp Business Account ID is mandatory when setting up a WhatsApp channel, so that PBX can automatically synchronize the related message templates based on it.

  

• Added a configuration item Extensions Allowed to Create Messaging Sessions, which allows you to select the extensions that are allowed to initiate a messaging session with customers.

  

• Added a configuration item Close Session Automatically, which can be used to control the closure of the session. If you want the system to automatically close the sessions that have been inactive for a specific period of time, enable this option and set a desired timeout.

  

• Added support for synchronizing specific Entra ID (Azure AD) users. You can search in specific groups and select the desired users to synchronize, and individually assign existing extensions or create new extensions for these users.

  For more information, see Synchronize Users from Microsoft Entra ID to Yeastar P-Series Software Edition.

• Added support for selecting specific Entra ID (Azure AD) users in specific group when setting up to synchronize personal contacts of selected users to their Linkus Contacts directory.

  For more information, see Synchronize Microsoft Outlook Contacts to Yeastar P-Series Software Edition.

• Added an authentication method Bearer Token. When enabled, all HTTP requests to the CRM/Helpdesk will automatically include the header Authorization: Bearer {{.AccessToken}}, and the access token can be automatically refreshed at a specified interval.

  

• Added support for adding custom request headers, which will be included in every HTTP request to the CRM/Helpdesk.

  

• Added support for monitoring API events via Webhook.

  For more information, see Developer Guide - Monitor Event via Webhook.

• Optimized API interfaces for the following features:

  Feature	Description
  Added Message Campaign	With the new API interfaces of Message Campaign feature, the followings can be implemented: Query the message campaign list. Search specific message campaigns. Query the information of one or more message campaigns. Upload one or more files for message campaigns. Retrieve content of WhatsApp message template for message campaigns. Add, edit, or delete a message campaign. Retry a message campaign. For more information, see Developer Guide - Message Campaign.
  Optimized System	Optimized the interface system/get_menuoptions: Added request parameter values message_channel and message_queue, which allow you to query the information of existing message channels and the ID of message queues. For more information, see Developer Guide - Get Menu Options.
  Optimized IVR	Optimized the ivr/list, ivr/search, ivr/get, and ivr/query interfaces: Added a response parameter client_unique_ringtone, which returns the distinctive ringtone that will be played on extension users' Linkus clients when they receive calls from this IVR. Optimized the ivr/create and ivr/update interfaces: Added a request parameter client_unique_ringtone, which can be used to specify the distinctive ringtone that will be played on extension users' Linkus clients when they receive calls from this IVR.
  Optimized Queue	Optimized the queue/search, queue/get, and queue/query interfaces: Added a response parameter client_unique_ringtone, which returns the distinctive ringtone that will be played on agents' Linkus clients when they receive calls from this queue. Optimized the queue/create and queue/update interfaces: Added a request parameter client_unique_ringtone, which can be used to specify the distinctive ringtone that will be played on extension users' Linkus clients when they receive calls from this queue.

• Added an API event notification (30030) Bulk Message Sending Failed, which will be triggered when some messages failed to send in a message campaign.

  For more information, see API Event - Bulk Message Sending Failed.

• Fixed the API event issue: After subscribing to the (30012) Call End Details Notification event for CDR, incoming calls via account trunk did not trigger the event notifications.

For more information, see Set Ringtones for Incoming Calls.