Lifesize Icon Monitoring Deep Dive

Document created by cmenesatti Employee on Mar 20, 2017Last modified by cmenesatti Employee on Jul 24, 2017
Version 5Show Document
  • View in full screen mode

How To Opt in and Opt Out

 

Premium and Enterprise Customers can go to the Lifesize Icon Event Alerts section of their Lifesize Admin Console under Advanced Settings > Features and Options.

  1. Select the check box to Enable Lifesize Icon event alerts.
  2. Enter the email address that Lifesize will use to send alerts. Note: Only a single email address can be entered.
  3. Click Update.

 

More https://www.lifesize.com/en/cloud-help/monitoring-alerts

 

Alert notifications will be generated in the language chosen by the customer if notifications are available in that language. Otherwise, notifications will be sent in English.

Known Limitations

Duplicate alerts for same condition

A customer device that has an ongoing condition (e.g. display disconnected) will generate alert notifications for that condition every time the device comes online (e.g. from a restart) or re-provisions its connection to Lifesize services (once every 24 hours).

Can take a while to detect physical offline conditions

When a customer device has been disconnected physically, it can take a few minutes before our monitoring services will detect the disconnect. The amount of time might be dependent on networking at the customer's site or their Internet service provider.

What Triggers a Tracked Incident

 

Incident Event Type

Possible Triggers

Alerts Generated If

Display Disconnected

  • The device was started with no displays connected.
  • All previously connected displays have been disconnected.

5 minutes have elapsed from incident start and no display has been connected in the meantime.

Camera Disconnected

  • The device was started with no cameras connected.
  • All previously connected cameras have been disconnected.

5 minutes have elapsed from incident start and no camera has been connected in the meantime.

Microphone

Disconnected

  • The device was started with no microphones connected.
  • All previously connected microphones have been disconnected.
5 minutes have elapsed from incident start and no microphone has been connected in the meantime.

SIP2 Registration Failed

  • The device was started with a custom SIP registrar configured, but the connection, handshake or registration failed.
  • The device has a custom SIP registrar configured and an existing connection or registration has failed.

The device is undergoing an update and 40 minutes have elapsed from incident start without a change to connectivity.

 

or

 

The device is not undergoing an update and 5 minutes have elapsed from incident start and all attempts to register with the SIP registrar were unsuccessful.

High Audio Packet Loss

  • Network traffic for a call's audio stream experienced 10 continuous seconds of 3% or higher loss.

The incident occurred and no other packet loss incidents have been reported for the call. Alert notification is published almost immediately.

High Video Packet Loss

  • Network traffic for a call's video stream experienced 10 continuous seconds of 3% or higher loss.

The incident occurred and no other packet loss incidents have been reported for the call. Alert notification is published almost immediately.

Critical Audio Packet Loss

  • Network traffic for a call's audio stream experienced 10 continuous seconds of complete packet loss.

The incident occurred and no other packet loss incidents have been reported for the call. Alert notification is published almost immediately.

Critical Video Packet Loss

  • Network traffic for a call's video stream experienced 10 continuous seconds of complete packet loss.

The incident occurred and no other packet loss incidents were reported for the call. Alert notification is published almost immediately.

Offline

  • The device was started, but no connection could be established or authenticated with Lifesize's call management services
  • The device had a connection to Lifesize's call management services and other services but at least one of these connections was closed and we have detected the closure.

The device is undergoing an update and 40 minutes have elapsed from incident start without a change to connectivity.

or

The device isn't undergoing an update and 5 minutes have elapsed from incident start without a change to connectivity.

23 people found this helpful

Attachments

    Outcomes