SMS失败可能是由于许多原因造成的。 CloudWatch日志中针对失败消息的provider response是什么?那将是开始调试的最佳位置。
我还将根据AWS的Pinpoint Phone Validation endpoint验证端点的有效性,以查看其是否返回有效响应。
{
"NumberValidateResponse": {
"Carrier": "ExampleCorp Mobile","City": "Seattle","CleansedPhoneNumberE164": "+12065550142","CleansedPhoneNumberNational": "2065550142","Country": "United States","CountryCodeIso2": "US","CountryCodeNumeric": "1","OriginalPhoneNumber": "+12065550142","PhoneType": "MOBILE","PhoneTypeCode": 0,"Timezone": "America/Los_Angeles","ZipCode": "98101"
}
}
SNS无法向PhoneType
VOIP,固定电话或未知地址发送消息。如果您仍然遇到问题,可以使用CloudWatch日志编辑问题。
如果存储桶策略允许SNS向S3添加对象,我将等待几天以使其反映出来。尽管成功消息会很快记录下来,但失败消息通常会重试直到其TTL过期,因此它会在S3上显示得很晚-这也与CloudWatch日志类似。
,
Cloudwatch Logs 是找出失败原因的唯一选择。
默认情况下,没有用户角色附加到 SNS,因此不记录日志!
开始记录日志
1.转到 AWS SNS 移动文本消息
2.点击编辑短信首选项
3.在交付状态记录部分创建一个新的服务角色
现在发送失败后,转到 Cloudwatch Logs 查看 json 错误响应,如下所示
{
"notification": {
"messageId": "xxxx-xxxxx-xxxxx-xxxx-xxx","timestamp": "2021-04-08 15:37:49.919"
},"delivery": {
"destination": "+xxxxxxxxxxxx","smsType": "Promotional","providerResponse": "Your account requires additional review prior to being able to send SMS messages. Please create a support ticket with an explanation of your use case. https://console.aws.amazon.com/support/cases#/create?issueType=service-limit-increase&limitType=service-code-sns-text-messaging","dwellTimeMs": 100
},"status": "FAILURE"
}
本文链接:https://www.f2er.com/3041746.html