Yeastar P-Series Software Edition 83.23.0.83-beta1

For more information, see Data Connector Integration Overview.

• Specify the Large Language Model (LLM) used by the AI receptionist based on your business needs, such as Gemini, GPT, or Claude, and customize the system prompt to define the AI receptionist's response style and behavior.

  For more information, see Create an AI Receptionist and Update Settings of an AI Receptionist.

• Set up custom rules for the AI receptionist to collect caller information (e.g., name, email, order number) from the call, and deliver the collected data to a human agent upon call transfer.

  For more information, see Manage Skills for an AI Receptionist - Information Collection.

• Added support for creating a custom account with root access privilege during the automated Ubuntu ISO installation process.
  Note: After installation, you can run sudo -i from this custom account to switch to the root user.

  

• Added the following configuration parameters for the XML configuration file used for PBX activation and setup.

  Module	Element	Description
  Extension Group	Group.UserEnbCallDistribution	Whether users in the Default_All_Extensions group have permission to distribute incoming calls on Operator Panel, including redirect, transfer, drag and drop operation.
  	Group.UserEnbExtCallDistribution	Whether users in the Default_All_Extensions group have permission to distribute incoming calls on Extension Page, including redirect and transfer operation.
  Client Permission	ContactVisibilityRules.Rule	Define the contact visibility configuration.
  Contacts	LdapSetting.Enable	Whether to enable LDAP Server.
  Auto Provisioning	PhoneOptions.EnbRandomPassword	Whether to assign randomly generated phone passwords to phones during the auto-provisioning.
  PBX Settings	EnbCallFwdPrompt	Whether to play call forwarding prompt.
  	EnbCallWaitingPrompt	Whether to play call waiting prompt.
  	EnbNumberFilter	Whether to automatically remove all special characters from dialed numbers before sending to the trunk.

  Download the XML configuration file for the latest parameters.

• Added support for configuring a function key for an extension to monitor and pick up incoming calls to members of a specified extension group to which the extension belongs (except for the Default_All_Extensions group) (Path: Extension and Trunk > Extensions > Function Keys).

  

  The function key can be applied to both Linkus clients and auto-provisioned IP phones, and achieves the followings:

  Note: For Linkus Mobile Client, users must upgrade their Linkus app to the following versions:

  • Linkus iOS Client: Version 5.26.15 or later
  • Linkus Android Client: Version 5.26.10 or later
  • Monitor whether there are incoming calls ringing on any member's extension in the extension group.
  • Display the incoming calls to members in the extension group (up to 10 calls on Linkus clients, and up to 2 calls on IP phones), allowing users to select a call to pick up.
  • Press the function key to directly pick up the first incoming call in the extension group.

  For more information, see Pick up a Call for a Group Member.
• Fixed the extension registration issue: Extensions registered on IP phones frequently went offline.
• Fixed the call forwarding setting issue: When bulk editing extension presence settings, call forwarding setting enabled under Do Not Disturb was disabled after switching to another status and then back.

For more information, see SIP Trunk Settings.

• Fixed the function key issue: When more than 120 function keys were configured, the excess keys did not take effect on an IP phone after auto provisioning.
• Fixed the custom template issue: The number of templates displayed in the list did not match the total count.

For more information, see Create a Ring Group.

• Optimized the IVR call recording logic (Path: Call Features > Recording):
  • Before this version: If the source channel of a call entering an IVR (e.g., trunk or queue) was selected for auto recording, the call would be recorded regardless of whether the IVR itself was selected.
  • After this version: If an IVR is not selected for auto recording, a call entering that IVR will not be recorded, even if its source channel is selected.
    Note: For a call flow, if the setting of a Record component is set to Enabled and the call is routed to an IVR, the system will follow the call flow's setting and record the call even if the IVR is not selected for auto recording.
• Added a limitation of up to 99 call recording files for each download. A prompt will appear when the selection exceeds this limit (Path: Reports and Recordings > Recording Files).

  

• Added support for Email template language of Polish (Path: System > Email > Email Templates > Notification Email Language).
• Added the {{.ExtensionName}} and {{.ExtensionNumber}} variables to the email template of Agent Auto Pause, which can be used to obtain the name and number of the agent extension.

• Added support for Chat Journal. When enabled, if the recipient's number of an external chat session is identical to a CRM/Helpdesk contact, the chat messages (including the message channel type and time-ordered message records) will be synchronized to the CRM/Helpdesk system when the chat session is closed.

  

• Optimized the Call Journal setting: Added support for variables {{.AI_Transcription}}, {{.AI_Summary}}, and {{.Call_Note}}. By adding these variables, the PBX will automatically synchronize the corresponding content to the CRM/Helpdesk system when the call ends or when the content is updated.
  Note: For Zoho Desk integration and Zendesk integration, if the When to Create New Ticket is set to Before the Call, these contents will not be synchronized, and will not be updated after the call.