Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
https://teleforge-dev.atlassian.net/browse/DIAL-395

 

Page Properties
labeljirareport
Latest Fix 
Issues26 issues
Versionv2.0.4

Summary

A major stability update, we combed through the entire operating stack and all the components and made fixes all along the chain to improve stability in edge cases. 

Several fixes are upstream and not listed here

any integrator on v1.6 can safely upgrade as no functional changes were made

Info

The First major release with the use of our massive dialer testing framework (which will be open sourced soon enough)

All updates for this release

Bug

  • DIAL-406 
    Status
    subtletrue
    colourgreen
    titleResolved
     
    Fix Celluloid: Enigma::StatsStore crashed!
  • DIAL-395 
    Status
    subtletrue
    colourgreen
    titleResolved
     RecordingManager fails to move Recording Files
  • DIAL-394 
    Status
    subtletrue
    colourgreen
    titleResolved
     
    Fix Memory leak probably with RecordingManager
  • DIAL-296 
    Status
    subtletrue
    colourgreen
    titleResolved
     Rejected Calls Stay in Dialing state
  • DIAL-276 
    Status
    subtletrue
    colourgreen
    titleResolved
     On agent connection asterisk fails to playback MOH file
  • DIAL-257 
    Status
    subtletrue
    colourgreen
    titleResolved
     Remove wrapup_time from API
  • DIAL-236 
    Status
    subtletrue
    colourgreen
    titleResolved
     After reaching max_retries all calls would go into failed
  • DIAL-234 
    Status
    subtletrue
    colourgreen
    titleResolved
     Dialer does not respond to API campaign start call
  • DIAL-233 
    Status
    subtletrue
    colourgreen
    titleResolved
     Objects not being serialized to json on some API call responses
  • DIAL-220 
    Status
    subtletrue
    colourgreen
    titleResolved
     recording file does not include extension
  • DIAL-217 
    Status
    subtletrue
    colourgreen
    titleResolved
     No Offline Notification for Agent[1978]
  • DIAL-210 
    Status
    subtletrue
    colourgreen
    titleResolved
     Duplicate offline notifications received when setting agent to offline
  • DIAL-208 
    Status
    subtletrue
    colourgreen
    titleResolved
     Campaign status not changing to "Stopped"
  • DIAL-207 
    Status
    subtletrue
    colourgreen
    titleResolved
     Callee stays in Dialing
  • DIAL-206 
    Status
    subtletrue
    colourgreen
    titleResolved
     Agent gets redialed when campaign is stopping and a make available request is received
  • DIAL-203 
    Status
    subtletrue
    colourgreen
    titleResolved
     Agents get connected to phantom channel
  • DIAL-198 
    Status
    subtletrue
    colourgreen
    titleResolved
     ElectricSlide::CallQueue crashes when agent is marked available
  • DIAL-194 
    Status
    subtletrue
    colourgreen
    titleResolved
     OutboundCall Crashes when Campaign stopped
  • DIAL-193 
    Status
    subtletrue
    colourgreen
    titleResolved
     ElectricSlide::CallQueue crashes on call bridge (undefined method)
  • DIAL-188 
    Status
    subtletrue
    colourgreen
    titleResolved
     RecordingMonitor is crashing when a file doesn't exist
  • DIAL-181 
    Status
    subtletrue
    colourgreen
    titleResolved
     Sidekiq crashes when a campaign is initialised and calls are not sent through to dialer

Maintenance

  • Platform Upgrade:
    • Centos 7
    • updated Jruby and Ruby versions
    • updated gems
    • several fixes made to upstream projects impacting stability
  • DIAL-196 
    Status
    subtletrue
    colourgreen
    titleResolved
     Added slack notifications for failed packager builds
  • DIAL-197 
    Status
    subtletrue
    colourgreen
    titleResolved
     Disable centos 6 builds
  • DIAL-383 
    Status
    subtletrue
    colourgreen
    titleResolved
     
    Dialer influxdb stats conflict on data types
  • DIAL-370

    Status
    subtletrue
    colourgreen
    titleResolved
     As TF, we want to be able to configure the dialer core for remote dependencies so that everything doesn't have to be installed on one box.

  • DIAL-371

    Status
    subtletrue
    colourgreen
    titleResolved
     As TF, we want to be able to configure the dialer API for remote dependencies so that everything doesn't have to be installed on one box.

Recommended Changes

  • ALL integrators will be updated to this version, no testing is required by integrators, it should just work.