Break down Beeline Cloud PBX call stats right in chat

The agent calls the Beeline Cloud PBX at cloudcc.beeline.ru: first it reads the list of PBX extensions, then call history from the CDR export, call recordings, forwarding rules, blacklists and voice files. From that it counts how many calls were answered and how many were missed, and breaks the result down by extension — across the users the connected API account opens up.

Call history is not handed over as an instant response but as an export: the agent orders a CDR for the period you need and works with the finished file, so the report is built from completed calls rather than from a live counter. Call recordings are separate files as well — the agent finds the one you need by number and date, downloads it from the PBX and retells what was agreed with the client.

On the write side the agent does exactly what the PBX allows: start a two-way call from a named extension, turn on permanent call recording for a user, change forwarding on busy or to a mobile, add a nuisance number to the blacklist. By default it works read-only and builds reports, and before changing a setting it names the extension and the rule and waits for confirmation.

Access boundaries are set by the API account: the agent sees the extensions and the calls of the PBX it belongs to and never looks into other numbers. Long periods are taken apart in pieces — it orders the export chunk by chunk and stitches the result together itself — and it holds the request rate so the PBX limits are not hit. Recordings are downloaded one at a time and only for a specific question, and when there is no data for the period it says so in words instead of showing an empty table.