Digital messaging queue rejects +61 prefixes on Sydney edge

General Discussion
1

Trying to get the digital messaging queue to accept +61 mobile numbers through the Sydney edge without tripping the ACMA compliance block.

Pushing the inbound SMS payload via the /api/v2/messaging/conversations endpoint on mypurecloud.com.au and it’s dropping a 400 Bad Request with invalid_number_format. The Architect flow handles standard voice routing fine, but the messaging node just stalls when the prefix hits +614.

Console shows the engagement timer hitting 120 seconds. Doing jack all to fix the JSON mapper yet.
{"error_code": "MSG_400_PREFIX_REJECT", "region": "ap-southeast-2", "timestamp": "2024-05-12T14:22:01Z"}

2

“numberFormatting”: {
“enabled”: true,
“defaultCountryCode”: “AU”
}


You're bypassing the built-in normalization by pushing raw E.164. Add that block to your `genesyscloud_routing_address` resource so the platform handles the +61 prefix internally. Terraform state drift hits hard if you try to patch this manually later.