FAQ

How can I send an SMS using the second SIM card?

To send an SMS using a non-default SIM card, you can specify the SIM card slot number in the simNumber field of request. For instance, the following request will send an SMS using the second SIM card:

curl -X POST \
    -u <username>:<password> \
    -H 'content-type: application/json' \
    https://sms.capcom.me/api/3rdparty/v1/message \
    -d '{
        "message": "Hello from SIM2",
        "phoneNumbers": ["79990001234"],
        "simNumber": 2
    }'

Does the app require power saving mode to be turned off to function without interruptions?

Local Mode

Power saving settings: No changes needed. The app uses a foreground service with a wake lock to operate, which allows it to run without power saving mode.
Battery impact: Using wake lock may lead to quicker battery drain.

Cloud Mode

Power saving settings: No changes needed. The app uses Firebase Cloud Messaging (FCM) for push notifications, which works without disabling power saving mode.
Potential delays: High message rates could lead to occasional delays when the device is in power-saving modes because of limits on high-priority FCM notifications.

Recommendations

Testing: It's advisable to test the app with and without power saving mode activated to see how it performs on your specific device and Android version.
Device manufacturers: Behavior might vary by device manufacturer.
Local + Cloud: For better responsiveness, consider running a local server alongside the cloud server connection.

How do I enable or disable delivery reports for messages?

As of version 1.3.0, you have the option to enable or disable delivery reports for each message. By default, the delivery report feature is turned on. If you prefer not to receive delivery reports, you can disable them by setting the withDeliveryReport field to false in the JSON body of your message request. Here is an example of how to send a message without requesting a delivery report:

{
  "message": "Your message text here",
  "phoneNumbers": ["79990001234", "79995556677"],
  "withDeliveryReport": false
}

How can I set up delays between sending messages?

To avoid mobile operator restrictions, we introduced a delay feature in version 1.6.0 of our application. You can set a random delay between messages by specifying a maximum delay time. The application will then randomly select a delay within this range for each message sent. This helps to reduce the likelihood of messages being flagged as spam by simulating a more human-like sending pattern.

Can I use long or non-standard phone numbers?

Yes, starting from 1.6.1 of the app, our system allows the use of long or non-standard phone numbers, which may be common with M2M (machine-to-machine) SIM cards or other special cases. To bypass the standard phone number validation, simply add the query parameter skipPhoneValidation=true to your API request. Please note that with validation disabled, you are responsible for ensuring the correctness of the phone numbers. They should still follow the E.164 format, beginning with a '+' and containing only digits.

What does the `RESULT_ERROR_LIMIT_EXCEEDED` error mean SMS?

The RESULT_ERROR_LIMIT_EXCEEDED error occurs when you've hit the sending limit imposed by your carrier or the Android operating system. This is a safeguard against spamming and typically happens if you try to send too many messages in a short period. To avoid this, try spacing out your messages or contact your carrier to inquire about their message sending limits. See also How can I set up delays between sending messages?

4.0 KiB Raw Blame History

FAQ