Statistics: profit, hangup causes & loss‑making calls

Statistics in the sidebar is a hub of reports, like CDR management. This page covers three of them: the period Profit summary, Hangup causes (with a table of what the common codes mean), and Loss Making Calls. The grouped/aggregate report lives on its own page: Usage report & aggregate templates.

The Statistics hub — every report is one tile, filtered by role.

Which tiles appear depends on the logged‑in role: reports that show money (self‑cost, profit) need permission to see finances; two system‑wide tiles (System statistics, Server load) are admin/accountant only.

Profit

A period summary: pick a date range and press Show. The top row of tiles is available to everyone — total/answered/no‑answer/busy/error call counts and their percentages, total and average duration, active users. A second row, visible to admin, accountant and reseller (not partner), adds Revenue, Self‑cost, Profit, Margin, and profit per call / per minute / per day / per user.

Profit: call counts on top, money underneath.

A PDF export link next to the date form produces the same report as a downloadable PDF for the chosen range.

Hangup causes explained

The Hangup causes report groups every call in a date range by its cause code, with the count, share of total, and total duration for each. Voiplix records standard telecom Q.850 codes (0–127) plus a set of its own codes (200 and up) for reasons that are specific to this billing/routing system rather than to the phone network — a low balance or a blocked account, for instance.

Hangup causes for a date range — Code, Designation, Disposition, Calls, Share, Duration.

This same code appears as Hangup Cause on the Calls list, as Hangupcause on a call's detail page, and as Q.850 on each row of a call's dial‑attempt trace.

The most common codes

CodeNameWhat it usually means
16Normal call clearingEither side hung up normally after the call — the expected code for a completed, answered call.
17User busyThe called party was on another call.
18No user respondingThe far end never answered the signalling at all — often a misconfigured or offline device.
19No answer from user (user alerted)It rang, but nobody picked up in time.
21Call rejected by ProviderThe provider actively refused the call — worth checking with the carrier.
34No circuit/channel availableNo free path to the destination at that moment — usually temporary.
38Network out of orderThe network is down or badly degraded, likely for a while.
1Unallocated (unassigned) numberThe number itself isn't valid or in service.
201User is blockedVoiplix‑specific: the calling user's account is blocked.
204No suitable providers foundVoiplix‑specific: nothing in the routing (LCR) could carry this call — an empty or misconfigured route.
211Low balance for userVoiplix‑specific: a prepaid user doesn't have enough balance to place the call.
225CallerID is bannedVoiplix‑specific: the caller ID used is on a blacklist.
231Provider unreachableVoiplix‑specific: the carrier could not be reached — check its IP/port settings.
Tip

Codes at 200 and above are never a phone‑network problem — they always mean something inside this system's own configuration (balance, blocking, routing, rates) stopped the call before it ever reached a carrier.

Loss Making Calls

Lists individual calls where the self‑cost (what the provider charged) was higher than the revenue (what the customer was charged) — in other words, calls that lost money. Same date‑range form as Profit; needs finance access to open at all.

Loss Making Calls — each row's Loss column in red.

Only the newest 10,000 matching calls are listed if a period has more than that — the report says so and the totals still cover everything, not just the shown rows.

Check

A spike in one hangup‑cause code across many calls at once is the fastest way to spot a systemic problem (a provider outage shows up as a jump in 38 or 231; a routing mistake as a jump in 204) — much faster than reading the Calls list row by row.