Voice SIP Proxy Service Release Notes
Not all releases or changes listed below may pertain to your deployment. Check the table below to see which releases apply to you.
|First availability||Released for||Highlights||Release number|
|March 08, 2022||
|November 12, 2021||100.0.100.0010: Resolved issue.||100.0.100.0010|
|September 15, 2021||100.0.100.0005:
|June 30, 2021||Early Adopter Program support for Genesys Multicloud CX private edition deployments on OpenShift.||9.0.000.09|
March 08, 2022
- 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. Voice SIP Proxy service both supports and facilitates the voice call rebalancing feature. (VOICEMCS-3638)
- Voice SIP Proxy no longer closes a TCP connection when it receives an incorrect SIP message over it. Instead, SIP Proxy now rejects the message with a 400 Bad request response and keeps the connection intact. (VOICEMCS-3855)
Voice SIP Proxy service now supports SIP devices reusing the same TCP connection for all communications with SIP Proxy. (VOICEMCS-3813)
November 12, 2021
- Voice SIP Proxy Service now includes an X-Genesys-Partition-Id header containing the tenant callcenterid (CCID) in the outgoing initial INVITE message. (VOICEMCS-3063)
September 15, 2021
For private edition
Voice SIP Proxy 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 Proxy 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 Proxy Service using the genesys-restricted SCC, Genesys recommends that you redeploy Voice SIP Proxy Service so that you use arbitrary UIDs.
More info: Configure Voice Microservices
As of October 29, 2021, Voice SIP Proxy 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 Proxy 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.
More info: Voice Microservices Private Edition Guide