Edge and Media Tier release notes


View a summary of the improvements and fixes in the latest Edge software version. Confirm the current version of your Edges and schedule automatic updates or manually update to the latest version as needed.

Manual and auto-update availability

  • Available for manual update in all regions starting July 10, 2019.
  • Auto-update enabled for all regions starting July 17, 2019.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Resolved issue that occurs when a PureCloud user adds a third party outside the organization into an ad hoc conference, and the third party sees the PureCloud user’s extension even though the trunk’s Address Override Method is set to Unassigned DID
  • Improvements to Edge Out-of-Service and In-Service state changes and call draining.
  • Resolved an incorrect Argentina city locality lookup.
  • Resolved SIP client transaction table update issue that occurs in retransmitted SIP requests.
  • Error handling improvements in WebSocket server code.
  • Eliminated potential for a cache lock on unexpected responses from the cloud.

Manual and auto-update availability

  • Available for manual update in all regions starting June 19, 2019.
  • Auto-update enabled for all regions starting June 26, 2019.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Resolved issue with call control responsiveness on long-running tasks.
  • Resolved issue where an Edge restart with trunk ethernet links down results In OPTIONs and REGISTERS failures.
  • Resolved issue that may cause large delays in media file uploads.

Manual and auto-update availability

  • Available for manual update in all regions starting June 12, 2019.
  • Auto-update enabled for all regions starting June 19, 2019.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Resolved issue where the system did not allow persistent connected remote stations to answer group ring calls.
  • Resolved issue where ringback did not function as intended on an external bridge transfer.
  • Resolved issue where the VoiceXML fetchaudiodelay property was not operating as intended.
  • Resolved issue potentially impacting Standard V3 Edge devices when all network interfaces have static addresses.
  • Resolved issue where emojis in a <prompt> element cause the VoiceXML interpreter on Linux to issue a document-terminating error.
  • Increased allowed response time for polling SystemD status to avoid unnecessary SystemD restarts.
  • Updated the line_outgoing.ccxml file to correct a non-existent tap_recorder_options() method.
  • Improved logic for cleaning up orphaned media resources when Edge Control restarts.
  • Ensured that JSON data returned from a <data> element does not run unintended ECMAScript code.
  • Call analysis model updates for Spain (es-ES).
  • Call analysis model updates for Peru (es-PE).
  • Resolved issue where call analysis detected a false positive fax CED tone after the call is answered.
  • Added logic to the media code to help detect unused resources.
  • The Edge now fully supports TLS connection reuse.
  • Improved SIP message retransmission sent over TCP and TLS connections.
  • Resolved issue where certain delivery receipt notifications result in a 500 status code returned to the sender.
  • Improved SIP library support for large SIP messages over TCP and TLS connections.
  • Low-level timer improvements.
  • Improved reliability of the UDP listener’s ‘close’ operation.
  • PureCloud WebRTC now supports DTLS 1.2.
  • Updated OpenSSL to version 1.0.2s.
Genesys found a regression in Edge and Media Tier version 1.0.0.8182. Edge and Media Tier version 1.0.0.8250 replaces version 1.0.0.8182 and includes the enhancements and fixes from that version.

Manual and auto-update availability

  • Available for manual update in all regions starting May 8, 2019.
  • Auto-update enabled for all regions starting May 15, 2019.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Resolved issue where a trunk REGISTER response without a contact header resulted in that trunk and other trunks sharing its interfaces to cancel REGISTER requests.
  • Added support for TLS connection reuse specified by RFC 5923.
  • Updated locality lookup data for April 2019.
  • Improved the timer class implementation.
  • Updated time zone data.

Manual and auto-update availability

  • Available for manual update in all regions starting April 10, 2019.
  • Auto-update enabled for all regions starting April 17, 2019.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Added support for the Polycom Trio 8500 conference phone.
  • Improved static route handling when NIC adapter settings are changed in Standard V2 hardware Edges.

Manual and auto-update availability

  • Available for manual update in all regions starting March 20, 2019.
  • Auto-update enabled for all regions starting March 27, 2019.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Improved call language detection logic that the system uses to determine which hold music to play.
  • Improved reliability of transfers initiated by hardware phones.
  • Improved stability of the Edge to Cloud connection.
  • Process management improvements.
  • Resolved a call control script syntax issue that could cause errors during a replacement speakTo transfer.
  • Resolved issue where a transfer that interrupts another transfer can result in the transfer dialog returning a failure, giving unexpected call flow results.
  • Improved handling of forked INVITE requests for logging and analytics data.
  • Resolved issue where the system parsed header field parameter values using HTTP syntax instead of the SIP syntax.
  • Improved handling of situations where SIP requests received over a connection (TCP or TLS) get closed before a corresponding response is transmitted back.
  • Updated OpenSSL to version 1.0.2r.

Manual and auto-update availability

  • Available for manual update in all regions starting February 27, 2019.
  • Auto-update enabled for all regions starting March 6, 2019.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Resolved issue where a consult transfer action from a supported hard phone model fails to complete the transfer as expected after the agent presses the transfer button.
  • The Edge now saves the system time to CMOS when setting it, if the kernel offers this functionality
  • Fixed a syntax error in the CCXML code that caused calls to terminate improperly when a speak-to party attempts to blind transfer a call.
  • Resolved issue that can occur when the Edge triggers a call in the process of being transferred to perform a second transfer. This situation can cause the first transfer to receive a disconnect, resulting in unexpected call flow results.
  • Call analysis model updates for South Africa (en-ZA).
  • Updated locality lookup data for January 2019.
  • Process management improvements.

Manual and auto-update availability

  • Available for manual update in all regions starting February 13, 2019.
  • Auto-update enabled for all regions starting February 20, 2019.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Resolved issue where external calls encounter one-way audio or no audio during a forked INVITE.
  • Updated Genesys QoS driver certificate.

Manual and auto-update availability

  • Available for manual update in all regions starting January 30, 2019.
  • Auto-update enabled for all regions starting Friday, February 1, 2019.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Improved Edge handling of in/out of service commands.
  • Resolved issue where a transfer that interrupts another transfer causes the transfer dialog to return a failure and the call flow to provide incorrect results.
  • Optimized static resource fetching after features are enabled for an organization.
  • Resolved issue where the Edge responded to a cloud query with an excessively large list of interface adapters. The Edge now sends a limited list of functional adapters.
  • Increased the maximum recording lengths for personal voicemail greetings and name prompts from 20 seconds to 60 seconds.
  • Resolved issue where an inbound INVITE with an SDP containing MIME data failed with a 480 SIP response code (temporarily unavailable). Subsequent retries failed for the same reason. The system now returns a 488 SIP response code, which cannot be retried.

Manual and auto-update availability

  • Available for manual update in all regions starting January 11, 2019.
  • Auto-updates are currently suspended while Genesys investigates reports of increased WebRTC disconnects in certain situations.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Improved Edge handling of in/out of service commands.
  • Resolved error handling path issue for a hex data UUI data element that failed to convert, resulting in stuck calls.
  • Resolved issue where voice activation of the auto-conference PIN did not work in any language other than English.
  • Resolved issue with “forked” INVITES occurring when the system processes a Cancel request response.
  • Modified handling of certain low-level errors to prevent a TCP or TLS connection from closing.
  • Updated to OpenSSL version 1.0.2q.

Manual and auto-update availability

  • Available for manual update in all regions starting December 5, 2018.
  • Auto-update enabled for all regions starting December 13, 2018.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Resolved issue that occurs when the Edge responds incorrectly after receiving a 401 (Unauthorized) response on an already closed dialog.
  • Resolved issue where the timing condition between a client API-issued transfer request and an external participant disconnect results in a stuck conversion that must be removed from PureCloud.
  • Resolved issue where the suppression of HTTP pipelining does not work if the server returns a provisional response.
  • Updated the ICU time zone code and data for October 2018.
  • Resolved issue with audio dropping on calls. SIP re-INVITE with silence suppression in the SDP was reordering the PCM codec.
  • Resolved issue where phone trunks that share a network interface are slow to update status after they are created or moved to an in-service status.
  • Resolved issue where the external party hears ringback on outbound campaign calls distributed to agents with whisper enabled.
Genesys found a regression in Edge and Media Tier version 1.0.0.7662.  Edge and Media Tier version 1.0.0.7730 replaces version 1.0.0.7662 and includes the enhancements and fixes from that version.

Manual and auto-update availability

  • Available for manual update in all regions starting October 31, 2018.
  • Auto-update enabled for all regions starting November 7, 2018.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Resolved TTS issue where pronunciation for years 1999 and earlier was incorrect for United States (en-US), Australia (en-AU), and Great Britain (en-GB).
  • Minor optimizations and fixes.

Manual and auto-update availability

  • Available for manual update in all regions starting October 18, 2018.
  • Auto-update enabled for all regions starting October 24, 2018.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Improved memory management in VXML library logging.
  • Resolved issue with Edge containing multiple IP addresses for the same interface. The system now allows only one IP address per NIC.
  • Resolved issue where phone numbers with an area code matching the Edge’s site country code failed to match the national outbound route.
  • Increased the default national number length for outbound routes from China from 10 to 11.
  • Resolved issue in VXML library that caused a parse error, resulting in a failed Architect flow.
  • Resolved issue where recent changes to detect INVITE forking affected how the Edge handles 101 through 199 responses lacking a tag parameter on the To field.
  • The media server now accepts a recording resume command when the recording is already in a resuming state.
  • Added support for the ‘isdn-interwork’ purpose field for UUI.
  • Updated locality lookup data for October 2018.
  • Resolved issue where erroneous handling of certain error conditions resulted in some SIP and HTTP-related modules to lose track of open active TCP/TLS connections.
  • Resolved issue with HTTP pipelining logic and WebSocket response handling logic that could cause the WebSocket connection establishment to fail.
  • Resolved issue in the code that establishes CONNECT tunnels.

Manual and auto-update availability

  • Available for manual update in all regions starting September 26, 2018.
  • Auto-update enabled for all regions starting October 3, 2018.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Resolved issue that occurs when a user accesses voicemail from the TUI and types an extension not enabled for voicemail, resulting in a message loop: “This voicemail box is not configured. Transferring to voicemail box retrieval.”
  • PureCloud Edge Standard v3 network configuration improvements.

Manual and auto-update availability

  • Available for manual update in all regions starting September 12, 2018.
  • Auto-update enabled for all regions starting September 19, 2018.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Resolved issue where the caller hears a short ringback tone when the system transfers the call to an internal IVR menu.
  • In cases where there are multiple edges or more than one interface per edge, administrators can now configure the custom external property “trunk_sip_fromHeaderHostnameLocalInterface” of data type ‘Boolean’ to indicate whether to use the local host IP (true) or just a host IP (false) on the call.
  • Resolved issue where phone numbers dialed locally in Germany were not matching the default IntraCountry numbering plan.
  • Resolved issue with failing external IVR transfers for customers using the BYOC Cloud model. The system now performs external IVR transfers using the Branch Site outbound routes.
  • Improved how the system handles network/gateway settings specified multiple times.
  • Resolved issue where default hold music plays intermittently even though override on_hold_music is configured in Architect.
  • Resolved issue where the network menu is visible on the LCD on some hardware platforms.
  • Resolved issue on physical edges where the system could not send SIP REGISTER and OPTIONS even though they are enabled in the trunk configuration.
  • The system now enforces a WAN network interface metric of 100.
  • Added support for forking of INVITE messages that result in multiple tag parameters appended to TO header fields.
  • Modified session timer so that SIP 200 OK responses to a SIP INVITE request do not include the Require header, as specified in RFC4028.
  • Updated to OpenSSL version 1.0.2p.

Manual and auto-update availability

  • Available for manual update in all regions starting August 22, 2018.
  • Auto-update enabled for all regions starting August 29, 2018.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Resolved Polycom station caller ID update issue caused by a regression.
  • Modified the system’s cleanup logic to correctly detect and automatically remove leaked media resources.

Manual and auto-update availability

  • Available for manual update in all regions starting August 1, 2018.
  • Auto-update enabled for all regions starting August 8, 2018.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Improved error handling when probing for network interfaces.
  • Enabled the following Polycom phone models for phone-home provisioning: SoundPoint 321, 331, all SoundPoint 4.x models, SoundPoint 560, 670, SoundStation 5000, 6000, 7000, and RealPresence Trio 8800.
  • Call analysis model updates for Chile (es-CL).
  • Call analysis model updates for Poland (pl-PL).

Manual and auto-update availability

  • Available for manual update in all regions starting July 18, 2018.
  • Auto-update enabled for all regions starting July 25, 2018.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Resolved issue where an empty media parameter passed into a VoiceXML session caused a VoiceXML ecmascript error.
  • Resolved issue where a fax session failed to release resources after a combined I/O error and fax session abort.
  • Resolved issue where the asynchronous read stream did not properly process the source’s stream content.

Manual and auto-update availability

  • Available for manual update in all regions starting July 5, 2018.
  • Auto-update enabled for all regions starting July 11, 2018.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Resolved issue where outbound dialing calls using call analysis experience an unexpected call duration timeout when the first call fails and the system attempts to redial.
  • The system now updates trunk status every hour to ensure that even rarely used trunks show the correct status. Previously, trunk status expired after seven days.
  • Call analysis model updates for Chile (es-CL).
  • Resolved issue where an exception could occur due to an invalid SDP fragment.
  • Reduced file retrievals after executing data elements in VoiceXML.
  • Resolved issue where ampersands in an Architect flow string variable cause the variable’s prompt playback to break.
  • PureCloud now supports these ASR diagnostic recording settings: ASR Recording Percentage (% of calls to record, from 0-100) and Type of ASR Diagnostics (Different types of recordings, for example, Basic).
  • Resolved issue where the system places a call from a Cisco CUCM on hold, the CUCM attempts to take the call off hold, but the call remains stuck on hold.
  • Improved Bridge Server HTTP retry operations.
  • The Polycom RealPresence 8800 conference phone now supports MTLS and cloud-provisioning for the PureCloud Phone-Home service.
  • Resolved issue that occurs when a fax session completes abnormally and causes high CPU usage on the Edge.
  • The system now accepts a recording resume command when a recording is already active.
  • Resolved issue where crashes can occur when call legs are accessed concurrently on multiple threads.
  • Resolved issue with muting when the opus codec is in use.
  • Resolved issue with silence and idle endpoint timeout notifications that results in disconnected calls.
  • Improved AddressResolver to eliminate a potential memory leak.
Genesys found a regression in Edge and Media Tier version 1.0.0.7252. Edge and Media Tier version 1.0.0.7292 replaces version 1.0.0.7252 and includes the enhancements and fixes from that version.

Manual and auto-update availability

  • Available for manual update in all regions starting May 9, 2018.
  • Auto-update enabled for all regions starting May 16, 2018.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • The system now sets dual channel recording only for audio/Opus, audioPCMU, and audio/L16 codecs. It sets all other codecs to mono channel recording.
  • TTS dictionary updates to Dutch Netherlands (nl-NL) to improve compound words.

Manual and auto-update availability

  • Available for manual update in all regions starting April 25, 2018.
  • Auto-update enabled for all regions starting May 2, 2018.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Added information to unencrypted and encrypted SAFS file header meta data to improve ad hoc recording identification.
  • Resolved ECMA script error that caused the Japanese (ja-JP) voicemail TUI to fail.
  • Resolved issue that occurs when a voicemail application recording attempts to send a cloud.event.voicemail.notification even though the caller did not leave a voicemail message.
  • Updated locality lookup data for April 2018.
  • Removed less secure RC4 cipher suites from default ciphers in SSL endpoints.

Manual and auto-update availability

  • Available for manual update in all regions starting April 4, 2018.
  • Auto-update enabled for ALL REGIONS starting April 11, 2018.
  • Automatic updates roll out to customers over a 10-day period during their organization’s defined maintenance window.

Enhancements and fixes

  • Resolved issue where the voicemail menu prompts users to listen to new or saved messages when the voice mail box is empty.
  • Resolved issue where the premises Edge or virtual Edge appears as down or unavailable after a restart, when it is actually running and available.
  • Resolved issue where the system cannot play data from a VoiceXML <record> element when using Media Micro Services.
  • To prevent user-initiated and outbound dialing campaign calls from failing due to invalid characters in the phone number, the system now removes those invalid characters when dialing the number. Examples of invalid characters are extended ASCII and white space characters.
  • Resolved issue where the customer’s PBX integration provided inaccurate caller name (caller ID) information on the conversation and user interface views when dialing phone numbers shorter than seven digits.
  • Added support for Edge rollback functionality for premises hardware Edges.
  • Resolved issue that occurs when the language is Portuguese Brazil (pt-BR) and the system plays a continuous failure disconnect tone after a failed outbound external call on behalf of a queue. The default disconnect tone for Portuguese Brazil (pt-BR) now has a timeout duration.
  • Added back-end configuration for idle detection and consent freshness for WebRTC stations with persistent connections. The new configuration prevents the system from prematurely disconnecting WebRTC calls.
  • Added controls to Media Server grammar compilation to avoid running out of memory due to exceedingly large numbers of alternative pronunciations.
  • Improved Media Server grammar compilation time.
  • TTS model updates for Spanish United States (es-US) to improve negative number and negative currency readout.
  • TTS model updates for Spanish United States (es-US) to improve abbreviated currency readout.
  • Call analysis model updates for Chinese Simplified (zh-CN).
  • Call analysis model updates for Spanish United States (es-US) and Ecuador (es-EC).
  • Resolved issue in TTS where two or more consecutive segments with missing voice prevent the system from processing the remaining valid segments.
  • Resolved issue where unencrypted opus recordings receive the default .wav file extension. These recordings now reflect the actual file format.
  • Locality lookups now include mobile numbers outside of North America, indicated by “Mobile Number” followed by the country name.
  • Resolved issue where Bridge actions in Architect flows fail when an action takes no input parameters, resulting in an empty body request. The Bridge host now replaces an empty body request with an empty JSON body.
  • Resolved issue where the system does not normalize the calling address (ANI/Caller ID) for outbound calls made on WebRTC phones.
  • Resolved issue where a race condition causes WebRTC phone calls to disconnect after a timeout.
  • The system now accepts a recording pause command when the recording is already paused.
  • Resolved issue where the diagnostic protocol traces for a combined UDP and TCP protocol trunk configuration sharing the same port configuration on the same PureCloud Edge work for only one of the trunks, due to duplicate protocol trace names.
  • IVR system prompt updates for Chinese Simplified (zh-CN).
  • Added byte-order-mark (BOM) filter to Bridge Server code to filter out BOM if present in text sent to Bridge connectors.
  • Resolved issue where authentication fails when an outbound SIP BYE method is challenged.
  • Call analysis model updates for Australia (en AU).
  • Enhanced the code that handles the upgrade from an insecure TCP connection to TLS to pass the Server Name Indication extension in the ‘client hello’ message.