09-27-2017 05:33 PM
Hello
I want to enable SMS notification for my Sponsor Portal and it's proving harder than I thought.
The SMS Provider (https://www.messagemedia.com.au/) provided me with an example URL, such as https://http-api.m4u.com.au/api/send.php?phone=$mobilenumber$&username=SMSProv_Username&password=SMSProv_Password&message$ (and I hard-code the SMSProv_Username and the SMSProv_Password into the URL) and as a test from my desktop PC I am able to send SMS's to my phone.
Now I am having a bit of a tough time translating that into an ISE configuration below. I will admit that I am not a web developer and phrases like "URL encoded portion" don't mean much to me. In the simplest case, can I take the URL that I was given, and plug that into the ISE GUI without much further config, and it should work?
The SMS Provider does mention a POST method (again, doesn't mean much to me - I wish I understood this better) - in layman's terms, why and when would I use that option? I just want to have the best option available.
And lastly, how the heck does one troubleshoot this (what log(s) can I trawl?)
When I try send SMS via Sponsor Portal I get the super useful error message "Unable to send SMS"
Solved! Go to Solution.