AWS sms-voice documentation change
Summary
Updated RCS country launch requirements: 1) Added compliance guide reference 2) Made screen recordings mandatory for both US and Canada launches 3) Added detailed video requirements links 4) Replaced denial reasons table with external reference 5) Updated section titles
Security assessment
The changes focus on compliance and procedural requirements for RCS messaging launches. There's no evidence of addressing security vulnerabilities, patching weaknesses, or incident response. The updates relate to carrier approval processes, documentation links, and screen recording requirements without security context.
Diff
diff --git a/sms-voice/latest/userguide/rcs-country-launch.md b/sms-voice/latest/userguide/rcs-country-launch.md index c50e5efb4..9ec03045f 100644 --- a//sms-voice/latest/userguide/rcs-country-launch.md +++ b//sms-voice/latest/userguide/rcs-country-launch.md @@ -40,0 +41,2 @@ For an overview of how the AWS RCS Agent relates to RCS for Business IDs, see [W + * [RCS country launch compliance guide](./rcs-country-launch-compliance.html) + @@ -76 +78 @@ The US launch registration requires the following information: - * **Screen recording** — You must provide a screen recording that demonstrates your RCS messaging experience. The recording should show the end-user experience of receiving and interacting with your RCS messages. This is a requirement specific to the US launch. + * **Screen recording** — You must provide a screen recording that demonstrates your RCS messaging experience. The recording should show the end-user experience of receiving and interacting with your RCS messages. For detailed video requirements, see [Launch video requirements](./rcs-compliance-video.html). @@ -85 +87 @@ The US launch registration requires the following information: -The screen recording requirement is specific to the US launch registration. You must provide a recording that clearly demonstrates your RCS messaging use case. Registrations submitted without a valid screen recording are rejected. +Both the US and Canada launch registrations require a screen recording. You must provide a recording that clearly demonstrates your RCS messaging use case. Registrations submitted without a valid screen recording are rejected. For detailed requirements, see [Launch video requirements](./rcs-compliance-video.html). @@ -98,0 +101,2 @@ The Canada launch registration requires the following information: + * **Screen recording** — You must provide a screen recording that demonstrates your RCS messaging experience. For detailed video requirements, see [Launch video requirements](./rcs-compliance-video.html). + @@ -106 +110 @@ The Canada launch registration requires the following information: -The Canada launch registration does not require a screen recording. The form field requirements differ from the US launch registration. Review the registration form carefully to ensure all required fields are completed for the Canadian market. +The Canada launch registration form field requirements differ from the US launch registration. A screen recording is required for both countries. Review the registration form carefully to ensure all required fields are completed for the Canadian market. @@ -292 +296 @@ To help ensure a smooth approval process: - * For US launches, provide a clear and complete screen recording that demonstrates your RCS messaging use case. + * Provide a clear and complete screen recording that demonstrates your RCS messaging use case. See [Launch video requirements](./rcs-compliance-video.html). @@ -303 +307 @@ To help ensure a smooth approval process: -The following sections describe common issues that you might encounter during the country launch registration process and how to resolve them. +The following sections describe common issues that you might encounter during the country launch registration process and how to resolve them. For detailed compliance requirements and how to avoid denials, see [RCS country launch compliance guide](./rcs-country-launch-compliance.html). @@ -311 +315 @@ If your registration enters the REQUIRES_UPDATES state, review the feedback prov - * Missing or invalid screen recording (US launches only). + * Missing or invalid screen recording. @@ -352,16 +356 @@ Carrier approval timelines for the United States and Canada are typically severa -When a registration is denied, AWS End User Messaging provides a denial reason that explains why the registration was not approved. The following table lists all RCS registration denial reasons and the recommended action for each. - -RCS registration denial reasons Denial reason | Description | Recommended action ----|---|--- -`REQUIRES_OFFLINE_REVIEW` | This registration requires manual offline review. | Create a support case in the AWS Support Center. Choose the RCS Agent assistance category and include your registration ID. See [Get more information through Support for registration issues](./registrations-request-support.html). -`CANNOT_UPDATE_REGISTRATION` | Certain RCS agent fields cannot be modified on an existing registration. | Create a new testing registration with the corrected fields. -`IMAGE_URL_INACCESSIBLE` | The image URL provided is not publicly accessible. | Provide a URL that can be accessed without authentication. Update the registration and resubmit. -`IMAGE_FORMAT_INVALID` | The image must be in JPEG or PNG format. | Upload an image in the correct format and resubmit. -`IMAGE_RESOLUTION_INVALID` | The image does not meet the required resolution. The logo must be 224 x 224 pixels and the banner must be 1440 x 448 pixels. | Resize the image to the required dimensions and resubmit. -`IMAGE_SIZE_EXCEEDED` | The image file size exceeds the allowed limit. The logo must not exceed 50 KB and the banner must not exceed 200 KB. | Reduce the file size and resubmit. -`ACCENT_COLOR_CONTRAST_INSUFFICIENT` | The accent color must have a contrast ratio of at least 4.5:1 relative to white. | Choose a darker accent color that meets the contrast requirement and resubmit. -`PRIVACY_POLICY_INACCESSIBLE` | The privacy policy URL provided is inaccessible or invalid. | Provide a publicly accessible privacy policy URL and resubmit. -`TERMS_AND_CONDITIONS_INACCESSIBLE` | The terms and conditions URL provided is inaccessible or invalid. | Provide a publicly accessible terms and conditions URL and resubmit. -`CONTACT_DETAILS_MISSING` | At least one contact method (phone, email, or website) is required in the agent profile, and each contact value must have a corresponding label. | Add at least one contact method to your agent profile. Ensure each contact value has a corresponding label (for example, if you provide a phone number, also provide a phone label). Update the registration and resubmit. - -For denial reasons that require AWS Support assistance, create a support case in the [AWS Support Center](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase). Include your AWS RCS Agent ID and registration ID in the case description. +When a registration is denied, AWS End User Messaging provides a denial reason code that explains why the registration was not approved. For the complete list of denial reason codes with descriptions and recommended actions, see [RCS registration denial reasons](./rcs-compliance-denial-reasons.html). @@ -377 +366 @@ Receiving inbound RCS messages -RCS CloudWatch metrics and monitoring +RCS country launch compliance guide