2 Replies Latest reply on Mar 28, 2017 7:21 PM by Sarah Mims

    Problem with SMS Messages Test

    Sarah Mims

      First off, I'd like to say that VizAlerts is super cool so thank you! I've successfully run the Simple Alerts test as well as the Advanced Alerts demo. I'm running into a challenge with the SMS test. Here is some background:

       

      Twilio

      1) I set up a Twilio account and confirmed that I'm using the correct Account SID and Auth Token

      2) I requested a phone number from Twilio to use as my "from" number

      3) I successfully tested sending a message to my phone number from my requested Twilio "from" number using their API explorer

       

      VizAlerts

      1) I confirmed that I entered the correct AccountSID and Auth Token information in the vizalerts.yaml config file under # SMS Settings and that smsaction.enable is set to true

      2) I changed the default_from_number value in the VizAlertsConfig.twb workbook to be the requested "from" number I got from Twilio (see #2 above)

      3) I followed all of the steps in the "Optional: Send Yourself Some SMS Messages Test" section of the Install Guide

      4) I did not receive any SMS messages to my phone number nor did I receive any error emails from VizAlerts

       

       

      Below is what I see in the log. Is there any insight you can provide on what may be happening? Thanks!

      MainThread - 2017-03-28 16:58:34 - [INFO] - LoggerQuickSetup - Logging initialized, writing to .\logs\vizalerts.log_2017-03-28.log

      MainThread - 2017-03-28 16:58:34 - [INFO] - main - VizAlerts v2.0.1 is starting

      MainThread - 2017-03-28 16:58:34 - [DEBUG] - trusted_ticket_test - testing trusted ticket: ############, ####, ###, None

      MainThread - 2017-03-28 16:58:34 - [DEBUG] - get_trusted_ticket - Generating trusted ticket. Request details: Server: ####, Site: , Username: ####, Url: http://####/trusted, Postdata: username=#####.

      MainThread - 2017-03-28 16:58:34 - [DEBUG] - get_trusted_ticket - NOT using SSL and NOT verifying cert

      MainThread - 2017-03-28 16:58:34 - [DEBUG] - get_trusted_ticket - Got ticket: #####==:#####

      MainThread - 2017-03-28 16:58:34 - [DEBUG] - trusted_ticket_test - Generated test trusted ticket. Value is: #####==:#####

      MainThread - 2017-03-28 16:58:34 - [INFO] - main - SMS Actions are enabled

      MainThread - 2017-03-28 16:58:34 - [DEBUG] - get_alerts - Pulling source viz data down

      MainThread - 2017-03-28 16:58:34 - [DEBUG] - get_trusted_ticket - Generating trusted ticket. Request details: Server: ####, Site: , Username: ####, Url: http://####/trusted, Postdata: username=#####.

      MainThread - 2017-03-28 16:58:34 - [DEBUG] - get_trusted_ticket - NOT using SSL and NOT verifying cert

      MainThread - 2017-03-28 16:58:34 - [DEBUG] - get_trusted_ticket - Got ticket: ####==:####

      MainThread - 2017-03-28 16:58:34 - [DEBUG] - export_view - Getting vizdata from: http://####/trusted/####==:########/views/VizAlertsConfig/ScheduledTriggerViews?&:format=csv&:refresh=y

      MainThread - 2017-03-28 16:58:34 - [DEBUG] - export_view - NOT Validating cert for this request

      MainThread - 2017-03-28 16:58:34 - [DEBUG] - _new_conn - Starting new HTTP connection (1): ####

      MainThread - 2017-03-28 16:58:34 - [DEBUG] - _make_request - http://####"GET /trusted/####==:####/views/VizAlertsConfig/ScheduledTriggerViews?&:format=csv&:refresh=y HTTP/1.1" ### #

      MainThread - 2017-03-28 16:58:37 - [DEBUG] - _make_request - http://####"GET /views/VizAlertsConfig/ScheduledTriggerViews?&:format=csv&:refresh=y&:embed=y HTTP/1.1" ### ####

      MainThread - 2017-03-28 16:58:37 - [INFO] - export_view - Attempting to write to: .\temp\20170328165837783000_MainThread_VizAlertsConfig-ScheduledTriggerViews.csv

      MainThread - 2017-03-28 16:58:37 - [INFO] - main - Processing a total of 1 alerts

      MainThread - 2017-03-28 16:58:37 - [DEBUG] - main - Queueing subscription id -## for processing

      MainThread - 2017-03-28 16:58:37 - [DEBUG] - main - Starting thread with name: 1

      1 - 2017-03-28 16:58:37 - [DEBUG] - run - Thread 1 is processing subscription_id -##, view_id ###, site_name #####, customized_view_id None, view_name SMS Success Tests

      MainThread - 2017-03-28 16:58:37 - [DEBUG] - main - Starting thread with name: 2

       

       

      1 - 2017-03-28 16:58:37 - [DEBUG] - execute_alert - Starting to download trigger data

      1 - 2017-03-28 16:58:37 - [DEBUG] - get_trusted_ticket - Generating trusted ticket. Request details: Server: ####, Site: , Username: ####Url: http://####/trusted, Postdata: username=####.

      1 - 2017-03-28 16:58:37 - [DEBUG] - get_trusted_ticket - NOT using SSL and NOT verifying cert

      1 - 2017-03-28 16:58:37 - [DEBUG] - get_trusted_ticket - Got ticket: ####==:####

      1 - 2017-03-28 16:58:37 - [DEBUG] - export_view - Getting vizdata from: ####/trusted/####==:####/views/VizAlertsDemo/SMSSuccessTests?&:format=csv&:refresh=y

      1 - 2017-03-28 16:58:37 - [DEBUG] - export_view - NOT Validating cert for this request

      1 - 2017-03-28 16:58:37 - [DEBUG] - _new_conn - Starting new HTTP connection (1): ####

      1 - 2017-03-28 16:58:37 - [DEBUG] - _make_request - http://#### "GET /trusted/####==:####/views/VizAlertsDemo/SMSSuccessTests?&:format=csv&:refresh=y HTTP/1.1" ### #

      Currently active threads:: [<VizAlertWorker(1, started 1896)>, <_MainThread(Main

      Thread, started 10932)>]

      1 - 2017-03-28 16:58:50 - [DEBUG] - _make_request - http://#### "GET /views/VizAlertsDemo/SMSSuccessTests?&:format=csv&:refresh=y&:embed=y HTTP/1.1" ### ###

      20170328165850232000_1_VizAlertsDemo-SMSSuccessTests.csv

      1 - 2017-03-28 16:58:50 - [DEBUG] - execute_alert - Got trigger data, now parsing fields

      1 - 2017-03-28 16:58:50 - [DEBUG] - parse_action_fields - Parsing action fields

      1 - 2017-03-28 16:58:50 - [DEBUG] - parse_action_fields - found field match! : SMS Header 1

      1 - 2017-03-28 16:58:50 - [DEBUG] - parse_action_fields - found field match! : SMS To

      1 - 2017-03-28 16:58:50 - [DEBUG] - parse_action_fields - found field match! : SMS Action

      1 - 2017-03-28 16:58:50 - [DEBUG] - parse_action_fields - found field match! : SMS Footer 1

      1 - 2017-03-28 16:58:50 - [DEBUG] - parse_action_fields - found field match! : SMS Message

      1 - 2017-03-28 16:58:50 - [DEBUG] - parse_action_fields - searching for action fields

      1 - 2017-03-28 16:58:50 - [DEBUG] - parse_action_fields - Advanced alert detected

      1 - 2017-03-28 16:58:50 - [DEBUG] - parse_action_fields - Retrieving all errorsfound in field parse operation

      1 - 2017-03-28 16:58:50 - [DEBUG] - execute_alert - Validating trigger data

      1 - 2017-03-28 16:58:50 - [DEBUG] - validate_trigger_data - Validating as an advanced alert

      1 - 2017-03-28 16:58:50 - [DEBUG] - validate_trigger_data - Validating SMS numbers

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating SMS field value: 1.###.###.####

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating presumed sms number: 1.###.###.####

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_to_e164 - Converting 1.###.###.#### to E.164 format, country code US

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_is_invalid - testing smsnumber +1########## against regex .*

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating SMS field value: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating presumed sms number: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_to_e164 - Converting 1########## to E.164 format, country code US

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_is_invalid - testing smsnumber +1########## against regex .*

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating SMS field value: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating presumed sms number: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_to_e164 - Converting 1########## to E.164 format, country code US

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_is_invalid - testing smsnumber +1########## against regex .*

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating SMS field value: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating presumed sms number: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_to_e164 - Converting 1########## to E.164 format, country code US

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_is_invalid - testing smsnumber +1########## against regex .*

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating SMS field value: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating presumed sms number: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_to_e164 - Converting 1########## to E.164 format, country code US

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_is_invalid - testing smsnumber +1########## against regex .*

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating SMS field value: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating presumed sms number: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_to_e164 - Converting 1########## to E.164 format, country code US

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_is_invalid - testing smsnumber +1########## against regex .*

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating SMS field value: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating presumed sms number: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_to_e164 - Converting 1########## to E.164 format, country code US

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_is_invalid - testing smsnumber +1########## against regex .*

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating SMS field value: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating presumed sms number: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_to_e164 - Converting 1########## to E.164 format, country code US

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_is_invalid - testing smsnumber +1########## against regex .*

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating SMS field value: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating presumed sms number: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_to_e164 - Converting 1########## to E.164 format, country code US

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_is_invalid - testing smsnumber +1########## against regex .*

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating SMS field value: +1 (###) ###-####

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating presumed sms number: +1 (###) ###-####

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_to_e164 - Converting +1 (###) ###-#### to E.164 format, country code US

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_is_invalid - testing smsnumber +1########## against regex .*

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating SMS field value: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating presumedsms number: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_to_e164 - Converting 1########## to E.164 format, country code US

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_is_invalid - testing smsnumber +1########## against regex .*

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating SMS field value: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumbers_are_invalid - Validating presumed sms number: 1##########

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_to_e164 - Converting 1########## to E.164 format, country code US

      1 - 2017-03-28 16:58:50 - [DEBUG] - smsnumber_is_invalid - testing smsnumber +1########## against regex .*

      1 - 2017-03-28 16:58:50 - [DEBUG] - execute_alert - Performing alert actions

      1 - 2017-03-28 16:58:50 - [DEBUG] - perform_actions - Performing alert actions now

      1 - 2017-03-28 16:58:50 - [DEBUG] - perform_actions - Processing as an advanced alert

      1 - 2017-03-28 16:58:50 - [DEBUG] - find_viz_refs - Identifying content references

      1 - 2017-03-28 16:58:50 - [DEBUG] - find_viz_refs - found content ref VIZ_LINK()

      1 - 2017-03-28 16:58:50 - [DEBUG] - find_viz_refs - Returning all content references

      1 - 2017-03-28 16:58:50 - [DEBUG] - get_unique_vizdata - Start of get_unique_vizdata

      1 - 2017-03-28 16:58:50 - [DEBUG] - get_unique_vizdata - Removing duplicates

      1 - 2017-03-28 16:58:50 - [DEBUG] - get_unique_vizdata - Sorting unique rows

      1 - 2017-03-28 16:58:50 - [DEBUG] - get_unique_vizdata - Done sorting, returning the list

      MainThread - 2017-03-28 16:58:57 - [INFO] - main - Waiting on 0 worker threads.

      Currently active threads:: [<_MainThread(MainThread, started 10932)>]

      MainThread - 2017-03-28 16:58:57 - [INFO] - main - Worker threads have completed

      . Exiting

        • 1. Re: Problem with SMS Messages Test
          Matt Coles

          Sarah, thanks for the comprehensive info! I believe this is a bug with the VizAlertsDemo workbook, actually--when Jonathan wrote the SMS feature initially, he overloaded the "Email Action" field with a value of "1" indicating an email, and "2" indicating an SMS. When I incorporated his code into 2.0.0, I changed it so that SMS Actions were triggered off their own, separate fields, and "1" indicates "yes, send an SMS". In the Demo, we changed the SMS Success sheet to use the right field name, but the "2" value was left in.

           

          So the fix is to simply edit the "test.xlsx" Excel workbook, on the sheet "SMS Tests", and set all the values for SMS Action to 1. Re-publish the workbook up and it should work for you this time.

          2 of 2 people found this helpful
          • 2. Re: Problem with SMS Messages Test
            Sarah Mims

            Thank you very much, Matt! That did it. I really appreciate it!

            1 of 1 people found this helpful