Health, Disconnect, and Troubleshooting
Monitor provider health, verify call events, troubleshoot common failures, and disconnect Telnyx or Zadarma safely.
Use the provider card and the shared call history together. A successful credential test proves that LeenOps can reach the carrier account; a successful test call plus final call event proves the complete production path.
Provider Card Signals
A connected provider card can show:
- connection and verification status;
- whether it is the default voice provider;
- the connection-specific signed webhook URL;
- the last verification time;
- recent provider events and calls;
- failed event or call counts;
- the last provider error.
After changing a credential, connection ID, public key, PBX source, or carrier webhook, select Test connection and place a controlled test call.
End-to-End Health Check
- Confirm the intended provider is Connected and Default.
- Run Test connection.
- Confirm the carrier uses the exact connection-specific HTTPS webhook URL.
- Start a call to an approved destination.
- Confirm the correct device rings or browser audio connects.
- End the call normally.
- Open Communications > Calls and verify direction, final status, duration, provider, and linked CRM record.
- If applicable, verify recording, transcript, or SMS delivery events.
Common Problems
| Problem | Check first |
|---|---|
| Provider will not connect | Credential belongs to the intended account; required connection/source values are present; carrier account is active |
| Call action is unavailable | A live default provider exists; caller has the required role; Telnyx caller has an assigned active number |
| Destination is rejected | International format, carrier balance, country authorization, outbound profile, and trial restrictions |
| Telnyx browser has no audio | Browser microphone permission, selected input/output device, corporate browser policy, and tab state |
| Zadarma source never rings | Callback source, PBX routing, source device reachability, balance, and predictive-callback setting |
| Call stays queued or ringing | Provider event webhook, signature key/secret, public HTTPS reachability, and carrier event delivery |
| Call history is missing | Correct connection-specific webhook URL and supported events; then inspect provider-card errors |
| Recording or transcript is missing | Provider capability and configuration, completed-call state, event status, and the member's view permission |
| Duplicate event appears | Capture the provider event ID and time; Telnyx queues and deduplicates signed events, while Zadarma updates are processed immediately |
Provider-Specific Event Handling
Telnyx
LeenOps verifies the Ed25519 signature and timestamp, stores the event before acknowledging it, deduplicates repeated events, and recovers queued failures. The same connection URL can receive supported voice and SMS events.
If failures continue, confirm webhook API version 2, the public key, and the
exact Credential Connection or Messaging Profile using the URL.
Zadarma
LeenOps verifies the Signature header and deduplicates matching payloads, but
processes call updates immediately rather than through a durable retry queue.
The provider card therefore has no equivalent queued-failure recovery view.
If history stops updating, confirm Zadarma's single PBX call-notification URL
still points to LeenOps and that the supported NOTIFY_* events are enabled.
Disconnect Telnyx
Before disconnecting, identify active users, numbers, SMS senders, and ongoing calls. Disconnecting:
- removes the encrypted Workspace credential;
- revokes Telnyx browser credentials created by LeenOps;
- disables the linked Telnyx SMS connection;
- keeps historical calls, messages, number records, and audit history.
Carrier-owned numbers remain in the Telnyx account unless you separately release them.
Disconnect Zadarma
Disconnecting clears the encrypted Workspace credentials and local connection status, but does not remove or restore Zadarma's PBX call-notification URL.
- Disconnect the provider in LeenOps.
- Open Zadarma Settings > Integrations and API.
- Remove the LeenOps URL or replace it with the next approved integration URL.
- Test the next integration's event delivery.
Zadarma has one PBX call-notification URL. Leaving the LeenOps URL in place after disconnect, or replacing another CRM's URL without a cutover plan, can break call-history delivery.
Evidence to Include in a Support Request
Include the Workspace name, provider, approximate time with timezone, destination country, call direction, provider connection status, and the local call ID if one exists. Never include an API key, secret, access token, recording, full webhook body, or customer-sensitive transcript in an ordinary ticket.