Skip to content
Phone Guides

AI call data and operations with Asterisk

An AI call route can send more than audio outside the PBX. The adapter may also send transcripts, caller details, prompts and tool results. List each data item and its destination before enabling a route.

Source-reviewed, 20 October 2026. This checklist draws on current Asterisk, provider and OAIC documents. Phone Guides has not tested an Asterisk-to-AI deployment. This page does not decide which recording notice, consent, privacy or retention rules apply to a particular organisation. Get advice for the service and jurisdiction in use.

Use the dated Asterisk AI provider contract checklist to check provider versions, media limits, session lifecycle, current public prices and stated data terms. Confirm the settings on the account that will handle the calls.

Draw the data path

Record the actual route, including every component that can receive call data:

Data Questions to record
Live audio Which Asterisk channel sends it? Does it pass through an ARI application, an adapter, a carrier media gateway or a provider-direct SIP route? Which region and endpoint handle the stream?
Recording Where is the original file written? Is it sent to a transcription or summary service? Which job retries a failed upload, and who can replay the file?
Transcript and summary Which service creates it, where is it stored, and which staff or downstream system can retrieve it? Can a summary contain information not present in the caller's final answer?
Prompt and call metadata Does the adapter send a name, number, queue, account identifier, language or previous-call notes? Remove fields the task does not need.
Tool requests and results Which backend receives an agent request? Can the request read records, change them, transfer a call or trigger a payment? Where are the input and result logged?
Operational records Keep call ID, timestamps, state changes, error codes, queue depth and usage totals where needed for diagnosis. Avoid routine logs of raw audio, full transcripts, secrets or payment details.

Draw the carrier, Asterisk or FreePBX system, media adapter, AI provider, business APIs, recording store and human destination. Mark the audio, transcript, control and administration connections separately. A provider-direct SIP route and an Asterisk media bridge send call state and media through different owners; see Asterisk AI integration architecture.

Check the provider setting for the exact service

Do not transfer a data policy from one product, API or contract to another. Before a call trial, write down:

  • provider organisation and project that hold the credential;
  • model, API, SDK and adapter revision;
  • media endpoint, processing region and any third-party speech or model service;
  • current setting for data use, application-state retention, abuse monitoring and usage logs;
  • account eligibility or contract terms needed for a requested data control;
  • deletion route for recordings, transcripts, prompts, tool results, backups and provider-held data;
  • checked date and link to each provider policy.

OpenAI's API data guide treats endpoint application state, abuse-monitoring logs, regional processing and account-level controls as separate questions. Read the entry for the exact endpoint and project. Deepgram's data guide describes its Model Improvement Program, request-level opt-out and regional endpoints; its Voice Agent may also send data to a separately configured third-party model provider. Microsoft's Voice Live data guide, checked 20 October 2026, says the Voice Live API does not retain customer data after processing, while its connected services may store or process data outside Azure's compliance boundary. Optional support-case logging stores speech data in the resource's Azure region and automatically deletes it after 30 days. The model, Foundry agent and other connected services retain their own terms. These documents state each vendor's own terms. They do not show that your adapter selected a setting or that another service follows the same terms.

For Sangoma Scribe, follow the Scribe guide and distinguish its recorded-call workflow from custom live-agent processing. A control documented for a direct provider API does not automatically configure Scribe or a separate FreePBX module.

Limit access and actions

The Asterisk ARI application connects through Asterisk's HTTP server and an event WebSocket. Asterisk documents TLS/WSS and ARI user settings in its ARI configuration guide. Keep the API and media listeners on the intended network path, restrict their peers with the controls appropriate to the deployment, and do not expose a PBX administration interface to caller devices or a browser client. See Asterisk's security considerations before opening external routes.

Store provider and business-system secrets in the trusted server environment for the adapter. Keep them out of dialplan text sent to callers, browser code, URLs, recordings and diagnostic output. Use separate credentials for telephony control and business actions. Revoke and replace a credential if it appears in a log, issue report or build artifact.

Treat a spoken request or model tool call as input, not as permission. The adapter should expose only named actions required for the task. Each backend must check the caller's authority and the requested record or destination. Require a separate human step for actions that cannot be safely reversed. A prompt that says “do not transfer money” is not a backend permission check.

Set a human route and failure behavior

Choose the result for each failure before callers reach the AI route:

Condition Record the intended behavior
AI connection cannot start Keep the caller on a known route, offer a human destination or play a clear service message.
Audio stops or arrives late Stop stale playback and use the call application's fallback timer. Bound adapter queues so old replies cannot play later.
Caller interrupts the agent Stop or flush queued speech. Cancel a pending action where the provider and backend allow it; a media flush does not reverse a completed database change.
Tool call is invalid, repeated or outside its permission Reject it at the backend, record a non-sensitive reason and keep the caller on a safe path. Deduplicate requests that may be retried.
Transfer target is unavailable Return to a named queue, extension or service message. Do not leave a caller connected to silent media.
Caller hangs up or a leg disconnects Stop both media streams, close the provider session where possible, release bridge resources and ignore late events for the ended call.
Usage limit or provider outage Apply a bounded retry policy and route to the planned fallback. Do not loop between the PBX and provider.

Keep Asterisk call IDs, provider session IDs and business request IDs linked only as long as operationally needed. Decide who may join, replay or export a call. Check call recording, transfer and emergency routes independently; this checklist does not establish that a service supports a particular carrier or location.

Plan retention and incident handling

Set separate retention rules for original recordings, transcripts, summaries, prompts, tool records, diagnostic logs and backups. Remove a field from a log at source if operators do not need it. Confirm whether deletion from the primary store also reaches provider systems, replicas, exports and backups; document any limit or delay instead of promising complete deletion without evidence.

The OAIC's APP 11 guideline discusses security and, where the Privacy Act provisions apply, reasonable steps to destroy or de-identify personal information no longer needed, subject to the stated exceptions. The OAIC guide to securing personal information covers planning for third-party providers and cloud services. Use the current legislation and qualified advice to decide whether a requirement applies to your service.

Write down who can disable the AI route, who takes over calls, how provider access is revoked and which records must be kept during an incident. Exercise a test call with synthetic details. Check that the fallback works when the adapter, provider and human destination fail separately. Keep troubleshooting records useful without copying caller audio or full transcripts into shared logs.

Pre-trial checklist

  • Record the exact Asterisk branch and patch, loaded modules, FreePBX release and supported customisation point, if applicable.
  • Name the carrier path, caller endpoint, provider account/project, API/model, region and adapter revision.
  • Trace every audio, transcript, prompt, tool and log destination.
  • Confirm who can access recordings, session results, credentials and backend actions.
  • Confirm the selected data controls and current retention terms from the exact provider account.
  • Use test calls without personal details. Exercise interruption, keypad input, duplicate tool requests, timeouts, transfer, caller hangup and rollback.
  • Check provider outage, quota exhaustion, blocked tools and unavailable human routes.
  • Read the records created by the test. Confirm that log filtering, retention and deletion steps match the written plan.

Mark a deployment as tested only after recording the environment and results. A successful API connection alone does not confirm two-way audio, safe call handling, privacy settings or failure recovery.

Sources and limits

This article does not prescribe a legal notice, consent process, retention period or approved provider. Confirm those decisions for the service, account and jurisdiction in use.