Cisco BroadWorks control plane
Cisco BroadWorks operations, without the XML work.
Dialplane turns Cisco BroadWorks OCI-P into clean REST and MCP workflows, with tenant-safe auth, scoped tokens, normalized JSON, and audit trails for every change.
Connect Claude, ChatGPT, Copilot, Gemini, Codex, and other MCP clients. See AI client setup or read about Cisco BroadWorks automation.
Cisco BroadWorks
OCI-P commands, sessions, service state
Dialplane
schema validation, normalized JSON, before / after audit
MCP
agent tools
REST
app APIs
SurgeMail
voicemail
What it does
One safer path into your telecom stack.
Use REST when your application needs a BroadWorks API.
Call Cisco BroadWorks provisioning, audit, backup, sync, and CDR workflows with JSON and get normalized JSON back. Dialplane handles the OCI-P rendering, response parsing, and release-specific command choices.
Use MCP when an agent needs safe telecom tools.
Expose controlled Cisco BroadWorks operations to AI tools without giving them raw sockets, XML construction, or unscoped credentials.
Use workflows when change needs evidence.
Provision, batch, replicate, backup, restore, and sync operations record scope, outcome, before state, after state, and redacted sensitive fields.
Tenant access control
Give every client exactly the BroadWorks reach it needs.
Tenant admins can issue API tokens with explicit operation scopes and optional service-provider or group bounds. Login-type policies add another ceiling for BroadWorks user, group, service-provider, reseller, provisioning, and system sessions.
Scoped tokens
Default to full access for fast setup, then narrow tokens by verb/resource scopes such as read:user, provision:dn, or backup:*.
Tenant bounds
Constrain a token to specific service providers or groups when an integration should only touch one part of the tenant.
Login-tier policy
Set per-login-type ceilings and inspect recent scope denies when a policy blocks a request.
SurgeMail integration
Voicemail mailboxes that follow BroadWorks.
When Voice Messaging User is assigned, Dialplane can create the matching SurgeMail mailbox, set the mailbox password, and write it back to BroadWorks. When the service is removed, the mailbox is deleted and the action is audited.
- tenant-admin config page
- save and test connection flow
- callback-driven mailbox updates
- backup and sync workflows
- password redaction in audit records
- delete on service unassign
- 01Voice Messaging User is assigned
- 02Dialplane reads BroadWorks state
- 03SurgeMail mailbox is created or updated
- 04Mailbox password is written back to BroadWorks
- 05Callbacks keep the mailbox current
- 06Unassigning the service deletes the mailbox
CDR Analytics
Upload BroadWorks CDRs and ask useful questions immediately.
Dialplane turns exported call detail records into tenant-scoped analytics for missed calls, trunk demand, user activity, group activity, and call duration trends. Customers keep a simple upload key on the CDR host and use a separate read-only analytics key for reporting.
Example records loaded
100
Four batches of demo-safe CDRs
Sample window
Apr 1-14
Ready for product demos
Answered calls
95
With missed-call and duration totals
Unique users
18
Enough spread for useful prompts
- 01Enable the CDR Analytics add-on for the tenant
- 02Generate an upload-only CDR ingest key
- 03Install the Dialplane CDR forwarder on the export host
- 04Point BroadWorks CDR files at the forwarder
- 05Verify the first upload and row count
- 06Query call history through MCP or the API
- Summarize call volume, answered calls, missed calls, and average duration for April 1-14.
- Which users had the most missed calls in the sample CDR window?
- Show trunk utilization by hour and call out any busy periods.
- Find groups with no CDR activity in the last 30 days and explain what to verify next.
Tokens and permissions
Upload access is not analytics access.
CDRs use two different credentials so a collector can upload files without becoming a reporting, admin, or billing client.
Upload key
bwb_cdr_...
Used only by the forwarder to upload CDR files. It cannot read analytics or call admin APIs.
Analytics key
read:cdr
A normal API or MCP key limited to CDR reporting. It cannot upload CDR files.
Add-on gate
CDR Analytics
Key creation, upload, and analytics access require the tenant add-on to be enabled.
Workflow vocabulary
Six verbs. Clear intent.
The same verbs show up in MCP tools, REST workflows, recipes, and audit records. That keeps human operators and AI agents speaking the same language.
Provision
Create or configure one user, group, service, or mailbox with an audit record.
Batch
Run controlled changes across many rows with per-item status and cleanup rules.
Replicate
Copy known-good configuration to a new target without hand-building XML.
Backup
Capture current state before change, or keep a clean reference snapshot.
Restore
Re-apply a prior state when you need recovery instead of guesswork.
Sync
Find and repair drift between BroadWorks and connected systems.
Security and audit
Built for systems people who need evidence.
Dialplane records state-changing operations with tenant scope, before and after data, source, outcome, and redacted secrets. That includes connected systems like SurgeMail.
Normalized responses
Clean JSON
CamelCase data from BroadWorks OCI responses. Clients do not parse XML.
Two interfaces
REST + MCP
Traditional integrations and AI tools use the same tenant-safe control plane.
Operational evidence
Before / after
State-changing workflows record source, outcome, and redacted snapshots.
CDR analytics
Fast summaries
Upload call records once, then ask for missed calls, trunk demand, and usage trends.
Next step
Bring your BroadWorks tenant online.
Start with Base for BroadWorks control-plane access. Add Backup + Restore, SurgeMail, or CDR Analytics when those workflows are ready.