OURCONNECT / OPERATIONS

Dashboard

Live operational health across OC-Core and every monitored node

—
CURRENT WORKSPACEOverviewMonitor, investigate and act
YOUR OPERATIONS TODAY

What do you need to get done?

Choose a task to work through. Your existing system data and advanced tools are one click away.

Operational attention

Live evidence from OC-Core
Loading current issues…

Your work in progress

Saved in OC-Core · available across sessions

Action Centre

Priorities and work in progress

Loading work…
OPERATOR WORKSPACE · REAL-TIME OPERATIONS

Good to have you on shift.

Everything that needs a decision, investigation, or follow-up. Data is supplied by your existing OC-Core services.

01 / PRIORITY QUEUE

Needs your attention

Evidence-based actions, sorted by urgency.

Loading operational priorities…
02 / CALL OPERATIONS

Recent call activity

Current calls, with an immediate path to investigation.

03 / TRAFFIC

Call activity trend

Inbound and outbound traffic over the last 14 days.

QUICK START

What are you doing?

Jump into a complete operating workflow.

PLATFORM

Infrastructure watch

INCIDENTS

Open issues

OPERATIONAL INTELLIGENCE

Shift briefing

Context from measured platform evidence.

Preparing the briefing…
OPERATOR WORK MANAGEMENT

Workflows

Resume an existing task or create a new workflow. Progress and notes are stored centrally.

Customer onboarding

GUIDED WORKFLOW

Operator task

Issued invoices, customer collections and balances. Figures include GST.
Loading financial summary…

Issued revenue over time

Monthly invoice totals for the selected period

Customer revenue

Issued, collected and outstanding amounts by customer

Only issued invoices are included in revenue figures.

Incident history, correlation and notification evidence
Technical incident evidence and notification diagnostics

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

Endpoint notifications

Recent individual endpoint state changes · informational only

DOES NOT AFFECT HEALTH
Node software, update policy and version history
Software and Update StatusCHECKING

Node software

Installed versions and approved update targets

Version history

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

Backup and Restore

Backup readiness, available copies and safe recovery tests

OC-Core currently supports PostgreSQL and selected recovery configuration backed up to Google Drive. It does not yet provide an automated production full-system restore.

Available backups

Google Drive uploads performed by OC-Core

Restore verification

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.
What is included in a backup?
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

Live calls

Current correlated call activity

Call History

Completed and failed calls

System Health

OC-Core and Asterisk nodes. Expand any system for its checks and components.

OC-Core

Awaiting host metrics
Unknown

Docker containers and application checksAwaiting evidence

Asterisk nodes

SIP trunks

Carrier connection and registration state

SIP endpoints

Registration, reachability and live extension presence

OC Phone devices

Manage customer phones, setup invitations and device status.

Select a customer to open their workspace.
Inventory and assignment checksExpand to investigate unassigned numbers, endpoints and other exceptionsCHECKING
Assignment inboxReview discovered endpoints and numbers using observed evidence and suggested ownership
Assignment audit historyWho changed ownership, classification or review state and when

Payments and Collections

Record payments, check settlement and review customer balances.

Payment history

One-time payments and their Stripe reconciliation status

Collections requiring attention View exceptions and receivables

Collections command centre

Resolve collection exceptions, follow up outstanding customer balances and confirm settlement before acting again.

Loading payment and billing evidence…

Payment exceptions

Customer collections

Broadband services

Customer connections, usage and allowance alerts

Billing checks and cycle exceptions are managed under Administration.

What should I do next?

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

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

Bulk import / export, assignments and rate simulator

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 and carrier costs are both entered ex GST (carrier invoices show GST-inclusive amounts; OC-Core divides by 1.10 to compare).

Assignments

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

Rate simulator

Preview a rating without storing or billing it.

Revenue assurance overview

Billing exceptions, carrier reconciliation and customer profitability. Financial figures are estimates until invoices are issued.

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.

Current priorities

Measured findings from current operational evidence. No repeated dashboard totals.

OC assessment

Evidence-grounded interpretation, clearly distinguished from measured facts.

Ask OC

Ask about current calls, customer impact or issues requiring attention.

READ ONLY
Ask a question to receive a read-only assessment with supporting evidence.

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.

Audit and History

Historical events across OC-Core, with their original source and outcome.

Loading records…

The workspace combines recorded audit actions with historical operational and financial records. Invoice and payment rows are business snapshots, not proof of who changed them. Specialist audit streams now include billing, payments, customer directory, customer portal and inventory assignments; some other customer and settings changes still require action-level audit coverage. Each source has its own retention and limit; this is not a guaranteed complete system-wide ledger. Raw operational logs remain in Diagnostics and Logs.

Billing production mode

Shadow is safe. Pilot allows issue/collection only for selected customers. Live enables production billing for all customers.

SHADOW

Monthly invoice preparation

Automatically prepare invoices for the previous calendar month. New invoices stay awaiting approval. No automatic issue, email or collection.

Recommended: first day of month at 06:00. Operator approval always required.

Invoice business details
Security evidence, ban history and detection rule configuration

Rule-engine monitoring

Attack-source evidence

Detection rules

Administrative tuning; does not belong in live operations

Scoped rule overrides

Diagnostics

Technical evidence and checks for administrators. Day-to-day invoice approval stays under Finance.

Billing acceptance testing

Technical preflight checks for billing and Stripe / BECS, kept separate from day-to-day Finance. No charges or invoices are created by this assessment.

Checking billing configuration…

A pass checks database and configuration evidence only. Live payment settlement and invoice email delivery remain unverified until controlled end-to-end testing.

Billing diagnostics

Review validation findings and billing-cycle evidence when investigating an issue. Preparing or issuing invoices remains a separate, controlled operator action.

Billing Validation

Review customer pricing, usage, carrier costs and billing-cycle exceptions before invoices are approved.

Validation checks do not issue invoices or collect payment. Resolve blocking findings before continuing billing.

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.

Billing health, technical checks and audit

Billing Health and 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

Aussie Broadband

API credentials, data collection and connection diagnostics

NOT CONFIGURED
Collection diagnostics and historyView recent collection results
Xero accounting integration
Connect XeroAccounting CSV

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

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 and Deployment

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

Deployment


Database


Redis


Web and 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 and 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.

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.

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

Notification history

Recent send attempts and provider results

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.

OC Intelligence

Scheduled whole-environment analysis and optional AI interpretation


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.

Google Drive backup settings

Connection, automatic schedule, retention and recovery-critical configuration

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.

Saving settings does not run or restore backups. Use Administration → Backup and Restore to run a backup or rehearse recovery.

Security Operations

Active threats, protection coverage and decisions requiring attention.

Current security findings

Open detections with the affected source, customer or node. Select a finding to investigate its incident.

Node protection

Firewall, Fail2Ban and SIP protection status by monitored node.

Currently blocked IP addresses

Triage queue

—
Loading…
Select an incident to focus on one issue.

Operational alerts

Current conditions requiring attention and their recovery lifecycle