OUR CONNECT · ADMIN CONSOLE

Dashboard

Live operational health across OC-Core and every monitored node

—

Call volume · last 14 days

Inbound and outbound call activity from canonical call evidence.

Open alerts

Correlated operational problems

Server status

Core and monitored servers at a glance

Live calls

Current Asterisk activity

Revenue breakdown

Revenue, carrier cost and gross margin for the selected period.

Daily call volume

Inbound and outbound calls by day.

Busiest hours (AEST)

Call activity by local hour.

Core Services

Operational status of the independent OC-Core services.

End-to-end monitoring intelligence

Proof from OC-Node collection through Asterisk, OC-Core processing and alert delivery.

Evidence-first: missing evidence is never reported as healthy. CDR, CEL and RTCP remain activity-aware so a quiet PBX is shown as idle, not broken.

OC-Core processor liveness

Monitor, security, revenue assurance, notifications, push, scheduler and backup workers.

Correlated root causes

Groups downstream symptoms under the most likely observed infrastructure failure so one outage does not become dozens of unrelated alerts.

Per-source evidence

Google Drive backup

The only backup destination supported by OC-Core.

G
Google DriveNot connected
Google OAuth setup: create a Web Application OAuth client in Google Cloud, enable the Google Drive API, and add this exact authorised redirect URI:

Includes the node agent secret and settings-encryption key so a database restore remains usable. Database/Redis passwords and Google OAuth credentials are never included.

Backup contents

Restore-ready data package

DATABASEPostgreSQL custom dumpCalls, CDR/CEL, customers, monitoring, security, settings and history
MANIFESTIntegrity metadataVersion, timestamp, database type and dump SHA-256 checksum
RECOVERYCore recovery configurationOptional recovery-critical OC-Core secrets; no database or Google credentials
Backups are created in temporary storage, uploaded to Google Drive using resumable upload, then removed from the OC-Core server. There is no configurable local backup destination.

Restoration rehearsal

Prove that a real Google Drive backup can be restored before an incident occurs.

Download recovery runbook
Non-destructive: OC-Core downloads and verifies the latest successful backup, restores it into an isolated temporary PostgreSQL database, checks required tables and representative row counts, then removes only that temporary database. Production remains online and is never overwritten.

Backup history

Google Drive uploads performed by OC-Core

Live calls

Current correlated call activity

Call history

Completed and failed calls

OC-Nodes

Monitored Asterisk servers and software compliance

Node fleet

Installed versions, release adoption and overdue updates

CHECKING
Version history

SIP endpoints

Registration, reachability and live extension presence

SIP trunks

Carrier, registration and detection state

OC Phone devices

Create client phone enrolments and generate a fresh one-time QR setup code whenever required.

Customer setup codes are single-use and remain valid for the selected onboarding period. Generating a replacement immediately revokes the previous unused code without changing SIP credentials.

OC Phone audit history

Creation, QR enrolment, revocation and client self-removal events.

Customers

Customers, services and telephony ownership in one place.

Inventory health

Ownership completeness, stale assignments, conflicts and attribution gaps.

CHECKING
Select a customer to open their workspace.
Assignment inboxReview discovered endpoints and numbers using observed evidence and suggested ownership
Assignment audit historyWho changed ownership, classification or review state and when

Take a payment

One-time AUD card or Australian bank debit processed securely by Stripe

NOT CONFIGURED
Card details are entered into Stripe-hosted fields.
Card and bank-account details are entered into Stripe-hosted fields and never pass through or remain in OC-Core. Direct Debit requires the account holder to accept Stripe’s Direct Debit Request.

Payment guidance

Before processing a card or bank debit

1Confirm the payerVerify the customer and the amount they have authorised.
2Record the referenceUse the invoice number from the external billing system.
3Use Stripe’s secure fieldsNever copy card or bank details into notes, email, chat or another field.
4Wait for confirmationBECS debits remain Processing until Stripe confirms settlement, normally around two business days.

Payment history

One-time payments and their Stripe reconciliation status

Aussie Broadband collection

Collect daily NBN usage securely from the Carbon API.

NOT CONFIGURED

Add NBN service

Link an ABB service ID to its OC-Core customer.

Customer data services

Download, upload and total usage for the last 31 days.

Collection history

Auditable results for every customer service and collection attempt.

Controlled billing: Approved drafts can be finalised into real invoices. Issued invoices can be collected by Stripe card or Australian BECS Direct Debit when configured, with manual payment recording retained for bank transfer and other methods. Invoice emails and PDF delivery are supported; accounting sync remains operator-controlled.

What should I do next?

OC-Core will guide you to the next item requiring attention.

Billing areas

Most work starts under Needs attention. Use the other areas only when required.

Draft readiness

Checks customer services, calls and carrier costs before preparing totals.

Previous checks

Prepare draft billing

Select the billing period, review the resulting customer totals and resolve any exceptions.

Prepared drafts

Customer totals, review status and exceptions.

Customer totals

Expected charges, carrier costs and estimated margin.

Billing health & production gate

Final pre-flight checks before a billing run. Integrity failures are blockers; optional integrations are shown separately.

TESTINGCHECKINGExport billing audit
Failed operations / retry queue

Invoices

Review, issue and email PDF invoices, collect payments, create credits, void or replace records.

Receivables

Outstanding customer balances by age. Open a customer statement PDF for the underlying invoice, payment and credit history.

Accounting integration · Xero
Connect XeroAccounting CSV

Xero remains a secondary accounting ledger. OC-Core keeps the immutable source invoice, payment and credit-note evidence.

Invoice business details
Recurring services, adjustments and credits

Recurring service

Effective-dated monthly service charge, entered ex GST.

Adjustment or credit

Positive amounts adjust upward; negative amounts create a credit. Enter ex GST.

Carrier cost checks

Calls recorded by OTW compared with the calls and expected costs recorded by OC-Core.

OTW connection and import settings

Automatic OTW CDR collection

Securely downloads completed daily carrier records for costing and drift comparison.

NOT CONFIGURED
Manual fallback import
Completed days only; current-day files are rejected.

Calls needing review

Only differences and calls that could not be cleanly checked need your attention.

Carrier totals and audit evidence

Carrier invoice totals

Imported GST-inclusive totals compared with expected costs.

Import history

Customer and carrier pricing

The easiest method is to open Needs attention and click an unrated call. OC-Core will identify the missing plan or rate and prefill it.

Advanced pricing controls

Rate books

Effective-dated customer pricing and carrier cost decks.

Create rate book

Rates remain inactive until assigned.

Bulk rate import

Upload a CSV to add or replace an entire customer or carrier rate deck in one operation.

Download template
Columns: prefix, destination, direction, connection_cents, per_minute_cents, billing_increment_seconds, minimum_seconds, minimum_charge_cents, effective_from, effective_to, priority.

Add effective rate

Longest matching destination prefix wins. Customer prices are ex GST; carrier costs are GST-inclusive.

Assignments

Connect effective price books to customers and carrier decks to trunks.

Rate simulator

Preview a rating without storing or billing it.

Revenue assurance command centre

Billing-period profitability, leakage signals, carrier drift and receivables in one place.

Customer profitability

Uses immutable shadow-billing snapshots so revenue, carrier cost and margin stay tied to the billed evidence.

Leakage indicators

Items that can prevent revenue capture or hide carrier cost.

Revenue trend

Monthly billed revenue, carrier cost and margin.

Assurance workflow

Acknowledge, disposition or resolve findings without losing the evidence trail.

Custom reporting

Build operational, billing and assurance reports, preview them immediately, save useful definitions and export CSV.

Saved reports

Reusable report definitions for month-end, customer reviews and investigations.

Needs attention

Click an item and OC-Core will explain the issue and guide you through the smallest fix.

All call records

Open any call to inspect or complete its billing setup.

Production readiness

Generation, evidence and delivery checks for the daily operational report

Sentinel Daily

Evidence-grounded whole-environment operational intelligence

Sentinel status

Schedule, evidence controls and AI narrative

Report history

AI provenance, operator review and delivery history

Logs

Search and investigate Asterisk and system events without loading the entire log history.

—

OC-Core Updates

Check, stage and install signed-release packages without SSH deployment.

Release channel

Optional online update discovery. Automatic installation remains disabled.

Install release package

Upload an OC-Core .tar.gz release and its published SHA-256 checksum.

Update activity

A pre-update PostgreSQL dump and application rollback copy are created before installation.

OC-Node releases

Publish node packages separately for authenticated one-click installation from each Node UI.

CONFIGURATION

Settings

System configuration grouped by what you are working on.

Stripe payments

Credentials and signed webhook used by the manual payment module.

NOT CONFIGURED
STRIPE WEBHOOK ENDPOINT—Subscribe to payment_intent.succeeded, payment_intent.payment_failed, payment_intent.processing, payment_intent.canceled, charge.dispute.created and charge.dispute.closed.

System & Deployment

Database, Redis, deployment role and web addresses. These settings replace normal .env configuration.

Deployment

Database

Redis

Web & TLS

Changing to a different database does not migrate call, log, security or historical data. OC-Core will initialise its schema and preserve administrator accounts on the target database.

Administrators & Node Enrollment

Database-backed administrators and the generated agent enrollment secret.

Administrators

Node agent secret

Used by oc-node to authenticate telemetry ingestion. It is generated automatically and is not stored in .env.

Production security posture

Authentication, session and recovery safeguards required for production operation.

REVIEW

Multi-factor authentication

Protect your administrator account with any standards-compatible authenticator app.

Active sessions

Review browsers currently signed in to this administrator account.

Administrator audit trail

Authentication and state-changing management requests.

OC Phone connectivity

SIP credentials used when an iPhone wakes for an incoming call.

Apple VoIP Push

PushKit wakes OC Phone before Asterisk offers the SIP call.

NOT CONFIGURED

Registered phones

Token state, APNs environment and the most recent push result.

Push delivery history

APNs acceptance and the latest acknowledgement received from OC Phone.

Outage correlation

Promote material multi-endpoint failures to alerts without treating one offline phone as an incident.

IMPACT AWARE
Default behaviour: one offline endpoint is informational; all endpoints in a group of two or more is an alert; otherwise at least three and 50% must be unavailable. Recoveries wait 90 seconds to avoid flapping.

Notification settings

Email, Mobile Message SMS and escalation policy

Email / SMTP

SMS · Mobile Message

OC Phone alert delivery

Only explicitly authorised phones receive operational alerts. Customer phones remain off by default.

SEPARATE FROM CALL PUSH

Alert policy

Control delivery and escalation by severity

Alert routing

Route, override or mute notifications by severity, incident kind, node or customer.

Routing changes notification delivery only. Incidents and evidence remain visible in OC-Core.

Phone alert history

Standard APNs acceptance and provider errors for operational alerts.

Notification history

Recent send attempts and provider results

Sentinel

Daily whole-environment report and optional AI narrative

Must be reachable from the OC-Core Docker host. Sentinel Detect and Sentinel Report will both use this Ollama server.

Models are loaded from the OpenAI project associated with the stored API key.

Only bounded, redacted evidence is sent to AI. Every narrative statement must cite stored evidence. Deterministic analysis is used automatically if AI is unavailable or exceeds its limits.

Node protection

Continuous evidence from OC-Node for firewall, Fail2Ban and Asterisk SIP TLS controls.

AU GEO-BLOCK RETAINED
Layered protection: Australian GeoIP filtering remains the outer boundary. Fail2Ban blocks malicious Australian sources and OC-Core retains the evidence.

Blocked IP addresses

Current bans and recently released addresses retained by OC-Core, including firewall enforcement evidence where available.

0 ACTIVE · 0 RECENT

Ban history

Ban and unban transitions retained centrally after the node removes them.

Security monitoring

Rule engine and alert pipeline health

Observed attack sources

Source addresses correlated from stored security evidence.

Open findings

Deterministic security detections requiring attention

Detection rules

Deterministic thresholds, evidence sources and evaluation windows

Scoped tuning

Override or disable a rule for one node or customer without weakening every tenant

Incident correlation

Root-cause groups combine dependent symptoms into one operator view.

CORRELATED

7-day soak metrics

Noise, repeat incidents, suppressions and notification delivery evidence.

SOAK

Operational alerts

Current conditions requiring attention and their recovery lifecycle

Endpoint notifications

Recent individual endpoint state changes · informational only

DOES NOT AFFECT HEALTH