What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

SMS Delivery configuration issue

Votes:

0

Your Vote:

Up

Down

I am trying to configure PRTG to send SMS notification and encountered the following issue:

1. My local bulk SMS provider is not in the list of supported providers in PRTG

2. Custom URL from my provider is as follow http://<username>:<password>@<sms provider ip>/cgi-bin/smsapi/send_sms.pl?&apikey=xxxxxx&msisdn=%SMSNUMBER&message=%SMSTEXT

It looks like PRTG's Custom URL can not handle the http://<username>:<password>@<server>...

On the other hand, Custom URL does not provide the field for me to define Username and Password (like in the supported list of providers).

Is there any work around for solve my problem?

sms-notification sms-provider system-administration

Created on Dec 30, 2013 7:43:57 AM by  sardjono (0) 1

Last change on Jun 22, 2015 8:15:27 AM by  Luciano Lingnau [Paessler]



3 Replies

Votes:

0

Your Vote:

Up

Down

Hello,

thank you very much for your KB-Post. It's correct, URLs in the format:

w http://<username>:<password>@<sms provider ip>...

To include username & password in the Custom URL though simply add them as parameters to the HTTP request (if the provider does support this of course):

http://<sms_provider>?MESSAGE=message&RECIPIENT=phonenumber&USERNAME=myuser&PASSWORD=mypassword

Otherwise maybe you can use a script notification, that then performs the HTTP request in the format, that is not supported by PRTG. best regards.

Created on Dec 30, 2013 11:43:15 AM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

This is seriously problematic as our provider only supports basic auth (not supported in the parameters).

Any workaround for this issue?

Created on Feb 4, 2016 8:16:53 PM by  Jonathan Senecal (0)



Votes:

0

Your Vote:

Up

Down

Jonathan, the only work around would be a script based solution running as a script notification then.

Created on Feb 5, 2016 8:42:12 AM by  Torsten Lindner [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.