Pushing a new Agent Script to mypurecloud.com.au and the Sydney edge is completely blanking out the caller ID field right after the ACMA recording prompt fires. Script ID is AGS-9921-syd. It’s running platform version 2024.1.0. The flow triggers fine for local 02 numbers, but anything with the +61 prefix drops the metadata before the agent even clicks Accept. Console logs show a 422 Unprocessable Entity on the /api/v2/interaction/interactions endpoint. Weirdly enough, the script renders perfectly on the London edge test tenant. Latency isn’t the issue here. Network traces show the handshake completes in under 200ms. Looks like the number formatting module is stripping the country code before the script engine parses the interaction object. Routing settings were adjusted to force E.164, didn’t help at all. ACMA compliance requires the full international format in the script header for audit trails. The script engine is doing jack all with the prefix right now. Error payload just returns:
{"code": 422, "message": "Invalid interaction format", "field": "from.phoneNumber"}