Why Can an SMS Sending Request to an Incorrect Recipient Number Be Successful?
The Message & SMS platform does not validate recipient numbers. The successful request of calling an SMS sending API does not indicate that the SMS message is sent successfully.
The Message & SMS platform checks whether SMS messages with the same content are sent to the same recipient number. If so, the platform sends only one SMS message to the recipient number and returns the status code E200041 for other SMS messages.
After the request is successfully sent, the Message & SMS platform returns a status report within 72 hours. If the platform fails to send an SMS message to the recipient number, a status code that indicates the error cause is returned. For details, see SMS Status Error Codes.
Secondary Development FAQs
- How Do I Obtain the Application Access Key from the Message & SMS Platform?
- How Do I Obtain the HTTPS Commissioning Certificate from the Message & SMS Platform?
- How Can I Get the Channel No. Required to Send a Short Message?
- Does SMS API Calling Have PHP and Java Version Requirements?
- Why a Preset 6-Digit Verification Code Becomes a 5-Digit Verification Code After Being Sent?
- What Is the Callback Address? How Do I Set This Address?
- Does the Message & SMS Service Support Privatized Deployment?
- Can the SMS API Be Called by an Internal Network (For Example, an ECS Server)?
- Why Can an SMS Sending Request to an Incorrect Recipient Number Be Successful?
- Must the Message & SMS API Request Address Be a Domain Name? Does the Service Provide a Fixed IP Address?
- Does Message & SMS Provide SDKs?
- Is the Message & SMS Service Affected If the Region Where the Service Is Enabled Is Different from the Region Where Servers Are Located?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
