Dialler configuration

All dialler telephony configuration lives under Dialler → Configuration (not Integrations). Calls map to projects; spinners are not required for the agent desk.

Setup order

Provider — CXGear Asterisk (dev/mock bridge) or your PBX / CPaaS (Exotel, RingCentral, etc.)
Trunk — links the provider to SIP endpoints; add DIDs (caller IDs for outbound, inbound numbers for routing)
Call routes — outbound dial patterns → trunk + CLI; inbound DID patterns → agent extension
Users — assign extension (and optional trunk) under Manage users for each agent
Test — use Simulate inbound in Configuration, or dial from My leads on the agent desk

Agent desk flow

Agent toggles Online in the header (registers extension with the provider bridge)
Outbound — Dial from project leads; routing picks trunk + CLI from the project scope
Inbound — PBX or simulate-inbound rings the floating call bar
Wrap-up — after hangup, pick a 3-level disposition; call lands in Call records (CDR)

PCA handoff

Completed calls store recording_ref, talk/ring seconds, trunk, project, and hierarchical disposition — ready for Post Call Analyzer intake webhooks or scheduled pulls.

Asterisk / FreePBX (BYO)

CXGear connects directly to AMI on the customer’s Asterisk. The customer must whitelist CXGear egress IPs.

Set CXGEAR_EGRESS_IPS on the API (comma-separated public IPs of your CXGear deployment)
In Dialler → Providers → Asterisk / FreePBX, the form shows those IPs to share with the customer
Customer allows inbound TCP from those IPs to AMI (usually port 5038) and adds them to manager.conf permit=
Enter AMI host, port, username, password in the provider form
Test Connection — CXGear attempts AMI login from our servers; if it times out, AMI is not reachable / not whitelisted yet

You do not need Bridge host / Bridge API key for BYO Asterisk.

Live AMI events

After a successful provider test, CXGear uses the stored AMI credentials for call control and event streaming.