Instructions for use SendApp

Why are messages stuck in the pending state?

Enable alternative service

You can try to enable the alternative service if your messages remain in the Pending state for a long time. You just need to open the app and click the Play button to start the service as highlighted in the screenshot below.

However, it is a good idea to follow the instructions below.

Note for phones without Android Stock

Custom battery saver devices

Some device manufacturers like Mi, Honor and others use their own battery saver app. You will need to add the SMS Gateway app to the list of exceptions in the battery saver app if your phone uses a custom battery saver. For example, you can see how I added the SMS Gateway app to the exceptions list on Redimi Note 3.

Autostart authorization

If you're using a device that doesn't have stock Android, it might have permission settings to start automatically. You need to download the latest version of the app from here . If after installation you are asked with the message “Your device is limiting the functionality of the application. Enable / add the application to the whitelist so that it can work normally ”. then it means it is throttling the app. Just hit the OK button and it will take you to the screen where you can whitelist your app.

The latest version of the app may not be able to detect the autostart permission because the app cannot be tested on all devices. If so, you should consult your device manufacturer to see if there is a setting like the one available on your device.

Xiaomi phones

If you are using Xiaomi phone, please make sure you have granted the autorun permission to SMS Gateway app as shown in the following video.

Phones with Vivo and Funtouch operating systems

If you are using the device with Funtouch OS, try the instructions shown here.

Even after following the instructions above, if the problem persists, you need to try the app on a different device. We recommend using a stock Android device or a Samsung device for the best experience. It is also preferable to use a device with 4GB or more of RAM for the best experience.

Why are my messages stuck in the Queued state?

This can happen if you don't have enough balance on your phone to send SMS. It can also happen if the app is unable to report status to the server due to a connection error.

Problems with Color OS devices

If you are using Oppo or Realme devices, the app will ask you every time you send the message. So it is not preferable to use Oppo or Realme devices to use this app.

Am I charged for sending SMS if I use this app?

This app uses your Android device to send SMS, so normal SMS costs will be charged when you send messages using this app.

How can I receive messages in the Admin Panel?

You can activate the read option received from the navigation pane within the SMS Gateway app on your Android device, as shown in the following screenshot. Any messages you receive after this will be synced with the Admin Panel.

How does the WebHook of the received message work?

The first thing you need to do is activate “Read Received” from the pop-up navigation pane. You can do this by following this guide.

You need to create a script as suggested in the WebHook Sample Script section of the API page in the admin panel and upload it to the server. Simply provide its URL in the Add Webhook form on the API page and hit the Save button. Now, whenever you get a message on your device, that script will run automatically.

Remember, you can't run the WebHook script directly. That will not work.

Here is a detailed example of how to add it.

[1] Log in to your admin panel and open the API page. The section will be called “Webhook Sample Script” as shown in the screenshot below.

[2] Copy all the text within this section. Now create a PHP file called “hook-example.php” in the root of your server and paste all the text you copied from that section into this file.

[3] Now to make it work you need to add the URL of the file we created. Log in to your Admin Panel and open your API page. You will see a section called “Add webhooks for received messages”. Just enter the URL for “hook-example.php” in the form and hit save as shown below. It is recommended that you provide a secure URL (starts with https: //) if the server URL is also a secure URL.

[4] Now you need to activate the "Read Received" from the mobile app as shown in the image if you haven't. Now, every time you receive the message on your device which is registered to the SMS Gateway account where you added this webhook, the webhook script will be called automatically.

Does this application control the delivery of messages?

Yes, this application requires a delivery report for every message you send when you activate “Request a delivery report for every message you send” as shown in the screenshot below. This change will take effect the next time you send messages.

Why is the SMS Gateway app no longer available via the Play Store?

 A policy change has been made by Google for all apps that require SMS-related permissions, as you can see from here .

I have submitted the app for review many times but they have rejected it every time. I also tried to send it with the instructional video with a demo page fully integrated with the app but they rejected the app without even watching the demo.

This does not mean that the app will stop working. The app will work normally but will no longer be available via the Play Store.

Unfortunately, this is out of my hand. I will provide update notifications via CodeCanyon.

If you don't know how to sideload apps, you can follow this guide to install the APK file.

If you have any questions, you can contact Google Play support.

Why am I getting "409 Conflict" when I try to access the SMS Gateway app on Android?

This error usually occurs due to the server blocking the app. Unfortunately, the only way to fix this error is to change your hosting. We were hosting the demo server on Namecheap Stellar Plan and it worked fine.

I cannot access the SMS Gateway web panel after installing it. What should I do?

This usually happens when the application is unable to remove the “install” folder after installation is complete. You need to remove the "install" folder to access the web panel. If you are still having trouble logging in. You can try the alternative session file. Just remove “includes / session.php” and rename “includes / session-alt.php” to “session.php”. It should now use the default file-based sessions.

The number of failed messages is high when I try to send bulk messages. What should I do?

You may get a high error rate when sending messages if you are trying to send them too fast. You can try setting a longer delay from the Profile page to decrease the number of failed messages.

Some countries have different rules for formatting the mobile number when sending messages.

This can also happen if your network operator is throttling your speed or blocking your messages.

Each network operator works differently and the network operator gives a "failed" response. It usually happens when your network operator cannot reach the mobile number. You can try to change the SIM card or use the same SIM on another device.

There is nothing you can do about it if you are still getting an unsuccessful response from the network operator after trying all the instructions given above. You can check the list of error codes shown below to get the reason for the error.

NO SERVICE Your device simply has no cellular reception. You are probably in the middle of nowhere, somewhere inside, underground or in space. Certainly far from any cell phone tower. Sometimes it also happens when you get a call while texting.
RADIO_OFF You have switched your device to airplane mode, which tells your device exactly “turn off all radios” (cellular, wifi, Bluetooth, NFC,…).
LIMIT EXCEEDED Error because the phone has reached the limit of the send queue.
GENERIC_FAILURE Something went wrong and there is no way to tell what, why or how.
GENERIC_FAILURE [1] This cause indicates that the destination requested by the Mobile Station cannot be reached because, although the number is in a valid format, it is not currently assigned (assigned).
GENERIC_FAILURE [8] This cause indicates that the Member State attempted to send a short message of mobile origin when the Member State's network operator or service provider prohibited such transactions.
GENERIC_FAILURE [10] This cause indicates that the outgoing call blocking service applies to the short message service for the called destination.
GENERIC_FAILURE [17] This cause is sent to the MS if the MSC is unable to fulfill a request generated by MS due to PLMN errors, such as problems in MAP.
GENERIC_FAILURE [21] This cause indicates that the equipment sending this cause does not want to accept this short message, although it could have accepted the short message since the equipment sending this cause is neither busy nor incompatible.
GENERIC_FAILURE [27] This cause indicates that the destination indicated by the Mobile Station cannot be reached because the interface to the destination is not working correctly. The term "not working correctly" indicates that it was not possible to deliver a warning message to the remote user; for example, physical layer or data link layer failure at the remote user, offline user equipment, etc.
GENERIC_FAILURE [28] This cause indicates that the subscriber is not registered in the PLMN (i.e. the IMSI is not known).
GENERIC_FAILURE [29] This cause indicates that the facility requested by the Mobile Station is not supported by the PLMN.
GENERIC_FAILURE [29] This cause indicates that the facility requested by the Mobile Station is not supported by the PLMN.
GENERIC_FAILURE [30] This cause indicates that the subscriber is not registered in the HLR (i.e. the IMSI or directory number is not assigned to a subscriber).
GENERIC_FAILURE [38] This cause indicates that the network is malfunctioning and that the condition is likely to last for a relatively long period of time; for example, a retry of short message transfer is likely to fail.
GENERIC_FAILURE [41] This cause indicates that the network is malfunctioning and that the condition is unlikely to last for a long period of time; for example, the Mobile Station may want to try another short message transfer attempt almost immediately.
GENERIC_FAILURE [42] This cause indicates that the Short Message service cannot be served due to high traffic.
GENERIC_FAILURE [47] Resources not available. This cause is used to report a resource unavailable event only when no other cause applies.
GENERIC_FAILURE [50] This cause indicates that the required short message service cannot be provided by the network because the user has not completed the necessary administrative arrangements with his or her support networks.
GENERIC_FAILURE [69] This cause indicates that the network is unable to provide the requested short message service.
GENERIC_FAILURE [81] This cause indicates that the equipment sending this cause has received a message with a short reference to the message that is not currently in use on the MS network interface.
GENERIC_FAILURE [95] This cause is used to report an invalid message event only when no other cause applies in the invalid message class.
GENERIC_FAILURE [96] This cause indicates that the equipment sending this cause has received a message in which a mandatory information element is missing and / or has a content error (the two cases are indistinguishable).
GENERIC_FAILURE [97] This cause indicates that the equipment sending this cause has received a message with a message type it does not even recognize because it is an undefined or defined message but not implemented by the equipment sending this cause.
GENERIC_FAILURE [98] This message is not compatible with the short message protocol status
GENERIC_FAILURE [99] This cause indicates that the equipment sending this cause has received a message that includes unrecognized information elements because the identifier of the information element is not defined or is defined but not implemented by the equipment sending the cause. However, the information element does not have to be present in the message for the equipment to send the cause to process the message.
GENERIC_FAILURE [111] This cause is used to report a protocol error event only when no other cause applies.
GENERIC_FAILURE [127] This cause indicates that there has been an interaction with a network that does not provide causes for the actions taken; therefore, the precise cause of a message being sent cannot be ascertained.
GENERIC_FAILURE [128] Telematic internetworking not supported
GENERIC_FAILURE [129] Short message type 0 not supported
GENERIC_FAILURE [130] Could not replace short message
GENERIC_FAILURE [143] TP-PID unspecified error
GENERIC_FAILURE [144] Data code scheme not supported
GENERIC_FAILURE [145] Message class not supported
GENERIC_FAILURE [159] TP-DCS error not specified
GENERIC_FAILURE [160] The command cannot be executed
GENERIC_FAILURE [161] Command not supported
GENERIC_FAILURE [175] Unspecified TP command error
GENERIC_FAILURE [176]  TPDU not supported
GENERIC_FAILURE [192] Busy SC
GENERIC_FAILURE [193] No SC subscription
GENERIC_FAILURE [194] SC System error
GENERIC_FAILURE [195] Invalid PMI address
GENERIC_FAILURE [196] SME destination prohibited
GENERIC_FAILURE [197] SM rejected-duplicated SM
GENERIC_FAILURE [198] TP-VPF not supported
GENERIC_FAILURE [199] TP-VP not supported
GENERIC_FAILURE [208] D0 SIM SMS memory full
GENERIC_FAILURE [209] No SMS storage capacity in the SIM
GENERIC_FAILURE [210] Error in MS
GENERIC_FAILURE [211] Memory capacity exceeded
GENERIC_FAILURE [212] Busy Sim Application Toolkit
GENERIC_FAILURE [213] SIM data download error
GENERIC_FAILURE [255] Cause unspecified error
GENERIC_FAILURE [300] ME Bankruptcy
GENERIC_FAILURE [301] ME SMS service reserved
GENERIC_FAILURE [302] Operation not allowed
GENERIC_FAILURE [303] Operation not supported
GENERIC_FAILURE [304] Invalid PDU mode parameter
GENERIC_FAILURE [305] Invalid text mode parameter
GENERIC_FAILURE [310] SIM not inserted
GENERIC_FAILURE [311] SIM PIN required
GENERIC_FAILURE [312] PH-SIM PIN required
GENERIC_FAILURE [313] SIM error
GENERIC_FAILURE [314] SIM busy
GENERIC_FAILURE [315] Wrong SIM
GENERIC_FAILURE [316] SIM PUK required
GENERIC_FAILURE [317] SIM PIN2 required
GENERIC_FAILURE [318] Requires SIM PUK2
GENERIC_FAILURE [320] Memory error
GENERIC_FAILURE [321] Invalid memory index
GENERIC_FAILURE [322] Full memory
GENERIC_FAILURE [330] Unknown SMSC address
GENERIC_FAILURE [331] No network service
GENERIC_FAILURE [332] Network timeout
GENERIC_FAILURE [340] No + CNMA expected
GENERIC_FAILURE [500] Unknown error
GENERIC_FAILURE [512] User interruption
GENERIC_FAILURE [513] Cannot store
GENERIC_FAILURE [514] Invalid state
GENERIC_FAILURE [515] Device busy or invalid character in string
GENERIC_FAILURE [516] Invalid length
GENERIC_FAILURE [517] Invalid character in PDU
GENERIC_FAILURE [518] Invalid parameter
GENERIC_FAILURE [519] Invalid length or character
GENERIC_FAILURE [520] Invalid character in the text
GENERIC_FAILURE [521] Timer expired
GENERIC_FAILURE [522] Temporary operation not allowed
GENERIC_FAILURE [532] SIM not ready
GENERIC_FAILURE [534] Unknown cellular transmission error
GENERIC_FAILURE [535] Busy protocol stack
GENERIC_FAILURE [538] Invalid parameter
UNKNOWN ERROR [*] Something went wrong and there is no way to tell what, why or how.

I am getting error 500 while loading the Excel file. What should I do?

Make sure the following requirements are met to upload the Excel file.

If you are uploading a large Excel file with thousands of messages.