Cisco Collaboration Setup
Prerequisites
| Tool or evidence |
Purpose |
Verify |
| Bash and Python 3 |
Run the offline renderer and validator |
bash --version && python3 --version |
| Reviewed intake spec |
Keep product routes, indexes, and privacy choices explicit |
Start from template.example |
| Local evidence files |
Qualify CDR/CMR, CIM, and partner-package claims; optional AXL/Expressway notes never qualify readiness |
Use relative, single-link regular files with SHA-256 values |
When to Activate
- Route CUCM remote-audit-logging syslog separately from CDR and CMR flat-file collection.
- Plan Expressway syslog and optional CDR or
local2 media-statistics readiness.
- Plan CMS syslog while keeping its HTTP(S) XML CDR receiver as an explicit gap.
- Plan Meeting Management system and audit syslog.
- Produce evidence-only RoomOS, BroadWorks, UCCX, or UCCE gap packets.
Do not use this skill for Webex REST collection itself; hand that work to
cisco-webex-setup. Use cisco-thousandeyes-setup for ThousandEyes data and
cisco-product-setup when the Cisco product is not yet known.
Workflow Overview
┌─────────────────────────────────────────────────────────────────┐
│ 1. REVIEW INTAKE │
│ Confirm product routes, privacy choices, and local evidence │
└─────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ 2. RENDER OFFLINE │
│ Build classifier, readiness, evidence, gap, and handoff assets │
└─────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ 3. VALIDATE │
│ Re-read trusted evidence and verify the private packet │
└─────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ 4. HAND OFF │
│ Operators review unresolved gaps before any child workflow │
└─────────────────────────────────────────────────────────────────┘
Safety Contract
- Rendering is the only mode and is the default. There is no apply, install,
execute, device-login, API, or credential mode.
- Never generate a child apply command or a Cisco device mutation. Delegated
commands are stored as argv arrays and use render/help modes only.
- Reject unknown fields, secret-bearing keys, path traversal, symlinks,
hard-linked evidence, unowned output directories, and executable artifacts.
- For CMS and Meeting Management, emit a deterministic classifier only for
compatible plain-TCP handoffs. Their sender profiles may select documented
TLS, but that selection keeps a blocking SC4S listener/certificate gap and
suppresses plaintext vendor-port argv. Classifiers must use an exact host,
exact IP, or unique dedicated port; regex and overlapping selectors are
invalid.
- Keep the documented syslog destinations fixed:
cisco:ucm to ucm,
cisco:tvcs to main, cisco:ms to netops, and Meeting Management
cisco:mm:system:* plus cisco:mm:audit to netops.
- Treat call analytics as product-specific normalized data. Do not claim a
Telephony or VoIP CIM model. Render Authentication or Change mappings only
when the spec supplies a constrained qualifying search, the conservative
field set, and hashed local evidence. Keep the operator query outside the
rendered bundle; persist only its SHA-256, structural review result, fixed
route/field allowlist, and a non-identifying
head 0 skeleton.
- Dashboard SPL must project
fields _time collaboration_route, explicitly
run fields - _raw as the final pre-aggregation step, and then aggregate.
_time survives for timechart; no raw or hashed identifiers are retained
or displayed.
- The private packet necessarily retains reviewed operational routing
identifiers: project/environment/owner, restricted role, exact host/IP
selectors, indexes/source types, and its marker-bound output path. The
no-event-identifier boundary applies to evidence values and dashboard/CIM
output, not those routing coordinates. Source spec names are never persisted.
Every intake string and the resolved output/derived child path are screened
for email, private-key, bearer, and a finite set of AWS, GitHub, Slack, JWT,
OpenAI, and Google API credential shapes before any write. UUID-like HEC or
client-secret strings remain allowed because their shape is indistinguishable
from legitimate operational identifiers; this is not universal secret
detection.
- Treat Splunkbase apps 669, 4434, 4640, 8413, 8592, and 8593 as optional
Sideview partner packages, never Splunk-owned official TAs. Do not emit
install commands; require exact version, tier, entitlement, and package
metadata evidence before recording a selection.
Commands: Render and Validate
Render the example spec offline:
bash skills/cisco-collaboration-setup/scripts/setup.sh \
--spec skills/cisco-collaboration-setup/template.example
Preview without writing:
bash skills/cisco-collaboration-setup/scripts/setup.sh \
--spec skills/cisco-collaboration-setup/template.example \
--dry-run --json
Validate the rendered packet without contacting Splunk, SC4S, or Cisco:
bash skills/cisco-collaboration-setup/scripts/validate.sh
Bare validation proves current structure, private ownership/modes, fixed
registries, and consistency with the renderer-created unkeyed marker
commitments. It does not authenticate historical provenance. If the packet
contains CDR/CMR local qualification, CIM evidence, partner evidence, or CMM
operator-attested evidence, validation fails closed until an externally trusted
spec is supplied and its bound evidence is re-read:
bash skills/cisco-collaboration-setup/scripts/validate.sh \
--spec /private/operator-owned/collaboration-spec.yaml \
--expected-spec-sha256 <externally-recorded-sha256>
The optional digest is an external trust anchor. Because the bundle and its
unkeyed SHA-256 marker are owner-rewritable, a coherent same-owner rewrite is
outside bare validate.sh authenticity guarantees. Trusted-spec mode strictly
re-parses the spec, verifies its digest, re-reads bound evidence, and compares
every rendered projection deterministically.
With no arguments, setup.sh renders template.example to the repository's
cisco-collaboration-rendered/ child directory. Review readiness/,
privacy/, sc4s/, evidence/, gaps/, and handoffs/ before any operator
uses a child workflow.
The renderer refuses an existing bundle by default. After reviewing it, use
--replace-existing to publish a fully validated private sibling stage and
preserve the prior output under a sibling backup name. The backup marker stays
bound to the original target path, so the backup is intentionally not a valid
bundle while it has the backup name. It is a
recoverable replacement under a private target lock, not a claim of gap-free
atomic replacement. It never clears an owned tree in place or deletes that
backup.
For reviewed recovery, stop concurrent renderers, verify that the exact target
is absent and its sibling lock is absent, verify the recorded backup is a
current-user-owned 0700 real directory, rename that exact backup to the
original target path, and run validate.sh --output-dir <original-target>.
If the restored packet carries historical/local evidence, also pass the trusted
original --spec and optional externally recorded --expected-spec-sha256.
Bare validation is expected to fail for that qualified restore. Never edit the
marker or validate the backup under its temporary sibling name. Replacement
preflight checks only ownership, structure, and marker commitments; it never
reports provenance success for the old packet.
Product Boundaries
| Product path |
Rendered result |
Boundary |
| CUCM remote-audit-logging syslog |
cisco:ucm parser readiness plus blocking SC4S listener handoff |
UDP/TCP/TLS evidence applies only to remote audit logging; every operator-selected port remains unresolved and does not prove transport support for all %UC_/%CCM_ service syslog |
| CUCM CDR |
SFTP billing-server or on-demand SOAP/SFTP evidence packet |
No AXL substitution; complete sample evidence required |
| CUCM CMR |
Independent flat-file evidence packet |
Never infer readiness from CDR evidence |
| CUCM AXL |
Configuration-enrichment readiness only |
SOAP/XML HTTPS POST to /axl/; not realtime CDR collection |
| Expressway |
cisco:tvcs syslog plus optional INFO CDR and local2 media checks |
Device mode is UDP/514 legacy-BSD or IETF, or TLS/6514 IETF with trust review; SC4S listener capability is separate |
| CMS |
TCP or tls: sender profile for cisco:ms |
TLS listener/certificate readiness and XML CDR receiver implementation remain gaps |
| Meeting Management |
Independent TCP or TLS 1.2 system/audit profiles |
Exact classifier cannot overlap CMS; TLS listener/certificate readiness remains a gap |
| RoomOS |
unsupported_roadmap evidence packet |
Separate Webex and ThousandEyes handoffs only |
| BroadWorks |
unsupported_roadmap evidence packet |
Vendor-document handoff; no local collector claim |
| UCCX/UCCE |
UNKNOWN evidence packet |
No implementation claim |
Evidence and Package Gates
When CDR or CMR is enabled, the spec must name its exact file type, two header
rows, a local sample file, exact SHA-256, nonzero record count, header fields,
export path, receiver owner, collection evidence, and the origin of the chosen
custom source type. The renderer reads only that local file and never copies
its contents into output.
Optional Sideview selections use partner_packages.mode: evidence_only. The
renderer fails when a release, tier, dependency, license/entitlement record,
or Splunk platform claim is unsupported. App 8413 remains non-selectable until
receiver and tier placement are verified; app 4640 remains blocked on Splunk
10.5 because its verified public compatibility stops at 10.4.
Source Discipline
Read reference.md for the collection matrix and
references/source-ledger.json for the
claim-level ledger. SC4S parser evidence is pinned to commit
f878a6e8031b07ae8777e97738b27afe735f118d; human documentation pages are
separately marked mutable and checked on 2026-07-19.
Completion Contract
This router can validate only the offline packet. Product routes remain
partial until operators complete child collection and prove index,
sourcetype, event-flow, privacy, and dashboard results. Any optional TA or app
must also satisfy the shared completion gate.
The permanent CMS XML receiver gap and roadmap/UNKNOWN packets must not be
reported as completed onboarding.
Troubleshooting
| Failure |
Meaning |
Resolution |
| Unknown or secret field |
The strict schema rejected an unsafe assumption |
Remove it; use only documented non-secret fields |
| CDR/CMR evidence incomplete |
Flat-file readiness is not proven |
Add a local sample, hash, fields, owner, export path, and collection evidence |
| Classifier overlap |
CMS and CMM could be misclassified |
Use unique exact sources or dedicated ports above 1023 |
| Output refused |
The path is a symlink, unowned, or tampered |
Choose an empty dedicated directory or review the existing packet |
| Partner package refused |
Version, tier, dependency, entitlement, or platform support is unproven |
Keep it disabled and record the residual evidence gap |
1---2name: cisco-collaboration-setup3description: >-4 Use when planning or reviewing Splunk onboarding for Cisco Unified Communications Manager syslog,5 CDR, or CMR; Cisco Expressway syslog, CDR, or media evidence; Cisco Meeting Server syslog or XML6 CDR; or Cisco Meeting Management system and audit syslog. Render a privacy-safe, evidence-gated7 collaboration plan with deterministic SC4S classification and explicit RoomOS, BroadWorks, Webex,8 and ThousandEyes handoffs without applying changes.9compatibility: "Splunk Cloud Platform 10.5.2605: delegated. Compatibility is determined by the canonical replacement or selected child skill; this compatibility alias or router does not own a runtime or package."10metadata:11 source: https://skillmd.com/skills/chambear2809/cisco-collaboration-setup12 splunk_cloud_10_5: "delegated"13 compatibility_verified: "2026-08-20"14---1516# Cisco Collaboration Setup1718## Prerequisites1920| Tool or evidence | Purpose | Verify |21|---|---|---|22| Bash and Python 3 | Run the offline renderer and validator | `bash --version && python3 --version` |23| Reviewed intake spec | Keep product routes, indexes, and privacy choices explicit | Start from `template.example` |24| Local evidence files | Qualify CDR/CMR, CIM, and partner-package claims; optional AXL/Expressway notes never qualify readiness | Use relative, single-link regular files with SHA-256 values |2526## When to Activate2728- Route CUCM remote-audit-logging syslog separately from CDR and CMR flat-file collection.29- Plan Expressway syslog and optional CDR or `local2` media-statistics readiness.30- Plan CMS syslog while keeping its HTTP(S) XML CDR receiver as an explicit gap.31- Plan Meeting Management system and audit syslog.32- Produce evidence-only RoomOS, BroadWorks, UCCX, or UCCE gap packets.3334Do not use this skill for Webex REST collection itself; hand that work to35`cisco-webex-setup`. Use `cisco-thousandeyes-setup` for ThousandEyes data and36`cisco-product-setup` when the Cisco product is not yet known.3738## Workflow Overview3940```text41┌─────────────────────────────────────────────────────────────────┐42│ 1. REVIEW INTAKE │43│ Confirm product routes, privacy choices, and local evidence │44└─────────────────────────────────────────────────────────────────┘45 │46 ▼47┌─────────────────────────────────────────────────────────────────┐48│ 2. RENDER OFFLINE │49│ Build classifier, readiness, evidence, gap, and handoff assets │50└─────────────────────────────────────────────────────────────────┘51 │52 ▼53┌─────────────────────────────────────────────────────────────────┐54│ 3. VALIDATE │55│ Re-read trusted evidence and verify the private packet │56└─────────────────────────────────────────────────────────────────┘57 │58 ▼59┌─────────────────────────────────────────────────────────────────┐60│ 4. HAND OFF │61│ Operators review unresolved gaps before any child workflow │62└─────────────────────────────────────────────────────────────────┘63```6465## Safety Contract6667- Rendering is the only mode and is the default. There is no apply, install,68 execute, device-login, API, or credential mode.69- Never generate a child apply command or a Cisco device mutation. Delegated70 commands are stored as argv arrays and use render/help modes only.71- Reject unknown fields, secret-bearing keys, path traversal, symlinks,72 hard-linked evidence, unowned output directories, and executable artifacts.73- For CMS and Meeting Management, emit a deterministic classifier only for74 compatible plain-TCP handoffs. Their sender profiles may select documented75 TLS, but that selection keeps a blocking SC4S listener/certificate gap and76 suppresses plaintext vendor-port argv. Classifiers must use an exact host,77 exact IP, or unique dedicated port; regex and overlapping selectors are78 invalid.79- Keep the documented syslog destinations fixed: `cisco:ucm` to `ucm`,80 `cisco:tvcs` to `main`, `cisco:ms` to `netops`, and Meeting Management81 `cisco:mm:system:*` plus `cisco:mm:audit` to `netops`.82- Treat call analytics as product-specific normalized data. Do not claim a83 Telephony or VoIP CIM model. Render Authentication or Change mappings only84 when the spec supplies a constrained qualifying search, the conservative85 field set, and hashed local evidence. Keep the operator query outside the86 rendered bundle; persist only its SHA-256, structural review result, fixed87 route/field allowlist, and a non-identifying `head 0` skeleton.88- Dashboard SPL must project `fields _time collaboration_route`, explicitly89 run `fields - _raw` as the final pre-aggregation step, and then aggregate.90 `_time` survives for `timechart`; no raw or hashed identifiers are retained91 or displayed.92- The private packet necessarily retains reviewed operational routing93 identifiers: project/environment/owner, restricted role, exact host/IP94 selectors, indexes/source types, and its marker-bound output path. The95 no-event-identifier boundary applies to evidence values and dashboard/CIM96 output, not those routing coordinates. Source spec names are never persisted.97 Every intake string and the resolved output/derived child path are screened98 for email, private-key, bearer, and a finite set of AWS, GitHub, Slack, JWT,99 OpenAI, and Google API credential shapes before any write. UUID-like HEC or100 client-secret strings remain allowed because their shape is indistinguishable101 from legitimate operational identifiers; this is not universal secret102 detection.103- Treat Splunkbase apps 669, 4434, 4640, 8413, 8592, and 8593 as optional104 Sideview partner packages, never Splunk-owned official TAs. Do not emit105 install commands; require exact version, tier, entitlement, and package106 metadata evidence before recording a selection.107108## Commands: Render and Validate109110Render the example spec offline:111112```bash113bash skills/cisco-collaboration-setup/scripts/setup.sh \114 --spec skills/cisco-collaboration-setup/template.example115```116117Preview without writing:118119```bash120bash skills/cisco-collaboration-setup/scripts/setup.sh \121 --spec skills/cisco-collaboration-setup/template.example \122 --dry-run --json123```124125Validate the rendered packet without contacting Splunk, SC4S, or Cisco:126127```bash128bash skills/cisco-collaboration-setup/scripts/validate.sh129```130131Bare validation proves current structure, private ownership/modes, fixed132registries, and consistency with the renderer-created unkeyed marker133commitments. It does not authenticate historical provenance. If the packet134contains CDR/CMR local qualification, CIM evidence, partner evidence, or CMM135operator-attested evidence, validation fails closed until an externally trusted136spec is supplied and its bound evidence is re-read:137138```bash139bash skills/cisco-collaboration-setup/scripts/validate.sh \140 --spec /private/operator-owned/collaboration-spec.yaml \141 --expected-spec-sha256 <externally-recorded-sha256>142```143144The optional digest is an external trust anchor. Because the bundle and its145unkeyed SHA-256 marker are owner-rewritable, a coherent same-owner rewrite is146outside bare `validate.sh` authenticity guarantees. Trusted-spec mode strictly147re-parses the spec, verifies its digest, re-reads bound evidence, and compares148every rendered projection deterministically.149150With no arguments, `setup.sh` renders `template.example` to the repository's151`cisco-collaboration-rendered/` child directory. Review `readiness/`,152`privacy/`, `sc4s/`, `evidence/`, `gaps/`, and `handoffs/` before any operator153uses a child workflow.154155The renderer refuses an existing bundle by default. After reviewing it, use156`--replace-existing` to publish a fully validated private sibling stage and157preserve the prior output under a sibling backup name. The backup marker stays158bound to the original target path, so the backup is intentionally not a valid159bundle while it has the backup name. It is a160recoverable replacement under a private target lock, not a claim of gap-free161atomic replacement. It never clears an owned tree in place or deletes that162backup.163164For reviewed recovery, stop concurrent renderers, verify that the exact target165is absent and its sibling lock is absent, verify the recorded backup is a166current-user-owned `0700` real directory, rename that exact backup to the167original target path, and run `validate.sh --output-dir <original-target>`.168If the restored packet carries historical/local evidence, also pass the trusted169original `--spec` and optional externally recorded `--expected-spec-sha256`.170Bare validation is expected to fail for that qualified restore. Never edit the171marker or validate the backup under its temporary sibling name. Replacement172preflight checks only ownership, structure, and marker commitments; it never173reports provenance success for the old packet.174175## Product Boundaries176177| Product path | Rendered result | Boundary |178|---|---|---|179| CUCM remote-audit-logging syslog | `cisco:ucm` parser readiness plus blocking SC4S listener handoff | UDP/TCP/TLS evidence applies only to remote audit logging; every operator-selected port remains unresolved and does not prove transport support for all `%UC_`/`%CCM_` service syslog |180| CUCM CDR | SFTP billing-server or on-demand SOAP/SFTP evidence packet | No AXL substitution; complete sample evidence required |181| CUCM CMR | Independent flat-file evidence packet | Never infer readiness from CDR evidence |182| CUCM AXL | Configuration-enrichment readiness only | SOAP/XML HTTPS POST to `/axl/`; not realtime CDR collection |183| Expressway | `cisco:tvcs` syslog plus optional INFO CDR and `local2` media checks | Device mode is UDP/514 legacy-BSD or IETF, or TLS/6514 IETF with trust review; SC4S listener capability is separate |184| CMS | TCP or `tls:` sender profile for `cisco:ms` | TLS listener/certificate readiness and XML CDR receiver implementation remain gaps |185| Meeting Management | Independent TCP or TLS 1.2 system/audit profiles | Exact classifier cannot overlap CMS; TLS listener/certificate readiness remains a gap |186| RoomOS | `unsupported_roadmap` evidence packet | Separate Webex and ThousandEyes handoffs only |187| BroadWorks | `unsupported_roadmap` evidence packet | Vendor-document handoff; no local collector claim |188| UCCX/UCCE | `UNKNOWN` evidence packet | No implementation claim |189190## Evidence and Package Gates191192When CDR or CMR is enabled, the spec must name its exact file type, two header193rows, a local sample file, exact SHA-256, nonzero record count, header fields,194export path, receiver owner, collection evidence, and the origin of the chosen195custom source type. The renderer reads only that local file and never copies196its contents into output.197198Optional Sideview selections use `partner_packages.mode: evidence_only`. The199renderer fails when a release, tier, dependency, license/entitlement record,200or Splunk platform claim is unsupported. App 8413 remains non-selectable until201receiver and tier placement are verified; app 4640 remains blocked on Splunk20210.5 because its verified public compatibility stops at 10.4.203204## Source Discipline205206Read [reference.md](reference.md) for the collection matrix and207[`references/source-ledger.json`](references/source-ledger.json) for the208claim-level ledger. SC4S parser evidence is pinned to commit209`f878a6e8031b07ae8777e97738b27afe735f118d`; human documentation pages are210separately marked mutable and checked on `2026-07-19`.211212## Completion Contract213214This router can validate only the offline packet. Product routes remain215`partial` until operators complete child collection and prove index,216sourcetype, event-flow, privacy, and dashboard results. Any optional TA or app217must also satisfy the [shared completion gate](../shared/ta_completion_gate.md).218The permanent CMS XML receiver gap and roadmap/UNKNOWN packets must not be219reported as completed onboarding.220221## Troubleshooting222223| Failure | Meaning | Resolution |224|---|---|---|225| Unknown or secret field | The strict schema rejected an unsafe assumption | Remove it; use only documented non-secret fields |226| CDR/CMR evidence incomplete | Flat-file readiness is not proven | Add a local sample, hash, fields, owner, export path, and collection evidence |227| Classifier overlap | CMS and CMM could be misclassified | Use unique exact sources or dedicated ports above 1023 |228| Output refused | The path is a symlink, unowned, or tampered | Choose an empty dedicated directory or review the existing packet |229| Partner package refused | Version, tier, dependency, entitlement, or platform support is unproven | Keep it disabled and record the residual evidence gap |