Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I have built an SMS portal. What you describe was also experienced in v1.0 of my application. The solution was to have my SMS gateway provide me with Bulk SMS access via HTTP. I could put up to 1000 destinations into an XML (or comma delimited) package and send to the Bulk SMS Gateway. Because I run on a shared host, I limited this to 500 destinations. </p> <p>I have a cache/temporary storage/table where I batch large destination (up to 1,000,000) in some cases and a scheduler (timer based) sends each batch of 500 every few seconds (by calling a script repeatedly) until the messages are sent. Works like charm! </p> <p>For personalized messages, I encourage the client to use my desktop application for personalization before forwarding to my SMS portal. Good luck</p> <p><strong>PROCESS:</strong></p> <p>You'll need three items</p> <ol> <li>The Script that receives the SendSMS request</li> <li>The script that sends the SMS</li> <li>The Scheduler/Timer (Script/Host Service)</li> </ol> <p>A. The Send SMS request arrives with</p> <pre><code>a. The Message and Sender ID/ Sender GSM Number. b. The Destinations (as a comma delimited list). We'll assume 10,000 destinations </code></pre> <p>B. Split the destinations into 500 (any size you wish) and log the 500 destinations along with the message and SenderID in each INBOX row/record. <strong><em>Note: if you count 500 out by looping (10,000 loops), the script could Time out. GSM Numbers in My country are 13 digits. So I do a loop Sub String of length 500</em>(13+1) to get 500 destinations per batch (20 loops).*</strong></p> <p>C. Call the Script that Sends the SMS. Sends the first 500 and tag the message as Sent. You can add Time Sent. Start the Scheduler</p> <p>D. The Scheduler checks every 1.5 minutes if any unsent messages exist in the INBOX and sends it. If nothing, Scheduler Stops. So, 10,000 messages are sent within 30 mintues</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload