Problem:
Current APIv2 allows sending TTS calls (/calls/tts_advanced) but provides no status endpoint. Alarm systems cannot determine if a call was answered.
Required Enhancements:
Status endpoint for TTS calls (GET /calls/tts/status/{id})
Return: status (answered/no_answer/busy/failed), answer (0/1), duration
Increase max ring duration from 30 to at least 90 seconds
Allows reaching voicemail (requires 45-60 sec.)
Parameter disable_voicemail (boolean)
Prevents voicemail forwarding for alarms
Parameter retry_on_no_answer with max_retries and retry_interval
Automatic retry when call is not answered
Webhook for TTS events (call.tts.completed)
Why?
For critical alerting (server down, AD-based escalation), knowing whether a call was answered is essential. Currently, complex external scripts are required as workarounds.

Migrated from the SMSEagle UserReport forum (2026-05-27). Legacy status: Being considered.