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?

Article Comments

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.


Dec, 2013 - Permalink

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

Any workaround for this issue?


Feb, 2016 - Permalink

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


Feb, 2016 - Permalink