Endpoint observed
PBX registration, OPTIONS, transport and codec prerequisites, tied to fresh observations.
PRE-CALL READINESS / THE CENTRAL PRINCIPLE
Can it actually
make the call?
The question to answer before wasting a human's time or consuming a paid attempt. Check the route first, report what was observed, and never confuse a reachable PBX with a guaranteed completed call.
FROM NATIVE DIAL-TONE
Qualify first.
Then commit.
The Windows Dial-Tone project improved its MicroSIP roots by giving operators a pre-call qualification check, an audible local dial tone when checks succeed, and detailed Call Trace reporting. That experience shapes the AI version: a bot should receive structured readiness evidence rather than an unexplained green light.
For a bot, audible feedback becomes machine-readable evidence. An isolated echo or tone test can test the local audio path without calling a person. The production design must link each observation to its authenticated PBX source and permitted route.
WHAT A PREFLIGHT CAN SUPPORT
- Account registration and configured PJSIP endpoint state
- Recent authenticated SIP OPTIONS response and latency
- TLS certificate and mandatory SRTP/DTLS-SRTP policy
- Approved route class, codec and audio-path prerequisites
- Internal tone/echo media on an isolated, non-human test destination
WHAT IT CANNOT PROMISE
- That the selected carrier route will accept the INVITE
- That the destination will ring, answer or be a real person
- That remote audio or dialogue will be intelligible
- That a booking or task will actually be completed
- That a previously valid route cannot change before origination
A STRUCTURED RESPONSE, NOT A GUESS
Readiness has
levels of evidence.
Local endpoint and network checks happen before a live call. Real carrier delivery, two-way media and the recipient's response become known only later. These statuses are a design proposal, not a deployed hosted API.
Permitted path candidate
Destination class and route permissions checked by an operator-controlled policy.
Non-human media proof
An isolated tone/echo test may provide measured audio feedback without calling a person.
Observed call outcome
Actual answer, RTP evidence and hangup are recorded only once a real connection is attempted.
Important: 0.0.1 does not implement all these gates. The BYOT connector currently has a read-only ARI endpoint-state check; the Windows-native readiness implementation has not been ported or independently validated on Asterisk.
THE DESIGN QUESTION
No unnecessary
human interruption.
Test the internal path using non-human destinations first. If registration, qualification or routing policy is uncertain, block the attempt and give the bot a specific, actionable reason rather than a fictional success.