AI
VOICE OPERATIONSTechnical decision document

Production blueprint · 10-channel reference design

AI Call Center
Technical Setup & Cost Plan

A decision-ready blueprint for a FreePBX/Asterisk call center using UZTELECOM SIP channels, Gemini Live voice AI, CRM integration and optional human agents on MicroSIP.

Prepared 12 August 2026 Currency: UZS + USD USD/UZS: 11,889.95 Pricing must be revalidated before purchase
Measured Gemini spend
3.84m UZS
$323.02 for 2,845 Live events in the audited 30-day production ledger.
Average AI cost
1,350 UZS
$0.1135 per event at 63.3 seconds average; not a carrier-minute charge.
Reference capacity
10 calls
Ten SIP channels mean roughly ten simultaneous public-network calls.
Software licences
0 UZS
Core FreePBX and MicroSIP are free; API usage, carrier service and support are not.
01

The short answer

What is actually required, and which commonly listed items are conditional.

Decision summary
AI-only operation

AI calls do not need a PC, headset or MicroSIP per call

The AI session runs on the gateway server. Buy operator stations only for supervisors, transfers, callbacks or a human queue.

Telephony capacity

Numbers, extensions and SIP channels are different

A DID is the public number. An extension identifies an internal endpoint. A SIP channel is one simultaneous external call.

Compute

No GPU is required

Gemini performs inference in the cloud. Spend on reliable CPU, RAM, SSD, networking, UPS, backup and operations—not a gaming GPU.

Bottom line.

For the audited traffic level, the measured Gemini bill was about 3.84 million UZS/month. A realistic greenfield 10-channel, 5-human-seat installation is roughly 77–162 million UZS in hardware and commissioning, plus 80–250 million UZS if the AI gateway, CRM tools, QA and production hardening must be engineered from scratch. Existing servers, PCs and the existing YangiAsrDialer code can reduce the initial cost substantially.

02

Reference architecture

One controlled path for telephony; one auditable path for data, leads and recordings.

10-channel design
AI call center reference architecture Public phone network connects through UZTELECOM SIP trunk, firewall and FreePBX to the AI gateway and Gemini Live, with CRM, storage, monitoring and optional human agents. Public callersPSTN / mobile network UZTELECOMDID numbers + SIP trunk10 concurrent channels Network edgeFirewall · QoS · VLANPrimary + backup WAN FreePBX / AsteriskPJSIP · queues · IVRrouting · recording · CDRconcurrency guard AI gatewayAudio bridge · sessionstools · retries · metering Gemini Live APIPaid project · quotasaudio-to-audio sessions Human agent queueMicroSIP + USB headsetor IP desk phone CRM & consentlead state · opt-in/out · owner Recordings & backupretention · restore · encryption Facts & QAapproved KB · native-Uzbek tests Monitoringhealth · spend · SIP · alerts
Voice/AI servicesCarrier boundaryNetwork controlExternal AI providerData/operations plane
03

Complete requirements list

A practical bill of materials for ten concurrent calls and up to five human seats.

Buy only what the design needs
PriorityComponentReference quantityMinimum / target specificationBudget allowanceDecision note
RequiredUZTELECOM business SIP trunk10 channelsPJSIP/SIP peer; G.711 A-law; DTMF RFC4733; defined RTP range; inbound/outbound CLI; CDR and provider SLA.Carrier quoteChannel count sets the simultaneous public-call ceiling.
RequiredPublic DID/IP phone numbers1–3+One main number; optional campaign/branch DIDs; documented number format and inbound routing.Carrier quoteA number does not automatically add capacity.
RequiredPrimary business connectivity1100 Mbps+; stable routing to carrier and Google; static/public or private routed IP as contracted; low jitter and packet loss.0.5–1.5m UZS/moConfirm whether the SIP trunk arrives over a private interface or public Internet.
RecommendedBackup Internet / carrier path1Different provider and physical route; 50 Mbps+; tested failover that does not break SIP source-IP rules.0.3–1.0m UZS/moInternet failover is not SIP failover unless the carrier supports the alternate IP.
RequiredRouter / firewall1Dual-WAN, VLAN, QoS, VPN, stateful firewall, logs; RB5009-class or equivalent.3–6m UZSNever expose FreePBX GUI, AMI, ARI or SSH broadly to the Internet.
RecommendedManaged switch + cabling116/24 Gigabit ports; voice/server VLANs; PoE only if buying IP phones; labeled Cat6 runs.2–7m UZSMicroSIP on PCs does not require a PoE switch.
RequiredPBX / AI gateway server18 CPU cores, 32 GB RAM, 2 × enterprise SSD in mirror, dual NIC, hardware health reporting, 3-year warranty.18–35m UZSNo GPU. Separate PBX and gateway VMs or hosts are preferable for failure isolation.
RecommendedBackup / recording storage14 TB usable with snapshots; encrypted backup; restore test; retention automation.5–15m UZSMixed mono WAV is roughly 58 MB per connected hour; confirm the actual codec and recording format.
RequiredUPS1–2At least 1500 VA for the small stack; online UPS preferred for server + network; graceful shutdown testing.1.2–6m UZSLocal examples ↗
RequiredFreePBX + Asterisk1 systemGreenfield: current supported FreePBX 17/Debian 12 and supported Asterisk release; backups, firewall and update policy.Core: freeOfficial install path ↗
RequiredAI voice gateway1 service poolAudio bridge, resampling, session lifecycle, reconnect deadline, tool allowlist, concurrency cap, stable call ID, metering and fallback.Custom engineeringThe existing YangiAsrDialer gateway is relevant, but production drift must be resolved before reuse.
RequiredGemini paid API project1+Billing-enabled project, production quota, spend cap, alerts, separate test/prod keys, restricted secret access.Usage basedOfficial pricing ↗
RequiredCRM + consent/opt-out registry1Lead ownership, source, consent evidence, do-not-call state, idempotent updates, retry/reconciliation queue.Existing or customNo outbound promotional call should bypass the consent check.
RecommendedMonitoring and alerting1 stackSIP registration/OPTIONS, call completion, silent-call detector, worker health, disk, queue depth, Gemini spend, CRM failures.0.2–1.0m UZS/moAlerts need a named on-call owner and documented action.
ConditionalOperator PCPer human seatCore i5/Ryzen 5 class, 16 GB RAM, 512 GB SSD, wired Ethernet. Existing office PCs often suffice.5.5–9m UZS7.03m example ↗
ConditionalUSB headsetPer human seatWired USB, boom microphone, replaceable ear pads, acoustic shock protection; noise rejection preferred.0.5–1.8m UZS771k example ↗
ConditionalMicroSIP softphonePer human PCIndividual PJSIP extension, strong random secret, correct codec/DTMF, auto-answer disabled unless operationally required.Free / GPLv2Licence source ↗
AlternativeIP desk phonePer human seatUse instead of MicroSIP + USB headset where a dedicated appliance is preferred.1–3m UZSDo not buy both for every seat unless there is a stated fallback requirement.

What else is needed beyond the shopping list?

  • Carrier technical sheet: peer IPs, SIP/RTP ports, codecs, DTMF, number format, CLI policy, failover, rate limits and support SLA.
  • Approved knowledge source with owner, validity dates and facts the AI is prohibited from guessing.
  • Human-transfer route, queue hours, fallback greeting and after-call follow-up ownership.
  • Call-ID correlation across Asterisk, gateway, CRM, recording, QA and billing.
  • Staging environment, test DIDs, synthetic audio set, native-Uzbek evaluation and canary rollout.
  • Retention schedule, access controls, backup/restore procedure and incident response.

What is usually unnecessary?

  • A GPU for Gemini Live inference.
  • A public IP for every MicroSIP or IP phone.
  • FXO/FXS or E1 cards when the carrier supplies a pure SIP trunk.
  • A computer, headset or softphone for every simultaneous AI call.
  • Commercial FreePBX modules unless a named feature and support need justifies them.
  • Exposing PBX management or SIP endpoints directly to the public Internet.
04

Capacity and performance sizing

Size from simultaneous calls and connected minutes—not from the number of leads in the CRM.

Engineering targets
10 SIP channelsMaximum of roughly ten simultaneous carrier calls. Keep one or two channels reserved for transfers or urgent inbound traffic if needed.
12 AI session slotsTen active plus headroom. Benchmark the actual gateway/SDK and apply a hard admission limit—do not rely on optimistic process counts.
20 Mbps reservedConservative budget for ten AI calls including PCM/WebSocket overhead. Use 100 Mbps+ access so voice is not competing at the edge.
<20 ms jitterOperational target; packet loss <0.5% and stable latency matter more than headline bandwidth. Monitor both SIP and Gemini paths.
ScaleSIP channelsAI concurrency capServer targetInternet targetHuman seatsDesign note
Pilot2–42–34 cores / 16 GB / mirrored SSD50 Mbps1–2Staff and opted-in canary traffic only.
Small production108–108 cores / 32 GB / mirrored SSD100 Mbps + backup0–5Reference design in this document.
Growth20–3018–28Separate PBX/gateway; 12–16 cores total; 64 GB200 Mbps + backup5–15Introduce HA, second carrier path and load/failure testing.
Large / regulated50+ValidatedRedundant nodes, replicated state, SBC, dedicated storageDual diverse linksAs requiredCarrier, quota, privacy and DR design become formal workstreams.
05

Cost model

Measured AI usage is separated from carrier quotes, hardware allowances and operational staffing.

USD/UZS 11,889.95
Gemini price floor vs. real call cost.

Gemini 3.1 Flash Live lists audio input at $0.005/min and audio output at $0.018/min. That is a simple audio-only ceiling of $0.023 when both directions each consume a full modality minute, but Live also bills the active text/audio context again on later turns. The audited production average was materially higher: $0.1135 per 63.3-second event, or about $0.1076 per connected minute.

Interactive monthly operating-cost estimator

Gemini estimate
Carrier minutes *
SIP channel fixed fee **
Fixed operations
Estimated monthly total incl. contingency

* Planning placeholder: replace with the signed UZTELECOM outbound tariff. ** Historical reference only: 16,840 UZS/channel/month is from UZTELECOM’s public price sheet effective 2018 for a 10-channel group; it is not confirmed as the 2026 contract rate.

Measured production baseline

Read-only 30-day ledger audited 11 August 2026

Live events2,845
Average duration63.3 sec
Gemini ledger cost$323.02
At 12 Aug CBU rate3,840,692 UZS
Average / event$0.1135 · 1,350 UZS
Inbound / outbound avg$0.1318 / $0.0586

Gemini volume scenarios

Scaled at the historical $0.1135 average/event

5,000 events$567.50 · 6.75m UZS
10,000 events$1,135 · 13.50m UZS
30,000 events$3,405 · 40.49m UZS
Carrier call minutesAdditional
Human salariesAdditional
Tax / FX / quota changesRevalidate

Indicative one-time investment

One-time itemLowHighIncluded assumptionEvidence quality
PBX / AI server18m35m8 cores, 32 GB, mirrored enterprise SSD, dual NIC, warrantyBudget quote
Backup / recording storage5m15m4 TB usable, snapshots and backup mediaBudget quote
Firewall, switch and cabling5m13mDual-WAN router, managed switch, Cat6, patchingBudget quote
UPS / power protection1.2m6mLine-interactive floor to small online-UPS configurationMarket range
Five human seats32.5m52.5mFive PCs and five USB headsets; omit if AI-only or reuse existing PCsMarket range
Installation, testing and documentation15m40mNetwork/PBX build, carrier testing, backup, monitoring and handoverService quote
Hardware + commissioning subtotal76.7m161.5mGreenfield 10-channel / 5-seat setupIndicative
Custom AI/CRM/QA engineering80m250mOnly if building the gateway, tools, dashboards, QA and hardening from scratchScope quote
Greenfield total156.7m411.5mBefore carrier deposits, VAT differences and ongoing operationsIndicative

All equipment and engineering values are planning allowances, not offers. Obtain at least two written supplier quotes with warranty, VAT, stock status and delivery included.

06

UZTELECOM order checklist

Ask for one signed commercial annex and one technical annex. Do not accept an informal channel count.

Call 1155 for corporate service

Commercial questions

  • One-time trunk connection charge and deposit.
  • Monthly price per channel at 10, 20 and 30 channels.
  • Monthly DID/number fee and cost of additional numbers.
  • Outbound local, mobile, intercity and international per-minute rates.
  • Billing increment, minimum charge and whether unanswered calls are billed.
  • Caller-ID presentation rights for each DID and campaign.
  • SLA, fault escalation contacts, service hours and restoration target.

Technical questions

  • Carrier signaling and media IPs; customer peer IP(s); static routes and interface.
  • SIP transport/port, RTP port range, G.711 A-law, DTMF and fax policy.
  • Authentication method: IP peer, registration or mutual TLS.
  • Inbound number format and outbound presentation format (+998/E.164 or national).
  • OPTIONS/keepalive interval, session timers and maximum CPS.
  • Failover to a second customer IP and carrier SBC redundancy.
  • Test plan: 100 inbound attempts, parallel calls, cause codes and packet capture window.
Important pricing limitation.

The only detailed public SIP-trunk price sheet found on the official UZTELECOM domain is effective from 1 February 2018. It lists a 93,600 UZS one-time access charge and 16,840 UZS per channel/month for a ten-channel group, with lower unit rates at larger groups. Treat this only as a historical reference. The signed 2026 carrier quote controls the budget.

07

Implementation sequence

Build a testable system in layers. Carrier, PBX, AI and CRM each get their own acceptance gate.

No production big-bang

Contract & policy

Approve purpose, consent evidence, recording notice, retention, DIDs, channel count, call windows and named owners. Obtain carrier annexes and Gemini paid project.

Network & power

Install VLANs, firewall, static routes, QoS, UPS, NTP and management VPN. Prove primary and backup Internet behavior before telephony.

PBX foundation

Install supported FreePBX/Asterisk, PJSIP trunk, DIDs, inbound routes, queues, recordings, CDR, backups and least-privilege management.

Human endpoints

Create individual extensions, configure MicroSIP or IP phones, test transfers/queues, and prohibit shared secrets. Confirm wired audio and headset levels.

AI gateway

Bridge call audio to Gemini, enforce concurrency, deadlines and cleanup, meter every session, correlate one stable call ID and add a safe fallback route.

CRM & facts

Connect consent/opt-out checks, lead writes and reconciliation. Generate scenario knowledge from an owner-approved, versioned fact manifest.

Failure testing

Test silence, packet loss, Gemini disconnect, carrier timeout, CRM failure, disk full, worker crash, long calls, repeated calls and human transfer.

Canary & scale

Run staff calls, then an opted-in 5% canary. Expand only when quality, cost, privacy, carrier delivery and rollback gates remain green.

Greenfield version choice is not an upgrade instruction.

FreePBX currently directs new installations to FreePBX 17 on Debian 12, and its March 2026 guidance calls Asterisk 22 the preferred current long-running choice. The audited production system used Asterisk 18. Migrate in parallel with rollback; do not in-place upgrade the active PBX simply to match this document.

08

Security, privacy and legal gates

These are launch requirements, not documentation to add after go-live.

Owner + counsel review
Marketing consent

Uzbekistan’s Advertising Law Article 30 allows advertising through telecommunications services only with the subscriber’s prior consent. Store evidence and enforce opt-out centrally.

AI and recording notice

Open with the organization, the AI identity and a clear recording/data notice approved by counsel. Provide a human route where the use case requires it.

Personal-data basis

Document processing purpose, fields, owner/operator, access, retention, deletion, subject requests and any cross-border transfer basis.

Uzbekistan storage rules

The Personal Data Law was amended in 2026. Certain categories must stay in Uzbekistan; other data may be stored abroad only under stated conditions. Obtain a written legal classification for call audio/transcripts sent to Gemini.

Gemini data controls

Use a billing-enabled paid project. Google says paid prompts/responses are not used to improve products; ZDR requires approval and avoiding session resumption, which creates a reliability trade-off.

Network least privilege

Allow SIP/RTP only from carrier peers, manage via VPN, restrict API keys by project/service account, remove phone numbers from filenames and use per-service filesystem permissions.

Retention and deletion

Set separate periods for recordings, transcripts, CDR, CRM leads, debug logs and QA files. Backups must inherit expiry and access restrictions.

Secrets and audit

Keep secrets out of code and operator PCs; rotate them; log access and changes; maintain reproducible deployment source, version hashes and rollback packages.

Factual control

Prices, dates, admission facts and promises need an owner, source, validity window and “do not quote” state. The model must say it does not know instead of inventing.

This section is an engineering checklist, not legal advice. Uzbekistan law and the exact controller/operator role must be reviewed for the organization’s actual flows.

09

Go-live acceptance criteria

No item below should be “assumed working.” Capture evidence and an owner for each result.

Release gate
AreaAcceptance testPass criterionEvidence
Carrier delivery100 timed inbound attempts across each DID and busy-hour route.No unexplained missing INVITEs; every failure has carrier/Asterisk cause evidence.Caller log + pcap + CDR
Concurrency1, 5 and 10 simultaneous calls; hold for 60 minutes; include transfers.No rejected call below the cap, silent audio, CPU runaway or leaked channel/session.Asterisk channels + gateway metrics
Audio qualityNative-Uzbek callers, male/female voices, echo, noise, interruption and digits/names.Intelligible both directions; no repeated missing audio; approved pronunciation/number accuracy.Blind review scorecard
LatencyMeasure answer-to-greeting, end-of-speech to first audio, and tool-call waits.Targets approved by operations; p95 regressions block release.Per-call timestamps
FactsAdversarial questions for price, date, branch, discount and unknown data.No invented value; verified fact hash recorded; unknown facts fail closed.Golden test set
CRM / leadsSuccess, timeout, malformed response, duplicate callback and retry.Deterministic final state; no “success” on error; reconciliation clears every pending item.State ledger + CRM record
Human handoffAvailable, busy, closed and abandoned transfer paths.Caller always receives a clear outcome; context reaches the human without over-sharing.Queue/CDR + agent review
CostCompare per-modality API usage with the local meter for a canary batch.Difference within 5% or explained; project spend cap and alerts proven.API bill + local ledger
PrivacyConsent denied, deletion request, unauthorized lookup and access review.Call blocked/limited as designed; least-privilege access; request handled within approved procedure.Audit log + ticket
RecoveryGateway crash, Gemini disconnect, PBX restart in staging, WAN failure and restore.Bounded fallback; no 35-hour wedge; tested restore and written rollback time.Incident drill report
10

Sources and verification notes

Primary sources are used for product pricing, software status, exchange rate and legal text. Local equipment ranges remain estimates.

Checked 12 Aug 2026
Confidence labels.

Verified: official vendor/law/exchange source or internal measured ledger. Historical: an official source whose effective date is old. Estimate: planning allowance that needs a current written quote. Do not use this document as a purchase order.