collabcowboy.net
Visual call-flow tracing across CUCM and Unity, read-only
🔍 Pathfindera Collab Cowboy tool
Type a DN. See exactly where the call goes. Every hop, one picture.
Answering “where does this call actually end up?” means clicking through twenty-plus CUCM and Unity admin pages, taking notes, and still not being sure. Pathfinder traces the whole call path for you. Enter a DN or extension and it recursively maps every hop (partitions, CSSs, translation and route patterns, route lists, hunt pilots and lists, gateways and trunks, voicemail pilots, and Unity call handlers) as an interactive node graph. It’s completely read-only.
Pathfinder walks the dial plan across both CUCM and Unity from a single starting number, follows forwards and route logic recursively, and draws the result as a graph. Export any trace to a self-contained HTML diagram with credentials stripped, to share or attach to a ticket.
Call-flow trace · DN 4785● read-only
DN 4785→Translation
9.XXXX→Route Pattern
HQ-PT→Hunt Pilot
4500
→Phone · 4021Phone · 4022Phone · 4023RNA → Unity voicemail
One DN, traced across CUCM and Unity · 11 hops · export to a self-contained diagram
The Trace
Every hop, followed automatically
From one DN, Pathfinder follows the call the way the switch does (through partitions and CSSs, translation and route patterns, hunt logic, gateways, and into Unity) and lays the whole path out as a node graph you can read at a glance.
- CUCM side: partitions, CSS, translation/route patterns, route lists
- Call routing: CTI route points, hunt pilots and lists, gateways, trunks
- Unity side: voicemail pilots, call handlers, transfer rules, menus
- Recursive: follows forwards and chained routing to the end
Share & Audit
A picture you can hand off
Export a trace to a single self-contained HTML diagram. No live cluster access is needed to view it, and credentials are stripped out. It’s the fast way to document a dial plan or attach evidence to a routing ticket.
- Self-contained export: one HTML file, opens anywhere
- Credentials stripped: safe to share outside the team
- Audit-ready: document the dial plan as it actually is
- Zero changes: Pathfinder only reads, never writes
Why teams reach for it
The safe first look that answers the routing question.
One DN, one picture. The trace replaces twenty-plus admin-page clicks with a single graph of where the call goes.
Both sides in one view. CUCM routing and Unity handling are traced together, so you don’t lose the thread at the voicemail boundary.
It follows the chain. Recursive tracing walks forwards and route logic to the actual endpoint instead of stopping at the first hop.
Read-only by design. It makes zero changes, which makes it a safe first thing to run on a production cluster you don’t fully know yet.
Documentation for free. Export a trace and you’ve got a dial-plan diagram to hand a teammate or attach to a ticket.
Cleanup starts here. Seeing the real partition and CSS path is how you find the dead pattern or the wrong forward to fix.
For sprawling, inherited dial plans
Most CUCM dial plans grew by accretion, and nobody has the whole map in their head. Pathfinder gives you that map on demand, without changing a thing. So troubleshooting a misrouted call or auditing a partition takes a trace, not an afternoon.
Setup & Fit
Works with
On-prem Cisco CUCM and Unity Connection you’ve connected.
Turn it on
Nothing. Enter a DN and trace. It only reads.
Sized for
Any dial plan, but it earns most on large, complex, multi-site routing.