Configure VoIP / PBX
Goal
Connect your Issabel PBX system to Nexus for click-to-call, CDR sync, and call analytics.
Preconditions
- You have an Issabel PBX system (or compatible Asterisk-based PBX) accessible via API.
- An n8n instance is running and reachable from both PBX and Nexus.
- You are an owner or admin of the Nexus organization.
Steps
- Configure PBX settings — Navigate to Settings → PBX and enter:
- PBX API URL (e.g.,
https://your-pbx-domain/api) - API credentials
- Default extension prefix
- PBX API URL (e.g.,
- Map user extensions — In Settings → PBX → Extensions:
- Assign each team member their PBX extension number.
- The
pbx-extensionsEdge Function manages extension data.
- Set up CDR sync — Configure n8n to forward CDRs:
- Create an n8n workflow that triggers on PBX CDR events.
- Point it to the
pbx-cdrorpbx-cdr-syncEdge Function webhook. - CDRs are parsed and stored in the
call_logstable.
- Test click-to-call:
- Open a contact record.
- Click the phone icon next to the contact's number.
- Nexus calls
call-initiate, which triggers the PBX to bridge the call between the agent's extension and the customer's number.
- Verify call logs — After a test call, check Calls in the sidebar. The CDR should appear within seconds.
Expected result
- Agents can initiate calls from contact records via click-to-call.
- Incoming and outgoing calls are logged in the Calls module with duration, status, and recording links.
- Call analytics are available in the Analytics dashboard.
Common issues
| Issue | Resolution |
|---|---|
| Click-to-call fails | Verify PBX API URL and credentials. Check that the agent's extension is mapped correctly. |
| CDRs not syncing | Check n8n workflow execution logs. Verify the webhook URL points to the correct Edge Function. |
| Call recordings missing | Ensure the PBX is configured to record calls and the recording storage is accessible. |