aws sns sms SENDERID何时从custom-id更改为aws的默认ID"NOTICE"? [英] When does aws sns sms SENDERID gets changed from custom-id to aws's default-id "NOTICE"?

问题描述

最近两个月以来，我一直在使用aws sns向印度电话号码发送短信.我正在使用PHP SDK进行api调用.

I am using aws sns for sending sms to Indian phone numbers since last two months.I am using PHP SDK for api calls.

我已经发送了7000多个成功消息，其中包含与我们公司名称相关的自定义senderid.但是，自最近4-5天以来，相同的客户/电话号码正在接收带有aws的默认senderid"NOTICE"的消息.

I had sent 7000+ successful messages with custom senderid relating to our company name.But since last 4-5 days same clients/phone no.s are receiving messages with aws's default senderid "NOTICE".

我正在将消息发布到某个主题以发送短信.现在，在过去的少数推送消息中，所有客户端都具有默认senderid，而在少数推送消息中，只有少数客户端具有默认id，而其他客户端则具有我的自定义ID.

I am publishing messages to a topic to send sms. Now in past few pushed messages all clients got default senderid, while in few pushed messages only few clients got default id while others got my custom id.

那么，问题出在哪里?

推荐答案

如果目标电话号码在印度，则必须注册发件人ID才能正常工作.您可以通过打开具有AWS支持的支持凭单(无需付费)来请求注册发件人ID.

If your destination phone number is in India, your Sender ID must be registered to be able to work. You can request to register a Sender ID by opening a support ticket with AWS support (which has no cost).

其他国家/地区无需注册，因此，某些交付仅需在您的发布请求中添加发件人ID值即可.

Other countries require no registration, thus, some deliveries will work by just adding a sender ID value to your publish request.

您可能会成功获取到印度目的地的有效发件人ID，具体取决于邮件到达最终用户的路线.但是，正确的做法(根据技术合作伙伴和提供商的规定)是在使用AWS之前先注册发件人ID(这就是为什么它没有在网站上标记的原因).

You might successfully get a working sender ID to an Indian destination depending on the route the message takes to reach an end user. However, the right course of action (given technology partners and provider regulations) is to register the sender ID before using it with AWS (which is why it's not marked on the website).

披露:我在AWS团队的移动消息部门工作.

Disclosure: I work at the AWS team for Mobile Messaging.

这篇关于aws sns sms SENDERID何时从custom-id更改为aws的默认ID"NOTICE"?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！