Pushing the latest screen recording config to mypurecloud.com.au and the Sydney edge keeps dropping the call metadata right after the ACMA consent prompt fires. Running v2024.1.0 on the platform. The agent desktop shows the recording indicator turning green, but the backend sync bombs out within twelve seconds. Console’s throwing a RECORDING_METADATA_MISMATCH error alongside a 408 Request Timeout on the /api/v2/recordings/conversations endpoint.
The flow’s pretty standard. Route group hands off to Architect, hits the Play Prompt block for compliance, then drops into the queue. Screen recording kicks off via the standard browser extension. Latency on the Sydney edge sits around 140ms during peak hours, which usually does jack all to the sync process. Today it mashed the +61 ANI formatting again. The recording file lands in S3, but the metadata JSON strips the country code completely. ACMA audit logs expect that prefix intact for every captured session. Without it, the compliance export breaks.
Tried bumping the webhook retry limits in the recording settings. Lowered the chunk size to 512KB. Still hitting the same timeout. The Architect trace shows the recording trigger firing at node rec-start-syd, but the payload never reaches the ingestion pipeline. Network traces from the Berlin office show the packets arriving, but the edge response hangs. Platform logs point to a validation step failing on the APAC endpoint. Added a custom attribute for acma_compliance_flag in the recording metadata schema. API’s returning 200 OK during the initial handshake, but the subsequent chunk upload stalls. The Sydney edge routing table shows the recording service hitting a secondary queue. DNS resolution for recording.mypurecloud.com.au takes 800ms from the Berlin jump box. Might be the geo-routing table misdirecting the APAC traffic.
{
"error": "RECORDING_SYNC_FAILED",
"code": 408,
"message": "Metadata validation timeout on syd-edge-03",
"traceId": "trc-9982-au"
}