With FW versions before 03.28.07.Rev.100 SMS notification for non-eventual events configured in multiple tabs which caused inconvenience. From firmware version 03.28.07.Rev.100 improvement in configuring SMS events will be made. SMS event configuration will be available in a single tab, which would allow more flexible FMB configuration, and improved visibility and readability of configured parameters. Additionally, now it is possible to send a SMS notification to multiple phone numbers simultaneously<be>

Note: This update will affect only non-eventual IO elements. Eventual IO SMS notifications (like Immobilizer, Overspeeding, etc.) will still have to be configured separately.

Feature description

SMS events functionality allows FMB to send a configured SMS when an event is triggered. This event can be triggered by every I/O element.
When any of the I/O elements are triggered, FMB sends a configured SMS message to a defined phone number.

File:SMSEventFunctionality.gif

FMB is able to send SMS messages to Predefined phone numbers (recipients) if any of the selected events are triggered. Users can send SMS alert messages of selected events to a maximum of 10 predefined phone numbers. AVL ID of the parameter has to be entered in the configuration to receive its SMS event. Predefined phone numbers must be entered in the SMS Events Numbers list in the ‘SMS \ Call Settings’ menu before it will be possible to pair them with AVL ID and SMS event text.

SMS Event Text is used to add additional text to standard SMS event message text.


	If FMB is in Deep Sleep mode and an SMS event occurs with Low priority (which does not wake up FMB), then the device does not send the message. It is saved to devise memory until it wakes up from Deep Sleep mode and the GSM modem starts working normally. After it wakes up, all the messages that are saved to memory will be sent.