Camera email alarms

Turn the alarm emails from your cameras and recorders into alarms, set up a camera's email route or a Site email input, copy the SMTP settings to the device, and see the attached pictures on each alarm.

Last reviewed Print view kalytera-cloud email-alarms smtp email-inputs alarm-evidence cameras
Contents

Many cameras and recorders can send an email when they detect something. Kalytera Cloud gives each one a private recipient address, and every email that reaches it raises an alarm with the pictures attached. Only portal administrators can set this up, and your service must include Email alarms (see Settings > System profile).

Camera route or Site email input

UseForEvidence cameras
The camera's Email alarms tabA camera that is already in the portal. Its alarms belong to that camera.Up to 16, the camera included
The Site's Email inputsA recorder, another VMS or any device that is not a camera in the portal.Up to 16

Evidence cameras need Video evidence in your service.

Set up a camera's email alarms

  1. Make sure the camera belongs to a Site. Until it does, the tab asks you to assign it first.
  2. Open the camera from Cameras and select the Email alarms tab.
  3. Keep Email route enabled on. Turn Dispatch alarms to monitoring station off if these alarms must not reach your monitoring station.
  4. Open Advanced settings and review the fields in the table below.
  5. Select Save email alarms. The Private recipient appears.
  6. If you chose a username and password, copy them from New SMTP credentials at once: the password is shown only once.
FieldWhat it does
Email evidence retention (days)How long the email and its attachments are kept, 1 to 3,650 days (30 by default).
Manage camera associationsOpens the Site's camera associations, where you add other cameras whose video joins the alarm. Evidence shows the limit: Up to 16 cameras total.
Allow any IP or dynamic addressOn by default. Turn it off to accept email only from the Allowed source IPs or CIDRs you list.
Transport securitySTARTTLS when available, Require STARTTLS or Require implicit TLS.
SMTP authenticationNo authentication, or Use SMTP username and password (TLS only).
Regenerate credentialsCreates a new password. The old one stops working at once, so update the camera.

Without TLS, Kalytera accepts email only from source addresses listed on the route. A camera that cannot use TLS needs its address under Allowed source IPs or CIDRs; with Allow any IP or dynamic address on, the camera must use TLS.

What to set on the camera

The tab lists the values to copy under SMTP server, Port and encryption and Recipient. In the camera's or recorder's email settings:

  1. Enter one of the SMTP server addresses that the device can reach.
  2. Enter the port shown for your Transport security, and set the device's encryption to match.
  3. Enter the Private recipient as the recipient. If the device insists on its own domain, keep the part before the @ and use any domain: Kalytera reads only that part.
  4. Enter the SMTP username and password only if the route uses them.
  5. Link the device's events, such as motion or line crossing, to sending an email with a picture attached.
  6. Send the device's test email, then select Refresh on the tab. It shows when the last email was accepted or rejected, and why.

Add a Site email input

  1. Go to Sites, select Open workspace, then Alarm sources > Email inputs.
  2. Select Add email input and enter a Name and the Email retention days.
  3. Keep Input enabled on. Leave Dispatch alarms through this Site on to send these alarms to the Site's monitoring station.
  4. For a monitoring station, enter a Reporting zone and Partition that no other source uses.
  5. Under Source and SMTP security, set the allowed addresses, Transport security and SMTP authentication as for a camera.
  6. Select Create input, and copy any credentials shown.
  7. To add evidence cameras, select Associations on the input.

The input's recipient address appears in the list, and Device SMTP settings below it shows the server addresses and ports to enter on the device.

How email alarms appear

Each email that Kalytera accepts raises one Alarm email alarm at the camera's or input's Site, handled like any other alarm (see Alarms and incidents). Kalytera does not read the sender, subject or text, so every email to the address counts as an alarm. If a device resends the same email, it still counts once.

The alarm shows the Evidence attached to the alarm email: still pictures (JPEG, PNG, GIF or WebP, one or a sequence) and MKV video, plus video from the evidence cameras. Other attachments are kept with the email and never shown.

Each camera route and email input is an Email input source for Cloud arming (see Cloud arming and site controls). With dispatch on, the monitoring station receives the alarm under the camera's reporting zone, or the input's own (see Send alarms to a monitoring station).

If email alarms are not available

  • If cameras have no Email alarms tab, your service does not include email alarms. Ask Kalytera.
  • If the tab or Email inputs shows a warning that inbound email is off or not running, email alarms are not enabled for your portal: contact Kalytera. You can still save routes; they receive email once Kalytera enables it.