Voice SIP Cluster Service Release Notes
- 1 August 02, 2022
- 2 July 25, 2022
- 3 April 04, 2022
- 4 March 28, 2022
- 5 March 07, 2022
- 6 February 16, 2022
- 7 November 19, 2021
- 8 September 27, 2021
- 9 September 22, 2021
- 10 September 15, 2021
- 11 June 30, 2021
Not all releases or changes listed below may pertain to your deployment. Check the table below to see which releases apply to you.
|Available||Genesys CX on||Private edition||Highlights||Release|
|August 2, 2022||
|July 25, 2022||
|Support for Genesys Multicloud CX private edition deployments on Azure Kubernetes Service (AKS).
|April 4, 2022||
|March 28, 2022||Generally Available release for Genesys Multicloud CX private edition deployments on the officially supported Kubernetes platforms.
|March 7, 2022||
|February 16, 2022||
|Updates to SIP node.||100.0.100.0024|
|November 19, 2021||
|September 27, 2021||
|September 22, 2021||
|100.0.100.0013: Resolved issue.||100.0.100.0013|
|September 15, 2021||
|June 30, 2021||Early Adopter Program support for Genesys Multicloud CX private edition deployments on OpenShift.||9.0.000.32|
August 02, 2022
Third-party dependency updates to maintain security and reliability. (VOICEMCS-4762)
In the INVITE message sent to a conference destination, the user part of the From header is now updated correctly with the value specified in override-domain-from when the override-from-on-conf option is set to true; in addition, the Tenant ID is not added to the From header. Previously, the value in override-domain-from was not used to update the user part of the From header and the Tenant ID was added to the header instead. (VOICEMCS-4023)
Call monitoring subscription in SIP Server is now cleared when a supervision conference fails to establish. Previously, the call monitoring subscription was not cleared in this scenario, meaning calls to the monitored DN were supervised even if the Supervisor canceled the monitoring session. (VOICEMCS-3676)
July 25, 2022
For private edition
This release includes:
- An updated container and new versions of the Helm charts.
- Helm chart upgrades compatible for Kubernetes version 1.22 and Consul version 1.10.
- Third-party dependency updates to maintain security and reliability.
Voice SIP Cluster Service supports deployments on Azure Kubernetes Service (AKS) in Genesys Multicloud CX private edition. (CPE-3613)
April 04, 2022
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)
SIP node no longer leaks memory when performing the periodic reading of configuration. (VOICEMCS-3969)
March 28, 2022
This release includes important security upgrades made to third-party software. (GCLOUD-18868)
For private edition
As of July 13, 2022, Voice SIP Cluster Service is Generally Available for deployment in Genesys Multicloud CX private edition on the Kubernetes platforms officially supported by Genesys.
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:
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".
March 07, 2022
In this release, SIP Cluster service introduces support for a new Voice call rebalance 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.
To enable this functionality, configure the following section in the values.yaml file:
The rebalanceEnabled: false option disables the feature.
For this functionality to work correctly, you must upgrade dependent services to the following versions or higher:
- SIP Proxy service: 100.1.100.0014
- SIP Front End: 100.1.100.0007
- Orchestration service: 100.1.100.0033 (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
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
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)
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
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
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
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
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