SMS Not Sending

We use self-hosted monitoring appliance. I've configured the SMS setting with our Alert UID and PIN, but when I send a test SMS I do not receive it, nor do I see the attempt when I log in to my my.serverscheck.com account.

Do I need to have any ports opened in order for the SMS service to work?

Comments

  • godsowngodsown
    I ran the debugging procedure I found in another post. Attaching the debug reports.

    alerts.txt:
    #
    #
    # ServersCheck Alerting & Notification Component
    # version 14.2.4 Build 2018012201
    #
    #
    # (c) Copyright 2003-2017 - ServersCheck BVBA
    # www.serverscheck.com
    #
    #
    # Wed Jul 17 09:14:14 2019 Sending error output to file sc-alerts-err.txt
    #
    #
    # ServersCheck Alerting & Notification Component
    # version 14.2.4 Build 2018012201
    #
    #
    # (c) Copyright 2003-2017 - ServersCheck BVBA
    # www.serverscheck.com
    #
    #
    # Wed Jul 17 09:24:08 2019 Sending error output to file sc-alerts-err.txt

    web.txt

    # Wed Jul 17 09:15:16 2019 Starting up web server
    # version 14.4.1 (Build 2019013101)
    #
    #
    # (c) Copyright 2003-2019 - MVL - Under License by ServersCheck BVBA
    # serverscheck.com
    #
    #
    #
    # Wed Jul 17 09:15:16 2019 DB Ver 5
    # Wed Jul 17 09:15:16 2019 Admin User callahanIT
    # Wed Jul 17 09:15:17 2019 License verification
    # Wed Jul 17 09:15:17 2019 System ID:53B5C3FC-F961-4187-83A4-BDA237A24112
    # Wed Jul 17 09:15:17 2019 License key:f26447-23e254-9a4565-8e5982-7ec197-f01c97-d86820-200109
    # Wed Jul 17 09:15:17 2019 Epoch expiry:1578549600
    # Wed Jul 17 09:15:17 2019 Version build date:1547919303
    # Wed Jul 17 09:15:17 2019 License is OK
    # Wed Jul 17 09:15:17 2019 Env:C:\Windows
    # Wed Jul 17 09:15:17 2019 Enabling HTTP Server
    # Wed Jul 17 09:15:17 2019 Configuration server ready, serving on port "1272"...
    #
    #
  • OhMySensorOhMySensor
    It may be a server problem, have you tried it again?
  • godsowngodsown
    I've tried it multiple times. When you say "server problem" do you mean on my end or Serverscheck end? If on my end, what do I need to make sure is open firewall wise?
  • AdministratorAdministrator
    edited July 24
    It is not the latest version that you seem to be using. Port 80 and 443 are required for the alerting module.
  • godsowngodsown
    Where can I download the latest version, and what is the destination I need to have open on these ports for the alerting module (web address or IP address)?
  • SchottkySchottky
    edited July 26
    hi godsown,

    I've tried it to my latest Monitoring Software v15.0.0 and I am using Premium Alert Service. I can only receive test SMS info on the number registered on my my.serverscheck account
  • AdministratorAdministrator
    godsown destination is not fixed; it is dynamic based on load. Ports used are 80 and 443.
  • AdministratorAdministrator
    To run your s-alerts.exe in debug mode, proceed as follows:
    1/ make sure there is NO other instance of the s-alerts.exe running
    2/ from the command prompt in the Monitoring Software directory run
    s-alerts > debug.txt
    3/ Trigger an alert by changing a sensor threshold
    4/ Wait until it changes to DOWN
    5/ Check debug.txt log

    Here is a sample output
    # 001 Sat Jul 27 20:19:09 2019 1564251548.4566174 - SMS notification
    # 001 Sat Jul 27 20:19:09 2019 Sms Configuration:
    P:TVOC%20Sensor1%20()%20changed%20to%20DOWN%20on%20Sat%20Jul%2027%2020:19:09%202019.%20Error:%20382.00%20(returned%20value)%20>%20100%20OR%20382.00%20(returned%20value)%20%20%20-%20 - length: 179
    # 001 Sat Jul 27 20:19:10 2019 SMS via ServersCheck SMS Service sent: OK:eb9af6d2d0c8a869c97c29c35f445a22
    646
    OK:e77b69ad226e753872708a4e2de034dc
    # 001 Sat Jul 27 20:19:10 2019 deleting 1 C:\Appliance\MonitoringAppliance\alerts\queue\1564251549.46316.alert
  • godsowngodsown
    edited July 30
    # 001 Mon Jul 29 14:47:18 2019 1564429635.7458850 - SMTPE - Mail Sent
    # 001 Mon Jul 29 14:47:18 2019 deleting 1 C:\Program Files (x86)\ServersCheck_Monitoring\/alerts\queue\1564429636.76624.alert
    # 001 Mon Jul 29 14:47:18 2019 1564429635.7458850 - 18410 processing new alert using SMS
    # 001 Mon Jul 29 14:47:18 2019 1564429635.7458850 - SMS notification
    # 001 Mon Jul 29 14:47:18 2019 Sms Configuration:
    P:Server%20Room%20Leak%20Sensor%20()%20changed%20to%20DOWN%20on%20Mon%20Jul%2029%2014:47:16%202019.%20Error:%20No%20numeric%20value%20returned%20(value%20was:%20-)%20-%20 - length: 168
    # 001 Mon Jul 29 14:47:18 2019 SMS via ServersCheck SMS Service sent:
  • AdministratorAdministrator
    From what it seems the s-alerts.exe is unable to access our servers.

    Following line:
    001 Mon Jul 29 14:47:18 2019 SMS via ServersCheck SMS Service sent:

    This should be succeeded with an OK: and then the message UID.
  • godsowngodsown
    Right, that is why I need to know what addresses to open up in our firewall. We're a hospital, so we only open up what we need to.
  • AdministratorAdministrator
    Unfortunately that is information I can not provide as there is no fixed IP for our messaging servers and domain name changes subject to load.
  • godsowngodsown
    So there's not an initial server it looks for first before getting sent to one of the servers? Can you provide all the domain names that could possibly be in use? Or is it a long list?
  • AdministratorAdministrator
    For security purposes we can not share them publicly.
  • godsowngodsown
    Well, that's not helpful at all. I would think I'm not the only one that has a locked-down network that would need to whitelist servers for using the SMS function. That information should be available.
Sign In or Register to comment.