Description

This error means the destination carrier requires a pre-registered numeric sender, but the sender being used has not yet been provisioned with that carrier. This error may also occur when a newly registered sender is still undergoing carrier provisioning before it can handle production traffic.

Possible causes

  • The numeric sender has not completed carrier provisioning.
  • A US A2P 10DLC number was recently registered, and carrier provisioning for the associated campaign is still in progress.
  • The short code is not fully provisioned for production traffic, or it has been disabled by the carrier due to cancellation or compliance-related issues.
  • The destination number was recently ported to another carrier, and the carrier routing updates have not yet been completed.
  • The toll-free number is not fully provisioned for production traffic, or toll-free verification has not yet been completed and approved for messaging in the US or Canada.
  • The destination number is not provisioned to receive SMS messages.

Possible solutions

  • Confirm the sender type being used for the destination and complete any required registration or verification before sending production traffic.
  • For US A2P 10DLC numbers, verify that the Brand and Campaign registrations are complete and allow sufficient time for carrier provisioning to finish.
  • For toll-free numbers sending to the US or Canada, complete toll-free verification and wait until the number is fully verified before sending production traffic.
  • For short codes, confirm that the short code is fully provisioned and approved by the carriers for the intended messaging use case.
  • For destinations that require registered senders, ensure a compliant and properly registered Sender ID is configured for the traffic.
  • If the destination number was recently ported to a new carrier, retry once the porting process and carrier routing updates have been completed.
  • If error 30024 continues, collect at least three Message SIDs with an undelivered status and contact Support for further provisioning review.