Increased Logging and Resiliency for the Vocera/Engage Proxy

A common issue seems to be with the Vocera/Engage Proxy Service, when this service is not healthy, the Voice Server does not Fail-Over.  This service does not restart itself or even have any real-time logging – there are windows events generated but I wouldn’t consider that real-time accessible logging.  Mostly it seems the any of the Proxy Logging is not helpful in indicating any issues with the health of the Proxy Service. Would like to see improved logging and ideally the ability for the proxy to self-recover in the event of a failure.

Another issue with this service is there’s only one for all Engage Servers, thus each of our current 4 sites communicate through this one proxy.  When it fails, all 4 sites lose their connection. Would like to see a way to address this single point of failure.

Posted by customer TAM.
  • Guest
  • Jan 31 2020
  • Will not do
  • May 15, 2020

    Admin response

    The Vocera/Engage Proxy service is no longer required in Vocera Platform 6.

  • Attach files
  • +1