Voice SIP Cluster Service Release Notes

From Genesys Documentation
Jump to: navigation, search

Not all releases or changes listed below may pertain to your deployment. Check the table below to see which releases apply to you.

Important
The Release table lists the initial availability date for each release and the deployment environments for which a release is made available. Except when otherwise stated in the description for a specific release, each release includes all of the features and resolved issues that were introduced on earlier dates, regardless of the deployment environment. The features and resolved issues that apply only to a specific deployment environment are noted as such.
First availabilityReleased forHighlightsRelease number
April 04, 2022
Azure.png
  • Voice SIP Cluster service introduces a configurable user data size limit for the RequestUpdateUserData and RequestAttachUserData requests.
  • Fixed a memory leak in SIP node.
100.0.100.0027
March 28, 2022
PrivateEdition.png
  • Important security improvements.
  • Support for deploying all private edition services in a single namespace.
100.0.100.0022
March 07, 2022
Azure.png
  • Support for a new voice call rebalancing feature.
  • Support for customization of the Designer Application Server (DAS) part of the dial-plan-moh option value.
100.0.100.0025
February 16, 2022
Azure.png
Updates to SIP node. 100.0.100.0024
November 19, 2021
Azure.png
  • Voice SIP Cluster Service now correctly selects an originating trunk for inbound calls.
  • Known issue related to call supervision.
100.0.100.0021
September 27, 2021
Azure.png PrivateEdition.png
100.0.100.0014:
  • Resolved issue.
  • Log redirection to standard output (stdout).
100.0.100.0014
September 22, 2021
Azure.png
100.0.100.0013: Resolved issue. 100.0.100.0013
September 15, 2021
Azure.png PrivateEdition.png
100.0.100.0012:
  • Early Adopter Program support for Genesys Multicloud CX private edition deployments on GKE.
  • Support for customized default Music On Hold.
  • Support for SIP redundancy in multi-tenant environments.
  • Support for arbitrary UIDs in private edition deployments on OpenShift.
100.0.100.0012
June 30, 2021
PrivateEdition.png
Early Adopter Program support for Genesys Multicloud CX private edition deployments on OpenShift. 9.0.000.32

April 04, 2022 Azure.png

What's New

  • Voice SIP Cluster service now has a configurable user data size limit for the RequestUpdateUserData and RequestAttachUserData requests. The default value is 16,000 bytes of packed user data. The maximum allowed value is 64 Kilobytes. SIP Cluster service rejects requests that attempt to attach user data above the maximum allowed size limit. The user data size limit is controlled by the following configuration option in the Helm values.yaml file: configDir/options/requestUserDataLimit. (VOICEMCS-3980)

Resolved Issues

  • SIP node no longer leaks memory when performing the periodic reading of configuration. (VOICEMCS-3969)

March 28, 2022 PrivateEdition.png

Security Fixes

  • This release includes important security upgrades made to third-party software. (GCLOUD-18868)

For private edition

  • Support for deploying the Voice SIP Cluster Service in a single namespace with other private edition services has been implemented. To deploy Voice SIP Cluster Service in a single namespace, override the namespace parameter in the SIP Cluster Service Helm chart values.yaml file:
    Voicemcs rn update namespace.png
    In the SIP Cluster Service Helm chart values.yaml file, you must also update the namespace specified in the rmAddress parameter so it matches the single namespace that you are configuring. That is, change "gvp-rm.gvp.svc.cluster.local;transport=tcp" to "gvp-rm.<single namespace for services>.svc.cluster.local;transport=tcp".
    Voicemcs rn update rmaddress updated.png
    (VOICEMCS-2912)

March 07, 2022 Azure.png

What's New

  • Voice SIP Cluster service now supports a voice call rebalancing feature that allows the transition of voice calls from a SIP Cluster service instance, undergoing graceful termination, to a successor service instance. This type of voice call transition enhances call handling continuation during a rolling upgrade or service scale-down. (VOICEMCS-3844)
  • Voice SIP Cluster service now allows customization of the Designer Application Server (DAS) part of the dial-plan-moh option value. To customize the value, specify a new designerDasAddress parameter in the Helm chart values.yaml file.

    Support for this feature begins with Helm chart version voice-sip-100.0.1000013.tgz. (VOICEMCS-3843)

February 16, 2022 Azure.png

Resolved Issues

  • When an agent initiates Single Step Conference (or 2 Step Conference) with an external caller and Routing Point (RP) and then leaves the call and logs out, a subsequent TRouteCall received on the RP executes successfully. Previously, the TRouteCall failed in this scenario. (VOICEMCS-3712)

November 19, 2021 Azure.png

Resolved Issues

  • Voice SIP Cluster Service now correctly selects an originating trunk for inbound calls. Voice SIP Cluster Service selects the trunk only if the partition ID of that trunk is the same as the tenant callcenterid (CCID) received in the X-Genesys-Partition-Id header of the initial INVITE message that is arrived from a Voice SIP Proxy Service. (VOICEMCS-3224)

Known Issues

  • When a supervision conference fails to establish, the call monitoring subscription in SIP Server is not cleared. The result is that calls to the monitored DN are supervised even if the Supervisor cancels the monitoring session.

September 27, 2021 Azure.png PrivateEdition.png

Resolved Issues

  • The call-cleanup idle timeout in the Voice SIP Cluster Service has been increased from 60 minutes to 4 hours. (VOICEMCS-2987)

For private edition

  • Voice SIP Cluster Service now supports optional forwarding of SIPNode logs to standard output (stdout) using a Fluent Bit sidecar and an ephemeral volume (emptyDir). You must override parameters in the voice-sip Helm chart values.yaml file to implement Fluent Bit log forwarding to stdout. (VOICEMCS-2662)

September 22, 2021 Azure.png

Resolved Issues

  • When a trunk, softswitch, or trunk group is deleted from the environment, the Voice SIP Cluster Service now correctly removes device's Prometheus metrics. Previously, the Voice SIP Cluster Service did not remove metrics of the deleted device, which led to invalid alerts on that device. (VOICEMCS-2751)

September 15, 2021 Azure.png PrivateEdition.png

What's New

  • Voice SIP Cluster Service supports customized default music per Tenant basis that is played when a call is placed on hold. For each Tenant, the Voice SIP Cluster Service composes a specific URIĀ  that points to the Music on Hold (MOH) resource, and then includes this URI in a SIP INFO message to GVP when an active call is placed on hold. The MOH resource is a media file stored in the Designer Music on Hold media collection. Designer release 9.0.119.08 is required for this feature support. Refer to the Designer documentation for details. (VOICEMCS-1996)
  • Voice SIP Cluster Service supports SIP redundancy in multi-tenant environments. SIP redundancy enables the Voice SIP Cluster Service to place an outgoing call to an external destination/remote agent using a trunk or softswitch DN in another region within the Tenant if local resources are not available. (VOICEMCS-1894)

For private edition

  • Voice SIP Cluster Service now supports the use of arbitrary, or random, user IDs (UIDs) in OpenShift.
    • The Dockerfile has been modified to specify container and file ownership as user=500 (genesys) and group=0 (root).
    • The securityContext settings exposed in the default values.yaml file specify the user and group IDs for the genesys user (500:500:500). You must override these Helm chart values if you want OpenShift to use arbitrary UIDs. For more information, see Configure Voice Microservices.
    • Voice SIP Cluster Service is deployed using ServiceAccounts that use the restricted Security Context Constraint (SCC). In an earlier implementation, Genesys required you to deploy all private edition services using a ServiceAccount associated with the custom genesys-restricted SCC, to control permissions for the genesys user (500). Genesys now expects OpenShift to use arbitrary UIDs in your deployment, and the genesys-restricted SCC has been deprecated. If you previously deployed Voice SIP Cluster Service using the genesys-restricted SCC, Genesys recommends that you redeploy Voice SIP Cluster Service so that you use arbitrary UIDs.
    (VOICEMCS-2614)
    More info: Configure Voice Microservices
  • As of October 29, 2021, Voice SIP Cluster Service supports deployments on Google Kubernetes Engine (GKE) in Genesys Multicloud CX private edition, as part of the Early Adopter Program. (CPE-1983)

June 30, 2021 PrivateEdition.png

For private edition

  • Starting with this release, Voice SIP Cluster Service is available for select customers in Genesys Multicloud CX private edition, as part of the Early Adopter Program. Deployments on OpenShift Container Platform (OpenShift) are supported. (VOICEMCS-1740)
    More info: Voice Microservices Private Edition Guide