Caveats
3CX controls the PBX
Section titled “3CX controls the PBX”TracsConnect does not manage 3CX users, extensions, call queues, routing, SIP trunks, departments, roles, or licensing. Keep those settings in 3CX.
API keys are shown once
Section titled “API keys are shown once”3CX shows the API key when the client application is created. If it is lost before saving 3CX in TracsConnect, create a new 3CX API client or rotate the key in 3CX.
License and role requirements matter
Section titled “License and role requirements matter”3CX restricts Configuration API access by edition, role, and service-principal settings. If the connection test fails even though the secret is correct, review the 3CX edition, department, role, and enabled API access.
Callback secrets are shown once
Section titled “Callback secrets are shown once”TracsConnect generates separate secrets for CRM callbacks and CDR ingest. Store them with the 3CX CRM template or CDR receiver settings before leaving the setup window.
CDR ingest may need a bridge
Section titled “CDR ingest may need a bridge”3CX’s native CDR feature writes records to files or sends them over TCP sockets. TracsConnect stores CDR records when a compatible CDR receiver or bridge sends those records to the generated TracsConnect CDR value.
Do not enable CDR ingest until you know how those records will reach TracsConnect.
Windows toasts are opt-in
Section titled “Windows toasts are opt-in”Windows toasts are off by default. Turn them on only for shops that want OS-level notifications on registered Client Monitor workstations.
Start with one shop
Section titled “Start with one shop”3CX setup touches phone-system behavior. Start with one shop, test with known calls, and expand only after lookup and journaling behave as expected.