Hitting the DTMF injection endpoint and the gateway drops the atomic PUT request. It’s choking on the tone frequency matrix. Throws a 422 past maximum sequence length limits.
Playback timing directives seem okay. Don’t see why inter-digit pause checking fails carrier verification.
- Format the payload
- Trigger automatic channel locking
- Sync CTI monitor callbacks
Latency kills menu nav. The audit log generation fails before the DTMF injector exposes the route. Payload: {“sessionId”: “cx-9921”, “matrix”: [{“freq”: 697}], “timing”: 150}
You might want to bypass the direct injection endpoint entirely and route the sequence through a standard user telephony call instead. The reasoning breaks down step by step. First, the SCHEMA VALIDATION layer rejects any dtmfSequence exceeding twelve digits in a single atomic request. It’s a common trap we ran into during our last pipeline deployment. Second, the PAYLOAD STRUCTURE expects a flat array rather than a nested frequency matrix. Third, you’ll need to chunk the transmission to avoid tripping the RATE LIMITS on the telephony gateway.
{
"tones": ["1", "2", "3", "4", "5", "6"],
"interDigitPause": 200,
"duration": 150
}
Run a quick loop in your DevOps script to push six-digit batches to POST /api/v2/telephony/users/{userId}/dtmf. The gateway handles the stitching automatically. Just make sure your OAUTH SCOPE includes telephony:dtmf:write. The interDigitPause and duration fields also need to stay within the carrier window. The response headers will confirm the chunk accepted.