- June 27, 2019 (9.0.007.09)
- May 10, 2019 (9.0.006.02)
- April 5, 2019 (9.0.005.10)
- March 8, 2019 (9.0.005.08)
- December 21, 2018 (9.0.004.10)
- July 2, 2018 (9.0.003.04)
- May 31, 2018 (9.0.002.06)
- March 29, 2018 (9.0.001.01)
- January 23, 2018 (8.5.401.05)
- December 20, 2017 (8.5.401.03)
- July 13, 2017 (8.5.400.04)
- May 5, 2017 (8.5.300.07)
- March 23, 2017 (8.5.300.04)
- December 10, 2015 (220.127.116.11)
- Known Issues
June 27, 2019 (9.0.007.09)
FIPS 140-2 compliancy
- Genesys Softphone secured communication channels, such as Secured RTP, are now compliant with FIPS 140-2.
TLS 1.2 support
- You can now force the communication between Agent Desktop and Genesys Softphone to use TLS 1.2 by setting the "sec_protocol" option in the "connector" section of the softphone.config file to the value "TLSv12".
- Genesys Softphone improved audio processing during hold/retrieve operations when interoperating with other SIP clients, such as Microsoft Skype for Business. (SOFTPHONE-704)
- Genesys Softphone HTTP connector security has been improved. (SOFTPHONE-634)
May 10, 2019 (9.0.006.02)
- Genesys Softphone can now be installed on all supported Windows 32-bit operating systems. (SOFTPHONE-657)
- Support for Windows 2016 in Citrix VDI environments. (SOFTPHONE-626)
WebRTC support for disaster recovery
- When integrated with Agent Desktop 9 in a WebRTC environment, Genesys Softphone automatically follows Agent Desktop fail-over from primary to backup. (SOFTPHONE-623)
- The security of the Genesys Softphone HTTP Connector has been improved by limiting the maximum size of the HTTP Request body. (SOFTPHONE-665)
- The robustness of the connectivity between Genesys Softphone and the WebRTC Gateway has been improved to reduce the number of session disconnections. (SOFTPHONE-662)
- Genesys Softphone has been improved to prevent distortion at the beginning of calls on certain headsets. (SOFTPHONE-649)
April 5, 2019 (9.0.005.10)
- Genesys Softphone no longer fails to establish a second WebRTC request through an HTTP Proxy when the second request immediately follows the first. Previously, a 3pcc SingleStepConference initiated from Agent Desktop could fail in a deployment where an HTTP Proxy was configured. (SOFTPHONE-638)
March 22, 2019 (9.0.005.09)
- The analysis of voice call quality has now been improved so that agents no longer receive misleading voice call quality alerts immediately after a call has been established or retrieved. (SOFTPHONE-631)
- You can now deploy Genesys Softphone in connector mode set up with a Self Signed Certificate so that it can be configured and activated from Agent Desktop running in Firefox. Previously, starting with Firefox version 57, it was not possible to use the self-signed certificate of the HTTPS connector from a web application running in Firefox. (SOFTPHONE-545)
March 8, 2019 (9.0.005.08)
HTTP Proxy support
- Genesys Softphone running with WebRTC signaling now supports HTTP Proxy with no authentication enabled.
- Genesys Softphone can now be deployed in the Citrix XenApp 7 and XenDesktop 7 virtual desktop infrastructures. Deployment requires Genesys Softphone VDI Adapter to be installed on the client workstations. Refer to the Supported OS and the Supported Virtualization system guides for details about the supported versions.
- When Genesys Softphone is set up to communicate with PureEngage Cloud through WebRTC protocol, the HTTPS certificate verification now behaves as expected. Previously, under some network conditions, the certificate could be incorrectly refused. (SOFTPHONE-622)
- Genesys Softphone now correctly initializes when it is using HTTP Connector and Agent Desktop is specifying a different log setting than the Softphone configuration file. (SOFTPHONE-608)
December 21, 2018 (9.0.004.10)
- Genesys Softphone is now able to maintain a sticky registration session with one data center when the connectivity is significantly delayed. (SOFTPHONE-568)
- Genesys Softphone now correctly displays audio device names that are defined with 2-byte characters (for example, Japanese characters) in the 'devices' view of the user interface. Previously, these audio device names were not displayed in the Softphone user interface. (SOFTPHONE-547)
- Genesys Softphone no longer insecurely stores connectivity credentials. (SOFTPHONE-564)
- You can now use Environment Variables and both forward slash and backslash characters when you specify the path to the Genesys Softphone log file using the sipendpoint.system.diagnostics.log_file option in Agent Desktop. (SOFTPHONE-561)
- Calls no longer get dropped if it takes extra time to establish the audio portion for a particular call. (SOFTPHONE-529)
July 2, 2018 (9.0.003.04)
WebRTC Media Service
- Genesys Softphone can now handle both inbound and outbound voice calls by communicating with the PureEngage Cloud platform through the WebRTC Media Service. Signaling and media encryption capabilities of WebRTC Media Service ensure appropriate security for voice communications over the public network. This communication supports G.711 and Opus codecs.
- The change of IP Address detection has been improved when, for example, the workstation switches from a wired network connection to a WiFi connection. (SOFTPHONE-485)
May 31, 2018 (9.0.002.06)
Local IP address
- The local IP address selection mechanism of Genesys Softphone has been improved to better support environments where the network to be used for SIP Communication, typically a VPN, is enabled after Genesys Softphone has started SIP registration. Edit the configuration file that is included with your Genesys Softphone package to set the value of the 'public_address' option to the network subnet addresses: "$net:<subnet>". For example: "$net:192.168.0.0/16".
Automatic Gain Control
- Genesys Softphone now supports Automatic Gain Control for the customer audio stream. This allows agents to hear their customers with a normalized volume level, meaning that they will not have to constantly manually adjust the volume controls. Edit the configuration file that is included with your Genesys Softphone package to set the value of the 'rx_agc_mode' option to '1'.
- If the HTTP Connector does not allow proper operations of Genesys Softphone in Agent Desktop, agents are now informed by a message in the System Tray. (SOFTPHONE-447)
- When Genesys Softphone is installed with a Secured HTTP connector based on a self-signed certificate by an Administrator, agent can now run Genesys Softphone with a non-Admin Windows account. (SOFTPHONE-472)
March 29, 2018 (9.0.001.01)
Real-time voice quality indicator
- The Genesys Softphone icon in the system taskbar now notifies agents of possible voice quality problems.
- Genesys Softphone now better handles the sending of dialing tones in different connection scenarios. (SOFTPHONE-398)
- The Disaster Recovery mechanism that switches from one Session Border Controller to another has been improved. (SOFTPHONE-408)
January 23, 2018 (8.5.401.05)
- Genesys Softphone now continues to leverage a particular SIP Proxy location after it handles an incomplete or timed-out SIP Communication from SIP Proxy. (SOFTPHONE-359)
- Genesys Softphone no longer drops outgoing calls when it has an issue initiating a connection with SIP Server. (SOFTPHONE-366)
- Genesys Softphone now uses the Default Communication Device specified in Windows Audio Settings when no audio device is specified in provisioning or the specified device is not found. (SOFTPHONE-362)
- Genesys Softphone now uses the audio-in and audio-out devices that you specify when you edit the application configuration file. Previously, if the entire name of the device was specified, the device was not found. (SOFTPHONE-360)
December 20, 2017 (8.5.401.03)
- For improved security, the local IP address is no longer included in the Call-ID header of SIP messages sent by Genesys Softphone.
- You can now specify the value for the 'headset_name' option when the value of the 'use_headset' option is set to '1' (indicating that Genesys Softphone selects the device specified as the default in the Windows Audio Settings). Previously, the value was not supported as a valid value.
July 13, 2017 (8.5.400.04)
- You can now specify the TCP port range used for client-originated connections when SIP communication is configured to be transported over TCP or TLS protocol by using the tcp_port_min and tcp_port_max options.
- The resilience of Genesys Softphone during network events, such as an IP address change, caused by workstation Sleep/Wake, VPN Connect/Disconnect, and so on, has been improved. This new behavior is permanent.
- You can now configure Genesys Softphone to include the MAC address of the host in the SIP message headers. This capability is enabled by using the include_mac_address option.
- Genesys Softphone installation package now upgrades the application when it detects that an older version is already installed on the workstation. It is no longer possible to install multiple instances of Genesys Softphone on a single workstation.
- Genesys Softphone is rebranded to reflect the new Genesys logo.
May 5, 2017 (8.5.300.07)
- Genesys Softphone now supports DNS SRV resolution for the URI specified in the server parameter of the Connectivity tag. You do not need additional configuration to enable this feature, but as described in RFC 3263, you should not include the port number in the server URI.
March 23, 2017 (8.5.300.04)
- Genesys Softphone now uses the pjNAT library for improved ICE, STUN & TURN support.
- The payload type for the telephone-event is now set correctly in the SDP Answer. Previously, Genesys Softphone put in the SDP Answer the payload type selected from a previous offer instead of using the payload type delivered in last SDP Offer, causing problems with some equipment that does not support asymmetric RTP payloads.
- You can now configure the Domain to be specified in the SIP REGISTER request separately from the address when this request is sent by using the domain option of the proxies sections.
December 10, 2015 (18.104.22.168)
- Basic first party call control, including answer, hold, retrieve, and hang up.
- Support of multiple DNS A-records for multisite deployments.
- Windows 10 support.
- Removal of the Microsoft .NET framework as a dependency.
There are currently no known issues.