This release note applies to all 8.1 releases of SIP Proxy.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information on third-party software used in this product, see the Legal Notices for SIP Proxy. Please contact your Genesys Customer Care representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new features and functionality:
This release includes the following corrections and modifications:
SIP Proxy now responds with 414 Request-URI Too Long
on a request with Request-URI longer than 1024 symbols. Previously, SIP Proxy could terminate unexpectedly in such cases. (SIPPROXY-720)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new features and functionality:
TServer
SSLv23
SSLv23, SSLv3, TLSv1, TLSv11, TLSv12, TLSv13
SSLv23
- The highest TLS protocol version supported by Genesys Security Pack 8.5.1. Currently, it is TLS version 1.3.SSLv3
- SSL version 3.0TLSv1
- TLS version 1.0TLSv11
- TLS version 1.1TLSv12
- TLS version 1.2TLSv13
- TLS version 1.3SSLv23
(default), SIP Server uses the highest TLS version supported by Genesys Security Pack 8.5.1. Currently, it is TLS 1.3.There are no corrections or modifications in this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new features and functionality:
There are no corrections or modifications in this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
In multi-site deployments, when the option peer-proxy-contact on the Trunk DN object is set with parameter transport=udp
, SIP Proxy now correctly proxy the parameter in the Record-Route header in the outgoing requests. Previously, the transport
parameter with udp
value was not proxied. (SIPPROXY-696)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
The communication port for inter-process communication is no longer exposed outside the host. Only applications running on the same host as the SIP Proxy server can connect to the communication port. (SIPPROXY-684)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
In a SIP Cluster deployment, SIP Proxy no longer terminates unexpectedly while handling a scenario where the response from SIP Server to a REGISTER request arrives after the REGISTER request expires. Previously, starting form version 8.1.100.85, SIP Proxy was not correctly handling this race condition scenario. (SIPPROXY-663)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new features or functionality:
503
response to the incoming SIP request with the header, Error-Info: transport-error
.
A new configuration option is introduced to support this feature.
reject-on-reliable-transport-exception
Setting: sipproxy section, Application level
Default Value: false
Valid Values: false, true
Changes Takes Effect: Immediately
If the option's value is set to true
, SIP Proxy reacts on receiving a transport error (TCP exception) on an outgoing SIP connection, when the exception occurs on sending a SIP request that is to be forwarded. In this case, SIP Proxy responds with a 503 Service Unavailable
error to the respective incoming SIP request. The header, Error-Info: transport-error
, is added to this response. To allow for backward compatibility with older versions, if the option is set to false
, SIP Proxy does not react on any exception in reliable transport.
(SIPPROXY-647)
There are no corrections or modifications in this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new features and functionality:
There are no corrections or modifications in this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new features or functionality:
This release includes the following corrections and modifications:
SIP Proxy now correctly reconnects to another SIP Proxy instance to synchronize DN registration between peers. Previously, in some rare circumstances, when the connection between SIP Proxy instances became stuck, it resulted in DN registration being out of sync. (SIPPROXY-625)
SIP Proxy now properly re-establishes a TCP connection to SIP Server after the network disruption. (SIPPROXY-623)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
When SIP Server is running in SIP Cluster mode with SIP Proxy and the sip-server-info option is configured, SIP Proxy now forwards the Server SIP header from SIP Server to an endpoint in a 200 OK response for a REGISTER request. Previously, SIP Server did not forward this header from SIP Server to an endpoint. (SIPPROXY-617)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following features or functionality:
Support for the Microsoft Windows Server 2019 operating system was added on 08/12/2020. See the SIP Proxy page in the Genesys Supported Operating Environment Reference for more detailed information and a list of all supported operating systems. (SIP-26865)
This release includes the following corrections and modifications:
SIP Proxy no longer terminates unexpectedly while handling SIP responses that are received over reliable protocols. (SIPPROXY-583)
When a SIP Endpoint sends a consecutive REGISTER request over a TLS connection from a different port, SIP Proxy now sends the next call to a correct port. Previously, SIP Proxy sometimes sent the next call to the previous port, which resulted in calls being dropped. (SIPPROXY-572)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new information:
This release includes the following corrections and modifications:
When the TCP is configured between SIP Server and SIP Proxy, SIP Proxy now always forwards 200 OK responses on INVITE messages to the primary SIP Server. Previously, SIP Proxy sometimes attempted to forward 200 OK responses on INVITE messages to the backup SIP Server and, as a result, those responses were lost. (SIPPROXY-573)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
When a 180 Ringing response sent by SIP Proxy does not reach SIP Server, SIP Proxy now correctly resends a 180 Ringing response after SIP Server re-transmits the initial INVITE message. Previously, SIP Proxy did not resend the 180 Ringing response. (SIPPROXY-560)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
This release includes the following corrections and modifications:
SIP Proxy no longer grows in memory while running in Cluster mode with the default type of connection between SIP Proxy instances. (SIPPROXY-546)
SIP Proxy no longer removes active SIP Registration if there are simultaneous SIP REGISTER requests sent for a DN. Previously, SIP Proxy incorrectly removed active registration when a second registration was expired, and, as a result, the call to that DN was dropped with a 404 Not Found
message. (SIPPROXY-540)
SIP Proxy instances no longer terminate unexpectedly if a SIP Proxy name is removed from the sipproxy-applications option of the VOIP Service DN containing service-type=sip-cluster-nodes
. (SIPPROXY-538)
SIP Proxy no longer terminates unexpectedly on startup if any configuration option of the SIP Proxy application is changed before the initialization process is finished. (SIPPROXY-527)
Supported Operating Systems
New in This Release
Corrections and Modifications
Note: This version was first released as a Hot Fix on 07/11/18.
There are no restrictions for this release. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
This release contains modifications to support Genesys Cloud implementations only.
Supported Operating Systems
New in This Release
Corrections and Modifications
Note: This version was first released as a Hot Fix on 03/27/18.
There are no restrictions for this release. This release contains the following new features or functionality:
This release includes the following corrections and modifications:
If a SIP device is registered without the port number, SIP Proxy now treats it as the default SIP port 5060 and sends SIP requests to that port and host address while communicating with this device. (SIPPROXY-512)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
Previously, when two SIP Proxy instances reconnected after a long period of disconnection, one of the instances could start a reactivation process for synchronization purposes. During the reactivation process, this SIP Proxy instance closed SIP listening sockets and did not process the SIP traffic. In some cases, if this SIP Proxy instance was disconnected from other SIP Proxies during the reactivation process, it could become stuck in the reactivation state and was not operable. Now, SIP Proxy gracefully handles disconnections from over SIP Proxies during the reactivation process. (SIPPROXY-501)
Previously, when two SIP Proxy instances reconnected after a long period of disconnection, one of the instances could start a reactivation process for synchronization purposes. During the reactivation process, this SIP Proxy instance closed UDP and TCP listening sockets and did not process UDP and new TCP connections. Existing TCP connections were kept open. As a result, connected TCP clients (SIP Server) considered SIP Proxy as active and unsuccessfully tried to use it to reach UDP destinations. Now, SIP Proxy closes all existing TCP connections and does not process any SIP traffic during the reactivation process. (SIPPROXY-500)
SIP Proxy now always forwards 200 OK responses on INVITE to the primary SIP Server. Previously, SIP Proxy sometimes attempted to forward 200 OK responses on INVITE to the backup SIP Server and, as a result, those responses were lost. (SIPPROXY-499)
When a TCP connection is configured between SIP Server and SIP Proxy, and a UDP connection is configured between SIP Proxy and SIP Endpoint, SIP Proxy now correctly sends retransmitted a 200 OK response to SIP Server. Previously, when a SIP Endpoint did not receive the ACK message and continued to send 200 OK on INVITE, SIP Proxy did not resend the 200 OK. (SIPPROXY-496)
SIP Proxy no longer sometimes stops processing SIP traffic because of the broken communication between internal threads. (SIPPROXY-493)
Supported Operating Systems
New in This Release
Corrections and Modifications
Note: This version was first released as a Hot Fix on 10/27/17.
There are no restrictions for this release. This release contains the following new features or functionality:
This release does not include any corrections.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
all
. Previously, SIP messages were not included in a SIP Proxy log. (SIPPROXY-477)
This release does not include any corrections.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and modifications:
SIP Proxy no longer grows in memory while processing SIP responses for non-existing SIP transactions. (SIPPROXY-471)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
This release does not include other corrections.
Supported Operating Systems
New in This Release
Corrections and Modifications
Note: This version was first released as a Hot Fix on 05/02/17.
There are no restrictions for this release. This release contains the following new features or functionality:
SIP Proxy now supports the new Application-level option:
report-sipserver-oosfalse
false, true
When this option is set to false
(the default behavior), SIP Proxy attempts to deliver the SIP request to the SIP Server HA pair even if the SIP Server pair is in out-of-service state. It might help to survive short temporary network outages between SIP Proxy and the SIP Server HA pair.
When this option is set to true
and if the SIP Server HA pair is in the out-of-service state, SIP Proxy rejects the SIP request by generating a 503 Service Unavailable error message.
(SIPPROXY-454)
This release includes the following corrections and modifications:
SIP Proxy now correctly recognizes the destination for SIP messages. Previously, if the INVITE message from SIP Server contained a custom header with the name starting with X-Genesys-Route
, SIP Proxy incorrectly used the value of this header as the destination for sending the next message. (SIPPROXY-451)
Supported Operating Systems
New in This Release
Corrections and Modifications
This hot fix is no longer available as it did not function as expected. If you downloaded it, do not install it. Hot fix version 8.1.100.67 will correct the identified issue.
This release does not contain other corrections.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains the following new feature or functionality:
Note: This version was first released as a Hot Fix on 11/09/16.
This release does not contain other corrections.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
This release does not contain other corrections.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
This release does not contain other corrections.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains the following new features or functionality:
Note: This version was first released as a Hot Fix on 05/03/16.
This release does not contain other corrections.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
This release does not contain other corrections.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
This release does not contain other corrections.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features or functionality:
This release does not contain other corrections.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release contains the following new feature or functionality:
Note: This version was first released as a Hot Fix on 04/27/15.
This release does not include any corrections.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release does not contain new features or functionality.
Note: This version was first released as a Hot Fix on 11/07/14.
This release includes the following corrections and modifications:
SIP Proxy now always adds the Record-Route
header when sending an initial INVITE request if it receives this INVITE from GVP. Previously, starting with version 8.1.100.42, SIP Proxy did not add the Record-Route
header to the initial INVITE request if the INVITE from GVP contained the Route
header with the SIP Proxy information. (SIPPROXY-403)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents above.
There are no restrictions for this release. This release contains the following new features or functionality:
Support of Windows 2012 64-bit.
Note: This version was first released as a Hot Fix on 05/28/14.
This release includes the following corrections and modifications:
While importing metadata from Genesys Administrator for the SIPProxy_811
application template, the Invalid application type
error message is no longer displayed. (SIPPROXY-394)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents above.
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
When sending a CANCEL request to a destination, SIP Proxy now correctly includes the same branch value in the first Via
header as the branch value of the request to be canceled. Previously, SIP Proxy included a new branch value in the first Via
header, which led to rejection of the CANCEL request with the 481 Call/Transaction Does Not Exist
error message. (SIPPROXY-390)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents above.
There are no restrictions for this release. This release contains the following new features or functionality:
SIP Proxy now supports SIP Business Continuity deployments. See the SIP Proxy Deployment Guide for details. (SIPPROXY-389, SIP-13949)
SIP Server now offers the Sizing Tool to evaluate the CPU load and network traffic of SIP Server and SIP Proxy applications in your environment. Download the tool from the Genesys SIP Server Documentation web page. (SIP-14141, SIP-13948)
This version was first released as a Hot Fix on 01/31/14.
This release contains no corrections or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents above.
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following corrections and modifications:
In multi-site deployments, ISCC calls to a remote site are no longer dropped when a SIP Server switchover occurs on the remote site. Previously, a local SIP Proxy did not send OPTIONS messages to a new remote primary SIP Server and as a result, the local SIP Server placed the Trunk pointed to the remote site to out-of-service state. Now, the local SIP Proxy sends OPTIONS messages to a new remote primary SIP Server, and the local SIP Server does not place the Trunk pointed to the remote site to out-of-service state. For proper handling of the pooling mechanism in a local SIP Server, Genesys recommends setting the oos-check
and oos-force
option values on the Trunk DN object (pointed to the remote site) to:
2 * (SIPProxyOosCheck + SIPProxyOosForce + 1)
where SIPProxyOosCheck
and SIPProxyOosForce
are the values of the oos-check
and oos-force
options, respectively, that are configured on the local DN with service-type=sip-outbound-proxy
.
(SIPPROXY-381)
Supported Operating Systems
New in This Release
Corrections and Modifications
The operating systems supported by this release are listed in the Contents above.
There are no restrictions for this release. This release contains no new features or functionality.
This release includes the following corrections and modifications:
After SIP Server switchover, SIP Proxy now retransmits 3xx – 7xx responses to the new primary SIP Server until an ACK is received. Previously, Sip Proxy would not retransmit responses to the new primary SIP Server. (ER# 322066776)
The mgmt-port
previously configured in the Server Info section
of SIP Proxy is no longer required in a standalone deployment. Previously,
the mgmt-port
was configured for SIP Proxy in a standalone
deployment, and used the default port of 5066 it if was available.
SIP Proxy in a standalone deployment no longer requires a list of all SIP
Proxies at all sites. Therefore, the sipproxy-application
option,
which provides this list, is removed from the sipproxy
section
of a SIP Proxy application in a standalone deployment.
SIP Proxy now reads the value that had been provided by the
internal-domain
option directly from the contact
option of the VOIP Service DN with service-type=sip-outbound-proxy
,
so the internal-domain
option is removed from the
sipproxy
section of a SIP Proxy application in a standalone
deployment. Previously, the value of the
internal-domain
option had to be the same as the value of the
contact
option configured on a VOIP Service DN with
service-type=sip-outbound-proxy
on the switch that belonged to
SIP Server.
SIP Proxy now reads the value that had been provided by the
contact-address
option directly from the external-contact
option of the VOIP Service DN with service-type=sip-outbound-proxy
,
so the contact-address
option is removed from the
sipproxy
section of a SIP Proxy application in a standalone
deployment. Previously, the value of the contact-address
option had to be the same as the
value of the external-contact
option configured on a VOIP Service
DN with service-type=sip-outbound-proxy
on the switch that
belonged to SIP Server.
(ER# 321171593)
SIP Proxy now uses the transport specified in the Request-URI of the received SIP request for the communication with SIP Servers and DNs. Previously, SIP Proxy used the same protocol for the outgoing connection as it used for the incoming connection, regardless of the Request-URI transport parameter of the received SIP request. (ER# 321009804)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.1 release of SIP Proxy.
There are no corrections and modifications in this release of this software.
This section provides the latest information on known issues and recommendations associated with this product.
There are no known issues for this product.
This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list. For more information on discontinued support for operating environments and databases, see Discontinued Support in the Genesys Supported Operating Environment Reference.
Red Hat Enterprise Linux 6 operating system
Discontinued As Of: February 14, 2020; 8.1.100.85 |
Microsoft Visual Studio 2008 (Visual C++ 9) and prior versions
Discontinued As Of: 8.1.100.83 |
Red Hat Enterprise Linux 5 operating system
Discontinued As Of: 8.1.100.79 |
Information in this section is included for international customers.
There are no known internationalization issues for this product.
Additional information on Genesys Cloud Services, Inc. is available on our Customer Care website. The following documentation also contains information about this software.
SIP Proxy 8.1 Deployment Guide contains detailed reference information for the Genesys 8.1 SIP Proxy, including configuration options and specific functionality.
Framework 8.1 SIP Server Deployment Guide contains reference information related to SIP Server.
Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD.
Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated.