Contact Sales
Demo
Buy now
Home / Integration plugins / Zabbix SMS and Voice Calls Integration

Zabbix SMS & voice call alerts - integration manual

Here we describe how to use SMSEagle for Zabbix SMS & text-to-speech voice call alerts. The configuration is very straightforward – it should take you about 5 min to have it up and running.

SMSEagle is an offline hardware SMS gateway. Therefore no external connection to 3rd party system is required. All notifications are generated on-premise and sent directly to a cellular network. This solution can be used in secure installations without Internet access.

SMSEagle Setup

  • Create a new user in SMSEagle (menu Users > + Add Users, user access level: “User”).
  • Grant API access to the created user:
    • click Access to API beside the newly created user
    • Enable APIv2
    • Generate new token
    • For text messages, add access permissions in section Messages for: Send SMS, Send MMS.
    • For voice call alerting, add access permissions in section Calls for: Make a ring call, Make a TTS call, Make a TTS Advanced call.
    • Save settings

Zabbix Setup

The configuration consists of a media type in Zabbix, which will invoke the webhook to send alerts to SMSEagle device through the Rest API.

  1. In the Administration > Media types section, import the media_smseagle.yaml.
  2. Open the newly added SMSEagle media type and replace all <PLACEHOLDERS> with your values.
    The following parameters are required:access_token – API access token created in SMSEagle
    url – actual URL of your SMSEagle device (for example: https://10.10.0.100 or https://sms.mycompany.com)
    type     – type(s) of message(s) to send. Possible values: sms, mms, tts and tts_adv, respectively for SMS, MMS, TTS Voice Call (text-to-speech call) and Advanced TTS Voice Call (high-quality audio conversion).
    Allows multiple types, separated by commas (e.g. “sms,tts_adv”).

Other required parameters are message type specific. More information can be found on our APIv2 page.

3. in the Administration > Users click on a User, and add a new media called SMSEagle. Enter SMS recipient. Available recipient formats:

  • Phone number: phone_number
  • Contact in SMSEagle Phonebook: contact_id:c
  • Group in SMSEagle Phonebook:group_id:g

Multiple recipients can be separated by comma.

For more information, please see Zabbix documentation.

Zabbix Template (optional)

If you would like to add a ready-to-use Zabbix template for monitoring your SMSEagle device in Zabbix:

  1. Extended template repository + instructions (Zabbix 7.0+)
  2. Simple template repository + instructions (Zabbix 6.0+)

Acknowledge Events via SMS (optional)

Beyond sending alerts, SMSEagle lets your team acknowledge or unacknowledge Zabbix events directly by replying with SMS – no need to log in to the Zabbix interface. This capability is built on the SMSEagle Webhooks feature.

How to configure it

  1. In SMSEagle webGUI > menu Webhooks, create a new rule and set the method to POST (Zabbix).
  2. Choose the action type the rule should handle:
    • Acknowledge (ACK) – an incoming SMS acknowledges the event. Expected SMS format: ACK [eventid] [optional message] (e.g. ACK 12345 Problem resolved).
    • Unacknowledge (NOACK) – an incoming SMS unacknowledges the event. Expected SMS format: NOACK [eventid] [optional message] (e.g. NOACK 12345 Re-opening issue).
    • Acknowledge / Unacknowledge (ACK/NOACK) – a single rule handles both actions, with the action determined automatically by the SMS prefix (ACK or NOACK).
  3. Enter the Zabbix API URL (for example: https://10.10.0.100/zabbix/api_jsonrpc.php).
  4. Select the authentication type:
    • API Token – recommended for Zabbix 6.4 and newer. Don’t have a token yet? See Generating a Zabbix API token below.
    • Login / Password – for Zabbix older than 6.4.
  5. Enter the authentication credentials and save the rule.

Generating a Zabbix API token

If you chose API Token authentication (Zabbix 6.4+), here’s how to create one in the Zabbix frontend:

  1. Go to Users → API tokens and click Create API token in the top-right corner.
  2. Fill in the token details:
    • Name – a descriptive label, e.g. SMSEagle ACK.
    • User – the Zabbix user the token will authenticate as. 
    • Expires at – clear it for a token that never expires.
  3. Click Add.
  4. Copy and save the Auth token value in a safe place before closing the page, then click Close.
  5. Paste this value into the API Token field of your SMSEagle webhook rule.

Where to see the result

Once an acknowledgment is sent, the updated status appears in the Zabbix interface in two places:

  • Monitoring → Problems – the Ack column changes to Yes.
  • Monitoring → Problems → Event details – the full acknowledgment history is shown, including the message text, timestamp, and the Zabbix user who performed the action.

How to Monitor Your Zabbix Server? (optional)

Zabbix is a perfect monitoring tool, but what if the Zabbix server hardware fails? Even the best hardware can experience failures. That’s where SMSEagle steps in with its cool tiny feature called Network Monitoring. SMSEagle can monitor IP addresses or TCP ports and instantly send an SMS or make a call when a failure is detected. This ensures you can always keep an eye on your monitoring server.

What is hardware
SMS Gateway?

Learn more

Learn more about
SMSEagle features

Explore all features

Explore SMSEagle Demo device

SMSEagle is a hardware & software solution that guarantees a swift delivery of your messages to designated recipients, whether it’s for notifications, alerts, or important updates.

After registering to a demo you get a remote access to our physical device NXS-9750.

  • 14-days free trial
  • Access to over 20 functionalities
Start 14-days trial