Zetta2Go uses the latest browser technologies, and recently in the interest of safety, Google has introduced a breaking change that affects Zetta2Go, if you aren’t already using SSL in your configuration. This really only affects gaining access to the Audio Input via the browser for Voice Tracking. No other functionality is affected. The net result is that access to your machine’s microphone is no longer supported unless requested from a secure origin (ie Secure Sockets Layer delivered via HTTPS) on Google Chrome. Support was ended in the latest version of Chrome (Version 47).
As you are probably aware, Chrome downloads new versions silently and will auto-update when you close and restart the browser. If a length of time has gone by with pending updates it will color the right-hand side “Hamburger” icon a different color to draw attention and get you to restart the browser. Users of Opera and Edge browsers are not affected. (Yes, Zetta2Go supports these other browsers, and Voice tracking works just fine regardless of whether you have installed the SSL components. Firefox is coming soon.)
Bottom line is if someone updates Chrome and tries to use Zetta2Go iVT on a non HTTPS connection it will not work and will present a message that says recording will not be possible. Implementing the SSL instructions will cure the problem and add the nicety of never having to be prompted for access to the audio card again. These instructions are available in your Zetta’s help file, or from Zetta2Go itself go to Help | Administration for further information on implementing SSL.
Google Deprecation reference: