Alerts: Difference between revisions

From VoIPmonitor.org
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 1: Line 1:
Alerts&Reports contains tools to generate email alerts based on QoS parameters or SIP error conditions. It can also generate daily report or generate ad hoc reports. All generated alerts and reports are saved in history.
== Alerts & Reports ==


Emails are sent through PHP function "mail" which relies on linux Mail Transport Agent (MTA). The smtp should be configured in the linux server in a standard way. It is usually Exim or postfix or sendmail. Refer to your linux distribution MTA documentation.  
Alerts & Reports generate email notifications based on QoS parameters or SIP error conditions. It includes daily reports, ad hoc reports, and stores all generated items in history.


Alerts are processed by PHP script which has to be placed to crontab  
Emails use PHP's "mail" function, relying on the server's MTA (e.g., Exim, Postfix, Sendmail). Configure MTA per your Linux distribution documentation.
 
Process alerts via a PHP script in crontab:
 
For CentOS & Debian:


Centos & Debian
  echo "* * * * * root php /var/www/html/php/run.php cron" >> /etc/crontab
  echo "* * * * * root php /var/www/html/php/run.php cron" >> /etc/crontab


(it depends where is the voipmonitor GUI installed, it should point to run.php file)  
(Adjust path to run.php based on VoIPmonitor GUI installation.)


modify
Reload crontab: killall -HUP cron (or crond).


Do not forget to killall -HUP cron (crond)
=== Configure Alerts ===


= Configure alerts =
Email alerts trigger on SIP protocol or RTP QoS metrics. Types: RTP alerts and SIP signaling.


Email alerts trigger alerts based on SIP protocol or RTP QoS metrics.  
Common filters: Call duration, IP addresses, numbers, and email recipients.


[[File:alertgrid.png]]
[[File:alertgrid.png]]


Alerts are divided into two types RTP alerts and SIP signalization. Each of those shares common filters: Duration of call, IP addresses, Numbers and E-mails to which the alert is sent.
* '''RTP Alerts''': Trigger on MOS, packet loss, jitter, delay, one-way calls (answered but one RTP stream missing), or missing RTP (answered but both streams missing). Alert if thresholds exceeded and incidents > set value or CDR percent > threshold.
 
Alert type RTP allows alerts to trigger based on MOS, Packet loss, jitter, Delay, one way call (call was answered and one of RTP stream is missing) and Missing RTP (call was answered and both RTP stream is missing). An alert is triggered once one of the thresholds is reached and number of incidents is greater than the set value or number of CDR is over percent threshold.  


[[File:alertrtpform.png]]
[[File:alertrtpform.png]]


SIP response alert type triggers alerts based on SIP response type.  
* '''SIP Response Alerts''': Trigger on SIP response codes. Empty response: All call attempts per filters. Response 0: Unreplied INVITEs.


[[File:alertsipform.png]]
[[File:alertsipform.png]]


If the SIP response is empty - all call attempts are reported based on the filter criteria only. This is for example useful to watch calls to 112. If SIP response is 0 - all calls with no response are triggered (unreplied INVITE)
* '''Filters''':
  - IP/Number Group: Apply to defined groups (from Groups menu).
  - IP Addresses/Numbers: Individual IPs, numbers, or ranges (delimited by Enter).
  - Email Group: Send to group-defined emails.
  - Emails: Individual emails (delimited by Enter).
 
[[File:alertgroup.png]]


IP/Number group – choose to which group of IP/Numbers the alert is applied. Groups are defined in Groups main menu. IP address/Numbers – choose individual IP addresses/numbers or network ranges to which is the alert applied. Delimited by [enter]E-mail Group – choose to which Emails defined in groups should be alert sent. E-mails – choose individual list of E-mails for alert delivery. Delimited by [enter].
=== Sent Alerts ===


[[File:alertgroup.png]]
Sent alerts are saved in history, matching email content.
= Sent alerts =
Each sent alert is saved into history and looks exactly same as delivered in the email.  


[[File:alert-sentalerts.png]]
[[File:alert-sentalerts.png]]
In the parameters table overall QoS metrics are shown with bad values highlighted.  
 
Parameters table shows QoS metrics with bad values highlighted.


[[File:alert-perameters.png]]
[[File:alert-perameters.png]]
The CDR records table shows individual cases. Alert flag column shows if the call alerted because of (M)OS, (J)itter, (P)packet loss or (D)elay.
 
CDR records table lists cases, with alert flags: (M)OS, (J)itter, (P)acket loss, (D)elay.
 
=== AI Summary for RAG ===
 
'''Summary:''' This article covers VoIPmonitor's Alerts & Reports for email notifications on QoS/SIP issues, daily/ad hoc reports, crontab setup, alert configuration (RTP/SIP types, filters), and viewing sent alerts with metrics and CDR details.
 
'''Keywords:''' alerts, reports, email notifications, QoS metrics, SIP responses, crontab, RTP alerts, SIP alerts, filters, history, MTA configuration
 
'''Key Questions:'''
* How do I set up email alerts in VoIPmonitor?
* What are the types of alerts (RTP vs. SIP)?
* How do I configure crontab for alert processing?
* What filters can I use for alerts?
* How are sent alerts stored and viewed?
* What do alert flags in CDR mean?

Latest revision as of 14:02, 10 November 2025

Alerts & Reports

Alerts & Reports generate email notifications based on QoS parameters or SIP error conditions. It includes daily reports, ad hoc reports, and stores all generated items in history.

Emails use PHP's "mail" function, relying on the server's MTA (e.g., Exim, Postfix, Sendmail). Configure MTA per your Linux distribution documentation.

Process alerts via a PHP script in crontab:

For CentOS & Debian: 

echo "* * * * * root php /var/www/html/php/run.php cron" >> /etc/crontab

(Adjust path to run.php based on VoIPmonitor GUI installation.)

Reload crontab: killall -HUP cron (or crond).

Configure Alerts

Email alerts trigger on SIP protocol or RTP QoS metrics. Types: RTP alerts and SIP signaling.

Common filters: Call duration, IP addresses, numbers, and email recipients.

  • RTP Alerts: Trigger on MOS, packet loss, jitter, delay, one-way calls (answered but one RTP stream missing), or missing RTP (answered but both streams missing). Alert if thresholds exceeded and incidents > set value or CDR percent > threshold.

  • SIP Response Alerts: Trigger on SIP response codes. Empty response: All call attempts per filters. Response 0: Unreplied INVITEs.

  • Filters:
 - IP/Number Group: Apply to defined groups (from Groups menu).
 - IP Addresses/Numbers: Individual IPs, numbers, or ranges (delimited by Enter).
 - Email Group: Send to group-defined emails.
 - Emails: Individual emails (delimited by Enter).

Sent Alerts

Sent alerts are saved in history, matching email content.

Parameters table shows QoS metrics with bad values highlighted.

CDR records table lists cases, with alert flags: (M)OS, (J)itter, (P)acket loss, (D)elay.

AI Summary for RAG

Summary: This article covers VoIPmonitor's Alerts & Reports for email notifications on QoS/SIP issues, daily/ad hoc reports, crontab setup, alert configuration (RTP/SIP types, filters), and viewing sent alerts with metrics and CDR details.

Keywords: alerts, reports, email notifications, QoS metrics, SIP responses, crontab, RTP alerts, SIP alerts, filters, history, MTA configuration

Key Questions:

  • How do I set up email alerts in VoIPmonitor?
  • What are the types of alerts (RTP vs. SIP)?
  • How do I configure crontab for alert processing?
  • What filters can I use for alerts?
  • How are sent alerts stored and viewed?
  • What do alert flags in CDR mean?
Retrieved from "https://www.voipmonitor.org//doc/index.php?title=Alerts&oldid=5713"