Threshold and Trigger Info

This section defines the type of activity to be monitored (Alert type) as well as the threshold criteria and time period for the alert. It also explains how alerts are processed and when devices are blocked and emails sent.

Note:

Before defining your alert, it is important to take note of the following definitions.

Time periods are based on Greenwich Mean Time (GMT).

• Per Hour: time period between :00 and :59. The period resets at the beginning of each hour.
• Per Day: time period between 00:00 and 23:59 GMT of one calendar day.
• Month to Date: time period between the 1st of the month and today.
• Device activity is tracked from the time the alert is created.

Entering Minimum and Maximum Values

• The user is required to enter only one threshold parameter. Both a minimum and maximum value are not required, therefore leaving a threshold blank is valid. For example, to detect if a device exceeds a specific amount of packet data usage, enter a maximum value, and leave the minimum value blank.
• If specifying both minimum and maximum values, ensure that the minimum value does not exceed the maximum value.  
• Specifying a minimum threshold of one (1) could generate unnecessary email traffic.
• Specifying a threshold value of zero (0) will result in an error.

Roaming

• A device is considered Roaming if it is not currently registered in its home network (determined by the device's OPC).

After selecting the Alert type, you will be able to enter your threshold criteria. You will then need to indicate a Time period as well. Please see the table below for information on the types of alerts supported by the portal.

Warning: Actual consumed packet data may exceed the amount specified by MyAlerts data blocking threshold. Because MyAlert actions such as blocking depend on the frequency that data usage records are available, it is possible for a device to consume more data than is specified by the MyAlert threshold. Some products may take as long as 75 minutes for the usage threshold to be detected, during which time the device may continue to consume data. For Fusion NA and Fusion Global products, this period is 11 minutes. For Dual-Mode A-LH and Global SIM, this period is 75 minutes. For more information, see "MyAlerts based data blocking" in MyAlerts Limitations.

Alert Type	Threshold Type	Threshold Unit	Time Period	Product Support and Limitations
Packet See Warning above.	Usage	KB, MB, or GB	Hourly, Daily, or Monthly	All Aeris products are supported.
Packet-Roaming	Usage	KB, MB, or GB	Daily or Monthly	Fusion NA and Fusion Global products are supported. Global SIM is supported, however these alerts may not be accurate due to the operational patterns of roaming partners. Dual-Mode A-LH is not supported.
SMS	Occurrence	Count (includes both MO and MT SMS)	Hourly, Daily, or Monthly	All Aeris products are supported.
Voice	Usage	Minutes (includes both MO and MT Voice)	Hourly, Daily, or Monthly	Fusion NA, Fusion Global, Global SIM, and Dual-Mode A-LH products are supported.
Registration	Occurrence	Count	Hourly, Daily, or Monthly	Fusion Global is supported. Global SIM is supported, however these alerts may not be accurate due to the operational patterns of roaming partners. Fusion NA and Dual-Mode A-LH products are not supported.
Registration-Roaming	Occurrence	Count	Hourly, Daily, or Monthly	Fusion Global is supported. Global SIM is supported, however these alerts may not be accurate due to the operational patterns of roaming partners. Fusion NA and Dual-Mode A-LH products are not supported.
Registration-Roaming	Duration	Seconds, Minutes, Hours, or Percentage % (absolute)	Hourly, Daily, or Monthly	Fusion Global is supported. Global SIM is supported, however these alerts may not be accurate due to the operational patterns of roaming partners. Fusion NA and Dual-Mode A-LH products are not supported.
Deregistration	Occurrence	Count	Hourly, Daily, or Monthly	Fusion Global is supported. Global SIM is supported, however these alerts may not be accurate due to the operational patterns of roaming partners. Fusion NA and Dual-Mode A-LH products are not supported.
Deregistration	Duration	Seconds, Minutes, or Hours (absolute)	Hourly, Daily, or Monthly	Fusion Global is supported. Global SIM is supported, however these alerts may not be accurate due to the operational patterns of roaming partners. Fusion NA and Dual-Mode A-LH products are not supported.
SwitchHopping	Occurrence	Count	Hourly, Daily, or Monthly	No longer supported.

Note that although any alert type can be defined for any product through the portal, the functional limitations listed in the table above still apply.

How Alerts are Processed

When you create an alert, it becomes effective immediately. This means that AerPort immediately begins checking devices to detect if they meet the threshold(s) defined in the alert.

On an hourly basis, AerPort records which devices met the threshold, and then begins applying the traffic policy on the individual devices. An email notification is sent to all users defined in the alert recipient list within 30 minutes.

• If an alert is defined with a Time period of Per Hour, this process repeats hourly. However, once an email notification is sent for a particular device, it is not sent again each hour.
• If an alert is defined with a Time period of Per Day or Per Month, once the alert has been triggered and an email sent, it is not sent again during that period.
• Devices that trigger an alert with a traffic policy will have their services blocked individually. Summary emails to report this activity will be sent every 15 minutes until all device blocking is completed.
• For devices that trigger an alert with no traffic policy, summary emails will be sent every 15 minutes until all devices have been communicated to the email recipients.

For more information, see the MyAlerts Video.